Related
Hi Guys,
I had CM 10 on my phone and I was able to use CWM successfully. But, then I flashed Pandroid 4+ (CM 11 based) Kitkat 4.4 ROm on my phone.
Now, I am not able to boot into recovery mode. As i try to enter into recovery mode, My phone gets stuck in the boot screen and does not boot up. After so many attempts of pressing power button, it starts. It's so painful.
I want to revert back to CM 10 stable rom, but I can't boot in to recovery mode.
I did some research and found a CWMFixed.zip as a solution. It contains a boot.img file. Please let me know how can i flash this file without entering into CWM.
Or if there is any other solution for this problem then please let me know.
It urgent.
@tysonraylee I hope you can help me in this as you had posted a similar query in other thread.
Thanks in advance.
My friend, If you would have only read the PA thread properly you would know that beta 5 has the bug where it breaks the recovery you would have avoided the problem altogether but anyways i would suggest that you flash an odin format (.tar) kernel using PC Odin which will get you a working recovery and from there it should be pretty easy, if you took a nandroid backup before you will be able to restore your previous rom and if you didnt you have to flash a different rom of your choice
flash this TW PC odin format (.tar) kernel by bauner https://www.androidfilehost.com/?fid=95784891001607164
make sure once you flash this to not let the phone boot into ROM, after flashing successful take off the battery and then insert back and boot into recovery.
Once you have a recovery then you need a SE Linux compatible recovery so for that connect the device to PC and mount the usb storage through recovery then transfer
This Bauner's KK kernel if you require CWM https://www.androidfilehost.com/?fid=95784891001608504
and this GeeckoDev Raw kernel if you require TWRP recovery http://forum.xda-developers.com/showpost.php?p=53978758&postcount=583 (download raw_kernel_r6_k44.zip)
once transfered to your device flash the one you require and remember we are flashing these kernel just for temporary use and once a rom is flashed they will get overwritten with the recovery that comes with the rom kernel so you dont have to worry about these kernels
Once flashed remember to reboot to recovery and not system, once the device boots into your desired recovery then either restore your previous rom from backup or falsh a new one
hope this helps and remember next time before flashing a rom read the OP and atleast 4-5 last pages. Believe me this will save you a lot of trouble in your future flashing endeavours
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.
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
Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!
How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579
dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.
If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app
you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1
Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.
hi every body
my device 18626 is always booting into recovery mod
i have cwm revovery v6.0.3.6
this happen when i trid to install cosmic 2 zips
it boots into cwm
i have trid factory reset
format data or system
no thing work
and still booting into cwm
when i enter to download mod triing to install stock rom
didn.t appear on odin
although i hear the beeb when i connect the device
i have checked the driver
and install it many time (clean install) either via susmung driver or online
i also tried soln.s in the intent like in the photo
i have also tried different pcs different ports different cables no thing work
odin or kies didnt recognize device
any help plz!
i think if there is flashable twrp zip it may work
i have one but it needs odin and i need it fashable zip sp ican falsh it via cwm as the device didn appear on odin
i have tried anthor rom super rom 6.0.1
and the same problem booting into recovery
i havent back up
there is additional photos in comment
AboodaBasher said:
hi every body
my device 18626 is always booting into recovery mod
i have cwm revovery v6.0.3.6
this happen when i trid to install cosmic 2 zips
it boots into cwm
i have trid factory reset
format data or system
no thing work
and still booting into cwm
when i enter to download mod triing to install stock rom
didn.t appear on odin
although i hear the beeb when i connect the device
i have checked the driver
and install it many time (clean install) either via susmung driver or online
i also tried soln.s in the intent like in the photo
i have also tried different pcs different ports different cables no thing work
odin or kies didnt recognize device
any help plz!
i think if there is flashable twrp zip it may work
i have one but it needs odin and i need it fashable zip sp ican falsh it via cwm as the device didn appear on odin
i havent back up
Click to expand...
Click to collapse
during flashing 1st ZIP
AboodaBasher said:
hi every body
my device 18626 is always booting into recovery mod
i have cwm revovery v6.0.3.6
this happen when i trid to install cosmic 2 zips
it boots into cwm
i have trid factory reset
format data or system
no thing work
and still booting into cwm
when i enter to download mod triing to install stock rom
didn.t appear on odin
although i hear the beeb when i connect the device
i have checked the driver
and install it many time (clean install) either via susmung driver or online
i also tried soln.s in the intent like in the photo
i have also tried different pcs different ports different cables no thing work
odin or kies didnt recognize device
any help plz!
i think if there is flashable twrp zip it may work
i have one but it needs odin and i need it fashable zip sp ican falsh it via cwm as the device didn appear on odin
i havent back up
Click to expand...
Click to collapse
successfull 1st flahing
AboodaBasher said:
hi every body
my device 18626 is always booting into recovery mod
i have cwm revovery v6.0.3.6
this happen when i trid to install cosmic 2 zips
it boots into cwm
i have trid factory reset
format data or system
no thing work
and still booting into cwm
when i enter to download mod triing to install stock rom
didn.t appear on odin
although i hear the beeb when i connect the device
i have checked the driver
and install it many time (clean install) either via susmung driver or online
i also tried soln.s in the intent like in the photo
i have also tried different pcs different ports different cables no thing work
odin or kies didnt recognize device
any help plz!
i think if there is flashable twrp zip it may work
i have one but it needs odin and i need it fashable zip sp ican falsh it via cwm as the device didn appear on odin
i havent back up
Click to expand...
Click to collapse
2nd zip during flashing
AboodaBasher said:
hi every body
my device 18626 is always booting into recovery mod
i have cwm revovery v6.0.3.6
this happen when i trid to install cosmic 2 zips
it boots into cwm
i have trid factory reset
format data or system
no thing work
and still booting into cwm
when i enter to download mod triing to install stock rom
didn.t appear on odin
although i hear the beeb when i connect the device
i have checked the driver
and install it many time (clean install) either via susmung driver or online
i also tried soln.s in the intent like in the photo
i have also tried different pcs different ports different cables no thing work
odin or kies didnt recognize device
any help plz!
i think if there is flashable twrp zip it may work
i have one but it needs odin and i need it fashable zip sp ican falsh it via cwm as the device didn appear on odin
i havent back up
Click to expand...
Click to collapse
successful 2nd zip flashing
AboodaBasher said:
hi every body
my device 18626 is always booting into recovery mod
i have cwm revovery v6.0.3.6
this happen when i trid to install cosmic 2 zips
it boots into cwm
i have trid factory reset
format data or system
no thing work
and still booting into cwm
when i enter to download mod triing to install stock rom
didn.t appear on odin
although i hear the beeb when i connect the device
i have checked the driver
and install it many time (clean install) either via susmung driver or online
i also tried soln.s in the intent like in the photo
i have also tried different pcs different ports different cables no thing work
odin or kies didnt recognize device
any help plz!
i think if there is flashable twrp zip it may work
i have one but it needs odin and i need it fashable zip sp ican falsh it via cwm as the device didn appear on odin
i havent back up
Click to expand...
Click to collapse
after wiping delvac and just before rebooting system
but it reboot into cwm
Ok, first of all, i would suggest you to use Cosmic Rom and latest version of twrp for the i8262.
TWRP: https://forum.xda-developers.com/ga...recovery-twrp-3-0-2-0-samsung-galaxy-t3468405 (Download the New Version.)
Cosmic Rom: https://forum.xda-developers.com/ga...osmic-rom-smooth-fast-stylish-kitkat-t2909037 (download the update too)
After that flash TWRP using your CWM.
Now first make sure all the data is properly backed up. Also keep these files in your SD Card.(use a reader or insert it another device and transfer it anyhow. Or you can use adb push to push your file to device after step 1.)
1st go to Wipe and advanced wipe and tick Internal Memory(just to make sure nothing is left that is causing problem), cache and delvik cache.
2nd Now go to Install, and select Cosmic Rom, now click add more zips to queue. Now select the update file (Optional: you can even add the SuperSu file now) and flash them.
3rd now clear cache and dalvik cache and go to reboot and click system.(options may wary as i dont remember them correctly)
4th Now enjoy this rom and click thanks if i helped
5th if it still booted in recovery than something is damm wrong with phone
FYI- I have written this answer while commuting so i dont remember the options correctly. Also sorry for my terrible English and feel free to DM me any query.
TheWarrior01 said:
Ok, first of all, i would suggest you to use Cosmic Rom and latest version of twrp for the i8262.
TWRP: https://forum.xda-developers.com/ga...recovery-twrp-3-0-2-0-samsung-galaxy-t3468405 (Download the New Version.)
Cosmic Rom: https://forum.xda-developers.com/ga...osmic-rom-smooth-fast-stylish-kitkat-t2909037 (download the update too)
After that flash TWRP using your CWM.
Now first make sure all the data is properly backed up. Also keep these files in your SD Card.(use a reader or insert it another device and transfer it anyhow. Or you can use adb push to push your file to device after step 1.)
1st go to Wipe and advanced wipe and tick Internal Memory(just to make sure nothing is left that is causing problem), cache and delvik cache.
2nd Now go to Install, and select Cosmic Rom, now click add more zips to queue. Now select the update file (Optional: you can even add the SuperSu file now) and flash them.
3rd now clear cache and dalvik cache and go to reboot and click system.(options may wary as i dont remember them correctly)
4th Now enjoy this rom and click thanks if i helped
5th if it still booted in recovery than something is damm wrong with phone
FYI- I have written this answer while commuting so i dont remember the options correctly. Also sorry for my terrible English and feel free to DM me any query.
Click to expand...
Click to collapse
thanks bro for help
i have made the stock flashable zip and flash it but it was the same problem i faced
afrer alot af search i finally found what is called heimdall suit
so i have used it instead of odin and i have flashed stock then device become detected by odin
so i falshed the stock again using odin
and flashed twrp 2.7.1 and used it to flash cosmic and its update and every thing now is fine
Do u suggest falshing the new twrp V3
and reflash cosmic ,
or just update twrp as now evwry thing works fine
AboodaBasher said:
thanks bro for help
i have made the stock flashable zip and flash it but it was the same problem i faced
afrer alot af search i finally found what is called heimdall suit
so i have used it instead of odin and i have flashed stock then device become detected by odin
so i falshed the stock again using odin
and flashed twrp 2.7.1 and used it to flash cosmic and its update and every thing now is fine
Do u suggest falshing the new twrp V3
and reflash cosmic ,
or just update twrp as now evwry thing works fine
Click to expand...
Click to collapse
I highly recommend to do it, its good to use updated version as they have many bugs fixed and some features likes in this updated version, MTP is working fine.
TheWarrior01 said:
I highly recommend to do it, its good to use updated version as they have many bugs fixed and some features likes in this updated version, MTP is working fine.
Click to expand...
Click to collapse
i'll do it , thanks bro
AboodaBasher said:
i'll do it , thanks bro
Click to expand...
Click to collapse
Welcome, glad i was able to help you out.