hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
chemicalinferno said:
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
Click to expand...
Click to collapse
Not many of the technical people have unlocked their devices uses the htcdev.co method, most of us have used the revolutionary method was it was released first and seems to unlock more of the device than HTC does.
With that said, based on your above command and error message it would appear the bootloader is not unlocked. Are you sure the HTCdev.com method worked properly?
The only other method for loading a custom recovery, which could work using the HTCdev method would be through ROM Manager in normal android mode, or using my application, Flash Image GUI.
Both these methods just mentioned will require the recovery partition write access to be allowed while booted in normal android mode. This is definitely accomplished with the revolutionary s-off method, but I'm not 100% sure the HTCdev method allows this. If the HTCdev method does not allow recovery write access from normal android mode, then the worse that will happen is the application will say it flashed correctly, but it will not have worked.
Keep us updated as I'm curious how much write access the HTCdev method provides to the internal partitions... hope that helps!
chemicalinferno said:
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
Click to expand...
Click to collapse
Did you happen to skip step 17 prior to flashing recovery by chance?
"Step 17. Put your Evo 3D in fastboot mode by first going to Settings->Power and make sure "Fast boot" is checked off. (Again, yes)."
rleonard55: when i went to turn off the fast boot option I found that it was still off. So i just continued on with the process. I don't know if that has anything to do with the error I had or not.
joeykrim: I know my device is unlocked because when i load it in hboot mode it says unlocked at the top. However I don't know if it was unlocked properly. It may bmhave been an error in my process so I'm gonna try it from the start again. If that doesn't work I will be researching the other methods you mentioned and then proceeding with them.
I also realized I did not have usb debugging mode on So I'm gonna check if that changes anything. I appreciate both of you helping me with this issue. Thanks!
ok so i have tried relocking my device and then unlocking it again and i came out with the same result. i was going to try the GUI app you suggested but you need root access to use it which i do not have. i am trying to root my device through this method which requires cwm recovery. could i possibly temp root my device and then install the recovery through android mode that way? or would that risk bricking my device? also if i can go the temp root method in your application should i have the clear the cashe and dalvik cashe options checked or not?
looking forward to hearing from you
SOLVED!!!!
ok so i figured out exactly what was going wrong. it was a very specific issue. after you have unlocked the device and you are about to flash cwm you must load up hboot (power, vol down) then BEFORE pressing any buttons you must plug in your usb cable. THEN go to fastboot and press power to select it.
the order i was doing it in (hboot, fastboot, then usb cable) was causing the issue because when i did it the other way it flashed with no problem.
thank you for your help and thanks for the app i will definately be using it
chemicalinferno said:
ok so i figured out exactly what was going wrong. it was a very specific issue. after you have unlocked the device and you are about to flash cwm you must load up hboot (power, vol down) then BEFORE pressing any buttons you must plug in your usb cable. THEN go to fastboot and press power to select it.
the order i was doing it in (hboot, fastboot, then usb cable) was causing the issue because when i did it the other way it flashed with no problem.
thank you for your help and thanks for the app i will definately be using it
Click to expand...
Click to collapse
wow! frustrating it was such a small step but definitely good to know. i have a feeling you won't be the only person running into that issue.
thanks for posting back your solution and glad everything is working now!
Yeah no problem glad no one else will have to go through that.
I did run into one other issue or a possible issue. After I installed my root it gave me an "error code:0" now I do have root but I'm questioning if its a full root. I don't know what stuff is specifically locked by HTC's unlock method so I've just been researching to see what I can find out. All I know is in the video I watched his Su install continued doing different installations where mine stopped. I'll figure out what's going on eventually but if its a known issue that has a solution it would definately save me some time.
this is the official error i got
creatng SYSTEM:xin/su symbolic link...
E:error in /sdcard/su-2.3.6.3-efgh-signed.zip
(status 0)
installation aborted
dont know if it matters or not it was the very last step in the root and like i said i have root access. thanks in advance for any response
and yet again SOLVED! lol you just have to install it 3 times in a row
CWM
@ chemicalinferno.
I tried the method of loading hboot first that worked for you but sadly didn't work for me . Any other suggestions?
This may sound like a way off question, but did you unlock using revolutionary or HTC? If HTC when the option to unlock your device appeared (lock screen where you select yes/no) did your phone reboot or did you have to take out the battery?
Thanks
UPDATE: Soooo ****ing weird. I had been trying to get cwm to flash for have the day yesterday (5 hours)
I went to this sight here: http://forum.xda-developers.com/showthread.php?t=1239821
and tried this method. It also wouldn't work. Went to bed at 3 am this morning, woke up at 9:30 this morning. Sat down, looked at the screen, typed in the adb commands and low and behold **** started working??? I didn't do anything different than I did yesterday. But hey, I'm rooted with SU.
Craziest thing every.
chemicalinferno said:
and yet again SOLVED! lol you just have to install it 3 times in a row
Click to expand...
Click to collapse
Hey, I was reading your post and I'm still stuck not able to get past the "fastboot flash recovery cwm-4.0.1.4-shooter.img" step. I'm trying to do exactly as you. Can you tell me exactly what you did that im still stuck as it is stuck in sending 'recovery' <4832 KB>.... and wont do anything else. You are right this is frustrating
IM STUCK IN A BOOT LOOP AND WHEN I TRY TO FLASH FROM FASTBOOT IT GIVE ME AN ERROR WONT LET ME FLASH cwm img FROM FASTBOOT ??? PLEASE ADVISE IM hboot 1.50 AND ext4 RECOVERY BUT MY RECOVERY GOT MESSED UP SO IM TRYING TO FLASH cwm.img FROM FASTBOOT SO I CAN FLASH A KERNNEL AND GET BACK GOING THANKS
I had updated my HTC Evo 3D OTA from 2.3.3 to Android 4.0.3 software version 3.28.707.1 then unlocked it using HTC Method. Unlock success than I flashed recovery with CWM Shooter. Flash success but when I load recovery, the phone just boot up normally. CWM screen not loaded to load custom ROM.
Option 1. ROM Manager says:
You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instruction to root your phone.
Option 2. Superuser apps says:
su binary not found
Option 3. SuperOneClick v2.3.1
Stuck at Step 7. No respond at all.
And, at the command "CheckIfRooted" my device gave result 'false'.
I already tried USB debugging mode, and flash with other .img with other version of CWM. Still not working. Is there any other method to gain superuser access?
Related
All I can see is the HTC logo with 4 ! inside of a triangle on each corner. This is a been bricked for a long time and I cant remember how it happened but just wonder is there is anyway to fix it
Thanks,
The state your phone is in sounds similar to this
http://forum.xda-developers.com/showthread.php?t=824290
but there is no way to be sure of that, based on the zero details you provided.
Read the ENTIRE POST, not just part of it (it is quite long).
WOW, exactly the same problem this phone has!
If I remember right it was a mix up with ClockworkMod recovery.
That was a very nice recovery, I will have to read and learn all that. That's a lot of info and stuff that I will have to learn to try to fix this phone.
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
stick2e said:
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
Click to expand...
Click to collapse
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
bftb0 said:
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
Click to expand...
Click to collapse
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
stick2e said:
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
Click to expand...
Click to collapse
Well, first off - you should say what version of the boot loader you have. It is shown on the fastboot screen. If you already have the 1.49.2000 S-OFF bootloader this current step can be skipped, And you can proceed directly to flashing a recovery using fastboot from the pc. If you do not have the S-OFF bootloader the whole point of this current step is to get it on the phone - in which case you should be using the ROOT PB00IMG.ZIP file, not the Leak-V3 PB00IMG.ZIP file.
All Eris RUU and PB00IMG.ZIP files can be found at:
http://forum.xda-developers.com/showthread.php?t=909921
When the RUU program is running, just prior to the moment when you would begin flashing to the phone, you use the search function on your PC in the folder
C:\Documents and Settings\<your_user_name>
(Edit - in Win7, C:\Users\<your_user_name> )
to look for the file named "rom.zip". (You will probably need to twiddle the dumbass Microsoft setting which prevents searching for hidden files and folders.)
Then, you delete the rom.zip file, rename the ROOT PB00IMG.ZIP file to rom.zip, and drop it into the same location.
Before starting this step, make sure your phone is completely charged and also be sure to verify the file size and md5 checksum of the ROOT PB00IMG.ZIP file you downloaded.
As I mentioned above if you already have the S-OFF bootloader present on your phone, this operation is not necessary and we can proceed to flashing a recovery using the fastboot program on the PC.
Lemme know how it goes.
PS - It would be helpful for you to answer a few questions about your current skill set and computer setup:
- have you used either the "fastboot" or "adb" programs in the past on your pc?
- if not, do you know how to verify communication with the phone in fastboot mode?
(Note that running the RUU utility will install drivers on your PC)
The original Amon_RA recovery for the Eris can be found here:
http://forum.xda-developers.com/showthread.php?t=648025
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
stick2e said:
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
Click to expand...
Click to collapse
"fastboot devices" when the phone is in fastboot mode.
adb only applies when the normal OS is running with USB debugging turned on, or if the Amon_RA recovery is booted.
What bootloader version do you have?
This is where the phone is right now.
1.49.0000 S-ON bootloader
When I get home today I will look for the proper img file and try the RUU option to see if I can get the S-OFF in there. We will see.
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot, then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
PS - don't let the phone sit in fastboot mode for extended periods of time - it will discharge rapidly even if it is plugged into the charger
This thread honestly scares me and I hope this never happens to me lol
willwgp said:
This thread honestly scares me and I hope this never happens to me lol
Click to expand...
Click to collapse
All you need to remember is this:
newb + Eris + ClockworkMod = disaster waiting to happen
In almost every bricking that has been reported here on the (XDA) Eris forums, ClockworkMod (or running the battery down to very low charge levels) was involved.
What is also notable is that in almost every case, the folks that got into trouble:
- got their rooting instructions from non-XDA sites (e.g. unrevoked, z4root, unlockr)
- could not clearly explain what they had been doing immediately prior to the event - even after repeatedly being asked to do so,
- were unaware what ROM signing is about (or that ClockworkMod doesn't perform it)
The second observation seems to imply a behavioral trait of innattention or sloppiness.
In the hands of people that are experienced, ClockworkMod seems to behave correctly.
For the moment though, let's stay on topic and see if we can revive stick2e's phone. At the moment, I am guessing that there is about a 30% chance of that. We'll find out more when we hear the result of his/her flashing attempt.
bftb0
I think this is going to work!!!! Thinks are looking better.
I try to flash the RUU but replace the rom.zip (what a pain to find it!!!) with the root rom (PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and now I have to load a rom in the sdcard to flash the phone. Fingers crossed we will see.
I'm downloading a ROM now.
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
stick2e said:
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
Click to expand...
Click to collapse
DId you rename the new PB00IMG.zip file to rom.zip?
bftb0 said:
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot,
Click to expand...
Click to collapse
Ok, HBOOT-1.49.2000 and S-OFF
bftb0 said:
then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Click to expand...
Click to collapse
C:\sdk\tools>fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... OKAY [ 0.826s]
writing 'recovery'... OKAY [ 1.357s]
finished. total time: 2.183s
bftb0 said:
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
Click to expand...
Click to collapse
RUU Utility report ERROR [110]: FILE OPEN ERROR
Parsing... [download ZIP]
[1] User Data - OK
[2] System - Fail-PU
[3] Recovery - OK
[4] Radio_V2 - OK
[5] Boot - Fail-PU
Partition update fail!
Update Fail!
Gimme a minute to fire up a real computer instead of this stupid phone browser.
Well, I fastboot recover revery-RA-eris-v1.6.2.img but nothing happen now :-(
Before used to take me to RA Recovery but now is not.
New to android. Using a MAC to unlock, root and install senseless ICS. I've unlocked the bootloader via htcdev. Everything worked and now shows unlocked. I downloaded amon ra version 3.11 and installed with this command:
./fastboot flash recovery recovery.img
It seemed to work:
sending 'recovery' (4124 KB)...
OKAY [ 0.908s]
writing 'recovery'...
OKAY [ 1.265s]
finished. total time: 2.173s
When I go back to the fastboot menu and select recovery it goes to the white HTC screen and freezes. At least I think it freezes. Waited 10 minutes and it didn't do anything. I am trying to root the phone now. It looks like I should be able to root by booting into recovery, go to developer and install su. I may be wrong though. Can someone help me with this? I've searched everywhere and there's not a lot of help on using a MAC. My phone boots normally if I don't go to fastboot.
Hey, man I know that its a pain because most people here don't use Macs, or the ones that do have iPhones or whatever but I feel your pain. I'd start from scratch and follow this post from start to finish. I did it and it worked fine.
A couple of notes that you should be careful of:
1. When copying the token identifier from your phone, do not copy the INFO text at the beginning of each line
2. At the end of the process it shouldn't reboot to HTC logo but back into the Hboot screen and say S-off at the top. (If it hangs anywhere after successful completion, try a battery pull and then reboot into hboot)
3. If you got there safely, boot back into your stock rom, and follow this post to flash custom recovery (choose AmonRa NOT cwm).
4. After you flash recovery, flash Super User (non-eng) from within Amon Ra (again follow directions from the post!) and then reboot and you should be perm root. Download Titanium Backup to test and back up your crap before flashing roms or something.
That's how I got mine going from my unibody macbook pro running Lion. Good luck my fellow mac-tard! (I say that with love )
mrmadrid said:
2. At the end of the process it shouldn't reboot to HTC logo but back into the Hboot screen and say S-off at the top. (If it hangs anywhere after successful completion, try a battery pull and then reboot into hboot)
Click to expand...
Click to collapse
I think you meant to say that the phone will say "unlocked" at the top, not S-off.
feralicious said:
I think you meant to say that the phone will say "unlocked" at the top, not S-off.
Click to expand...
Click to collapse
Yep Un-Locked on the top left corner.
are you typing this exactally?
./fastboot flash recovery recovery.img
If so that may be your problem, recovery.img should be whatever the recovery file name is.
I was using the latest amon ra recovery and it wasnt working. I used an older version and it worked. Been running scotts senseless ics for 2 days now. Working very well.
If you want to avoid this issue in the future, don't buy a Mac lol
Sent from my ADR6425LVW using Tapatalk
Hello all,
First post, excuse my ultra noobishness. I was attempting to restore my evo to factory settings so I could take it back to the Sprint store(aware they probably can still tell since I have hboot 1.5, but still worth a try). Tried using the following instructions, bricked it when I typed "fastboot OEM unlock" into CMD. Phone has been in a constant loop around the white bootscreen, adb won't recognize my phone, and I'm not sure how to use fastboot effectively but the commands I've been trying aren't working. If anyone could guide me in the right directions, or if I need to provide additional details. Also- I was running a custom rom, (VIPER ROM) I think before all this happened.
Thanks!
update: fastboot commands don't work
I tried issuing the following command into fastboot "fastboot boot recovery img" this is the result...
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [1.210s]
booting...
FAILED <remote:not allowed> // <-- I keep seeing this! Also with ADB
finished. total time: 1.210s
Thanks again for any help
Your phone isn't bricked, if it was bricked you wouldn't be stuck in a bootloop. Your phone would not come on at all if it were bricked. What you could try is running an ruu to see if it will help since you were trying to do a factory restore already.
#Root-Hack_Mod*Allways\
Releif
You just saved me a lot of heartache, thanks!
No prob man we've all been there. Hope you get back up and running. If you need anything else just post.
#Root-Hack_Mod*Allways\
bhujwala said:
Hello all,
First post, excuse my ultra noobishness. I was attempting to restore my evo to factory settings so I could take it back to the Sprint store(aware they probably can still tell since I have hboot 1.5, but still worth a try). Tried using the following instructions, bricked it when I typed "fastboot OEM unlock" into CMD. Phone has been in a constant loop around the white bootscreen, adb won't recognize my phone, and I'm not sure how to use fastboot effectively but the commands I've been trying aren't working. If anyone could guide me in the right directions, or if I need to provide additional details. Also- I was running a custom rom, (VIPER ROM) I think before all this happened.
Thanks!
Click to expand...
Click to collapse
Your not bricked man. A brick is a dead phone when you relock it wipes the recovery.. You need the latest RUU exe 2.17 and you will be set since your CDMA....
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0
Hi all, been ages since I've been here,
I picked up a google nexus one off a friend that appears to have a corrupt recovery. (fastboot, bootloader, everything works fine) but as soon as recovery is selected, It will launch into a screen with a multi-colored cross icon and a unlocked padlock at the bottom and won't go any further... This is the same screen it will go to if booting normally.
I've tried;
re-unlocking the phone
rooting using superroot
flashing several different new recoveries (RAs, CWMs)
erasing cache
tried erasing existing recovery but get access denied error ;
erasing 'recovery'...
Permission denied
FAILED (remote failure)
etc..
But I cannot get passed this screen when it's supposed to be going into recovery so I can flash a new rom..
Few questions;
Is there any hope for this phone? or is it bricked?... Can I flash a rom without using recovery?
Thanks in advance for any help or advice, be cool to get this phone working again, Happy to provide any info or do anything you suggest
Just just booting one of those recoveries
fastboot boot recovery.img
But I would consider blackrose s-off, see the developer threads in the nexus one section
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for the reply, i've tried just straight booting one of those recoveries using fastboot but still to same screen, Here's a pic
i42.tinypic.com/2wnu0ch.jpg
Will look into blackrose s-off thanks for the pointer, I am a total noob with phones, android and such, and any help or tips is appreciated!!!
Tried Blackrose S-OFF, not working the output is below, I am not sure if Debugging is enabled on the phone; and I am unable to enable it as I can't get into the phone's settings
EDIT;
So i've tried installing Blackrose S-OFF (My device is S-ON even though being *** UNLOCKED *** and superrooted) maybe this is my trouble. Am having a little trouble getting it to S-OFF any help would be appreciated,
Here's the command outputs from my efforts both auto and manually;
tinypic.com/r/2d2awid/5
tinypic.com/r/2afg610/5
Ok so blackrose successfully installed, used the go2.lol exploit, and even though I couldn't see recovery or anything when that launched I was able to flash hboot successfully. Phone is now S-OFF!! yay
Unfortunately.. There's still no recovery (the open padlock symbol has disappeared) but I'm still left with a Cross every time i try to go into recovery.
I assume with s-off i'll be able to try some of the things that weren't working before (from other threads), like erasing recovery before flashing etc. But would appreciate it if someone could point me in the right direction
Thanks!
Triple post even!! (sorry mods!) But worth it !!! Finally fixed it.
I followed this guide;
http://forum.xda-developers.com/showthread.php?t=1312540
Installed stock, now it boots fine into stock, flashed new bootloader (cwm), sim works fine, no issues whatsoever. fixed phone. Now onto cyanoagen! THANK YOU XDA!!
Glad it all worked for you, tried responding this morning but tapatalk must have failed me!
For newer ROMs be sure to see requirement for partition sizes and always make a backup, best of luck to you!
Sent from my Nexus 4 using XDA Premium 4 mobile app