Related
Hello,
I 'm new to the android community and i'm so glad to be among you. So i rooted my HTC Desire X (with ICS) a couple of days ago using CWM recovery and now I want to install this DEODEXED stock ROM: http://forum.xda-developers.com/showthread.php?p=40682127
(Note: I have CID:T-MOB101 and HBOOT 1.24.0000).
While rooting the phone i installed CWM recovery while the guide on the link demands to install TWRP. How can i install TWRP over CWM? Because while doing the steps of the guide i got stuck in the 3rd step(Command Prompt says:sending "recovery" but the process never finishes)...
Forgive me if i have forgotten any info of my phone, just let me know!
Thanks in advance,
Tassos
Download this tool http://forum.xda-developers.com/showthread.php?t=1943822
Its much easier.
Important! make a nandroid backup first before flash anything,
ειναι σημαντικο να εχεις ενα!!
Tried with the way above, didn't worked...
I tried this and it didnt worked, i also tried manually through terminal with no luck. As i said above the process gets stuck when the terminal says "sending recovery" and the bar on the screen of my phone doesn't fill. I 've been reading that there are some other users of HTC DX that have the same problem with me, that is they can't flash TWRP and finally they install CWM. Has this something to do with the details of my phone(CID, hboot, etc.)?
So can anyone help me on how to flash TWRP on my phone with CWM on it.?
tassos_chry said:
How can i install TWRP over CWM?
Click to expand...
Click to collapse
Try Clearing the Dalvik Cache
Download this toolkit ,extract it on desktop
replace its recovery.img with this RECOVERY
boot into bootloader
Connect to PC
run 'Install Recovery.img.bat'
AND U"RE DONE :laugh:
if this does not work then try factory format
AND REMEMBER MAKE AN NAND :good: BEFORE DOING THIS
Thanks
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
tassos_chry said:
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
Click to expand...
Click to collapse
1. Start your PC
2. Go in folder containing fastboot.exe and related binaries.
3. Download the recovery.img for (ICS or JB) as required.
4. Type this command in cmd.exe
fastboot.exe flash recovery recovery.img
5. Press power button so that phone goes from fasboot to hboot mode. Then press VOLDOWN and then POWER to boot into recovery.
Its a simple enough process, just try to be calm and do it one step at a time.
Regards
Yasir
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
tassos_chry said:
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
Click to expand...
Click to collapse
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
ckpv5 said:
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
Click to expand...
Click to collapse
All the times I've tried to flash a recovery i 'm on the fastboot/bootloader screen, which says Fastboot USB. I tried with neXus PRIME's way too but it didn't work out. I think i'm not doing anything wrong and don't know why it doesn't work...
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
ckpv5 said:
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
Click to expand...
Click to collapse
FML. It was the USB port that caused the mess(I was using USB 3). Just flashed TWRP using USB 2
Thank you man. I was so dissapointed, thinking that something is wrong with my phone!!
Thank you very much!:laugh:
Update:Any info when the official update for JB from HTC comes out for all of us who don't have it yet?
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer
Hello, fellow Android hackers.
Short: I am trying to install CM on a L21, but fail booting into TWRP (getting only stock recovery).
What I did, working with a brand-new phone:
Unlock bootloader.
Flash TWRP 3.0.2.
Boot to TWRP. It worked.
Try flashing CM, which failed due to some failed assert. Googling revealed a thread on these forums which suggested I had to do a stock update to Marshmallow first.
Downloaded the update through EMUI's updater.
The updater booted to TWRP which aborted the installation because of a failed zip signature check.
I disabled signature checking and ran the installation again. It succeeded.
Tried to directly install CM over it. I got the error message stating I couldn't flash on top of incompatible data.
At this point, I probably should just have wiped system and flash CM, but for some reason I decided to boot to stock.
Here is where it all seems to have gone wrong.
Try to flash and boot to TWRP, like in steps 13 to 18.
Push the B340 UPDATE.APP to /sdcard/dload.
Start the phone using power + vol down + vol up.
I have verified that the phone is on B340 and the builtin updater won't find further updates.
(I have repeated this step and the following ones countless times.)
Boot to bootloader and flash TWRP. Yes, the command succeeds.
Code:
…$ sudo fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.418s]
writing 'recovery'...
OKAY [ 0.641s]
finished. total time: 2.059s
fastboot reboot
adb reboot recovery # boots to stock recovery
Boot to bootloader and flash TWRP.
Hold power + vol up
I read that the duration holding the keys matters, so I tried this very often, but I always got to one of two different stock recoveries.
Factory reset and cache wipe with one of the two stock recoveries.
I also considered crushing the phone on the wall on multiple occasions, but then decided it would not help me with my goal.
Okay.
L21 with B340, how u boot to TWRP? -_-
Also, the two stock recoveries have the menu options "Download latest version and recovery, Reboot, Shutdown" and "Reboot, Wipe data/factory reset, Wipe cache partition".
I humbly thank everyone in advance who might have some contributions to share.
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b34p, but b320 is a great base and supports all custom roms..try it
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
Romiui said:
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
Click to expand...
Click to collapse
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
thilak devraj said:
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b340, but b320 is a great base and supports all custom roms..try it
Click to expand...
Click to collapse
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears pretends to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
but I know of no way to flash recoveries via ADB.
D
Click to expand...
Click to collapse
All recoveries can be Flashed throw Fast-boot ADB Boss .
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
Click to expand...
Click to collapse
glad you did it
thilak devraj said:
glad you did it
Click to expand...
Click to collapse
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
muradulislam said:
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
Click to expand...
Click to collapse
I did, but to no avail. Reunlocking had no effect either.
muradulislam said:
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
Click to expand...
Click to collapse
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
ksdug said:
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
I did, but to no avail. Reunlocking had no effect either.
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
Click to expand...
Click to collapse
wait......
you couldnt make it?? ok right now were are you at??
how to boot Honor 5x into TWRP
I know this is an old post, but since I tried for nearly a week to get my Honor 5x to boot in TWRP when pushing volume up + power button, I just wanted to post how I finally got it working, just in case anyone else should have the same problem...
1. First, I downloaded the latest stock rom. On my Honor 5x Android 5 (Lollipop) was installed, so I downloaded an Android 6 (marshmallow) stock rom. Make sure to get the correct version for your region (e.g. C432 for Europe). I found the correct rom file by simply googeling. If you are in a boot loop or do not have a working android on your phone, read instructions below.
2. I un-zipped the rom file and copied the update.app to my sd card to folder "dload"
3. I booted regularly into Android and started the update installation from the settings, where I could select option to install from SD card.
4. once that was done, i enabled USB debugging in developer tools and booted into TWRP from ADB with command
fastboot boot twrp-3.1.0-0-kiwi.img
5. Then, I installed SuperSu (SuperSU-v2.82-201705271822.zip)
6. Then, I flahed TWRP directly FROM TWRP. To do so, I clicked "Install" button, clicked "Install Image" and then selected TWRP file (which i copied to my SD card earlier). BE CAREFUL TO FLASH TWRP as Revovery (NOT boot). Actually, I first flashed twrp-3.0.0-0-kiwi.img, then directly after flashed twrp-3.0.2-0-kiwi.img and then I flashed twrp-3.0.0-1-kiwi.img (you see I was kind of desperate...). After that, from TWRP I booted into bootloader and again flashed twrp image from PC using adb:
fastboot flash recovery twrp-3.1.1-0-kiwi.img
7. from ADB, I again booted into TWRP
fastboot boot twrp-3.1.1-0-kiwi.img
8. ... where I once more installed TWRP.
After that I clicked reboot and selected to boot into Recovery. Then it finally worked.
After endless tries to get my phone to boot into TWRP when pushing volume up and power button, I am not sure which of the above steps made the difference. I think the important part is to update to the latest android version.
BTW: my first problem was I bricked my phone by trying to install lineageos from TWRP 3.1.1.1 and was in an endless bootloop. Here is how I got a regular android running:
I booted into bootloader (power + vol DOWN) and flashed the following files from adb (i got the files by extracting an android stock rom with Huawei Update Extractor (HuaweiUpdateExtractor_0.9.9.3.zip)):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Hope this helps...
It's better to post in a new thread, that will be more helpful for you
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.