Okay this is a weird one, Note 10.1 runs out of battery a few nights ago, go to plug it in for charging and it hangs on the "samsung galaxy note 10.1 screen". I had been running Cyanogen 11 for a few months just fine and before that Omni (Both 4.4.2) no dramas with CWM recovery 6.0.3.6. I can still get to Download/ODIN mode and CWM.
Now here is the fun part(s)
1. Firstly I tried reflashing the roms from CWM, after all I flashed both of them from the same recovery and they were still on the external sdcard. Both gave set metadata recursive status 7 error messages.
1.NB Whenever I selected the internal storage to search for a zip CWM would close immediately (crash?) and go back to the galaxy note 10.1 screen and hang there still. Also does this on other options, so I can't reach the backup I made on the internal storage
2. After googling that it seems that 6.0.3.6 can't flash 4.4.2 roms so I flash a later version using ODIN, it says success on the PC side, yet nothing changes in tablet, same when trying with twrp. CWM 6.0.3.6 won't budge
3. Try flashing the official rom (N8010XXUCMK2_N8010XSACNA2_HOME) from sammobile using ODIN, same problems as before, download mode shows the bar filling up so does ODIN, says it passed, still nothing.
4. Try old 10.2 Cyanogen build, no error message but still hangs on samsung galaxy note screen
5. Try repartitioning whilst flashing, various .pit also used, no dice. However I can now mount /data from cwm still can't mount /efs
6. Read about eMMC bug possibly being induced by Cyanogenmod, open up tablet to to check numbers on eMMC module, doesn't match any of the affected numbers.
7. Try above steps multiple times, including flashing each right after each other.
8. Cry
9. Look at new tablet options (Damn no good ones with softkeys)
10. Back to desperate flashing ODINing and scrolling through CWM
So any ideas?
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
jika23 said:
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
Click to expand...
Click to collapse
Where exactly is the PIT file I should be looking for? Been looking for a while now.
Related
Hello.
First of all - I did try to search my problem but it is unique and I did not find the answer.
I am new to flashing ROM's and recoveries, but I do understand a little bit.
Here is my situation:
I bought a tab 2 10.1 inch wifi EUR version in a carboot sale for 20 quid. The guy showed me that it boots, and everything works, EXCEPT, it will do random restarts and sometimes drop the wi-fi signal.
When i got home it was running CM 10.2 something rather and it had a PhilZ 5.0 touch recovery. Obviously this was rooted. I wiped everything using odin 3.07 and it was restored to original samsung firmware and software. However the tab is either 1. Stuck in boot loop at samsung logo OR 2. loads to the welcome screen then freezes - restarts - stuck on boot logo.
I have tried to put a new recovery on it CWM 6.XXX but with no luck. When i try to install from SD card I get this error: E: failed signiture verification.
Anyone have any ideas what I should try to do now?
Thanks
Are you sure that before you flashed the new ROM you did a thorough reset and format of the system / data partitions? I've had similar symptoms from doing less than fully clean flashes.
Also I've seen lots of people have trouble with cwm (including me), so I've moved on to TWRP ( version at least 2701) or the Philz 6.something.
My best experience was with TWRP / full reset, format / omnirom for KitKat.
Good luck. Report back what works for you.
Marc
Frankenscript said:
Are you sure that before you flashed the new ROM you did a thorough reset and format of the system / data partitions? I've had similar symptoms from doing less than fully clean flashes.
Also I've seen lots of people have trouble with cwm (including me), so I've moved on to TWRP ( version at least 2701) or the Philz 6.something.
My best experience was with TWRP / full reset, format / omnirom for KitKat.
Good luck. Report back what works for you.
Marc
Click to expand...
Click to collapse
Yes i wiped everything i could. There were no errors given when wiping.
Will try TWRP recovery and see if that changes anything.
Thanks
I got bored of my now aging Samsung Galaxy tab 2 10.1 and decided to try and flash it to CM 10.1 . in hopes of a speed boost. I had never flashed before But these are the steeps i followed.
First i rooted device through Kingo Root aplication, No problems there.
Then i got Odin Mobile from the app store . I put these 3 files on my device .
E4GT-EL29-directbootCWM-v3.tar.md5
CM 10.1 ROM 4.2.2 JB
CM 10.1 Gapps zip
taken from here **cant post link as i am a new member**
Then in ODIN Mobile in the section that says kernal i loaded the first file and clicked flash firmware. But instead of rebooting into clock work recovery (which is what i think was meant to happen??) the tablet rebooted and then stalled on the Samsung logo, where it remained, even if i reboot . Samsung comes up on screen and it stays there.
i can reboot into what i think is recovery mode where i have some options i tried selecting "wipe data/factory reset" but the problem still persisted .
I have no idea how to proceed from here. Can someone please help me recover my tablet to its original state.
Thanks
ronanbrowne88 said:
I got bored of my now aging Samsung Galaxy tab 2 10.1 and decided to try and flash it to CM 10.1 . in hopes of a speed boost. I had never flashed before But these are the steeps i followed.
First i rooted device through Kingo Root aplication, No problems there.
Then i got Odin Mobile from the app store . I put these 3 files on my device .
E4GT-EL29-directbootCWM-v3.tar.md5
CM 10.1 ROM 4.2.2 JB
CM 10.1 Gapps zip
taken from here **cant post link as i am a new member**
Then in ODIN Mobile in the section that says kernal i loaded the first file and clicked flash firmware. But instead of rebooting into clock work recovery (which is what i think was meant to happen??) the tablet rebooted and then stalled on the Samsung logo, where it remained, even if i reboot . Samsung comes up on screen and it stays there.
i can reboot into what i think is recovery mode where i have some options i tried selecting "wipe data/factory reset" but the problem still persisted .
I have no idea how to proceed from here. Can someone please help me recover my tablet to its original state.
Thanks
Click to expand...
Click to collapse
U just need to boot into recovery and flash cm10 and gapps from there after wiping system, data, dalvic cache and cache. These r the steps for CWM.
E4GT -EL29 CWM doesn't sound like a file that is for this tablet, it has to do with a Samsung phone.
Recheck your info and if possible post where you got this file from.
If you flashed the wrong file your tablet could be toast.
Pp.
Phone Info:
Samsung Galaxy s5 (sm-g900p) (Sprint)
Android Version 5.0
Build: LRX21T.G900PVPU1BOA6
Hi, Thank you ahead of time to anyone who might have a minute to help me out. I have been combing XDA and as well as some other sites trying to find a solution myself but given my limited experience in this area Im at the point where I thought it best to stop and ask for help rather than do the wrong thing and have my phone blow up in my hands TNT style
I rooted my s5 a few weeks ago using Odin with C-f--auto-root, which went perfectly and I had zero issues afterwards.. This was only my second rooted device so of course I was exploring all of my new options out there to customize my phone.
The problem occurred after installing the apps Layers Manager and Layers Showcase (BitSyko Development) from the Playstore. Both seem like great apps and were not to blame for this problem, I just happened to be using them when I jacked something up.
Basically, over a day or two I tried several Layers Themes and they applied just fine, but one did not. Shortly after applying the Layer, and rebooting my phone I ended up on the bright Yellow Sprint Spark startup screen and my phone wont budge past this point.
I am able to boot into Recovery Mode as well as Download mode. I tried wiping the cache Partition as i had read to do as well as doing a full data clear and reset ,but it still; wouldnt move past the yellow screen. Then I very carefully followed directions to flash the stock firmware using Odin, making sure i used the right one for this phone and Odin displayed PASS! at the end. From what i could tell, it all went fine... But it STILL wont move past that enraging yellow screen!!
I think I may have missed something in regards to flashing stock firmware but i dont know. Ive read some other suggestions and things to try but, like i said, at this point and with my limited experience, I thought it best to concede and ask the experts for some help.
I hope I included any information needed...
Are you waiting long enough to allow for loading? Did you try installing a stock rom that matches bootloader version?
gdrocks said:
Are you waiting long enough to allow for loading? Did you try installing a stock rom that matches bootloader version?
Click to expand...
Click to collapse
Hi, thank you for your reply. Yes, the stock rom i used matched the original rom on the device. I had taken some screen shots of the Device Info screen a while back for something else, so luckily i had a lot of general info right there shot the s5. And i waited a good amount of time. Odin took a few minutes and it read PASS at the end. From what i could tell, it was all done and i still waited just to be sure. But the more i think about it, the more i feel that i did do something wrong at this step. I'm just not certain what
Amandajbee86 said:
Hi, thank you for your reply. Yes, the stock rom i used matched the original rom on the device. I had taken some screen shots of the Device Info screen a while back for something else, so luckily i had a lot of general info right there shot the s5. And i waited a good amount of time. Odin took a few minutes and it read PASS at the end. From what i could tell, it was all done and i still waited just to be sure. But the more i think about it, the more i feel that i did do something wrong at this step. I'm just not certain what
Click to expand...
Click to collapse
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
Click to expand...
Click to collapse
Thank you so much! I am going to give this a try hopefully tonight, or in the morning if I cant make time tonight. I will report back once I do. Again, thank you so much for taking the time to help me out. It really means a lot! :fingers-crossed:
i had the same problem and tried over 10 other ways to fix it. i finally found this post and it worked! ty so much. was almost ready to throw the phone out
daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
Click to expand...
Click to collapse
see, nw this is the type of post i like to see!! @daniel3x , for future reference, idoneapps.com has WAAAAAAY faster downloads then sammobile and the tar.md5 files are 100% legit! But youre reply is pretty much exactly what i would have said. I personally would have advised on OK4 vs OG1. OK4 is just easier to mess with on TWRP and stuff.
wait a while for first stock boot from yellow screen
I've read that flashing a stock firmware will take 10 to 20 or more minutes on your first boot. Let the heat sink from your body and give it time.
I want to flash to a stock as well. Can I just full system wipe in twrp and Odin og1 or ok4>what I'm currently on and would like to keep it? Should I take out my SIM? Should I take out my sd card? Will I need to re partition my ext2/4 on the sd? Does the stock image replace the bootloader? I have a twrp backup on my extsd, can I use it after attempting to flash stock? Flash stock tar/zip should stock be a tar?, Odin kltespr twrp in pda mode, leave everything alone, root method of choice, phh su so flash in twrp, should I update Odin? I have 3.07 and 3.10.6. Then wait out that initial boot. I don't want a backup of what I have now because I've done things I wantedd to revert and do differently this time as I'm not AS clueless
Amandajbee86 said:
Phone Info:
Samsung Galaxy s5 (sm-g900p) (Sprint)
Android Version 5.0
Build: LRX21T.G900PVPU1BOA6
--SNIP--
I hope I included any information needed...
Click to expand...
Click to collapse
Oh, some app permissions can cause a bootloop. Instead of flashing the whole stock rom, you can flash the recoveries through odin.
You can either:
-Flash stock recovery through Odin (BL slot) and perform a factory reset/cache wipe
-Go through TWRP and restore your backup
-Go through TWRP and wipe your cache partitions on ADVANCED WIPE
SAMSUNG S5 SPRINT STOCK RECOVERIES:
mega(DOT)nz/#!bRxE1QRD!1-mAR_T6tvb-83xohTD6Q8uNxW4TdpcqnDT3Uq6s5ms
mega(DOT)nz/#!mEwQCDrS!I8pGn8Wa4TSlCpsazD2_ZOh7t1r9sy5kJZ_ujk6viOY
Bl is the recovery? Odin can't flash a bootloader?
This salvaged my sprint phone
I had to flash back from LineageOS 14.1 to stock rom temporarily to "update profile" so I could make phone calls again after moving the phone to a new line. I tried several different versions of stock rom and flashed via ODIN, but all got stuck on the boot loop. It felt like I had searched endlessly for a solution until I came across this thread. I followed the process (Thank you @daniel3x & @youdoofus) using the stock rom ending in OK4; it worked flawlessly!
If possible, I would like to see this thread "stickied" for Sprint Galaxy S5. It will likely save other users a lot of time.
:good: :victory:
kentc said:
I had to flash back from LineageOS 14.1 to stock rom temporarily to "update profile" so I could make phone calls again after moving the phone to a new line. I tried several different versions of stock rom and flashed via ODIN, but all got stuck on the boot loop. It felt like I had searched endlessly for a solution until I came across this thread. I followed the process (Thank you @daniel3x & @youdoofus) using the stock rom ending in OK4; it worked flawlessly!
If possible, I would like to see this thread "stickied" for Sprint Galaxy S5. It will likely save other users a lot of time.
:good: :victory:
Click to expand...
Click to collapse
glad to help
Ok, using a Samsung galaxy s5, kltespr, running 5.0 lollipop. recovery twrp 2.8.1 Been failing to install a custom rom tried a nightlie from cyanogenmod 12.1 i belive..didnt work recovered had no problems. Reboot recovery to try again. Pulled my sd card, did the stupid thing and typed yes to wipe all data, thinking once i put sd back in my recovery would fix it. Turns out i didnt have 100% backup now i dont have a ui...any pointers??
Odin a full tar and start over
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