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....
Related
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?
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
My name is David, I'm a noob, and I need help. I rooted my EVO3D about a year ago. Until yesterday, things were great. I used the HTC unlock method originally. For at least the past six months I've been running Scott's Clean Rom Gingerbread Reborn with no issues. Over the past two or three weeks, my phone has been rebooting itself in the middle of phone calls. I decided it was time to upgrade to a different ROM in hopes of correcting the issue. I chose the RC2 version of Scott's Clean Rom ICS. I used the app Flash Image GUI to flash the Kernel, and then flashed the ROM using Revolutionary. The ROM booted up, installed an update, and rebooted the phone. The system reloaded, and within 5 seconds rebooted again. The system kept rebooting each time after reloading. I tried a recovery to my Gingerbread ROM, but that ROM would no longer load either. I tried flashing a Team 420 ICS ROM as well as a MEANROM ICS ROM, and they were both rebooting just like the Clean Rom did, loading for about 3 seconds then powering down the phone. I even used the superwipe program as suggested by MEANROM and that didn't help. I'm out of ideas. Do you guys have any suggestions? Here are my specs:
HBOOT-1.50.000 S-ON
Revolutionary CWM v4.0.1.4
I've wiped the memory, cache, dalvik, even repartitioned my memory card. Nothing has helped.
I would suggest you to follow this guide and get s-off. will also update you to the latest ics firmware and newer radios
http://forum.xda-developers.com/showthread.php?t=1889438
EM|NEM said:
I would suggest you to follow this guide and get s-off. will also update you to the latest ics firmware and newer radios
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Thank you for the advice. I'm trying to work through the directions and get to s-off, but I'm already hitting a road block. The first thing the thread tells me to do is to lock the boot loader, which my phone apparently will not allow me to do. I have updated all of the necessary software on my PC so that I can connect to the bootloader, and I have achieved fastboot USB connection according to my device. However, when I execute the command "fastboot lock oem", the command prompt tells me "< waiting for device >". I wonder if this could be the result of a bad boot image? To some degree, the ROM's and kernels have worked, with the system simply rebooting after a few moments of operation.
davidmech21 said:
Thank you for the advice. I'm trying to work through the directions and get to s-off, but I'm already hitting a road block. The first thing the thread tells me to do is to lock the boot loader, which my phone apparently will not allow me to do. I have updated all of the necessary software on my PC so that I can connect to the bootloader, and I have achieved fastboot USB connection according to my device. However, when I execute the command "fastboot lock oem", the command prompt tells me "< waiting for device >". I wonder if this could be the result of a bad boot image? To some degree, the ROM's and kernels have worked, with the system simply rebooting after a few moments of operation.
Click to expand...
Click to collapse
Connecting to the device in "fastboot usb" mode does not depend on the boot image or anything other than the bootloader (hboot), and should work with any hboot. Try issuing the "fastboot devices" command and if you don't get a response with your serial number, starting with an "HT", you are not properly connected to the phone.
See the tips for Step1 and the post here, which is linked after Step3 of that guide, for additional tips for troubleshooting RUU.exe problems.
ramjet73
ramjet73 said:
Connecting to the device in "fastboot usb" mode does not depend on the boot image or anything other than the bootloader (hboot), and should work with any hboot. Try issuing the "fastboot devices" command and if you don't get a response with your serial number, starting with an "HT", you are not properly connected to the phone.
See the tips for Step1 and the post here, which is linked after Step3 of that guide, for additional tips for troubleshooting RUU.exe problems.
ramjet73
Click to expand...
Click to collapse
EM|NEM and Ramjet73, thank you so much for the help. I finally got the fastboot to connect correctly. I was able to lock the bootloader as outlined, and install the RUU. Now I'm on to the next steps of S-OFF. I cannot thank you guys enough. EM|NEM, I see your donate button, and the goods are coming. Ramjet73, do you also have a button?
David
I really didn't do it for donations my friend. Just glad you got it to work
Sent from my Evo 3D GSM
I suggest all of the above.
Also, try to flash the rom before the kernel. This may solve your issue.
Hey guys, I need to return my phone to verizon because of a simcard/PUK lock error. I'm on the current OTA update (2.06) but still unlocked, rooted and S-off. I need to go back to bone stock if possible. Can I still follow the guide in this thread to go back to stock??
http://forum.xda-developers.com/showthread.php?t=2017525
Anyone?
scheirere said:
Anyone?
Click to expand...
Click to collapse
You don't have to relock your phone all you have to do is flash the ENG Bootloader then you can run the RUU. Make sure you have all the drivers you need installed first or it WILL fail.
ENG Bootloader:
http://forum.xda-developers.com/showthread.php?t=2156713
Also this won't take away your S-Off the only way to get to S-On is by running a special command. Once S-Off always S-Off.
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
scheirere said:
zone23,
Thanks a million! One more question....I'm not familiar with RUU. Do you have a link to were I might find that file?
Thanks again,
Eric
Click to expand...
Click to collapse
Yes try here:
http://forum.xda-developers.com/showpost.php?p=37277937&postcount=66
Oh and don't forget to hit thanks on that post.
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
scheirere said:
Ok, now I'm a little confused. I downloaded both files. The modded ENG bootloader and the RUU zip file from the links. But what order. Sorry but I'm not familiar with this stuff and don't want to dig myself into a deeper hole by bricking this thing.
Is this the proceedure?
1. adb reboot bootloader
2. fastboot oem rebootRUU (using the RUU_DLX_WL_JB_45.exe file?)
3. fastboot flash zip ModdedPL832IMG.zip
Anything else I'm missing? Also, what drivers? The same ones I installed when I rooted the phone?
Thanks in advance guys!
Click to expand...
Click to collapse
This first:
1. adb reboot bootloader
2. fastboot oem rebootRUU
3. fastboot flash zip ModdedPL832IMG.zip
4. Profit
making sure that the .zip is in the same folder as fastboot
then run the RUU after you reboot the phone.
Yes it should be the same drivers you used when rooting.
Looks like I spoke too soon on those downloaded files. The download of the RUU file bombed out on me and I didn't realize it. When I go back to the site in the link, and try to download the file now, it just sits waiting. I guess the site is down? Any other links or locations?
Downloads working now maybe keep trying they say they are under a DDOS attack. Here it is from hotfile but I can't confirm this as real.
HERE
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
scheirere said:
OK, I got partway thru the steps. everything went well until I tried to fastboot flash the ModdedPL832img file. I get a message "writing 'zip'....FAILED (remote not allowed)"
Any ideas/suggestions?
Click to expand...
Click to collapse
After step 1, but before step 2, do this:
fastboot devices
If you don't get a device id, then you don't have the proper drivers installed.
If you get a device id, then try step 2 again ...
If that doesn't work, then I don't know
Maybe try a different USB port on your computer also use the OEM cable if you can.
Thanks guys for the suggestions. Unfortunately, still no luck. Same results when flashing the Modded file. I did try adb devices as suggested and got the device ID. So I think the drivers are OK. I also tried another USB port just to see if it helped. No go.
Just because I'm pretty new to this stuff, here's a detailed list of what I'm doing.....
1.) ADB reboot bootloader (from a command prompt)
Phone reboots to bootloader screen with Fastboot USB in red, hightlighted.
The screen no longer displays the "TAMPERED" heading at the top. So it looks like I'm making some progress.
2.) fastboot oem rebootRUU (from a command prompt again)
Phone screen goes from white to black with nothing but a large HTC logo in white.
Nothing else happens at this point. I've let the phone sit for 30 minutes with no apparent change and nothing on the host PC.
I then went thru my computer to the directory were the RUU_DLX.... file resides and executed (double clicked) it. I get an RUU - InstallShield screen and then I go thru the HTC rom update utility steps. After a few steps the utility does it's thing and the phone then reboots.
3.) ADB reboot bootloader again
Phone reboots into bootloader screen
4.) fastboot flash zip ModdedPL832IMG.zip (from a command prompt)
Phone does nothing but the command screen returns:
sending 'zip' (485 KB)...OKAY [ 0.266s]
writing 'zip'...FAILED (remote: not allowed)"
pretty much immediately
Am I doing this correctly?
At this point the bootloader screen no longer says tampered. Can I just relock the bootloader so it's s-on again?
BTW, here's what the bootloader screen shows:
*** UNLOCKED ***
MONARUDO PVT SHP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Or can I just send the phone back as it is?
Bootloader uses a different driver than ADB. My advise is to boot into the bootloader then verify in device manager that the driver is loaded. See attached. Flashing the RUU will not get you S-On you need a command to do that and I don't know what it is off the top of my head I have never used it.
hello every one, like alot of you guys i was stuck on white HTC Screen and only able to get to HBOOT and Fastboot, after a lot of Effing research over google and xda, almost a month an a thousand post with the same problem Finally Solved-it!!! im pretty sure it will work on your forgotten devices soooo. first of all i didnt uploaded the file just find it messing arround the web so all tanks go for those who uploadit.
an some months after a friend let me his phone with similar problems and got solved the same way.
booth phone were with lastest HBOOT 2.28.!! aln lastest radio.!
Attention.!! Im not responsable for any more DAMAGE or/if it can happen even if you have your phone already briked.. so play responsable..!!
ok. let me be a bit clear, i've got 2 diferent rezound with similar problems and booth got solved the same way
phone 1: Only showed white htc boot logo, and also onle let me acces hboot and fastboot, no recovery(custom or stock).NO BOOT.
phone 2: showed white htc logo,hboot,fastboot and also recovery but it was giving me emmc error an couldnt acces to any partition.
you will need some knowledge in FASTBOOT.!!! look for help over the web.!
STEP BY STEP GUIDE:
1)Fully Charge your Battery.!
2)Download this file-----> it have Hboot 2.28 and Radios 2.23 at: http://d-h.st/BIj http://d-h.st/BIj place it in your Fastboot folder.!
3)open CMD with Administrative Permitions(right click run as administrator)
4)cd to fastboot folder
5)put device in Fastboot mode(turn on pressing power + vol.down, then select fastboot).
5.1)if hboot unlocked relockit with fastboot oem lock, will reboot phone and show RELOKED.
6)run: fastboot oem rebootRUU. phone will reboot again and show Black Screen with HTC.
7)run: fastboot flash zip Firmware.zip (firmware.zip should be the file you downloaded in step 2!).
8)if everything goes well you will see a green bar moving on your phone and fastboot should start working and showing some files flashing i dont know hahaha.
9) wait it takes about 5 mins. when your cmd window shows that it finish, your phone will still have a green bar on it. just run
fastboot reboot
and the magic its done.!! wait other five mins for the phone to boot and start messing with it again.!!!
will attach a picture with my cmd windows if someone got lost.!try to figure them out hahah those are the things i saw all my files were on downloads but i already have fastboot preinstaled.
as i said before i hope this mini tutorial works for you guys. it will be cool if people in the forum put this as stickie.!! i've seen like a 1000 post with the same problem.!!
have fun.!!
Be VERY careful if you have custom recovery installed (TWRP/CWM/PhilZ/AmonRa), locking or re-locking the bootloader well S-ON can result in a hard brick situation.
acejavelin said:
Be VERY careful if you have custom recovery installed (TWRP/CWM/PhilZ/AmonRa), locking or re-locking the bootloader well S-ON can result in a hard brick situation.
Click to expand...
Click to collapse
In my situations one never entred in recovery and the other one didnt show any problem.
acejavelin said:
Be VERY careful if you have custom recovery installed (TWRP/CWM/PhilZ/AmonRa), locking or re-locking the bootloader well S-ON can result in a hard brick situation.
Click to expand...
Click to collapse
I know but this is the only solution ive founde wirh my two problems and i think theres nothing to loosenif your phone is already bricked trust me ive try everything with these phones
inchewazu said:
I know but this is the only solution ive founde wirh my two problems and i think theres nothing to loosenif your phone is already bricked trust me ive try everything with these phones
Click to expand...
Click to collapse
I'm not knocking your procedures or process... What I am saying is that if you have custom recovery installed and you relock, there is a definite potential for hard brick, if you are going to relock well S-on with custom recovery, there is a real possibility of bricking... One should flash stock recovery via fastboot prior to relocking.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I'm not knocking your procedures or process... What I am saying is that if you have custom recovery installed and you relock, there is a definite potential for hard brick, if you are going to relock well S-on with custom recovery, there is a real possibility of bricking... One should flash stock recovery via fastboot prior to relocking.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
well i guess you'r right so hope that doesnt happens to anyone around, well by the way probably no one uses this phone any more but tanks for pointing that important info.