Related
I'm an idiot and tried to flashboot a new ROM on my phone without an engineered SPL. I got the standard error
"failed <remote: signature verify fail>"
In my defense i'm a noob who only now understands that I can't remote fastboot using my current SPL.
Now my phone hangs on the ROGERS splash screen.
I can get into HBOOT, FASTBOOT and RECOVERY. However I do not have any previous .img files to flash (I created a backup a few months ago and now I can't find it).
I have searched this forum (and elsewhere) and I cannot find how to restore my phone (I find lots of threads saying you can, but none with any useful steps)
Fastboot menu says:
- SPL 1.33.0009
- Radio 3.22.20.17
Please HELP!
if u have RA's recovery .. ther should be no problem
just booot in recovery mount ur sd card put any rom in it and flash
otherwise u can try the gold card method
P.S. : plz try to do ur homework b4 posting a new thread
Newfy said:
I'm an idiot and tried to flashboot a new ROM on my phone without an engineered SPL. I got the standard error
"failed <remote: signature verify fail>"
In my defense i'm a noob who only now understands that I can't remote fastboot using my current SPL.
Now my phone hangs on the ROGERS splash screen.
I can get into HBOOT, FASTBOOT and RECOVERY. However I do not have any previous .img files to flash (I created a backup a few months ago and now I can't find it).
I have searched this forum (and elsewhere) and I cannot find how to restore my phone (I find lots of threads saying you can, but none with any useful steps)
Fastboot menu says:
- SPL 1.33.0009
- Radio 3.22.20.17
Please HELP!
Click to expand...
Click to collapse
you can fastboot flash recovery images man! search for AMON RA'S RECOVERY IMAGES, FASTBOOT FLASH IT, THEN BOOT INTO RECOVERY AND FLASH A ROM AND YOU ARE ALL SET! good luck brother!
oshizzle1991 said:
you can fastboot flash recovery images man! search for AMON RA'S RECOVERY IMAGES, FASTBOOT FLASH IT, THEN BOOT INTO RECOVERY AND FLASH A ROM AND YOU ARE ALL SET! good luck brother!
Click to expand...
Click to collapse
Thank you guys.
I did search and read tons of threads and how to's but without knowing exactly what to search for, it is really hard for a noob.
I got it all up and running now. Thanks again.
Ok now I have a new problem.
I upgraded my SPL to 1.33.2010.
I'm trying to upgrade my Radio next however fastboot just hangs. It recognizes the device but when I "flash radio" it just sits at "send" forever.
I have tried reinstalling all my drivers and the sdk tools. Same problem.
Anybody have ideas?
Are you trying to follow the Cursordroid's guide to update to Radio 6.35.x / SPL 1.76? In that case it's strange to hear the send process loops forever.
1. have you double checked fastboot recognises your device? (fastboot devices)
2. is your USB cable plugged?
elegos said:
Are you trying to follow the Cursordroid's guide to update to Radio 6.35.x / SPL 1.76? In that case it's strange to hear the send process loops forever.
1. have you double checked fastboot recognises your device? (fastboot devices)
2. is your USB cable plugged?
Click to expand...
Click to collapse
Yes I am following Cursordriods guide and Amrons. I spent 12 hours and didn't go to bed last night working on this stupid problem. I was at my wits end. Hair sticking up, nervous eye and head twitches, rings around eyes, and 20 hail mary's later I tried an absolutely desperate move and plugged my USB cable into the back USB ports instead of the front ones.........it worked. I didn't know if I should cry or beat my computer with a baseball bat.
Anyway. Thank you to everyone who were helping me out. Nice community here.
Cursordriods Sense ROM rocks. Highly recommended.
Hello. I am new to this forum so bare with me lol. Recently I rooted my G1 using the following guide.
http ://forum.xda-developers. com/showthread.php?t=727688
Everything was working perfect. I went to Rom Manager app and updated recovery image and my phone was rebooting fine. Today I could not send text messages so I rebooted my phone and it gets stuck on G1 screen. Home+power doesnt work but camera+power works. What can I do?? I searched for 3 hours already and I only read that people fixed it but no one gave step by step instructions
radekkacz07 said:
Hello. I am new to this forum so bare with me lol. Recently I rooted my G1 using the following guide.
http ://forum.xda-developers. com/showthread.php?t=727688
Everything was working perfect. I went to Rom Manager app and updated recovery image and my phone was rebooting fine. Today I could not send text messages so I rebooted my phone and it gets stuck on G1 screen. Home+power doesnt work but camera+power works. What can I do?? I searched for 3 hours already and I only read that people fixed it but no one gave step by step instructions
Click to expand...
Click to collapse
Does it only get stuck on the splash screen when you try to boot into recovery? Or does it not boot into the ROM at all?
Same thing
I have the same thing happening to me but there is no ROM. So I am able to get into FASTBOOT but it wont flash anything but I have no ROM or RECOVERY IMAGE
In fastboot you can flash, either download the original RC29 DREAIMG.NBH, or get the fastboot executable on your PC (mostly in PATH in sdk/tools/ with adb) and flash recovery with fastboot:
Code:
fastboot flash recovery recovery.img
In the Cyanogen Wiki there is a link for both recoveries (RA and CWM).
fonix232 said:
In fastboot you can flash, either download the original RC29 DREAIMG.NBH, or get the fastboot executable on your PC (mostly in PATH in sdk/tools/ with adb) and flash recovery with fastboot:
Code:
fastboot flash recovery recovery.img
In the Cyanogen Wiki there is a link for both recoveries (RA and CWM).
Click to expand...
Click to collapse
When I go into fastboot which I suppose is camera+power, I dont have any options to flash. I have 4 options...
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
To clarify, my phone does not boot at all and no recovery.
radekkacz07 said:
When I go into fastboot which I suppose is camera+power, I dont have any options to flash. I have 4 options...
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
To clarify, my phone does not boot at all and no recovery.
Click to expand...
Click to collapse
The fastboot command is entered on the computer , Windows command line for example
http://android-dls.com/wiki/index.php?title=Magic_Rooting
Is good guide to show you the basics, just download a dream recovery instead of sapphire/magic recovery image
radekkacz07 said:
When I go into fastboot which I suppose is camera+power, I dont have any options to flash. I have 4 options...
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
To clarify, my phone does not boot at all and no recovery.
Click to expand...
Click to collapse
Are you able to go through the root process again. Sounds like your only option to me.
I have absolutely no clue how to get the fastboot to load. My adb doesnt turnon on pc nor the fastboot. Im a noob to this stuff.
"Java not found in your path" .
radekkacz07 said:
"Java not found in your path" .
Click to expand...
Click to collapse
You need to have a java jre/jdk within your classpath.
Sent from my Htcclay's Superfly G1 using XDA App
? Im so confused with this lol
There is a Guide for ADB and Fastboot in the Q&A section. Please read there how to set up an appropriate environment.
Sent from my Htcclay's Superfly G1 using XDA App
Thank you for the link but I cant run sdk setup because it doesnt detect my java although I installed it. Also I will not be able to put my phone in debug mode since I cant boot it.
How can I put java in my classpath? could you clarify?
radekkacz07 said:
How can I put java in my classpath? could you clarify?
Click to expand...
Click to collapse
In Linux you have to enter:
export PATH=$JAVA_HOME/bin:$PATH
On the shell, where JAVA_HOME points to the directory where java is installed.
In Windows you have to open your settings, and to find the PATH configuration. There you have to add the bin-Directory of your Java-Installation. But you have to separate by a ';' instead of ':'.
Hope that will help you ...
Sent from my Htcclay's Superfly G1 using XDA App
i am having this same problem.
i can get into the "android system recovery" menu, but i dont know what to do from there...if anything.
nandroid restore gives me an error.
do i need to put the ROM and update ZIPs back on the SD for a restore to work?
rdub202 said:
i am having this same problem.
i can get into the "android system recovery" menu, but i dont know what to do from there...if anything.
nandroid restore gives me an error.
do i need to put the ROM and update ZIPs back on the SD for a restore to work?
Click to expand...
Click to collapse
So you dont have the same problem because you can get into the recovery and I cant...
If anyone lives around chicago land area, I am willing to pay for someone to help me out withthis problem.
there have been a load of issues flashing recovery from within a rom when running CM5 or 6....unfortunately, most of the "clear warnings" are far from that....
if you are having trouble setting up fastboot, have a look at this guide, it may be of benefit to you....you only really need to follow the fastboot instructions (note. the guide is for ubuntu 9.10 and 10.04)
http://www.lineardroid.co.uk/2010/04/how-to-set-up-adb-in-ubuntu/
i have the same problem but when i try to flash a new recovery img i get MTD: a bunch of numbers and it keeps on telling me that i dont have enough memory.. is there anyway i can fix this?
Hi there. I was fooling around with my TF300T (I was foolish at some point, probably) and managed to install Jellybean using this method. It started working fine. So it did that I restored my files using Titanium Backup Pro, installed from the App store right after the first boot. The apps/data I restored with Titanium Backup, as far as I can remember, were mostly games and Dolphin stuff, nothing directly related to system, as far as I know.
After this backup restoration, I used the tablet a little more, played the games to check if my progress was not lost and all that. It worked, Angry Birds at least had all the levels I completed before yet marked as completed after restore the procedure.
So far so goo... no! For some reason I can't remember I restarted the tablet, at least I tried! It got stuck on the loading screen (the white Asus, not the shiny one). So, after that I tried to restore it again, and then I probably did something completely stupid and I can't even remember what.
I even tried superwipe on it, but that didn't work neither.
At this point my tablet let me flash recovery image, CWM and TWRP. I can use adb shell with CWM but not with TWRP.
For some reason, I don't know, when I use CWM it doesn't mount /sdcard, TWRP seem to be mounting it, but go figure, I can only access the /sdcard that TWRP mounts using TWRP, if I change the recovery to CWM for some bizarre (or obvious to you guys) reason, I can't mount it.
And no matter what recovery I use, I can't flash any ROM. Both recovery tells me it was flashed, no error message (at least not at the screen) but every time it reboots to finish the installation, I see the Asus logo with a progress bar that goes from 0% to 100% in less then one second, and once it's filled, the tablet reboots itself and show me the regular boot screen with the Asus logo (again, the white one, not the silver-shiny).
So, resuming my problem, I can fastboot and adb shell it (adb only with ClockWorkMod Touch), but flashing doesn't seem to work. And I believe the internal memory/storage structure have been compromised.
How do I fix this?
Here is what I did to fix it
brbjr said:
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Click to expand...
Click to collapse
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
Man you saved my life. Thank you very much!
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Itege said:
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Click to expand...
Click to collapse
You're welcome!
Now click thank you so you can help me
I recommend you to use the CleanROM 2.5, it's stable and fast! Really fast! Faster then the ASUS Stock ROMs. I'm really enjoying it.
Still can't flash ROMs
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
poisondminds said:
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
Click to expand...
Click to collapse
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
allram said:
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
Click to expand...
Click to collapse
For CleanROM he'll need a specific TWRP version. It's better give CleanROM thread a read before install it.
allram said:
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Guticb said:
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Click to expand...
Click to collapse
1. Please, make sure the Tablet is the only one Android device connected to your computer
2. The bootloader is unlocked, right?
3. It's not the matter (almost impossible to be the case), but what are you using as recovery, TWRP or CWM?
4. Are you trying to flash the Official ROM?
- Sent from the Future, using my Delorean
- Enviado do Futuro, usando meu Delorean
mizifih said:
Originally Posted by brbjr View Post
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Quote:
Originally Posted by manegonzalez View Post
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
This is an awesome fix, thought I was buggered with a tablet that couldnt mount anything, couldn't get into download mode, recovery was fubared.. and then I stumbled on this
THANK YOU
I get this problem in y htc evo 3d when i open recovery it shows yellow exclamation mark i proceed with pressing volume up+power buttons. Then in bottom of the commands it says Can't open /cache/recovery/command. After i press begin update from external storage it says invalid operation. Success rebooting by reason oem_00. Help me please I tried to install other rom. It is unlocked S-ON non-rooted hboot 1.53.007 latest android 4.0.3
Help please! Need to install Custom ROM!
twingle said:
I get this problem in y htc evo 3d when i open recovery it shows yellow exclamation mark i proceed with pressing volume up+power buttons. Then in bottom of the commands it says Can't open /cache/recovery/command. After i press begin update from external storage it says invalid operation. Success rebooting by reason oem_00. Help me please I tried to install other rom. It is unlocked S-ON non-rooted hboot 1.53.007 latest android 4.0.3
Help please! Need to install Custom ROM!
Click to expand...
Click to collapse
In other words, you haven't installed a custom Recovery yet. Don't worry, at least you haven't bricked it like I did with my Old Epic 4G.
Here's what you have to do.
Download SDK-Tools. http://goo.gl/zmFNr
Move it to your C:\ directory (assuming that's you're on Windows otherwise I can't help), afterwards... unzip there.
Then, download TWRP, (this is from my own personal stash please don't go around distributing it) http://goo.gl/oeA2b
And take the "recovery.img" and put in your now unzipped SDK-Tools folder.
From here on out you're going to be using the command prompt to control your phone. Pray that you have Android Debugging checked on your phone, otherwise this probably won't work.
Go to the Windows flag on the bottom left corner, and type in "cmd" and hit enter.
Command prompt open. Time to get into SDK-Tools. From here on out I'll be using code to explain, it there's an extra space between a line, that means you have to hit enter.
Code:
cd c:\sdk-tools
adb reboot bootloader
fastboot flash recovery recovery.img
And there you have it, you've now flashed your recovery. You now have two options, you can reboot into the System (GUI, ROM, whatever you want to call it.)
Code:
fastboot reboot
(if that doesn't work, try "adb reboot" but I believe the first is correct)
Or you can now go to the recovery...
Code:
fastboot boot recovery recovery.img
That's it! Enjoy!
And when you eventually get the courage to obtain S-Off, check my signature. Make sure to thank Globatron when you're done!
thebeastglasser said:
In other words, you haven't installed a custom Recovery yet. Don't worry, at least you haven't bricked it like I did with my Old Epic 4G.
Here's what you have to do.
Download SDK-Tools. http://goo.gl/zmFNr
Move it to your C:\ directory (assuming that's you're on Windows otherwise I can't help), afterwards... unzip there.
Then, download TWRP, (this is from my own personal stash please don't go around distributing it) http://goo.gl/oeA2b
And take the "recovery.img" and put in your now unzipped SDK-Tools folder.
From here on out you're going to be using the command prompt to control your phone. Pray that you have Android Debugging checked on your phone, otherwise this probably won't work.
Go to the Windows flag on the bottom left corner, and type in "cmd" and hit enter.
Command prompt open. Time to get into SDK-Tools. From here on out I'll be using code to explain, it there's an extra space between a line, that means you have to hit enter.
Code:
cd c:\sdk-tools
adb reboot bootloader
fastboot flash recovery recovery.img
And there you have it, you've now flashed your recovery. You now have two options, you can reboot into the System (GUI, ROM, whatever you want to call it.)
Code:
fastboot reboot
(if that doesn't work, try "adb reboot" but I believe the first is correct)
Or you can now go to the recovery...
Code:
fastboot boot recovery recovery.img
That's it! Enjoy!
And when you eventually get the courage to obtain S-Off, check my signature. Make sure to thank Globatron when you're done!
Click to expand...
Click to collapse
Thank you very much for your tutorial, everything was very clear and I made everything easily. Now there's another, even funnier problem. When I am trying to access Recovery, it just reboots my phone? How can be this?
twingle said:
When I am trying to access Recovery, it just reboots my phone...
Click to expand...
Click to collapse
My only guess would be the recovery I sent you. It's for the Evo V 4G... which is essentially the same phone (same hardware, different software).
Try this one. http://goo.gl/PyVdR
It's TWRP 1.1.1 for the 3D, the official one. Let's see how this works... :fingers-crossed:
EDIT: Or, while you're in fastboot and bootloader is highlighted... http://goo.gl/SEh0o
Press the power button, then hit the volume rockers until Recovery is highlighted. Press the power button and that could work as well.
No, this also doesnt load. I think something can be wrong with cmd. Theres an error.
Code:
C:\Users\aser>cd c:\Android
c:\Android>adb reboot bootloader
error: device not found
c:\Android>adb reboot bootloader
error: device not found
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)...
OKAY [ 1.328s]
writing 'recovery'...
OKAY [ 8.887s]
finished. total time: 10.223s
c:\Android>fastboot boot recovery recovery.img
cannot load 'recovery'
c:\Android>
Everything what I do: I connect my phone, open fastboot(in bootloader) than in pc open cmd type everything what I should, when it is installed I reboot bootloader than open recovery... And BAM! HTC is loading to boot my phone, gets black screen (turns off) after a sec turns on . Also after it I tried doing Bootloader Reboot mannualy, I pressed to reboot the bootloader. The same happened.Thats all
Do you have USB debugging enabled?
For the record, the same thing happens with my device, but I have S-Off. There's nothing wrong with command, I can tell you that. But if you can flash the recovery, clearly something's going right.
What I'd recommend from this point, is rooting your phone and getting something that can put you into recovery. Be it ROM Manager, Goomanager or Quickboot, clearly it doesn't want to manually work.
Before I get into that though... you do have HTC Sync installed... correct?
thebeastglasser said:
Do you have USB debugging enabled?
For the record, the same thing happens with my device, but I have S-Off. There's nothing wrong with command, I can tell you that. But if you can flash the recovery, clearly something's going right.
What I'd recommend from this point, is rooting your phone and getting something that can put you into recovery. Be it ROM Manager, Goomanager or Quickboot, clearly it doesn't want to manually work.
Before I get into that though... you do have HTC Sync installed... correct?
Click to expand...
Click to collapse
Sure, USB debugging is always enabled! Yes i have installed htc sync. You think i need to delete it?
twingle said:
You think i need to delete it?
Click to expand...
Click to collapse
No, you certainly need it for this.
Clearly the conventional tactics are not going to work. I'm afraid you're going to have to go all out. This will be easily achieved if your computer can boot from a Live CD. (and when I say easily, I mean more easily than UnknownForce's method)
Go for this, it's the last piece of help I can get you. It'll also save you a lot of work in the long run.
http://forum.xda-developers.com/showthread.php?t=1563342
There you go. Go for it. :highfive:
KEEP IN MIND THIS ONLY WORKS IF YOU HAVE AN EVO 3D NOT AN EVO V 4G, AND MUST BE CDMA.
thebeastglasser said:
No, you certainly need it for this.
Clearly the conventional tactics are not going to work. I'm afraid you're going to have to go all out. This will be easily achieved if your computer can boot from a Live CD. (and when I say easily, I mean more easily than UnknownForce's method)
Go for this, it's the last piece of help I can get you. It'll also save you a lot of work in the long run.
http://forum.xda-developers.com/showthread.php?t=1563342
There you go. Go for it. :highfive:
KEEP IN MIND THIS ONLY WORKS IF YOU HAVE AN EVO 3D NOT AN EVO V 4G, AND MUST BE CDMA.
Click to expand...
Click to collapse
Thanks for your help. Mine phone is GSM, so this won't go. I realy want to install custom rom, but I am doing that too much (about 8hours of trying) and I didn't do it just only unlocked from htcdev.com
That is awkward, that only you try to help me, theres so many people in xda (45000) online. I unlocked my evo 3d, people say that it is enough to install other rom. I don't want to do the S-OFF because I think it will be the same and we need to find solution now. Its because I won't do the S-OFF, because to make it unlocked was hard, and to make S-OFF is 10x harder! I know that you know more than me, please help me!
To be perfectly honest, I have the CDMA version, so I don't necessarily know anything more than you... nonetheless, I'll do what I can. It seems with the GSM version, you may need to flash the whole .zip versus just the recovery.
Skip to 10:17.
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-htc-evo-3d-gsm/
Also, before I continue, you're on HBOOT 1.5.X... so we're working with a totally different creature right now. I could be wrong, as I've heard the HBOOT 1.4.X. for the GSM can flash just about anything using 4ext (an app) or by flashing the kernel in fastboot. But I don't know how that applies to HBOOT 1.5.X.
If that's true, you may want to get S-Off so you can flash an older bootloader, otherwise I don't know whether or not you can flash custom ROMs.
And for the record, I know what it feels like. I've had a bunch of questions in the past and gotten 1 or no people responding. If you can't get the answer here, keep in mind there are more forums than just this. Something I did not initially know.
For example... androidcentral.com androidforums.com (aka phandroid.com ) and more...
Try posting there too if this doesn't work. That way you'll get the maximum amount of help. Good luck...
By the way, for the record, if you'd like to get S-Off, you can through this... afterwards everything's going to be easier. I know you'd rather not, but nonetheless I'd recommend it. To be honest I thought the same thing before I did it...
http://unlimited.io/jb_shooteru.htm
Either way, good luck in your endeavors.
You know what? It worked! I did it yesterday. I thought it will not work, that I will be with stock rom forever . I followed a bit of that video and the only things that I needed were to unlock bootloader from htcdev.com, download 4ext recovery updater from 4ext.com and downloaded latest final version of 4ext. Than download 4ext recovery.img put in computer and do the work with cmd (fastboot) which was explained before. And install the rom . And also the problem was that I needed to flash custom recovery (4ext). I gave thanks to every post you posted. Thanks a lot to you for your big help :highfive:
Hey, no problem come back any time. Happy flashing.
Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.
i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.
Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!
Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.
just hold up like normal after
fastboot reboot
ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.
Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.
arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>
Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !
Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app
4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:
I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.