Thought I would try to upgrade Android from 2.3.5 to 4.0. HTC said it would work...
I've now got it stuck, though and can't move on. I do not own a Windows computer (I'm on Ubuntu).
What I did
I unlocked the phone using HTC's website tools. It uses adb, and you have to send some key to them and they generate an unlock code for you which you then do: fastboot flash unlocktoken Unlock_code.bin
I downloaded the RUU (RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068) from HTC.
Try 1: OpenRUU
I extracted the rom.zip file by using Wine, then searching on rom.zip. I moved it to ~/rom.zip
I then tried running the OpenRUU scripts which failed on attempting to flash (and failed on the automatic reflash attemtp, too):
sending 'zip' (410735 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
Try2: using hboot
I then tried with the hboot script. This is not for the "desire S" and has the wrong code in for the renamed rom.zip file. I then tried manually putting rom.zip, renamed as PG88IMG.zip into the root of the SD card as clearly summarised at (1)
I booted up into fastboot and the phone opened the zip file but then said "Wrong zipped image!".
Try3: using WinXP in VirtualBox
I then tried to run the RUU exe file in an XP VirtualBox VM. To do this I enabled USB devices for the phone (i.e. added filters for it both in fastboot and android modes), installed the stuff (HTC Sync) and tried running the RUU file.
It keeps saying "error 170 usb connection error". I've tried with the phone turned on (normally) and plugged in via USB, in charge only, Disk Drive and in USB debugging modes. I've also tried with the phone in fastboot mode. I always get this error.
...disable VirtualBox's USB2.0 support
Then it's able to connect to the phone. It ran all the way through the update process except that (a) there was never a progress indicator on the phone itself, (b) at the end it gave an 155 "image error". The recovery process then didn't really relate to anything I could see on the phone. The phone is again back in a2.3.5, so at least not bricked.
Trying to re-lock bootloader...
Then I thought that maybe the bootloader should be locked again (step 11 at (2)) - I had skipped this step before because I thought "I've just UNlocked it, why would I now want to RElock it?". But this won't work either! In fastboot mode, from a terminal, I type
Code:
$ fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Protocol error))
then the phone reboots itself, and it still shows unlocked. My fastboot screen (in case it's useful) says:
Code:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 20111, 15:22:13
HBOOT
Can anybody help?!
Links: (1), (2) : see pastebin dot com slash 1wKTF8Am (I am not allowed to post links here)
Rename rom.zip to PG88IMG.zip (not .jpg) then put on the root of ur sdcard (not in any folder) then boot into bootloader, it should find it
jmcclue said:
Rename rom.zip to PG88IMG.zip (not .jpg)
Click to expand...
Click to collapse
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.
I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
(yes, you flash it twice - it asks you 'please flush[sic] image again immediately' because it's upgrading your hboot)
obviously, replace YOURRUUZIP.zip with the zip file you extracted (e.g. PG88IMG.zip)
From the looks of your errors, though, it looks like your zip is simply corrupt...?
shinyblue said:
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.
Click to expand...
Click to collapse
What error exactly? What does it say?
Aquous said:
I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
Click to expand...
Click to collapse
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Aquous said:
From the looks of your errors, though, it looks like your zip is simply corrupt...?
Click to expand...
Click to collapse
Could be but I don't think so. I've extracted it twice, once under Windows and once under Wine and the md5s are the same. I have no way of testing the integrity of the file I downloaded since htc don't apparently provide any hashes, but I would think that the .exe file probably checks its own integrity before running.
Thanks anyway! it looks like I need to re-lock it as a first step, maybe.
jmcclue said:
What error exactly? What does it say?
Click to expand...
Click to collapse
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png
shinyblue said:
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png
Click to expand...
Click to collapse
and is the PG88IMG.zip on the root of ur sdcard? im guessing not coz that green writing comes up every time u enter bootloader. make sure the PG88IMG.zip is NOT inside a folder
EDIT: heres a wee guide my mate wrote, its for the htc desire but its the exact same method.
PG88IMG Method
jmcclue said:
and is the PG88IMG.zip on the root of ur sdcard?
Click to expand...
Click to collapse
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.
shinyblue said:
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.
Click to expand...
Click to collapse
Oh rite. Must be corrupt download id say, coz it should work. When u downloaded the ruu, was there a md5 next to the download? If so, check it, make sure it matched, if not then try re download the ruu and try again.
Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.
shinyblue said:
Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.
Click to expand...
Click to collapse
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.
jmcclue said:
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.
Click to expand...
Click to collapse
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands
turekk said:
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands
Click to expand...
Click to collapse
Haha what a tit i am.
I know that u need to be s-off, cant believe i forgot, what a noob. I even made 16 hboots for the desire and 4ext recovery this way. Hope thats the last noobie moment for the year :sly:
shinyblue said:
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Click to expand...
Click to collapse
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?
Aquous said:
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?
Click to expand...
Click to collapse
Maybe, but I think VirtualBox was working fine (e.g. HTC Sync worked).
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
I have been in touch with HTC directly (they told me initially the 4.0 upgrade was available), but they now say that this won't work with my phone.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Thing is, I don't want to risk bricking the phone by trying to get S-OFF and forcing the update because handsets are expensive! I've given up on this project for now...
Thanks to all for the help and advice.
shinyblue said:
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
Click to expand...
Click to collapse
Nope, all it does is this:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Click to expand...
Click to collapse
My phone wasn't WWE either and that was no problem for me.
Aquous said:
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
My phone wasn't WWE either and that was no problem for me.
Click to expand...
Click to collapse
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html
shinyblue said:
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html
Click to expand...
Click to collapse
Yeah it was a DS. The article you link to even mentions that flashing a WWE RUU should always be possible: 'Everyone can de-brand his device easily by flashing a stock system image' (although, that sentence continues, that will make you unable to receive carrier OTAs, but that doesn't matter for our device)
Can I confirm that
Aquous said:
Code:
fastboot flash zip YOURRUUZIP.zip
Click to expand...
Click to collapse
means the whole RUU.zip as downloaded from HTC, or the rom.zip as extracted from running the .exe file within the downloaded RUU?
And also, http://www.htc1guru.com/2013/09/new-ruu-zips-posted/ says "You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first."
AFAICS the RUU I have downloaded has a different CID so won't work. Also my bootloader is unlocked (and the oem lock command fails, as mentioned above). (And I'm S-ON.)
Related
Ok im not sure where to start but anyway
i have the vodafone ireland htc sense and few months back i rooted the phone but didnt change the stock mod.
every so often updates came out and i didnt update cuz it wouldnt allow me it would give me that error with the android fella and i would have to do something to fix it i forget what.
anyway
so last night i wanted to install THIS ROM (black forest)
http://forum.xda-developers.com/showthread.php?t=1423684
it said i needed to update the firmware and then thats when it went into a bootlooping
i fixed the eventual bootlooping but formatting just about everything but i backed everything up when i mounted
but now it doesnt load past the white HTC screen
in the recovery screen it says all this
*****LOCKED****
pyramid PVT SHIP s-off RL
HDBOOT-1.27.0000
Radio-10.14.9035.01_m
eMMC-boot
jane 13 2012,17:33:34
also when i load it it automatically looks for an image which i dont have any more
pg58diag.zip
edit:
i read and did this
You need to re-flash the ICS firmware from here --> http://forum.xda-developers.com/showthread.php?t=1412618
If it's an ICS ROM, flash the second one. If it's a Gingerbread ROM, flash the first one. Put the PG58IMG.zip on your SD card along with your ROM. Hold VOL-DOWN while you boot, and I think it asks you if you'd like to update (you do). You then need to remove the PG58IMG.zip from your SD card.
Boot into recovery after that and flash your ROM. If it still boot loops, that means you didn't flash the PG58IMG file correctly.
it says
cid incorrect update failed
stonedparadox said:
Ok im not sure where to start but anyway
i have the vodafone ireland htc sense and few months back i rooted the phone but didnt change the stock mod.
every so often updates came out and i didnt update cuz it wouldnt allow me it would give me that error with the android fella and i would have to do something to fix it i forget what.
anyway
so last night i wanted to install THIS ROM (black forest)
http://forum.xda-developers.com/showthread.php?t=1423684
it said i needed to update the firmware and then thats when it went into a bootlooping
i fixed the eventual bootlooping but formatting just about everything but i backed everything up when i mounted
but now it doesnt load past the white HTC screen
in the recovery screen it says all this
*****LOCKED****
pyramid PVT SHIP s-off RL
HDBOOT-1.27.0000
Radio-10.14.9035.01_m
eMMC-boot
jane 13 2012,17:33:34
also when i load it it automatically looks for an image which i dont have any more
pg58diag.zip
edit:
i read and did this
You need to re-flash the ICS firmware from here --> http://forum.xda-developers.com/showthread.php?t=1412618
If it's an ICS ROM, flash the second one. If it's a Gingerbread ROM, flash the first one. Put the PG58IMG.zip on your SD card along with your ROM. Hold VOL-DOWN while you boot, and I think it asks you if you'd like to update (you do). You then need to remove the PG58IMG.zip from your SD card.
Boot into recovery after that and flash your ROM. If it still boot loops, that means you didn't flash the PG58IMG file correctly.
it says
cid incorrect update failed
Click to expand...
Click to collapse
Hi,
You need to go HERE
Read the thread carefully,and it will guide you to which PG58IMG.zip you need for your phone.
Once you have flashed the appropriate firmware (PG58IMG.zip) it is important to delete the PG58IMG.zip from your sd card.
Then ,you can super wipe and flash your ROM.
right ill try this
but at the moment
when i get into recovery it loads the some file and it says wrong cid and it asks to reboot but it didnt
i dont have a card reader so im going to to a cafe of something
cheers for this
1. fastboot load into the bootloader and do:
fastboot getvar cid
fastboot getvar mid
If you don't have fastboot I have provided a download of it at the bottom of this post. Read the Read-Me file inside of it.
2. For those without fastboot you can use an app called CID Getter. CID is displayed at the top. MID is at the line ro.mid
This will not tell if you are SuperCID or not it just tells your original CID.
3. If you want to do it by terminal, open a terminal on the phone and do:
su
getprop ro.cid
getprop ro.mid
Click to expand...
Click to collapse
how to type IN fastboot?
stonedparadox said:
how to type IN fastboot?
Click to expand...
Click to collapse
Hi,
Fastboot is done on the pc,once you plugged your phone in with a USB.
If you cannot do this,then use method 2 or 3 .
i cant do 2 or 3
the link for the cidgetter is down
i got fastboot on my machine its just not recognizing my phone at the moment
edit:as far as i understand it here
http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode.html
im supposed to get the phone drivers to see eachother but there not :/
stonedparadox said:
i cant do 2 or 3
the link for the cidgetter is down
i got fastboot on my machine its just not recognizing my phone at the moment
edit:as far as i understand it here
http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode.html
im supposed to get the phone drivers to see eachother but there not :/
Click to expand...
Click to collapse
Hi,
You must have ADB installed on your PC in order to s-off
Use the same terminal on your PC to fastboot getvar cid
i do have adb installed but it looks like i dont have the right htc driver installed
when i type in fastboot getvar cid it says waiting for device
stonedparadox said:
i do have adb installed but it looks like i dont have the right htc driver installed
when i type in fastboot getvar cid it says waiting for device
Click to expand...
Click to collapse
Hi,
In order to make sure that you have the correct drivers,install the latest version of HTC Sync.
If it does not work the first time,close it all,then try again.
ok
cool
cid is vodaP001
mid is pg5813000
ok so i got it that working
its stuck on the HTC screen .. i assume i gotta put the mod i want in now right?
edit: i now need to super swipe and then add the mod and remove the update
stonedparadox said:
ok
cool
cid is vodaP001
mid is pg5813000
ok so i got it that working
its stuck on the HTC screen .. i assume i gotta put the mod i want in now right?
Click to expand...
Click to collapse
Hi,
Now You need to go HERE .Post # 2
Look for VODAPHONE Part 1:
DOWNLOAD 3.24 Unlocked: http://goo.gl/HWJJh
It has the PG58IMG.zip that contains:
cid is vodaP001
mid is pg5813000
Don't forget to thank Kohr-Ah for his efforts.
And flash that.Make sure it flashes fully(Including a reboot in the middle)
Then,delete the PG58IMG.zip,flash super wipe,then the new ROM.
ok ok
i got the dark forest os installed its just sim locked and in spanish
god damn
its in english just sim locked
is there a reason why my htc sensation wont see or read/see the nbh file in zip format on the sdcard while in hboot?
stonedparadox said:
is there a reason why my htc sensation wont see or read/see the nbh file in zip format on the sdcard while in hboot?
Click to expand...
Click to collapse
Hi,
It needs to be in the PG58IMG.zip format.
ok it reads it but i had to put it in a zip already used by something else in the phone and take out the stuff inside it
it gets as far as parses but then it stops
stonedparadox said:
its still not seeing the zip file
Click to expand...
Click to collapse
Hi,
It must be exactly PG58IMG.zip
Make sure there is no (1) in there
ok
so i did as you say
it gets as far as parsing and then stops ( that happens as soon as i enter the hboot screen )
if i go to install a zip it says
installing /sdcard/PG58IMG.ZIP
finding updating package
opening update package
installing update..
installation aborted
stonedparadox said:
ok
so i did as you say
it gets as far as parsing and then stops ( that happens as soon as i enter the hboot screen )
if i go to install a zip it says
installing /sdcard/PG58IMG.ZIP
finding updating package
opening update package
installing update..
installation aborted
Click to expand...
Click to collapse
Hi,
can i ask which PG58IMG.zip you are installing,and what you are trying to do?
ok
im trying to unlock my sim
Method 1 and method 2 dont work
http://forum.xda-developers.com/showthread.php?t=1192300
Hi,
My phone freezes on the boot up screen (where T-mobile pops up) I know there are LOADS of threads on help for problems like that, but I think it's fair to say, I've tried quite a few of them (or at least looked to see if they could help me) but I'm still epically stuck I'll describe what i can in order, because I tried quite a few things..... -.-
I've got Htc desire S, from T-mobile UK
Hboot- 2.00.2002
I tried to root it to get pdroid, of course, found out that i needed to downgrade it to 0.98 for zergRush......got the "Hellions with BLUE flames" message so moved on to tacoroot. it was fine until i got permission denied at the last cmd code. (the posts on the thread suggested using zergRush if tacoroot did not work -.-)
this is the most problematic part i'm guessing. I gave up on those 2 and found this "guide-how-root-desire-s" on android forums, it uses revolutionary and cwm
But while i was trying out that, i found revolutionary-0.4pre4, which sounded alot easier therefore i alternated between both since the rev 0.4 made the guide a lot easier (took out half of part 1 and whole of part 2). I managed to finish, reboot.
At this point Hboot screen had ***locked*** on top and S-off, but it was still on 2.something
I realized I had a RUU left over from one of the previous guides....(RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed)
so thinking i had to use it (since i was still on hboot 2.00.something), I stuck my phone on fastboot USB and started RUU up. it ran smoothly and soon finished, I rebooted my phone to check if i was in 0.98, which i was,and happily booted up my phone. But i didn't notice S was ON. Next thing i know, I've frozen on the boot up screen, so i take the battery out, booted to Hboot.
Now i can't access recovery menu, factory reset, and i can't reboot since it freezes on "t-Mobile" screen.
Have i broken it for good? if not what can i do to fix it?
Sorry this was a bit wordy, i didn't know what was useful so i just put it all in (well as much as i can remember accurately)
-quick summary-
HTC desire S
T-mobile
Hboot: 2.00.2002 (now 0.98)
S-ON (now, managed to have it off at a point...)
zergRush > tacoroot > revolutionary + guide using cwm recovery > messing it all up cause i forgot to put rom in SD card + used RUU > mega stuck...
I'm completely new to this rooting and stuff, please help. Thanks
edit..
oh, i don't know if it'll help but on cmd (I've installed adb, fastboot correctly) adb commands do not work, and says something like "device not found" or "waiting for device". Fastboot DOES work when on fastboot USB only.
edit....
change hboot version listed here from 2.00.002 to 2.00.2002
carelessness
Have you tried changing your miscellaneous version then running the RUU again and then use revolutionary to gain S-OFF then flash any rom you want P.S >>>> FALLOUT is probably the best at the moment
Good luck.
Hi, Duty09
Thanks for the quick reply. how do i change my misc version?i can't "adb push" since my phone wont register with cmd.....adb devices show nothing. Do i stick it in root and flash from fastboot?
Thanks
Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100
Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA
Forcefire said:
Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100
Click to expand...
Click to collapse
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...
Eclipse_Droid said:
Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
I can't, because when i run revolutionary, it gives me "waiting for device". i've tried running it while in Fastboot USB, HBOOT USB PLUG, even during the frozen t-mobile screen..... is there another way of doing this?
iinock said:
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...
Click to expand...
Click to collapse
From what I recall, you just select "All Other Supported Models"
SimonTS said:
From what I recall, you just select "All Other Supported Models"
Click to expand...
Click to collapse
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??
iinock said:
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??
Click to expand...
Click to collapse
Did you type
/android/fastboot oem get_identifier_token
Click to expand...
Click to collapse
or
./fastboot oem get_identifier_token
Click to expand...
Click to collapse
SimonTS said:
Did you type
or
Click to expand...
Click to collapse
neither,
started up cmd, cd to file with adb, fastboot, and the other one. and typed in fastboot oem get_identifier_token
i've just tried both 2nd one gave me
'.' is not recognized as an internal or external command,
operable program or batch file.
the first one gave me
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.031s]
finished. total time: 0.031s
0.015s longer than fastboot oem get_identifier_token.......
Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Ignore that - just reread the thread. You did have v2.00.002, but you've changed it to v0.98 something?
Have a look here http://androidforums.com/desire-s-all-things-root/444571-unlock-using-htcdev-com.html
You need HBOOT v2.* upwards to use HTCDEV unlock method.
SimonTS said:
Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Click to expand...
Click to collapse
right now its 0.98.0000
it was 2.something, but after loads of attempts at tweaking, it changed. think it was the RUU i ran after revolutionary, guessing thats what messed it up as well. but that's just my blind guess...
problem is, i can't change it back, OR change it to anything
Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.
Forcefire said:
Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.
Click to expand...
Click to collapse
Thanks, will definitely try that when adb works again. but i can't do that yet since adb is not working with my phone, it wont show up on "adb devices" any commands given just get "waiting for device" as a reply
just found this thread that seemed to have a lot in common with my problem
http://forum.xda-developers.com/showthread.php?t=1412398
but i'm running in to problems with CID, tried to do it with gold card but still no luck (i think gold card is done properly...)
im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks
@iinock not sure if this will help but ive got a T-Mobile RUU if you need it or have you already tried this ?
and have you tried android flasher yet ?
iinock said:
im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks
Click to expand...
Click to collapse
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF
DuTY09 said:
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF
Click to expand...
Click to collapse
Thanks for the links.
I managed to fix my phone by using a different SD card as a gold card (used LG 1gb) then flashed OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210uj1q93xrps74xzje
now it works , got to try install rom and pdroid now
thanks for your help guys :good:
Hello,
i wantted to flash stock rogers ruu since my wifi woudnt connect and was showing me wifi error even after factory resetting. so i searched a bit and found that it could be kernal related and so decided to flash it completely fresh ruu . now i have unlocked the bootloader before but dint relock it and just flashed clean rom.. everything was well.. but after wifi error i decided to go back to stock.. so i had to relock the bootloader.. so i relocked it.. changed superCID to 11111 adn now when i want it to go to the previous rom .. it wont.. nor can i go to recovery.. any help?.. just want to go to stock rogers ruu...
http://forum.xda-developers.com/showthread.php?t=1658929
so now my current state is .. i can acess bootloader menu .. but cant boot to rom or recovery.. how can i flash an ruu then?
thanks
When you relock the bootloader you can only get to hboot. This is normal, happened to me all 6 times I relocked mine across 5 different phones. You have to run a RUU to be able to boot back into your phone. Just follow the instructions in the thread you linked.
_MetalHead_ said:
When you relock the bootloader you can only get to hboot. This is normal, happened to me all 6 times I relocked mine across 5 different phones. You have to run a RUU to be able to boot back into your phone. Just follow the instructions in the thread you linked.
Click to expand...
Click to collapse
thanx.. yea its updating now...
if you dont mind me asking what is the wifi bug with htc one x which everyone talks about.. i thought its only related to the signal strength ..
mine one apparently wouldn't connect at all ..strange
jags_the1 said:
Hello,
i wantted to flash stock rogers ruu since my wifi woudnt connect and was showing me wifi error even after factory resetting. so i searched a bit and found that it could be kernal related and so decided to flash it completely fresh ruu . now i have unlocked the bootloader before but dint relock it and just flashed clean rom.. everything was well.. but after wifi error i decided to go back to stock.. so i had to relock the bootloader.. so i relocked it.. changed superCID to 11111 adn now when i want it to go to the previous rom .. it wont.. nor can i go to recovery.. any help?.. just want to go to stock rogers ruu...
http://forum.xda-developers.com/showthread.php?t=1658929
so now my current state is .. i can acess bootloader menu .. but cant boot to rom or recovery.. how can i flash an ruu then?
thanks
Click to expand...
Click to collapse
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
kilo89 said:
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
Click to expand...
Click to collapse
This is the information I had been hunting for. Thanks a lot!
i have no idea why it keep telling me failed (remonte: 43 main version check fail)
i tired many times already
still the same
a lil help here ...
kilo89 said:
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
Click to expand...
Click to collapse
madsatan said:
i have no idea why it keep telling me failed (remonte: 43 main version check fail)
i tired many times already
still the same
a lil help here ...
Click to expand...
Click to collapse
nevermind
i figured it out
madsatan said:
nevermind
i figured it out
Click to expand...
Click to collapse
what did you do? i get the same error 43 failed
please, Thanks
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred
fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom
Question in short: I have Fallout but it doens't go past the bootscreen. What can I try?
I have a european non-branded Desire S (Dutch) and wanted to try custom roms. I grabbed the most detailed tutorial I could find and started working on it. This was some months ago, but i basically ended up using MIUI because no other rom worked. Now, I am completely tired of all the fails this rom has (lagging, crashing, shutting down for no reason and the rom is just ugly imo) and therefore want to switch to another one. Now, my preference laid with the official beta for android 4.0 from the HTCdev website. I downloaded the RUU, followed the instructions, but I get an error everytime during the installation. Now as far as I have found out, this is because my phone is S-OFF. Searching how to change this, I found some commands:
Code:
fastboot oem lock
I thought, or something close. I don't think I will be helped by just this, but how do you execute this code? I believe somewhere in cmd, but where is fastboot.exe?
Given up on the idea of getting an official rom installed, I tried to install Fallout, the rom which appealed to me the most of all. Now, I remember this one from earlier, but it simply stops at the "HTC One" bootscreen. I did a full wipe as far as I know how to:
Code:
wipe data/factory reset
wipe cache
wipe dalvik cache
wipe battery stats
format system
format data
format boot
I did all of the above. And that is the situation I am in right now. I have Fallout installed and would like to use it (if it turns out to be good), but the official 4.0 beta would be good for me too. The rest of my phone's information:
Code:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
I just realized it is already S-ON. I don't know how, but i used the program Revert to Stock too, but it gave an error. Please tell me any extra information you need to help me, I hope you can help me solve this.
Thanks in advance.
Did you flash the boot.Img after you flashed the rom?
Java is C++ without guns, knives and clubs. - James Gosling (Co-inventor of Java).
I had exactly the same problem. Try to flash Boot.img Via Fastboot.
jugg1es said:
Did you flash the boot.Img after you flashed the rom?
Java is C++ without guns, knives and clubs. - James Gosling (Co-inventor of Java).
Click to expand...
Click to collapse
Kingdomds said:
I had exactly the same problem. Try to flash Boot.img Via Fastboot.
Click to expand...
Click to collapse
I found a tutorial: http://forum.xda-developers.com/showthread.php?t=1752270
I used a boot.img from the "Revert to Stock" application. Sending returns OKAY but writing returns FAILED (remote: image error! (BootMagic check fail)).
First of all, can I use this boot.img with Fallout? Secondly, how do I fix the fail in fastboot?
Robbertkooiman said:
I found a tutorial: http://forum.xda-developers.com/showthread.php?t=1752270
But I have no boot.img and it now says HBOOT USB PLUG in the recovery.
The command "fastboot devices" does nothing. It's recognized, but returns nothing.
What do I do?
I now found out I had to select fastboot. Now it says "FASTBOOT USB" and "fastboot devices" recognises my phone, but I still have no boot.img. Is there a specific boot.img for Fallout or do I need one for my phone?
Click to expand...
Click to collapse
Get the boot.img by extracting it from the fallout .zip file.
teadrinker said:
Get the boot.img by extracting it from the fallout .zip file.
Click to expand...
Click to collapse
Thanks, and sorry if this is already in every tutorial to install roms. The command gave "OKAY" twice now.
My rom works! Thanks so much.
Robbertkooiman said:
I found a tutorial: http://forum.xda-developers.com/showthread.php?t=1752270
I used a boot.img from the "Revert to Stock" application. Sending returns OKAY but writing returns FAILED (remote: image error! (BootMagic check fail)).
First of all, can I use this boot.img with Fallout? Secondly, how do I fix the fail in fastboot?
Click to expand...
Click to collapse
Stop whatever u are doing and start reading before u brick ur phone.
Here is a link for what and all u need to know.
From adb commands, unlocking/s-off, recoveries and roms.
U can flash rom with unlock or s-off, u need not need both. Unlock is less desired but in terms of flashing rom it works just fine, all u need to remember is to flash the boot.img at each point.
rain987 said:
Stop whatever u are doing and start reading before u brick ur phone.
Here is a link for what and all u need to know.
From adb commands, unlocking/s-off, recoveries and roms.
U can flash rom with unlock or s-off, u need not need both. Unlock is less desired but in terms of flashing rom it works just fine, all u need to remember is to flash the boot.img at each point.
Click to expand...
Click to collapse
Thanks for the help, but I'm already done. I'm sorry I didn't catch this in the tutorials, but I really tried.