Related
Ok, here's the procedure for returning to stock S-ON after running revolutionary if required for warranty reasons.
Preparation
(Windows): Uninstall HTC Sync and any other sync software ( eg Androsync ) that you have been using.
(Windows) : Install these fastboot drivers
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
Download the RUU for your device
Download the downgrade hboot for your device:
Flyer downgrade hboot MD5SUM=6f82c00e2029c4bf3cb00e861789e2f8
View downgrade hboot MD5SUM=d3462b3587564db133c2215127485fe4
Check the mdsum of your download
Check the mdsum of your download
Reboot to to fastboot mode
Flash the downgrade hboot
Flyer:
Code:
fastboot flash hboot flyer_downgrader.nb0
View:
Code:
fastboot flash hboot express_downgrader.nb0
Run the RUU for your device
I can't use adb on recovery mode. Can you upload your fastboot driver?
buidung said:
I can't use adb on recovery mode. Can you upload your fastboot driver?
Click to expand...
Click to collapse
1. Yes, you can use adb in recovery mode if you followed the instructions correctly.
2. Done
an system's update
...can be installed if i use this procedure?
I get an error
C:\Users\Namit>fastboot flash zip RUU_Flyer_BrightstarUS_WWE_2.27.1540.31_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204116_signed.zip
sending 'zip' (500195 KB)...
OKAY [ 77.287s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 157.279s
Click to expand...
Click to collapse
EDIT1: Just moved the zip to sdcard as PG41IMG and went into bootloader. It is working right now; will report on results.
EDIT2: Worked! Flashed Radio and rebooted to finish the rest of the installation.
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
chong5379 said:
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
Click to expand...
Click to collapse
It is something like hboot_xxxxx.nb0
I try to flash the stock recovery by fastboot on my Htc View but not success. It shows "failed, signature .... Bla bla". My device is still s-on and hangs at htc screen. Hmm, I think its recovery partition was damaged and RUU can't overwrite another recovery.img on it. Can someone help me out ? Thanks
Namit1994 said:
It is something like hboot_xxxxx.nb0
Click to expand...
Click to collapse
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Hello there,
I'm really desperate as I have this problem and I hope someone could help me, I'd be really grateful.
My following problem is :
I have an HTC FLYER and I tried to flash a new hboot FROM HERE ( http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 ) but mistakenly it was from another device, now my FLYER wont turn on at all.
Can someone help me how to flash a new hboot so my device can finally power up ? Please I really need my HTC FLYER to start working.
I tried running ADB and "adb devices" but my device serial doesn't how in the list of attached devices and i don't know neither how to flash the new hboot through adb.
Please I'm really desperate, I hope someone can help me . I'm really afraid my Htc Flyer is dead.
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
hm
globatron said:
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
Click to expand...
Click to collapse
yes but its bought in sweden and now i live in balkans so no warranty for me and i was thinking if i can fix it with some box method like jtag jig?
I motion that this thread either be stickied or combined with the S-OFF sticky thread.
hboot_1.11.0003.nb0
chong5379 said:
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Click to expand...
Click to collapse
It was hboot_1.11.0003.nb0 in my case.
It can be either, mostly it will be .nb0 but it can be a .img. The important thing is that it is hboot not boot.
Where i can find RUU for my 3g flyer.
Now I use Leedroid rom i want to go back to official 2.3 to wail for official 3.2.
When or where?
Sent from my HTC Flyer P510e using xda premium
Where is can download RUU for my 3g flyer
^_^
I will correct my post
Thz
hi,
I updated to honeycomb using your method, but my tablet is now slower so I wanted to revert back to gingerbread.
The problem is I can't use ADB commands with it. It responds to fastboot commands but doesn't respond to adb commands. It shows: Error: device not found.
I have tried to put the rom.zip in the sd card, which seems to install gingerbread back, but it won't boot.
What can I do? I am desperate now.
Reflash honeycomb before you run out of battery
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
My phone was acting buggy with the radios and had HUGE performance issues. To be frank, i think a SNAIL was faster than this phone at the time... I am S-OFF, unlocked and i cannot flash recovery.
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
here is the current HBOOT Config and display:
Code:
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.0000
OpenDSP-29.1.0.45.622
eMMC-boot
Just for good measure i re-wrote the CID to 11111111 and locked and unlocked the bootloader again to no avail, thinking it was possibly that being unlocked during an RUU. The thing is, while unlocked, the RUU still processed... Oh and the phone boots up fully. i have ZERO issues with actually using the phone, but i cant believe i am stuck on a stock rom and not allowed to flash a custom recovery... >_>
Other thing... just to see if this would help, i used junkmail9's ENG HBOOT with the RegawMOD Customizer to flash the ENG hboot to try my luck. STILL no good. i can flash hboot directly, and whatever else, but is recovery just stuck??
i really want to be free again, so can someone please explain to me why after an RUU even WHILE S-OFF and unlocked, that i cannot flash recovery?
cyberkeeper1 said:
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
Click to expand...
Click to collapse
You did not mention either the recovery image you tried to flash, nor the command you used to try and flash it. There's no point in messing with bootloader lock/unlock if you're s-off. Just leave it alone.
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
cyberkeeper1 said:
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
Click to expand...
Click to collapse
alright, i am a dodo-bird... apparently, i really need glasses because i JUST noticed that i was flashing a zip file.... dang it... for whatever reason, it can flash zip files, but i guess i didnt have the right one. anyhow, no help needed now. Mods, you can close the thread... my apologies for the wasted space. If its any consolation, i havent really slept so.... yea. lol. thanks for the help thus far.
i wasnt flashing the IMG file like i should have been.
similiar issue
hello users of the almighty xda!
I have obtained s-off using dirtyracun and flashed between team venoms viper rom and cyanogenmod10.1 multiple times
this last time I tried to flash back to viper2.2.0 from cyanogenmod because of the problems with the m2 snapshot I wiped everything as usual including cache,data, and even a factory reset and installed the viper rom and said everything was good to go and now the phone wont boot past the htc screen
so I figured i'd reflash the viper boot.img to see if that would help and doesn't
not only will it not boot but when I go to the bootloader and try to enter recovery it flashes and I see the clockwork mod symbol and then it boot loops back to the htc logo endlessly
wtf! ugg! any ideas oh great xda users?
p.s im also under the impression that because im s-off I cant RUU back to stock is this the case?
styxking said:
im also under the impression that because im s-off I cant RUU back to stock is this the case?
Click to expand...
Click to collapse
This is not true. You may at any time run the RUU to restore borked programming. Besides, the dirtyracun method of flashing s-off is risky to say the least. I used facepalm s-off and it was stupid easy. Anyhow, run the RUU and then immediately run a factory reset. The RUU formats and repairs all partitions on the device and the factory reset restores the radio and baseband as described by mdmower.
Sent from my ADR6410LVW using xda app-developers app
Do the following to prepare for RUU-
Run these commands in order:
fastboot oem resetRUUflag (wait for reload)
Fastboot oem rebootRUU
Fastboot erase cache
Fastboot flash zip name_of_file.zip
Alternatively, you can run the automated HTC RUU utility, but it often fails vs. A manual reflash.
Sent from my ADR6410LVW using xda app-developers app
ignore please, came late and didnt notice
gonna try it
thanks for the response. I agree the dirtyracun method is pretty risky, but at the time I think it was the only s-off method I could find
well I will ruu then
thanks for the detailed fastboot commands and such
I don't have to relock the bootloader do I?
HTC preloaded some image files for the "stickers" in the duo effects camera. They are preloaded to /data/preload so you can either flash the zip at the bottom of the second post or manually copy them over to that directory. They (HTC) haven't fully implemented this yet... so you probably won't even notice them missing. The also preload calc and flashlight app this way too.
NOTE- This will work for S-on users provided their current software level is at or below this version. S-off users can user this either way.
OPTION 1)
Rename download file to 0P3PIMG.zip. Make sure you use an SD card formatted to fat32!! (otherwise the phone might not see it) Place file on physical SD card (not internal phone memory)... i repeat physical SD card. Boot up phone to bootloader mode and the phone will auto-detect the file and prompt to install it. Follow any remaining prompts to allow the RUU to flash the software to your phone.
-or-
OPTION 2)
Download file into working fastboot directory. Boot phone to fastboot mode and connect to pc. Type in the following commands.
fastboot oem rebootRUU
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
first time you run this it will be short... so run it a second time
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
The command prompt output will show you details as it flashes each partition and will show you when it has completed. At this time the green bar on the phone will appear 99% of the way across the screen.. Completely normal!~ Issue the next command to kick it out of RUU mode or optionally flash the custom recovery TWRP if you intend to root/flash custom roms and THEN issue the below command to get out of RUU mode.
fastboot reboot
(note) if you just want to reboot back to bootloader you can issue the command fastboot reboot-bootloader This will allow you to boot directly to recovery and start flashing/rooting fun.
I don't own this model phone... so if someone would like to capture the output of the command prompt I would be happy to add it to the OP similar to how I have my VZW ruu threads.
Downloads Do NOT mirror these elsewhere.
RUU Download link
https://www.androidfilehost.com/?fid=23622183712460121
Data preload apps/stickers
https://www.androidfilehost.com/?fid=23622183712460132
RUU Mode TWRP 2.7.1 (must be s-off or unlocked)
https://www.androidfilehost.com/?fid=23622183712460136
Getting error, too many links
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
martinoj2009 said:
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did your md5 check out fine?
dottat said:
Did your md5 check out fine?
Click to expand...
Click to collapse
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
martinoj2009 said:
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
Click to expand...
Click to collapse
Do you have an sd card to try it via option 1?
dottat said:
Do you have an sd card to try it via option 1?
Click to expand...
Click to collapse
I'm sure I do, I'll let you know, and thanks for the prompt reply!
martinoj2009 said:
I'm sure I do, I'll let you know, and thanks for the prompt reply!
Click to expand...
Click to collapse
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
dottat said:
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
Click to expand...
Click to collapse
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
martinoj2009 said:
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
Click to expand...
Click to collapse
How long did it take to run the zip?
dottat said:
How long did it take to run the zip?
Click to expand...
Click to collapse
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
martinoj2009 said:
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
Click to expand...
Click to collapse
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
dottat said:
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
Click to expand...
Click to collapse
Lol, shhhh, forgot to S-Off
martinoj2009 said:
Lol, shhhh, forgot to S-Off
Click to expand...
Click to collapse
OK... so if you aren't S-off AND this firmware is older than what you have it will fail. Only S-off can downgrade. You guys don't have a newer RUU yet and there were two OTAs after this one. Definitely S-off that thing while you still can (assuming it's not too late).
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
mido.fayad said:
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
Click to expand...
Click to collapse
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
dottat said:
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
Click to expand...
Click to collapse
Yes I know that I should be s-off
And that's why I said I should downgrade first to sense 5.5 firmware then flash the ruu
And I won't be able to downgrade without s-off
So I was writing only about the error when I already have a-off because it took me 2 days till I found this fix after many trials
posted a current RUU for s-off users here...
http://forum.xda-developers.com/htc...rint-ruu-3-02-651-5-s-off-pre-rooted-t2865704
i have some troubles here
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
w1n73rf3ll said:
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
Click to expand...
Click to collapse
IF sunshine doesn't work on your current rom (have you tried running it yet).... you need to unlock your bootloader and flash a 100% stock older rom. Then use that to s-off. Then flash whatever rom you want and sim unlock.
I successfuly rooted , Cyanogenmod 10.2.1-dlx. It was a stumbly road for me, fully grasping the steps (which now, i get it), S-off, waeksauce, SU, then the ROM.
my issue: after S-off, weaksauce, and SU, i was rooted, able to use the great apps etc, and had my stock - still tuned as it was before. was GREAT. none of that required a FULL wipe of my apps and data. Then i flashed Cyanogenmod, and as great as much about it is, (i had it years ago on HTC Incredible) there are a few issues that i CANNOT stay with.
Gmail account contacts / sync is all kinds of screwed. (not worried about cus all backed up and will get resolved)
My MHL adapter - usb misco to HDMI adapter - not supported
The HTC stock camera i LOVED. slow motion video camera i NEED. I hate the cyanogenmod camera. my instagram - www.instagram.com/benjamin.blue
and other(s) i forget this moment.
point is, can i uninstall the ROM and go back to the previous state of ROOTED stock, as oppposed to starting from scratch? and if i have to start from scratch, kindly point me towards quickest steps. If thats the case, i WILL now backup everything via titanium backup AND MyBackup Pro.
guessing i could use the backups i SHOULD have in CWM recovery, assuming i made one pre-cyanogenmod, and pretty sure i get md5 errors trying any restore.
thanks for patience - i have indeede googled like hell before making this post, on top of many full nights of brain implosion.
ben
EDIT - see next post - all i want is to unroot completely.
http://forum.xda-developers.com/showthread.php?p=48250930
You must wipe data and cache when changing ROMs. App backup apps can cause some issues, so restore wisely.
Sent from my One using XDA Free mobile app
i have been searching far and wide and am desperate to get my DNA back to stock, so i can activate it and use it again. i am trying every bit of sense and good advice and tutorials and my brain is just exhausted. i know i can get this, i just need a little help.
i have relocked it, and followed the instructions for running the RUU - RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed - exactly, and keep getting ERROR 155.
one thing i notice is during the RUU, it says going "from image" "to image" the from is blank. i click update ROM, it fills the "to" field with the RUU, 1.15, and, it runs for a minute ish and i get ERROR 155. Thanks guys I am really having a tough time.
i just tried again with new download of RUU. same results.
bluedimensional123 said:
i have been searching far and wide and am desperate to get my DNA back to stock, so i can activate it and use it again. i am trying every bit of sense and good advice and tutorials and my brain is just exhausted. i know i can get this, i just need a little help.
i have relocked it, and followed the instructions for running the RUU - RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed - exactly, and keep getting ERROR 155.
one thing i notice is during the RUU, it says going "from image" "to image" the from is blank. i click update ROM, it fills the "to" field with the RUU, 1.15, and, it runs for a minute ish and i get ERROR 155. Thanks guys I am really having a tough time.
i just tried again with new download of RUU. same results.
Click to expand...
Click to collapse
Why did you relock it?
Why didn't you just flash a stock rooted rom and be done with it?
probably because i didnt realize what i could or couldnt do along the way. i'm pretty noob and created a mess, a phone that boots up, into cyanogenmod, but will not activate. now i just need to get to square one.
Since you flashed cm, then your stock ROM was overwritten unless you made a backup. You'll probably have to reflash a stock from and setup everything again.
orangechoochoo said:
Since you flashed cm, then your stock ROM was overwritten unless you made a backup. You'll probably have to reflash a stock from and setup everything again.
Click to expand...
Click to collapse
i'm ok with that - exactly what i'm attempting.
this is what you were referring to, right? http://forum.xda-developers.com/showthread.php?t=2017525.
doing that i keep getting ERROR 155, searching what that could be. (now if i boot to CM recovery, files are missing, telling me the RUU install may have begun to overwrite files...but doesnr get too far.
by stock ROM you meant RUU as mentioned in thread above, right? as opposed to adb sideloading a zip ( "reflash a stock rom?")
im not sure where i went wrong, and at this point all i want is to get my dna to be able to be activated and have cell service working. (currently it boots up into CM, verizon tries to activate it, says it looks right on their end, i receive their test text, but, dialing anything, i get "mobile network unavailable.) so you can see, being not too apt in all this, there may be more than one way to get where i need. whether back to total stock, or able to activate in its current state - i'll take it.
i hope that all makes sense, i'm so appreciative for any of you guys' help.
The thread you referred to is to ruu (return to completely stock). If you can boot into CM, then do that and download Santods stock ROM in the development section. Then go into recovery and flash it.
orangechoochoo said:
The thread you referred to is to ruu (return to completely stock). If you can boot into CM, then do that and download Santods stock ROM in the development section. Then go into recovery and flash it.
Click to expand...
Click to collapse
Will try that for sure. I am still preferring to RUU and I keep getting the ERROR 155 - if can run that I can be at square one which is OK . I will try your suggestion though.
bluedimensional123 said:
Will try that for sure. I am still preferring to RUU and I keep getting the ERROR 155 - if can run that I can be at square one which is OK . I will try your suggestion though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2570548
That ruu zip should work if the exe is giving you trouble. Be warned: ruu will wipe the internal SD, so back everything up before flashing the ruu.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
http://forum.xda-developers.com/showthread.php?t=2570548
That ruu zip should work if the exe is giving you trouble. Be warned: ruu will wipe the internal SD, so back everything up before flashing the ruu.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
i tried and the results, of That ruu zip, and notice failing t the end..
fastboot oem rebootRUU
fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 35.228s]
writing 'zip' ...
(bootloader) rom parsing start
(bootloader) rom parsing finish
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
Finished. total time 41.495s
fastboot reboot
i'm grateful and still need direction. desperately. at this point happy to flash to stock. thanks guys. after that process it boots right back into cyanogenmod, nothing stock..
bluedimensional123 said:
i tried and the results, of That ruu zip, and notice failing t the end..
fastboot oem rebootRUU
fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (920285 KB)...
OKAY [ 35.228s]
writing 'zip' ...
(bootloader) rom parsing start
(bootloader) rom parsing finish
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
Finished. total time 41.495s
fastboot reboot
i'm grateful and still need direction. desperately. at this point happy to flash to stock. thanks guys. after that process it boots right back into cyanogenmod, nothing stock..
Click to expand...
Click to collapse
That will happen and continue to happen, if the firmware on your device is newer then that of the RUU.
If you can downgrade your firmware, then you may stand a chance of flashing that old RUU.
But since you have relocked, I'm not sure you can.
I know you have to at least be s-off to downgrade, maybe unlocked bootloader isn't needed.
But I think that it may be. Good luck. :good:
If it were me, I would go back to unlocked and s-off.
Then flash latest firmware and rooted stock rom and be done with it.
thank you so much for the last few suggestions, i'm just wanting my phone back to stock i'm losing my mind.
could any point me to the way to downgrade my firmware to successfully run the old RUU?
Ive tried running the new RUU and i, as above, get ERROR 155. excuse my noobness, the help is great.
if i cant get this thing back to stock, so i can activate it - my goal - im gonna shell out the $100 and get insurance replacement. this is too complicated, but im not giving up.
thanks
ben
should running the newer RUU possibly finish installing? have tried but will again.