Related
Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App
Hi! I'm trying to install a cm rom in my xt926, I have the bootloader and, aparently, I can flash properly the custom recovery, but when I try to reboot onto recovery it doesn't work, shows the motorola logo and, after 1 or 2 minutes, reboot normally, and I can´t enter the recovery to flash the cm rom... Anyone can help me? I don't know what else to do... A lot of thanks.
Sorry for my bad english
I have this Problem as well! Stock KK on XT926 build 183.46.10.XT926.Verizon.en.US. I've tried all the methods I could find.
RALPstat said:
I have the bootloader
Click to expand...
Click to collapse
Is your bootloader unlocked? If it is and you can really flash recovery while in fastboot mode - what do you do after that? Reboot the phone into Android and then try to reboot into recovery? If you're doing that, then that's the problem.
You need to reboot to recovery straight from fastboot, otherwise the stock system deletes the custom recovery. When you flash the recovery - unplug the cable and just press the power button once and the phone will turn off. Then hold Volume UP + Power and the boot menu will show up and then you select recovery and you should be good to go
Solved!
I've found the solution! I've flashed the wrong recovery. My stock rom is kit kat 4.4.2, this recovery works very fine
http://forum.xda-developers.com/showthread.php?t=2747535
The link don't work, can download from here http://www.mediafire.com/download/09c5f08owus1350/CWM6049-RAZR-HD_M-KITKAT.img
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
MrSeler said:
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
Click to expand...
Click to collapse
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
gsmyth said:
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
Click to expand...
Click to collapse
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
MrSeler said:
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
Click to expand...
Click to collapse
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
gsmyth said:
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
Click to expand...
Click to collapse
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
MrSeler said:
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
Click to expand...
Click to collapse
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
gsmyth said:
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
Click to expand...
Click to collapse
Im doing what Im told, so - After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode.
Wish I wasnt so braindead on this field =/ and the cyanogen recovery welcomes me every time
okay so instead of fastboot reboot command i should write the one you gave me? gonna try
EDIT: ERROR, DEVICE NOT FOUND
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
MrSeler said:
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
Click to expand...
Click to collapse
Your boot loader shouldn't be touched.
gsmyth said:
Your boot loader shouldn't be touched.
Click to expand...
Click to collapse
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
MrSeler said:
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
Click to expand...
Click to collapse
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
oasisdave said:
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
Click to expand...
Click to collapse
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
MrSeler said:
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
Click to expand...
Click to collapse
Yeah, that's not working for me, still goes straight to Cyanogen Recovery.
See last question in FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon
EDIT: IT FINALLY WORKED! I just flashed an older version of twrp. Pretty weird how that's working and the newer one isn't. Should I keep this post for people with the same problem?
I know about the problem with cm12s and with the cm recovery thing.
I tried everything. Searched and tried nearly all of the different recovery or root install tutorials. But it's still not working!
Every time I install a recovery (both twrp and cwm) it won't install even though it said it worked. When I do the "remove usb, vol down + power" trick after flashing it just won't boot. It just shows the logo and then it reboots. If I release everything it boots my phone up normally. Even clicking recovery reboot in the reboot menu doesn't work. Then it will bring me to the cyanogen recovery.
My debugging mode is on.
Cyanogen recovery update is OFF.
I'm now using cm12.1s but it didn't work on cm12s either.
ADB and Fastboot are working fine. I tested it and my phone reacts when I give it commands (like fastboot reboot or adb devices)
My bootloader is unlocked (confirmed with fastboot oem device-info)
I just got this phone yesterday. I didn't expect this much trouble with just rooting.
ps: this is one of those "it should work, but it doesn't" moments.
Yes. After cm12 the cyanogenmod is ignoring the cyanogen off recovery mark.
After flashing recovery twrp via fastboot, direct reboot to recovery manually via button. Try look at faq. See q22. http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Always keep a post like this, it's good for future reference (people having the same question will thank you for sure)!
Use Philz recovery. Many are facing same issues with TWRP
realbabilu said:
Yes. After cm12 the cyanogenmod is ignoring the cyanogen off recovery mark.
After flashing recovery twrp via fastboot, direct reboot to recovery manually via button. Try look at faq. See q22. http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Click to expand...
Click to collapse
Just like every other method I've tried, that method doesn't seem to work either.
Hi Benalimarwan,
Thanks for your post. I flashed openrecovery-twrp-2.8.5.0-bacon.img. but, it still didn't work. When I logged into recovery mode it still logged into cynogen recovery. Which version of twrp did you flash? Thanks!
lotherius said:
Just like every other method I've tried, that method doesn't seem to work either.
Click to expand...
Click to collapse
Works for me from latest stable CM12
1. Unlocking Bootloader via fastboot
fastboot oem unlock
fastboot reboot
2. USB Debugging -
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
3. Disable CM Recovery Protection -
On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
4. Installing a Custom Recovery
fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img
got it from http://techerrata.com/browse/twrp2/bacon (one recommends don't use 2.8.7)
reboot to system
5. Flash your custom recovery again, but after flashing don't do a normal reboot. (DONT FORGOT TO Disable CM Recovery Protection first in normal boot before)
After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.
gawd i nearly went out of my mind last night trying to flash TWRP , everything was working fine , fastboot checked out , unlocked the OEM also but it refused to flash TWRP , threw up errors "cannot open recovery' then i remembered the "hide file extensions for known file types" in win7 which was checked and ran
fastboot flash recovery rec[TAB]
Click to expand...
Click to collapse
.i.e hit tab button before hitting enter and it flashed it like a charm !! and i was already to throw this new cell out of my window
Please help me understand Step 5.
Once 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img' is completed, I shouldn't do a 'fastboot reboot'. Instead of that disconnect USB, and then Poweroff using power button. Now use Power + Volume down to boot into recovery. This should allow me to use twrp recovery. Is my understanding correct?
Regards,
Kiran
Hi Guys,
Just did step 5 again.
Did 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img' and disconnected USB, Powered off the device and powered it on using Volume down + Power button. It logged into twrp recovery. I then selected 'Install' and phone automatically got rebooted. Not sure why. I powered it off and powered on again using volume down + Power buttons. It then logged into CM recovery.
Repeated above step again. Again faced same issue. Any ideas?
I unlocked boot loader 4/5 days back. Since twrp recovery was not working, I continued using phone. Installed several apps. Do you think this might be an issue? Do I have to unlock boot loader again and then do 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img'??? Please suggest
Regards,
Kiran
Do it this way with fastboot:
fastboot flash recovery recovery.img (you know the drill...)
when this is completed type in fastboot reboot
BUT MOST IMPORTANT! hold the volume down button on your opo the whole time before you press enter to run the command and keep holding it until TWRP boots up.
This worked on 5 OPO's. (3 were mine, one was my brother's and one is a friend's)
im too on stock 12.1..So which twrp recovery version ll i flash????
1+1
Wug's Bacon Root Toolkit
I had this problem when I tried flashing the custom recovery (TWRP) manually. It didn't matter what I tried, I could never manage to make TWRP persist over CM Recovery after a reboot. After giving up and staying in stock for some time, I decided to try again after getting the OTA to CM 12.1S, but, as no surprise, the same thing still happened. So, as a last try, I downloaded Wug's Bacon Root Toolkit and voila... it finally worked, I had a TWRP that persisted over CM Recovery after a reboot. I don't know what the toolkit did different than me when I did it manually, but it managed to make it work! Hopefully it also works for you...
only used toolkit for Fastboot driver installation...Good step by step instructions...but flashed 2.8.7.0 twrp with adb commands as described by Heisenberb...finally installed recovery n rooted my opo...
1+1
---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------
Never used cyanogenmod on my N4 N5...Flashing process ws easy on nexus devices
1+1
AcmE85, Your suggestion worked like a charm bro. Finally was able to fix the issue. Thanks much for your help!
It's been two days since i have been trying and now it's driving me crazy. I am on stock marshmallow with unlocked bootloader and root. I was trying something (irrelevant here) , and now the phone won't boot into recovery.
No green light when the phone turns on to press the volume buttons to boot into recovery.
Tried adb commands but they just reboot the device. Tried flashing ftf files but still the recovery won't come up.
Tried each and every recovery image out there but still no luck.
The recovery flashes with success but adb returns error "no devices/emulators found"
Btw I'm installing twrp recovery. If anyone knows a solution to this problem, please help
Ikhlaq737373 said:
It's been two days since i have been trying and now it's driving me crazy. I am on stock marshmallow with unlocked bootloader and root. I was trying something (irrelevant here) , and now the phone won't boot into recovery.
Click to expand...
Click to collapse
Could be relevant, you never know.
Ikhlaq737373 said:
No green light when the phone turns on to press the volume buttons to boot into recovery.
Tried adb commands but they just reboot the device. Tried flashing ftf files but still the recovery won't come up.
Tried each and every recovery image out there but still no luck.
The recovery flashes with success but adb returns error "no devices/emulators found"
Btw I'm installing twrp recovery. If anyone knows a solution to this problem, please help
Click to expand...
Click to collapse
How did you manage to "successfully" flash a recovery if adb doesn't even find the device. Usually when I flashed a TWRP I just booted into fastboot and did a quick fastboot flash. Never had any issues with that whatsoever. Maybe try that.
Here's the full story. I first unlocked the bootloader and flashed twrp, rooted and everything went fine. After a couple of months i decided to install lineage os , so i booted into recovery and wiped data, system etc. But i forgot to copy the lineage os zip , so i switched off the device(despite the error message "no os installed"), removed memory card and put files on it and inserted the card back. After this procedure, the phone stopped booting into recovery. Ever since then i am able to flash stock ftf files and everything but the device won't enter recovery so I'm unable to root it again. I hope this will help you understand the situation
Somebody please help
Ikhlaq737373 said:
Somebody please help
Click to expand...
Click to collapse
Try an alternative route.
Fully flash a stock ftf .291. Everything will be up to date then and you'll have the latest bootloader.
Then try two things.
First try fastboot flashing the latest TWRP from Nailyk.
Then boot to recovery holding power and volume keys as you boot and it will boot directly to recovery.
You could also try fully flashing an ftf.
Then use adb to fastboot flash a custom stock based kernel like advanced kernel which includes TWRP 3.0.2.
Use that to boot to recovery the old way and voila you have recovery.
Dobsgw said:
Try an alternative route.
Fully flash a stock ftf .291. Everything will be up to date then and you'll have the latest bootloader.
Then try two things.
First try fastboot flashing the latest TWRP from Nailyk.
Then boot to recovery holding power and volume keys as you boot and it will boot directly to recovery.
You could also try fully flashing an ftf.
Then use adb to fastboot flash a custom stock based kernel like advanced kernel which includes TWRP 3.0.2.
Use that to boot to recovery the old way and voila you have recovery.
Click to expand...
Click to collapse
Are you talking about the .291 ftf obtained from xperifirm ? Does that include the bootloader ?
I'll try the second solution(advanced kernel), thanks.
Ikhlaq737373 said:
Are you talking about the .291 ftf obtained from xperifirm ? Does that include the bootloader ?
I'll try the second solution(advanced kernel), thanks.
Click to expand...
Click to collapse
Yeah that's the one. At the least it will set your phone back to factory settings and you can just start all he root tutorials from the beginning.
Option 2 should work for you.
You should definitely make sure your adb on your PC is working and make sure fastvoot is as well. Just to be sure its not the PC side of things.
I realize this is a bit of a necro-post but I thought it might help someone.
At some point TWRP on the Z3 Compact switched from Volume Up+Power to enter recovery to Volume Down+Recovery.
I spent about an hour trying to get into TWRP because every bit of documentation I read said you have to "power on and then press volume up several times" to get into recovery.
However that is NOT the case.
To get into TWRP after it's been flashed you have to hold Volume Down and Power at the same time, then release Power once the screen lights up.
Dobsgw said:
Yeah that's the one. At the least it will set your phone back to factory settings and you can just start all he root tutorials from the beginning.
Option 2 should work for you.
You should definitely make sure your adb on your PC is working and make sure fastvoot is as well. Just to be sure its not the PC side of things.
Click to expand...
Click to collapse
Thanks dear . It (advanced kernel) worked like a charm
I spent about an hour trying to get into TWRP because every bit of documentation I read said you have to "power on and then press volume up several times" to get into recovery.
However that is NOT the case.
To get into TWRP after it's been flashed you have to hold Volume Down and Power at the same time, then release Power once the screen lights up.
Click to expand...
Click to collapse
this little titbit just saved me. been hours on this!!
Can't get into Recovery and Custom ROM Android
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
However, I no longer get into recovery and the Android system, but I still get into Fastboot mode.
Now I thought I flashed the recovery again but I can't boot in there .....
majikfox said:
I realize this is a bit of a necro-post but I thought it might help someone.
At some point TWRP on the Z3 Compact switched from Volume Up+Power to enter recovery to Volume Down+Recovery.
I spent about an hour trying to get into TWRP because every bit of documentation I read said you have to "power on and then press volume up several times" to get into recovery.
However that is NOT the case.
To get into TWRP after it's been flashed you have to hold Volume Down and Power at the same time, then release Power once the screen lights up.
Click to expand...
Click to collapse
I signed in just to say thanks! And yes, people still use the Z3 lol