Related
This Thread Is For Them Who Bricked There Phones
Don't start a new thread for your bricked phone & post here.
We will help you with every possible solutions.
Here are some quick tips :
(Here I'll use the terms like Download-Mode & Recovery-Mode, If you dont know what are they please click here. There "BOOT to RECOVERY" & "BOOT to BOOTLOADER" means how to enter into Recovery-Mode & Download-Mode respectively.)
A Bricked Phone May Have One or More (Below Problems) :
1. Booting to the ROM(Android) not possible.
2. Booting to the Recovery-Mode not possible.
3. Black screen or Bootloop(Repeated Restarting of Phone at Boot Animation or Samsung Galaxy Y Logo).
Possible Solutions :
(Remember there'll be data loss using these solutions so always try to keep a backup)
1. If you can still enter into Recovery-Mode
(a). Try to clear Data & Cache then check.
(b). Try Installing a Custom ROM using CWM(ClockWorkMod Recovery) & check.
(For Custom ROM & CWM Visit here.)
2. If Recovery-Mode didn't helped Enter into Download-Mode & flash an odin supported stock rom(using ODIN 1.84 or 1.85) from Doky73's Thread(Flashing Guide in 2nd post).
*You can inform me, if anything left out.
Note :
1. I'll be not held responsible for anything that happens to your phone.
2. Before posting try to search for similar type problems out there & try the solution, if that doesn't solve your problem then post here.
Make this a sticky.. there are many users who say that their phone is bricked
help! bricked SGY
galaxy y bricked
i bricked my sgy last 3 weeks.
here's what i did.
-installed creedsix rom.
-installed UOT kitchen Themes.
-wipe data
problem
-stuck in bootlogo
-softbricked.
-cant go to recovery mode
-flashed too many times, still stuck in bootloop
i flashed at least 20 times, with different firmwares.
but still no luck, still boot lop.
my professor said something about secondary bootloader that might help. but i had definitely no idea what it is.
i asked some techies on the mall, and they said that this phone must undergo the JTAG process. but it cost $20.
help me. thanks.
jmpotter said:
galaxy y bricked
i bricked my sgy last 3 weeks.
here's what i did.
-installed creedsix rom.
-installed UOT kitchen Themes.
-wipe data
problem
-stuck in bootlogo
-softbricked.
-cant go to recovery mode
-flashed too many times, still stuck in bootloop
i flashed at least 20 times, with different firmwares.
but still no luck, still boot lop.
my professor said something about secondary bootloader that might help. but i had definitely no idea what it is.
i asked some techies on the mall, and they said that this phone must undergo the JTAG process. but it cost $20.
help me. thanks.
Click to expand...
Click to collapse
can you go to download mode??
(try pressing volume down+ home button + power button all at the same time)
if it still can, then your SGY is still good
go to this ---> thread
and just flash your country's firmware
From where you got the firmwares.... How you flashed...
Ever tried re partitioning.... Ever flashed boot loader....
For info... Jtag or boundary-scan is used for testing & servicing high technology electronic boards...
Sent from my GT-S5360 using Tapatalk 2
Millan.SIS said:
From where you got the firmwares.... How you flashed...
Ever tried re partitioning.... Ever flashed boot loader....
For info... Jtag or boundary-scan is used for testing & servicing high technology electronic boards...
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
just for info, jtag will not fix the problem. IT IS SCANNING.. like trouble shooting.
that only means that those technicians are pretending to be well educated but the truth is that they only wanted to get some cash out of your pocket.
static28 said:
just for info, jtag will not fix the problem. IT IS SCANNING.. like trouble shooting.
that only means that those technicians are pretending to be well educated but the truth is that they only wanted to get some cash out of your pocket.
Click to expand...
Click to collapse
ya, that's what those wannabees really do..
Sent from my GT-S5360 using Tapatalk 2
this one will a little bit off topic...what is creedsix?is it a rom for SGY?
if the phone still can boot that means everything is fine. pull out the battery, wait 10 seconds, reinsert the battery, do three magic combo button, you'll enter recovery mode. don't worry about our bootloader. our bootloader is stored in different partition thus installing any custom rom won't affect our bootloader. as far as i know, there is only one person who have messed up with bootloader and got an ultimate hard brick.
kurotsugi said:
this one will a little bit off topic...what is creedsix?is it a rom for SGY?
if the phone still can boot that means everything is fine. pull out the battery, wait 10 seconds, reinsert the battery, do three magic combo button, you'll enter recovery mode. don't worry about our bootloader. our bootloader is stored in different partition thus installing any custom rom won't affect our bootloader. as far as i know, there is only one person who have messed up with bootloader and got an ultimate hard brick.
Click to expand...
Click to collapse
Really its great thread ........ Many many thanks for helping ppl ......
is it possible repair hard brick ..... what is hard brick... if device hard brick device gos life time dead ??
Sent from my GT-S6102 using xda premium
a hard brick is when our device doesn't respond to power button.
the guy that I've mentioned above is doky73. he accidentally flash a bootloader for sgs2 into his sgy. last time he said that he send his sgy to samsung service center and buy a new one. I'm not sure if samsung has revived his sgy.
edit: I didn't to offend him but I think I've mispelled doky's username. edited.
manoranjan2050 said:
Really its great thread ........ Many many thanks for helping ppl ......
is it possible repair hard brick ..... what is hard brick... if device hard brick device gos life time dead ??
Sent from my GT-S6102 using xda premium
Click to expand...
Click to collapse
whatever It may be... You should never mess up with bootloaders, if you don't actually know what's there significance...
Brief description on android starting process :
pbl(primary boot loader "boot.bin") executes first and then it executes sbl ...
Sbl(secondary boot loader "sbl.bin") is responsible for responding to combos...download mode.. Intercepting odin commands..... booting system...booting kernel.... Charging your battery while switch off... Etc etc
Harm anyone of them... And Your phone goes into lifetime hibernation, Hard-bricked.
Sent from my GT-S5360 using Tapatalk 2
thanks for the big info friend...... so hard bricl is mot repairble ......
Sent from my GT-S6102 using xda premium
my device might be bricked, can you please help me out
Hi to all, it's only my second post but i have a major problem with my samsung s-5360. it's won't boot anymore, but it can enter cmw and recovery. This is what i did wrong i believe. At first i installed morocs 1.8 kernel on creed fusion version 3.1 and it wouldn't boot anymore, so i ended up using a back-up i made before with cmw. And it worked well and phone was booting again and was on stock again. ( because back-up was made with stock-version obviously )
Then i thought: well let's try repensis noob version. And installed it and there was also an update 2 and installed it over it as well before booting the os, maybe this is what i did wrong dunno .. But afterwards it didn't boot anymore and whatever i tried, restoring one of the 3 images i made, or using one of the roms posted here like Creed fusion 3.1 rom or Aurora 2 nor Chobits didn't work.
I also tried reverting to stock with odin 1.85 but when i connected my phone via usb to the pc, odin didn't see my phone. ( after selecting the 3 tar files in odin ) Maybe i'm doing wrong something there.
What i also have to add is that when doing factory wipe in recovery it says formatted E: but unable to format E:\dev10 and dev11. clearing cache is no problem and also cleared dalvik cache. Can you please help me out ? I know, it sounds very noobish but well, i have to face it because can't do it myself without help anymore it seems ... Thanx a lot in advance.
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
kurotsugi said:
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
Click to expand...
Click to collapse
Thanx a lot for responding ! I only used kies for connecting my phone because i couldn't find a driver for it, and had to disconnect it, but i will search for it again now and hopefully it will work now. i have to go now and return back in three hours. i'm very curious ! i'll come back in a couple of hours and gonna tell if it worked out of course
kurotsugi said:
a hard brick is when our device doesn't respond to power button.
the guy that I've mentioned above is doky77. he accidentally flash a bootloader for sgs2 into his sgy. last time he said that he send his sgy to samsung service center and buy a new one. I'm not sure if samsung has revived his sgy.
Click to expand...
Click to collapse
to be precise: the guy was Doky73...
I was playing with different revisions of SBLs because on SGS2 some old SBL gives the possibility to reset custom bin counter via JIG. At a given point accidentally browsed SGS2 bootloader instead of SGY one...
But I did perfect job, the service center wasn't able to detect the cause of bricking, but they recovered my phone under warranty. (I think they're not reading this forum )
Doky73 said:
to be precise: the guy was Doky73...
I was playing with different revisions of SBLs because on SGS2 some old SBL gives the possibility to reset custom bin counter via JIG. At a given point accidentally browsed SGS2 bootloader instead of SGY one...
But I did perfect job, the service center wasn't able to detect the cause of bricking, but they recovered my phone under warranty. (I think they're not reading this forum )
Click to expand...
Click to collapse
Thanks friend.............
if i install some custom rom custom kernel via odin or CWN its gos to hard brick ???
in odin re-partition option for why ............ its disbl by default if i enable it wats problem........
dear friend if u have any odin full tutorial /guide /ref please provide me for learn syep by step one by one option or problem......
ops...my mistake. I guess I'm too sleepy when was typing your name. I'll edit it. sorry.
manoranjan2050 said:
Thanks friend.............
if i install some custom rom custom kernel via odin or CWN its gos to hard brick ???
in odin re-partition option for why ............ its disbl by default if i enable it wats problem........
dear friend if u have any odin full tutorial /guide /ref please provide me for learn syep by step one by one option or problem......
Click to expand...
Click to collapse
if u flash something through odin or cwm then you wouldnt hard brick ur phone.. it would be just a temporary brick which can be easily revived... i dont know abt that partioning thing
Sent from my GT-S5360 using XDA
kurotsugi said:
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
Click to expand...
Click to collapse
Hi, there i am and sry for disturbing you again or someone else but i managed to install a non kies usb driver and i'm flashing thru odin 1.85 right now but i'm stuck at BcmCP.img for over an hour . Is it because i forgot to remove the sd card ? I only removed the sim and is it safe to stop the process and start over again or should i wait ?
---------- Post added at 02:35 AM ---------- Previous post was at 01:47 AM ----------
mickeyindahouse said:
Hi, there i am and sry for disturbing you again or someone else but i managed to install a non kies usb driver and i'm flashing thru odin 1.85 right now but i'm stuck at BcmCP.img for over an hour . Is it because i forgot to remove the sd card ? I only removed the sim and is it safe to stop the process and start over again or should i wait ?
Click to expand...
Click to collapse
Well after trying this proces for the 5th time i finally managed to go to stock rom and it only lasted a couple of minutes Of course thanx to doky73 who made all this possible ! So i unbricked it for the second time i guess
Can someone pls. help me. I have a rooted Lenovo IdeaTab A3000-H that accidentally got soft bricked after I edited build.prop on /system/build.prop
Info:
Model Number: Lenovo A3000-H
Android Version: 4.2.2
USB Debugging: Disabled
Currently Bootable To: Stock Recovery and Fastboot
(I could boot to ADB but it could only do sideload commands)
I have a recovery.img (CWM) that I can't flash since my PC can't detect my tablet while it's turned off
(And also if possible, can someone give me an original unmodded Lenovo A3000-H build.prop.bak and CWM flashable zip compatible for my tab.)
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Droidriven said:
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Click to expand...
Click to collapse
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
CEDoromal said:
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
Click to expand...
Click to collapse
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
CEDoromal said:
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
Click to expand...
Click to collapse
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
CEDoromal said:
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
Click to expand...
Click to collapse
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
CEDoromal said:
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
Click to expand...
Click to collapse
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You nay have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
CEDoromal said:
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
Click to expand...
Click to collapse
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
CEDoromal said:
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
Click to expand...
Click to collapse
I don't think so but don't quote me, it'll either flash an succeed or fail, I doubt it will make things worse.
Have you looked at the possibility of using an extsdcard and a debrick.IMG or its equivalent to boot from a bootable extsdcard the same as PC does with a bootable USB? If it works on your device like it does some other devices you can boot into system from extsd and then do what you need to do to fix your device then return the sdcard to normal use after you are going again on its own.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
CEDoromal said:
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
Click to expand...
Click to collapse
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
CEDoromal said:
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
Click to expand...
Click to collapse
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA... >
Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA or a repair shop... >
Guys, I'm making this thread for those people who are using Sprint's Note 4 (N910P) outside of US and are stuck with Sprint's ROM (or the ROMs that are based on it) and have certain issues in using the ROM.
For instance, I'm using the unlocked variant of N910P with a GSM carrier, so I was having problem in connecting to the Hot-Spot feature as all of my devices were stuck at "Obtaining IP Address" loop and eventually would never connect.
I did try various "hacks" present here on XDA for enabling Hot-Spot feature like using Galaxy Tools, using SQLite Editor, etc but wasn't able to overcome the problem.
Since, XDA is a great platform for sharing solutions to various problems, I decided to create a thread especially for those who don't want Sprint's bloatware but want to stick with "Stock ROM features" like S Pen.
Hence, here's the step-by-step guide for installing other carrier's ROM on N910P:
Before attempting all this,make sure to be on OK1 Bootloader & Baseband (Do not try this on Marshmallow Bootloaders) for N910P.
Step 1:
Install TWRP recovery version 3.0.1 (Yes, you read it right..it's 3.0.1 & not 3.0.2)
Once you have downloaded, flash it through ODIN (the TAR file) or through existing TWRP (using ISO image).
Step 2:
Make a backup of your current ROM so that you can revert to it in case of unsuccessful flash.
Step 3:
Go to Wipe (in TWRP)-----> Factory reset (do this 3 times.....yes, 3 times!)
Then, go to Advanced Wipe & wipe Dalvik/ART cache,Cache,Data,Internal Storage, System (Do not wipe external SD Card).
Hit the back button to come out of the "wipe window"
Step 4:
Click on "Install" and choose the files in following order:
a) Dr Ketan's ROM
b) Data Fix for the ROM
c) Kernel
d) SuperSU (I used beta 2.71)
Once the flashing process is finished, reboot the system and wait for the phone to boot.
It will take a long time (around 10-15 minutes) to boot.
Once you are on setup wizard screen, choose to apply "Dr Ketan's fix" and then you can proceed like you do in any other ROM.
Downloads:
TWRP: https://dl.twrp.me/trltecan/
(Choose TAR or ISO as per your choice and flash accordingly)
ROM:
http://www.drketanrom.com/n910g.html
(All credit goes to Dr Ketan for his hard work & awesome ROM)
(Its for G variant)
Data FIX:
https://drive.google.com/folderview?id=0B1I0vyV3onrjemR2YlY2V0s0ME0&usp=sharing
(Credit goes to @dr.ketan, & @Lanc-City for providing all the required info)
Kernel:
http://d-h.st/rb3d
(The credit for this Kernel goes to @Hani K.)
Super SU:
http://forum.xda-developers.com/showthread.php?t=1538053
(Credit goes to @Chainfire)
Note: I am in no way to be credited for all this as the links provided above are a result of hard work from the respective developers. I have just compiled all the links into one thread so that it can help anyone like me to switch to other ROM.
Also, neither I nor any of the above mentioned developers/members are responsible for any fault that may arise due to improper flash or other reasons..
Do all of it at your own risk!
Last but not the least, I would like to thank @ricohz for helping me out when I was stuck in some steps..
(In the screen-shot attached, the model number is 920T for obvious reasons...so don't ask why it's not 910P..)
Do note that the APNs have to be edited manually, else the data connectivity would not be there!
(This thread should benefit the non-Sprint users........)
Update:
There are some more ROMs that can be flashed successfully on N910P such as:
1. Maximum Overdrive
http://forum.xda-developers.com/note-4-tmobile/development/s7-portn910t-n910w8-t3375956
2. Nameless ROM
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-nameless-mm-lightfastdeodexed-t3363547
Kindly say Thanks to the developers on their respective threads for all their hard work.
Thanks for sharing im gonna give it a shot
But why did you say to be on ok1 if you have marshmallow version in the screen shot
Sent from my Not4 Mod using Tapatalk
NICE
SPRINT USERS IF YOU FLASH THIS TEXT WON'T GO OUT
MMS ARE FINE TEXT COME IN BUT WON'T GO OUT
this works for him because he's using a gsm sim card
Google Drive link is broken
Sent from my SM-N910P using Tapatalk
Data fix and Kernel fix link broken...
Anybody get text going I'd be happy too pay bounty
Jedi Aaris said:
Thanks for sharing im gonna give it a shot
But why did you say to be on ok1 if you have marshmallow version in the screen shot
Sent from my Not4 Mod using Tapatalk
Click to expand...
Click to collapse
OK1 bootloader has been suggested so as to avoid any incompatibility issues for the ROM!
Shiva758 said:
Data fix and Kernel fix link broken...
Click to expand...
Click to collapse
Links have been updated!
ricohz said:
NICE
SPRINT USERS IF YOU GLASH THIS TEXT WONT GO OUT MMS ARE FINE TEXT COME IN BUT DON'T GO OUT
thus works for him because he's using a gsm sim card
Click to expand...
Click to collapse
@ricohz: Yes,buddy...
For GSM carriers, this method works flawlessly..
Kudos to you for helping me out!
bddpolo said:
Anybody get text going I'd be happy too pay bounty
Click to expand...
Click to collapse
Some one said bounty?
Lol jk
I got boot loops what I do now right now I am on ok1 !!!!what mistake i did? Is that ROM marshmallw? May be I downloaded that one ? Which kernel we have to use ? When I go to download section it shows me three kernel variants ?
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
Do we have to download n910pb6 mm firmware ?
I just messed my 4 hours on this ROM but every time I qm getting bootloops...I am on lollipop ok1 firmware and bootloader .I tried everything bit nothing works ..or may be its not complete clear what I download ?
Shiva758 said:
I just messed my 4 hours on this ROM but every time I qm getting bootloops...I am on lollipop ok1 firmware and bootloader .I tried everything bit nothing works ..or may be its not complete clear what I download ?
Click to expand...
Click to collapse
Tinkering and flashing custom ROMs on Android is not always a piece of cake...
Loads of patience is required and if the process is not carried out as stated/expected, time is bound to get wasted.
Anyway, here's what you need to do (Or at-least, expected to do..):
1. Take a backup of the current ROM.
2. Do Factory reset 3 times ( First time, do it again & do it yet again..making it three times)
3. Wipe everything(except External SD Card) again 3 times as above.
4. Flash the ROM.
5.Once ROM is flashed, do not reboot & flash the Data Fix.
6.Again, do not reboot and flash the Vitamin Kernel (originally meant for F variant).
7. Do not reboot yet again & flash the SuperSU (I FLASHED 2.71).
Now, reboot and wait for the setup screen to appear. It will take quite a long time to appear and the phgone will be stuck on Samsung logo for quite a while.
Now, if you have patience, wait for the process to finish, and if not, you know what to do..
Shiva758 said:
I got boot loops what I do now right now I am on ok1 !!!!what mistake i did? Is that ROM marshmallw? May be I downloaded that one ? Which kernel we have to use ? When I go to download section it shows me three kernel variants ?
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
Do we have to download n910pb6 mm firmware ?
Click to expand...
Click to collapse
The direct link for the ROM is:
http://d-h.st/m9bj
The direct link for the kernel is:
https://www.androidfilehost.com/?w=files&flid=54698
Hope, this much of help will make things clear for you.
Finally it worked . Actually i am doing ( kernel) mistake .Thanks for providing direct links and for your kind help.
robinhood1808 said:
Guys, I'm making this thread for those people who are using Sprint's Note 4 (N910P) outside of US and are stuck with Sprint's ROM (or the ROMs that are based on it) and have certain issues in using the ROM.
For instance, I'm using the unlocked variant of N910P with a GSM carrier, so I was having problem in connecting to the Hot-Spot feature as all of my devices were stuck at "Obtaining IP Address" loop and eventually would never connect.
I did try various "hacks" present here on XDA for enabling Hot-Spot feature like using Galaxy Tools, using SQLite Editor, etc but wasn't able to overcome the problem.
Since, XDA is a great platform for sharing solutions to various problems, I decided to create a thread especially for those who don't want Sprint's bloatware but want to stick with "Stock ROM features" like S Pen.
Hence, here's the step-by-step guide for installing other carrier's ROM on N910P:
Before attempting all this,make sure to be on OK1 Bootloader & Baseband for N910P.
Step 1:
Install TWRP recovery version 3.0.1 (Yes, you read it right..it's 3.0.1 & not 3.0.2)
The reason for choosing 3.0.1 is that the ROM successfully booted using this version instead of 3.0.2 (Don't ask me the reason for it..)
Once you have downloaded, flash it through ODIN (the TAR file) or through existing TWRP (using ISO image).
Step 2:
Make a backup of your current ROM so that you can revert to it in case of unsuccessful flash.
Step 3:
Go to Wipe (in TWRP)-----> Factory reset (do this 3 times.....yes, 3 times!)
Then, go to Advanced Wipe & wipe Dalvik/ART cache,Cache,Data,Internal Storage, System (Do not wipe external SD Card).
Hit the back button to come out of the "wipe window"
Step 4:
Click on "Install" and choose the files in following order:
a) Dr Ketan's ROM
b) Data Fix for the ROM
c) Kernel
d) SuperSU (I used beta 2.71)
Once the flashing process is finished, reboot the system and wait for the phone to boot.
It will take a long time (around 10-15 minutes) to boot.
Once you are on setup wizard screen, choose to apply "Dr Ketan's fix" and then you can proceed like you do in any other ROM.
Downloads:
TWRP: https://dl.twrp.me/trltecan/
(Choose TAR or ISO as per your choice and flash accordingly)
ROM:
http://www.drketanrom.com/n910g.html
(All credit goes to Dr Ketan for his hard work & awesome ROM)
(Its for G variant)
Data FIX:
http://forum.xda-developers.com/not...guidehow-to-flash-dr-ketan-rom-6-0-1-t3364025
(Credit goes to @dr.ketan, & @Lanc-City for providing all the required info)
Kernel:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-h-vitamin-t3364213
(The credit for this Kernel goes to @Hani K.)
Super SU:
It can be found here on XDA
(Credit goes to @Chainfire)
Note: I am in no way to be credited for all this as the links provided above are a result of hard work from the respective developers. I have just compiled all the links into one thread so that it can help anyone like me to switch to other ROM.
Also, neither I nor any of the above mentioned developers/members are responsible for any fault that may arise due to improper flash or other reasons..
Do all of it at your own risk!
Last but not the least, I would like to thank @ricohz for helping me out when I was stuck in some steps..
(In the screen-shot attached, the model number is 920T for obvious reasons...so don't ask why it's not 910P..)
Do note that the APNs have to be edited manually, else the data connectivity would not be there!
(This thread should benefit the non-Sprint users........)
Click to expand...
Click to collapse
what about flashing a stock N910F rom is it possible ?
if it is could you PLEASE, provide a flashable zip for N910F rom
Shiva758 said:
Finally it worked . Actually i am doing ( kernel) mistake .Thanks for providing direct links and for your kind help.
Click to expand...
Click to collapse
Glad to know that you finally made it to boot.
Hossam. AbdELHakim said:
what about flashing a stock N910F rom is it possible ?
if it is could you PLEASE, provide a flashable zip for N910F rom
Click to expand...
Click to collapse
I don't think that you can directly flash the stock ROM of "F variant" directly. Doing so might result in a bricked device.
My advise to you will be to carry out the procedure as stated in this thread.
The ROM provided in this thread is 99% stock so you will not face any compatibility issues.
got echoe data fix MO here I come fallow by Dr ketans data fix should apply to all roms with minor tweaks
ricohz said:
NICE
SPRINT USERS IF YOU FLASH THIS TEXT WON'T GO OUT
MMS ARE FINE TEXT COME IN BUT WON'T GO OUT
this works for him because he's using a gsm sim card
Click to expand...
Click to collapse
Will third party apps work for text?
Sent from my SM-N910P using Tapatalk
Hurray! Finally, I fix the touch calibration issue; many many thanks to God who showed me the right path.
After suffering hard in last 15 days, even not getting any help from YU Officials, finally God bestowed upon me his blessings and provided me the hint to fix the issue.
What caused the Issue?
YU Televentures recently released a new batch of Yureka Plus (YU5510A-LP) devices with VoLTE feature. This created a storm in Yureka /Plus section of the forum. Some users even bricked after flashing the new firmware since it was totally different from the previous Yureka firmware. I got the backup of /system and /boot from a YU5510A-LP user. I deodexed the files and made a ROM out of it and flashed on my device to test whether it boots or not (a common process of ROM porting). It didn’t boot but it went beyond the boot logo and since the Kernel of YU5510-A didn’t have the correct display drivers for AO5510, I was getting strange characters on the screen. After that I rebooted to TWRP recovery. I was shocked the touch was malfunctioning. If I touch up it was working down, it was totally a mess.
This issue is much dangerous than bricking the device. Even if we brick, we may recover it by following @ricks guide, but with malfunctioning touchscreen phone is utterly useless. It can’t be fixed even after flashing the EMMC backup.
After that I reported to the YU Officials about the touch calibration issue, they didn’t provide any fix, but created a Warning thread regarding it. So sad.
They were even not ready to provide me the touch firmware of Yureka AO5510. They told me that they are also trying to find the cause of touch calibration issue and don’t have the required files. Here is the quote of the reply from YU Officials:
I am afraid that we don't have any files for fixing the issue. To make sure that such thing does not happen we internally test every case before releasing the software. In your case, you got the software from unknown sources and flashed it on your device with your own consent and understanding. Yes, we have devs but they work on cases which have higher reproducibility rate like the proximity sensor issue.
Click to expand...
Click to collapse
After that I analysed the YU5510A-LP VoLTE firmware and found that it was created by Coolpad, a Chinese Smartphone Company. So YU Televentures has imported not only the smartphone (YU5510A-LP) but also the firmware from Coolpad. That’s why it has some unknown bugs which the YU Offical Devs don’t know because they haven’t made the firmware. That’s why the devs didn’t have fix for touch calibration issue. YU is spending very less on service and devs, which very much disappointing. YU, an Indian brand made Yureka for tech freaks and that’s why so many devs engaged in it and even some noobish users like me became devs to raise the company above cheap Chinese brands. But now it’s status is deteriorating, it broke its partnership with Cyanogen and lost the support of so many great devs; and now it is left with some official noobish devs who are taking time like hell to provide a VoLTE patch for other users, this shows how irresponsible is the YU Company. And now it has already been provided by a YU Forum user. Even the Official YU OS is provided by our friend dev @AudioGod.
I hope my above words reaches to the YU Company and they take this criticizing in the right way and improve itself. I want to see this Indian Company rise beyond heights.
After lot of analysis and research I found that the cause of touch calibration issue was the kernel of YU5510A-LP ROM. It changed the TP-Firmware version and touch parameters of Yureka AO5510 (HD) according to Yureka YU5510A-LP (FHD) device and messed up the calibration.
This TP firmware is different in Yureka and Yureka Plus and it never changes after flashing any firmware (fastboot or ROM).
Yureka AO5510 : Each:GT970:0x1039:0x46
Yureka Plus YU5510 : Ofilm:GT970:0x1039:0x48
And mine was : Each:GT970:0x1039:0x47
Yureka (Plus) Touch Panel is manufactured by Goodix, a Chinese Touch Panel and Fingerprint Sensor company.
What didn’t fix the issue?
These are the things which didn't fix the calibration issue:
[/SIZE]
Flashing stock COS 12.1 ROM through recovery
Flashing COS 12.0/12.1 fastboot firmware
Flashing COS 12.0 CPB using YGDP tool (which threw an error of incompatible device before flashing)
Flashing all other partitons (=EMMC backup)
Using Annabathina’s Yureka Unbricking Tool
How did I find a Fix?
While surfing through internet I found a way to check the touch firmware version. Then I checked mine and also asked about it from other Yureka users. Then I searched about the firmware version and got an XDA Thread and also got to know about Goodix Touch Firmware and Goodix Firmware Upgrade Tool (GTP ADB Tool) from Elephone (another Chinese company) forum which I didn’t get from YU.
I read the XDA thread learned about the whole thing and created a Goodix TP Firmware/Config myself.
How to Fix Yureka AO5510 Touch Calibration Issue?
STEP 1: Download GtpAdbToolV1.7_20140424.zip and GT970_1039_AO5510-TP-Firmware.zip on your Windows PC and extract it. Go to the extracted folder of Gtp Adb Tool and run the GtpAdbTool.exe application. Then connect you YUREKA AO5510 to your PC (be sure USB debugging is enabled in your device). You will see the GTP ADB Tool window similar to the screenshot below:
STEP 2: Now click on the button as indicated in the screenshot below and navigate for the GT970_1039_AO5510-TP-Firmware.cfg file (that you extracted in Step 1) and select it.
STEP 3: Then click on the button indicated in the screenshot below to execute firmware upgrade process. Once completed, you can unplug your device and reboot. Voila touchscreen issue fixed!
NOTE (Important):
If the GTP ADB Tool doesn't detect your device or TP firmware, then flash any of the following ROMs:
Official Lineage OS ROMs
Hexagon ROM by @MoreSushant48
Or any other ROM
OR
Go to TWRP Recovery and mount all the partitions. Then connect your phone to the PC. It should detect.
If any of the above methods doesn’t work then try flashing
CoolUI 6.0 for YUREKA (Test build): https://www.androidfilehost.com/?fid=457095661767103935
(After flashing this ROM you may see a 'root' indication on YU LOGO, but you can fix that using Annabathina's Tool)
Important Files
GTP ADB Tool: https://www.androidfilehost.com/?fid=385035244224387037
YUREKA AO5510 TP Firmware: https://www.androidfilehost.com/?fid=385035244224387256
More information: https://www.osbusters.net/2016/10/fix-yureka-ao5510-touch-calibration-issue.html
Credits
Special thanks to @iamreal2 (XDA member) and @Ethan (Elephone forum member)
Special thanks to @darshan1205, @ricks and @Men_in_black007 who supported me in bad times
Special thanks to @manis99 for providing me YU5510A-LP VoLTE Firmware
Special thanks to @prasoon Mehra for providing me original Yureka AO5510 TP Config.
And finally thanks to me for making this fix.
Original TP Firmware Files for Different Devices
These are Original Stock Touch Panel Firmware/Configs for users who are suffering calibration issue not due to VoLTE firmware but due to other unknown causes.
YUREKA (AO5510) : https://www.androidfilehost.com/?fid=457095661767104421 (Thanks to @Prasoon Mehra)
YUREKA PLUS (YU5510) : https://www.androidfilehost.com/?fid=385035244224388338 (Thanks to @darshan1205)
Users of other YU Devices may share their working TP Firmware to help others....
Mirror Links
https://mega.nz/folder/Z4ckFbDA#bw4HnjUntLbiOLcdT-qpLQ (MEGA)
[Guide] How to Backup or Edit Touchscreen Firmware using GTP ADB Tool (For all devices with Goodix touchscreen)For users of all devices. Backing up the current TP-firmware is useful for saving the device from any future accident.
STEP 1: Download GTP-ADB-Tool Zip on your Windows PC and extract it. Go to the extracted folder and run the GtpAdbTool.exe application. Then connect your smartphone to your PC (be sure USB debugging is enabled in your device). You will see the Gtp Adb Tool window similar to the screenshot below:
STEP 2: Now click on the Menu item as indicated in the screenshot below:
STEP 3: Now you will see a window similar to the screenshot below. Click on the indicated button to read the current TP configuration from your connected device.
STEP 4: Hereafter you will see a window similar to the screenshot below. Take a screenshot of your current window and click on the button indicated to export your current config. Save the resultant config file to your preferred place. Thereafter, if required, you can also edit the firmware by playing with the Hex values.
STEP 5: Upload the Screenshot and your exported config file and save it in a safe place. That's it.
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
shailesh1985 said:
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
Click to expand...
Click to collapse
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
shailesh1985 said:
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
Click to expand...
Click to collapse
I am glad that it worked for you...
BTW you better use TWRP Recovery to flash newer ROMs. CWM Recovery is very old and is abandoned and deprecated.
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
dhrtlockeroo9 said:
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
Click to expand...
Click to collapse
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
nitesh9
nitesh9 said:
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
dhrtlockeroo9 said:
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
Click to expand...
Click to collapse
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
dhrtlockeroo9 said:
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
Click to expand...
Click to collapse
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
nitesh9
nitesh9 said:
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
nitesh9 said:
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
dhrtlockeroo9 said:
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
Click to expand...
Click to collapse
Tried using OTG mouse?[emoji15]
nitesh9 said:
Tried using OTG mouse?[emoji15]
Click to expand...
Click to collapse
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
dhrtlockeroo9 said:
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
Click to expand...
Click to collapse
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
nitesh9 said:
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
Click to expand...
Click to collapse
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
dhrtlockeroo9 said:
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
Click to expand...
Click to collapse
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
nitesh9 said:
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
Click to expand...
Click to collapse
No it's KitKat version.
dhrtlockeroo9 said:
No it's KitKat version.
Click to expand...
Click to collapse
Still you are getting bricked now and then?
What are you flashing actually?
Please please please guys !! I really need your help with my tablet lenovo a3000 !!
my tablet stuck at the logo screen !! I can access the recovery menu I tried factory reset and wipe data 5 times and it didn't help at all !!
my 2 pcs can't recognize my tablet '' the MTK thing won't appear in device manager " already downloaded the drivers on my both pscs with no luck the tablet only charges !!
I notice in the recovery menu I can install zip file there !! so I figured out the only way to install the stock rom is to flash it via recovery menu since my pcs won't recognize the tablet !! I just need the stock rom in a zip file flashable via recovery menu !! anyone can provide me the file it would be really really appreciated please guys it's really urgent !!
It seems that we all have the same problem with this A3000 H device but is seems that people in this forum don't want to help each other. Why is that? We just all need a proper .zip file with a backup that is flashable or restorable from Sd card and job done but where to find such files? I tried to find in some russian forums but they're also not flashable, I almost tried every file that is suitable for flashing through the recovery these files are not just simple .img but must be made as an official Ota updates by its structure with all the meta files and etc. And I bet If we find the proper files we could be able to restore our devices but I started to think that there many people that just do not want old devices to be restored! ): I personaly have such an ota update file but it's only 6mb and when flashing it the process stopped at the half ot it and I know why because we are already rooted and these files are only for the original rom. Mine is 14027 and probably pc stops recognizing the tablet from USB when we all flash it with that rom. So if you have a custom rom installed you have already made my mistake too, but I'll do everything to restore it somehow because the device should work properly and it is working properly I just have to manage to get through this boot loop stuff, I' m sure mine is still working but I' m affraid I did not make a backup so now I'm stuck as well! The only option for us is to flash it through the recovery but with the files I have stored at once there' s an error with the Contacts.app at the half way of flashing. Do I need to delete that app and try again? I can upload the file I have somewhere but it was an update from the OTA and didn't remember which rom was it for . It must have been... 1309 or 11, but not exactly sure and it's only 6 mbs but we could probably use it for something. I think the only option for us is becoming developers. :laugh: Why don't you give us any backups from your personal roms so we could restore our devices?
Does this tablet stopped working for us all, I hope not so we could start helping each other again?
I am a smart guy and know exactly the reason why our old devices stopped working because of the google play apps and updates that are not suitable for us anymore like messenger, facebook lite and etc. It' s not our fault guys! :laugh:
I'm not gonna buy a new tab because someone is telling me to do that I will try restore mine own Lenovo A 3000 H somehow with a little help of course!