Related
Hi Well I had this big problem and I was close to solving it until i messed things up, I tried to not ask for help here but it's been a week and I can't find anything ): My g925p is just useless right now. I hope you can help me
Short version
Using Twrp I picked the efs.img to flash it and I didn't see it had two options ( Boot, recovery ) It's on boot by default so I guess the file flashed as boot and now everytime i turn the phone on it goes directly to download screen ( for odin ) ... I think if someone can make a backup of their boot.img file and upload it somewhere i could flash it and then everything would be back to normal ? At least boot into the rom .-. Thanks for your time !
By the way, When I try to transfer files via sideload twrp tells me i need a higher version for that device, And I have the latest version .-. Thank you guys
Long version
It all started when I tried to flash twrp with flashify, I guess i flashed a wrong version and my phone got stuck on a bootloop, I fixed it by installing the latest version of twrp and factory reset, But then it got into a bootloop in the initial setup, So I decided to Flash a light rom and it worked ! but it wouldn't connect to data, Before I had this problem I backed up esf.img and I thought it would restore connection, But then ... ( Continue in short version B) )
Thanks you so much for reading guys !
Download and install the firmware via odin that should fix your problem
dhonzik said:
Download and install the firmware via odin that should fix your problem
Click to expand...
Click to collapse
That was the first thing I tried but Odin would give me the nand write error, And googling People would just say " Try different cable, different usb port, your nand is burned and you need to replace it " I did the two first things but the second, Well I succeded flashing a rom through twrp so i dont thing there's something wrong with it.
Thanks for the answer tho.
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
You could have an faulty emmc firmware or your emmc reached end of life.
You are from europe? I know someone who can fix it for you.
You can also read the faq on my github userpage for more information about your bug.
kozyn said:
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
Click to expand...
Click to collapse
Once I had same problem with Motorola xoom and guess what was realy the problem. It was the external SD memory remove it then flash the stock rom.. If problem persists see with Andi
Thank you for your response. To me it also seems like faulty emmc. I have check the frequently asked questions on your blog and the description there exactly matches with what I'm experiencing on my device. Yes I am from Europe, Czech Republic. I have already tried to get in touch with two people who have the proper tooling to flash the firmware (JTAG). Hope I get some response fast and the solution is going to work. Still if you have someone in the CZ that you can recommend I'm grateful for any advice.
@zidane: All of the above steps where performed without external SD card.
kozyn said:
@zidane: All of the above steps where performed without external SD card.
Click to expand...
Click to collapse
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
zidane01 said:
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
Click to expand...
Click to collapse
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
kozyn said:
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
Click to expand...
Click to collapse
sounds like that you have a faulty emmc. same what android-andi said.
@kozyn Hi buddy.. have the same thing on a p5110 -- emmc is in read only mode and I can't seem to PM Andi for some contacts.
Can you help me recover this galaxy tab2 pls? Appreciate your time
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
light401 said:
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
Click to expand...
Click to collapse
did you also installed a rom??
No. I'm running the stock rom, no root. I just wanted to get the twrp installed because I need to copy my personal files to an sd card. My stock rom is rebooting itself after completing the normal system startup. I can barely open any app. So I need to backup my files and do a factory reset. Any ideas? Thanks!
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Ka-B00M said:
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Click to expand...
Click to collapse
That doesn't make sense. Odin exists for the exact purpose of flashing through a PC, in case your recovery or anything gets damaged.
i have a galaxy j7 sm-J700P boost mobile it is stuck in boot loop at the boost mobile boot logo... i have tried:
flashing stock rom with odin.. it says pass ... still boot loops...
iv tried re installing cm auto root... still boot loops
installed twp custom recovery... made a img file b4 all this happend (boot loop was caused by trying to install a rom) try and restore the img file it says it was passes but still boot loops... i have tried wiping everything int the phone through twp wipe (everything but the ex sdcard) then restore and with/with out md5 checking.... still boot loops...
i know the phone is not done for or i would not be able to use oden or recovery but even though both programs say they are not failing at there jobs the phone still boot loops and i cant think of anything that im doing wrong is there any one out there that can pointing me in the right direction or lend me a hand please...
nathanful said:
i have a galaxy j7 sm-J700P boost mobile it is stuck in boot loop at the boost mobile boot logo... i have tried:
flashing stock rom with odin.. it says pass ... still boot loops...
iv tried re installing cm auto root... still boot loops
installed twp custom recovery... made a img file b4 all this happend (boot loop was caused by trying to install a rom) try and restore the img file it says it was passes but still boot loops... i have tried wiping everything int the phone through twp wipe (everything but the ex sdcard) then restore and with/with out md5 checking.... still boot loops...
i know the phone is not done for or i would not be able to use oden or recovery but even though both programs say they are not failing at there jobs the phone still boot loops and i cant think of anything that im doing wrong is there any one out there that can pointing me in the right direction or lend me a hand please...
Click to expand...
Click to collapse
factory reset ?
Hi once I faced same problem with my mobile j700F.
I used KIES pc sute
Use model no. (It is behind the battery in a sticker) u can install stock Rom latest version by using it I forgot steps please search YouTube for that all the best ?
messi2050 said:
factory reset ?
Click to expand...
Click to collapse
nope
cherry1991 said:
Hi once I faced same problem with my mobile j700F.
I used KIES pc sute
Use model no. (It is behind the battery in a sticker) u can install stock Rom latest version by using it I forgot steps please search YouTube for that all the best
Click to expand...
Click to collapse
I tried something like that with another program called smart switch and when I looked at the back of the phone for the (S/N there isn't one just the dex and the hex... so I called boost mobile to ask them to look up the S/N for me... they gave it to me and I put in what they told me it was and it said that it wasn't a valid S/N so I called them back relayed the S/N they told me and they said I had it correct.... so I don't know what to do...
Find the firmware for your phone online, download file (should have .md5 at end of file) then flash file with odin on windows.
Sent from my SM-J700P using Tapatalk
hbranha
messi2050 said:
factory reset ?
Click to expand...
Click to collapse
I have the same phone and carrier. Find and download the following 3 files once you have completed a wipe and factory reset with twrp. 1. Odin 3.12.3 2. Youe stock firmware: j700pvpu1apb7_j700pspt1apb7_j700rvpu1apb7_Home tar.md5---2.90gb. 3. cf-auto-root
j71techn-j71tezm-smj7008.zip found here I believe. 4. twrp 3.0.2-d-j71tespr.img.tar. You must be careful when you install twrp. You must go directly into recovery to prevent a boot loop! Do not use anything that you used to make a backup to restore your phone. Just start all over again!!!