How can flash rom ruu.exe whithout any error
i have xl and original rom is 1.06.707.1
but my curremt rom on my xl is custom rom 1.05.401.4
when i run ruu.exe 1.06.707.1 coming error !!!
conclude:
if current rom is any custom rom ...
1- must flash rom zip 1.06.707.1 ... with fastboot oem lock
2- then (if necessary) run ruu.exe , without any error ...
that is correct ?!
When flashing back to stock you must use the same as the original rom, because stock roms are region specific, whereas custom roms are different and you must relock your bootloader to be able to flash a stock RUU
Related
Is it possible to make s- off with hboot 1.16 with 2.3.3 STOCK OPTUS ROM?
If so, can anyone link me to a proper guide?
I searched and found contradictions, some say yes, some say no....
LOSTLOGIC89 said:
Is it possible to make s- off with hboot 1.16 with 2.3.3 STOCK OPTUS ROM?
If so, can anyone link me to a proper guide?
I searched and found contradictions, some say yes, some say no....
Click to expand...
Click to collapse
There is no current method available to truly gain S-OFF status with HBOOT 1.16. However, that being said, you can use the HTCDEV site to unlock HBOOT 1.16 so that you can flash a custom recovery such as ClockworkMod and then flash a custom ROM. The thing to keep in mind with this solution is after you flash the custom ROM you will probably have to manually flash the boot.img file from the custom ROM using 'fastboot flash boot [path to image file]\boot.img'
There is also some thread posts about downgrading HBOOT 1.16 to HBOOT 1.13 and then you can use Revolutionary to get a true S-OFF HBOOT.
tpbklake said:
There is no current method available to truly gain S-OFF status with HBOOT 1.16. However, that being said, you can use the HTCDEV site to unlock HBOOT 1.16 so that you can flash a custom recovery such as ClockworkMod and then flash a custom ROM. The thing to keep in mind with this solution is after you flash the custom ROM you will probably have to manually flash the boot.img file from the custom ROM using 'fastboot flash boot [path to image file]\boot.img'
There is also some thread posts about downgrading HBOOT 1.16 to HBOOT 1.13 and then you can use Revolutionary to get a true S-OFF HBOOT.
Click to expand...
Click to collapse
I see, i will give it a try .
Thanks.
tpbklake said:
There is no current method available to truly gain S-OFF status with HBOOT 1.16. However, that being said, you can use the HTCDEV site to unlock HBOOT 1.16 so that you can flash a custom recovery such as ClockworkMod and then flash a custom ROM. The thing to keep in mind with this solution is after you flash the custom ROM you will probably have to manually flash the boot.img file from the custom ROM using 'fastboot flash boot [path to image file]\boot.img'
There is also some thread posts about downgrading HBOOT 1.16 to HBOOT 1.13 and then you can use Revolutionary to get a true S-OFF HBOOT.
Click to expand...
Click to collapse
i unlocked my hboot 1.16 with htc dev and downloaded 4ext recovery. How can i flash it ?
EDIT: Never mind, i found out how.
So basicly now i can flash any rom i want ?
LOSTLOGIC89 said:
i unlocked my hboot 1.16 with htc dev and downloaded 4ext recovery. How can i flash it ?
Click to expand...
Click to collapse
Unzip the EXT4.zip file and extract the recovery.img file to your PC. Then with your phone connect to the PC in FASTBOOT mode, type the following command:
fastboot flash recovery [path to your image file]\recovery.img
The command window on your PC should have the working directory set to where you have installed the Android SDK tools with adb.exe and fastboot.exe.
tpbklake said:
Unzip the EXT4.zip file and extract the recovery.img file to your PC. Then with your phone connect to the PC in FASTBOOT mode, type the following command:
fastboot flash recovery [path to your image file]\recovery.img
The command window on your PC should have the working directory set to where you have installed the Android SDK tools with adb.exe and fastboot.exe.
Click to expand...
Click to collapse
Ok i have it installed.
The problem now is i wiped and installed a custum rom (bliss with sense 3.5) and got a stock on htc then tried to go on fastboot usb then flash the img file and still stock at htc. Any ideas?
Edit: never mind forgot to wipe boot.works like a charm thanks again .
http://forum.xda-developers.com/showpost.php?p=20795908&postcount=1
I'm on this page and it's telling me to download the RUU for my device, but I don't know which one to download. I'm on AT&T and I was on stock ICS before I loaded a custom rom.
Okay, Download this RUU (PM Me for the link, unable to post)
Relock your bootloader using fastboot commands "fastboot oem lock" then go into hboot < fastboot < plug in usb < run ruu it will make everything stock once that is finished if you want to install a new custom rom unlock bootloader again < install a recovery < flash a kernel "boot.img" < install custom rom
Need Anymore Help PM Me
Thank you, helped me unbrick one of my vivid's
Nikolas0418 said:
Okay, Download this RUU (PM Me for the link, unable to post)
Relock your bootloader using fastboot commands "fastboot oem lock" then go into hboot < fastboot < plug in usb < run ruu it will make everything stock once that is finished if you want to install a new custom rom unlock bootloader again < install a recovery < flash a kernel "boot.img" < install custom rom
Need Anymore Help PM Me
Click to expand...
Click to collapse
Initially I was running stock froyo 2.2.1 and 2.28xxx Radio and it was running fine with the below mentioned hboot info
my bootloader info is something like
Blackrose
vivo pvt ship s-off rl
radio-3805.04.03.27_m
eMMC-boot
june 02 2012. 00:00:54
I then flashed a different radio version (corresponding to Froyo ROM) but after that It continously boot loop .
I can only enter into hboot and fastboot etc menus but cannot go to recovery anymore. when i go to recovery it again starts boot loop.
I unlocked and s-offed hboot an year back and i hardly remember those methods and my memory card is changed recently.
I tried flashing recovery using fastboot but problem persists. Still no recovery.( previously ClockwoodMod )
I have stock rom backup so once i can get into clockwood recovery i can restore those settings. Please help me out Guys . I did a huge mistake coming into custom roms after 1 year . lost all info .Now i'm pretty confused with all those terms and methods.
The only option is to flash recovery image. This is the reason you are not able to get into recovery.
What is the command you are using to flash recovery image?
Try to flash recovery image again.
Don't worry your phone is not bricked.
Sent from my HTC Incredible S using xda app-developers app
@di said:
The only option is to flash recovery image. This is the reason you are not able to get into recovery.
What is the command you are using to flash recovery image?
Try to flash recovery image again.
Don't worry your phone is not bricked.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
1.on a freshly installed win 7 - 64 bit
2.installed java working
3.installed android-sdk installer_r20.0.3-windows.exe
4.opened sdk manager and installed platform tools
5.downloaded cwm recovery image and placed it in the platform tools folder
6.open cmd and inside platform tools folder
7.conned htc in fastboot mode and it showed fastboot usb after connecting
8.i typed follwing commands
fastboot flash recovery cwm-4.0.1.4.img
sending ' recovery ' <3700 kb>....
OKAY [1.150s]...
writing 'recovery'...
OKAY [0.799s]...
finished total time 1.947s
the fastboot usb in mobile stayed the same and i rebooted into hboot and went recovery . It rebooted into htc logo and boot loop continous . dint see any recovery. Where have i done wrong ? .. do i need any specific HTC Incredible S drivers for the PC ? ... what should i do now ? ...otherwise can i flash any ROM directly from fastboot usb mode ?
Thank you very much bro .. please help me out ..
What is your hboot version? 2.02.002?
Did you try flashing boot.IMG also?
If not then try that also...
Sent from my HTC Incredible S using xda app-developers app
@di said:
What is your hboot version? 2.02.002?
Did you try flashing boot.IMG also?
If not then try that also...
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
yes hboot version is 2.02. and which boot.img ? i dont get u .. of any ROM ?
Try a more recent recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
and erase cache in fastboot
Code:
fastboot erase cache
Nonverbose said:
Try a more recent recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
and erase cache in fastboot
Code:
fastboot erase cache
Click to expand...
Click to collapse
i tried the recent recovery image too but still it boots the moment it shows HTC logo( 2 secs logo and boot ) ... going to recovery after flashing also does the same boot loop. Do i need any adb drivers to detect vivo specifically ? .. i installed htc sync but dint connect vivo after that (when incS was actually working ).
also flashing boot.img from backed up froyo rom says FAILED writing. Battery is draining out on the otherside . It goes to boot loop when i charge it switched off too.
BTW Like i said I was running froyo stock rom which was also restored from backup but when i flashed the Radio maybe md5 or something dint match up and the firmware got corrupted . there's any bruteforce method to flash a custom or stock ROM or RUU ? ... I tried flashing nik_auro sense _4a ROM in fastboot usb but it says FAILED writing ! ... Can i solve this ? or my device is gone forever ?
I flashed boot.img of the backed up clockworkmod backup (froyo)
fastboot flash boot boot.img
it says
OKAY
Writing 'boot.img'
Finished.
Then i flashed recovery again
it says OKAY
Writing
Finished.
But same problem no difference.
BTW Everytime the usb is connected while booting up and al ... Windows 7 says USB driver not recognized ... ?? but flashing actually shows in cmd and hboot !!
You should install the driver correctly. Install htcsync and then uninstall it. Try flashing the recovery again. If that doesn't work, go into fastboot mode and type
Code:
fastboot getvar all
and post result here minus imei and serial number so we can get an ruu for you to flash.
boot loop
1.Exact boot loop time from vibration : 5 secs
2.i removed and reinstalled HTC Sync application but then it says
It popped up " HTC Sync Driver installed " when I went to Fastboot USB mode first time but also says
"USB Device not recognized . one of the USB devices attached to this has Malfunctioned . click for assistance " when connected in HBOOT mode as well as normal boot loop.
3.Tried flashing latest CWM recovery again and boot.img of backed up file. but still no difference .
4.IMEI and serial u mean the one in this below screenshot right ?
5.Previously i was on Codename Jellybean ROM and it worked fine then i wanted to get back to stock so i restored previous stock back up and it worked fine too and when i flashed this Froyo radio after which this problem started ( last froyo radio in the list )
Radio : From the 1.47.1400.3 RUU:
20.28.30.0802U_38.04.01.07
md5: eb83213f5a093a7baf7571409c9c2498
other info:
Blackrose
HBOOT 2.02.0002
Radio - 3805.04.03.27_M
jun 02 2012
I sent you PM, but it's nice to know that most problems connected to recoveries, boot.imgs and permissions get fixed with RUU. Of course it's easiest for s-off users (Revolutionary and BlackRose) cause all they need is to run RUU, and their phone will stay s-off and hboot won't be touched. For Alpharev and HTC unlocked users it's a bit different, Alpharev will lose their s-off cause hboot will be overwritten, and HTC unlocked have to relock their bootloader before RUU.
After successful RUU:
-S-off user have to flash recovery via fastboot
-HTC unlocked, so as Alpharev, have to unlock bootloader again (Alpharev for the first time) and flash recovery
The rest is magic...
Also, remember that flashing Froyo radio can cause you leaving with an expensive construction material (a hard brick)...
EDIT:
As I understood the last RUU is the same for all regions (same ruu.exe inside package One_Generic_code_Vivo.zip), so no need for gold cards anymore and the rest is handled with RUU itself. I already experienced that with Desire's 2.3 RUU.
n4naveen said:
1.Exact boot loop time from vibration : 5 secs
2.i removed and reinstalled HTC Sync application but then it says
It popped up " HTC Sync Driver installed " when I went to Fastboot USB mode first time but also says
"USB Device not recognized . one of the USB devices attached to this has Malfunctioned . click for assistance " when connected in HBOOT mode as well as normal boot loop.
3.Tried flashing latest CWM recovery again and boot.img of backed up file. but still no difference .
4.IMEI and serial u mean the one in this below screenshot right ?
5.Previously i was on Codename Jellybean ROM and it worked fine then i wanted to get back to stock so i restored previous stock back up and it worked fine too and when i flashed this Froyo radio after which this problem started ( last froyo radio in the list )
Radio : From the 1.47.1400.3 RUU:
20.28.30.0802U_38.04.01.07
md5: eb83213f5a093a7baf7571409c9c2498
other info:
Blackrose
HBOOT 2.02.0002
Radio - 3805.04.03.27_M
jun 02 2012
Click to expand...
Click to collapse
The last official Rom you had installed on your phone was not froyo, that may be why you're getting bootloops. You're actually extremely lucky you didn't get bricked but it seems only the phones shipped with gingerbread have that issue. Your main version shows you had a HK 2.3.3 ruu installed but that doesn't match your cid (india). Do you have a goldcard?
Try flashing a gb radio. That will likely fix your issue.
Here's the ruu matching your main version. http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_189979_signed.exe
Nonverbose said:
The last official Rom you had installed on your phone was not froyo, that may be why you're getting bootloops. You're actually extremely lucky you didn't get bricked but it seems only the phones shipped with gingerbread have that issue. Your main version shows you had a HK 2.3.3 ruu installed but that doesn't match your cid (india). Do you have a goldcard?
Try flashing a gb radio. That will likely fix your issue.
Here's the ruu matching your main version. http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_189979_signed.exe
Click to expand...
Click to collapse
Main version shows HK because i might've installed it before jellybean version or i also flashed GB boot.img after boot loop problem .
India is correct . My original ROM came with mobile is froyo in india .I have the back up of this Froyo ROM but dont know the exact RUU details . I have goldcard but it was made with another SDCARD dont know if that works with new SDCARD ...
Is it ok to flash this rom in fastboot usb mode for my mobile ?
ROM : HTC RUU Latin american version 4.14.405.2 ? ( it has file named One_generic_code_viva.zip) actually i need asia RUU but that link has incomplete file.
Mobile details : http://dl.xda-developers.com/attach...f7c459e3/50857d5a/1/4/1/9/7/4/1/vivo-info.jpg
I tried to flash HTC Canadian RUU(one_generic_code_vivo.zip ) in fastboot usb since i required asian RUU was a broken file in the link. ROM Update utility started , it identified my firmware version/ hboot so on .. like something like 2.12.xx to update latest 4.14.x so on .. but when i started to flash .. it started to show progress bar 1% .. but then immediately it changed to ----sending--- Bar(on PC) ......... (on mobile screen it showed HTC with black background without any progress bar ) it kept showing sending for 30 mins then i removed it and nothing flashed . same boot loop yet. any comments ? ... do i have to lock bootloader before flashing stock RUU ?... or can i flash a custom ROM ? ... I've no idea whats going on .. this is my device info http://www.4shared.com/photo/bgN6aHfQ/vivo-info.html?
It doesn't look like you flashed the gb radio like I suggested. Or even the ruu that I linked. You cannot flash a Canadian ruu because of the fact its a different model id.
Nonverbose said:
It doesn't look like you flashed the gb radio like I suggested. Or even the ruu that I linked. You cannot flash a Canadian ruu because of the fact its a different model id.
Click to expand...
Click to collapse
How am i supposed to flash the RUU which u gave ? cos none of these methods work ...
from PC in fastboot usb ... The rom update utility keeps showing sending ........ and on mobile HTC black screen logo without a progess bar .. i waited for 30 mins.
I made PG32IMG.zip and added my CID in android-txt file and placed it on SDCARD ... in Hboot mode it loaded the file ... showed parsing--for 1/10th of a sec and gone and the red progress bar dint appear. and the writing dint happen.
I extracted the rom.zip from RUU and flashed in fastboot flash zip file-name.zip . it says sending....and then stopped REMOTE : not allowed !
I also fastboot usb flashed 3805.4.03.27 radio of GB of my main version ... says the same error REMOTE : not allowed !
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
nlooooo said:
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
Click to expand...
Click to collapse
Not entirely true but thanks anyway.
boot loop
nlooooo said:
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
Click to expand...
Click to collapse
I flashed the Latest GB Radio . says REMOTE : NOT ALLOWED)
I flashed CUstom ZIP nik_rebirth says REMOTE : NOT ALLOWED
it pretty much says the same except for cwm backed up boot.img
I flashed boot.img and it was written !!
I also changed modelid , cidnum , mainversion hbootpreupdate values same as my device details before flashing some GB radio and latest generic rom.zip but all it says is REMOTE : NOT ALLOWED !!
commands im using
fastboot flash zip PG32IMG.zip
fastboot flash zip rom-name.zip
fastboot flash boot boot.img
other conditions :
Cable is not the one provided by HTC
battery is around 10% now 3722mV
sdcard is not the goldcarded sdcard but i have the goldcard file with me.
below are the images before applying Blackrose HBOOT and running GB successfully
Hi. I seek for guide on how to backup my HTC One stock firmware.zip and stock recovery.img
I have two HTC One phone:-
Phone A - unroot, KitKat stock ROM
- S-ON
- Locked
- Firmware: 4.20.707.6
- Hboot 1.56
- CID: HTC__044
- MID: PN0710000
Phone B - rooted, KitKat stock ROM
- S-Off
- Unlocked
- Firmware: ***
- Hboot 1.56
- CID: HTC__044
- MID: PN0710000
***Phone B has messed up firmware. Software firmware showing version 4.20.707.6 while running "getvar all" showing firmware 2.24.707.1.
I'm unable to find the KitKat stock firmware and stock recovery for this phone model.
I'm planning to return Phone B to unroot stock ROM state.
My questions:-
1) How to backup firmware.zip from Phone A to flash it into Phone B?
2) How to backup recovery.img from Phone A to flash it into Phone B?
3) Is stock recovery.img universal? Can i just get stock recovery.img for KitKat from any CID/MID version and flash it to Phone B to return it to stock ROM state?
Appreciate if someone could answer this. TQ.
mi
padey88 said:
Hi. I seek for guide on how to backup my HTC One stock firmware.zip and stock recovery.img
I have two HTC One phone:-
Phone A - unroot, KitKat stock ROM
- S-ON
- Locked
- Firmware: 4.20.707.6
- Hboot 1.56
- CID: HTC__044
- MID: PN0710000
Phone B - rooted, KitKat stock ROM
- S-Off
- Unlocked
- Firmware: ***
- Hboot 1.56
- CID: HTC__044
- MID: PN0710000
***Phone B has messed up firmware. Software firmware showing version 4.20.707.6 while running "getvar all" showing firmware 2.24.707.1.
I'm unable to find the KitKat stock firmware and stock recovery for this phone model.
I'm planning to return Phone B to unroot stock ROM state.
My questions:-
1) How to backup firmware.zip from Phone A to flash it into Phone B?
2) How to backup recovery.img from Phone A to flash it into Phone B?
3) Is stock recovery.img universal? Can i just get stock recovery.img for KitKat from any CID/MID version and flash it to Phone B to return it to stock ROM state?
Appreciate if someone could answer this. TQ.
Click to expand...
Click to collapse
I think a guru reset will work for your phone 2.
http://www.htc1guru.com/downloads/stock-rom-downloads/
Iwould find the newest one available for your cid and model id, since that phone is s-off you can downgrade firmware. Leave it s-off
mb_guy, appreciate your response.
Yes, Guru Reset M7 2.24.707.1 will do but i need to manual update to 3.63.707.3 then manual update to 4.20.707.6.
I just wonder how someone shared the stock firmware.zip and stock recovery.img online and what method they used to backup those files.
Now i have a new question:-
I've download OTA_4.20.707.6-3.63.707.3.zip files and found there's firmware.zip (4.20.707.6) inside.
Also there's recovery.img inside firmware.zip.
Can I used this firmware.zip and recovery.img to flash to Phone B to revert to stock ROM, Firmware & Recovery?
padey88 said:
mb_guy, appreciate your response.
Yes, Guru Reset M7 2.24.707.1 will do but i need to manual update to 3.63.707.3 then manual update to 4.20.707.6.
I just wonder how someone shared the stock firmware.zip and stock recovery.img online and what method they used to backup those files.
Now i have a new question:-
I've download OTA_4.20.707.6-3.63.707.3.zip files and found there's firmware.zip (4.20.707.6) inside.
Also there's recovery.img inside firmware.zip.
Can I used this firmware.zip and recovery.img to flash to Phone B to revert to stock ROM, Firmware & Recovery?
Click to expand...
Click to collapse
I think the firmware and recovery may flash, but you will have no ROM
mb_guy said:
I think the firmware and recovery may flash, but you will have no ROM
Click to expand...
Click to collapse
I have twrp stock rom backup. Just need the correct firmware and recovery img. I'll try and see if it works.
Hi, it is possible to to flash stock recovery and get LOCKED flag together ?
If I will use htcguru tool to LOCKED flag i must have twrp recovery, but if I LOCKED bootloader then will be problem with install stock recovery ?
If I install stock recovery first it will be will be unable to use guru tool?
I got S-OFF and tried to use "fastboot oem LOCK", but recieve ***RELOCKED*** flag...
deejay89 said:
Hi, it is possible to to flash stock recovery and get LOCKED flag together ?
If I will use htcguru tool to LOCKED flag i must have twrp recovery, but if I LOCKED bootloader then will be problem with install stock recovery ?
If I install stock recovery first it will be will be unable to use guru tool?
I got S-OFF and tried to use "fastboot oem LOCK", but recieve ***RELOCKED*** flag...
Click to expand...
Click to collapse
use the guru bootloader tool to set back the bootloader to locked and then pack your stock recovery image in a firmware.zip file with an android-info.txt file that match your phone info. flash the firmware.zip in ruu mode.
alray said:
use the guru bootloader tool to set back the bootloader to locked and then pack your stock recovery image in a firmware.zip file with an android-info.txt file that match your phone info. flash the firmware.zip in ruu mode.
Click to expand...
Click to collapse
due to "orangb10" cid I've got only nandroid backup, because is no ruu from polish orange........ so can I put recovery to nandroid backup folder and then restore firmware ?
@edit: I put recovery to nandroid backup folder but it doesen't work..
deejay89 said:
due to "orangb10" cid I've got only nandroid backup, because is no ruu from polish orange........ so can I put recovery to nandroid backup folder and then restore firmware ?
@edit: I put recovery to nandroid backup folder but it doesen't work..
Click to expand...
Click to collapse
The only way you can flash the recovery partition with a locked or relocked bootloader is by using a firmware.zip file in RUU mode
so like I said, pack your recovery.img and your android-info.txt file in a firmware.zip and flash it in RUU mode (require s-off)
Code:
fastboot oem rebootRUU
fastboot flash firmware.zip
fastboot flash firmware.zip
fastboot reboot-bootloader