Related
Hi,
I feel very bad asking but can you please help me with my Magic(32A) - Rogers.
Here is the story,
I bought the phone on ebay and the seller indicated that he rooted the phone before he sold me. So I thought okay as its rooted I can go to fast boot and just apply update.zip. So I did the below
1. switched off the phone
2. pressed home + power on and went to fast boot
3. did clean swipe
4. applied update.zip
It applied the custom rom(CyanogenMod 32a) and after that I am stuck on Roger's boot-up screen. So after this I removed my battery and I tried to going to fastboot and clicking Nandriod v2.1.1 restore and I get this error "E:Can't mount /dev/block/mmcblkop1". After that I did wipe and tried to apply restore but can "Error running nandriod restore. Restore not performed".
Can you please advise me of any options I have to restore my magic back.
Thanking you
FD
If you where not flashing the SPL you "should" still be ok if you can get into fastboot.
If you can just try to apply the ROM again, you might want to download another copy or different ROM (Hero maybe).
Clinton
do me a fav and power on holding down the vol down. see if you go into fastboot. if you do then you are not bricked. if so, see what your radio and spl is plus check if your (s) is off. if so you are rooted and you flashed the wrong board rom. if its on then your seller lied and you are not rooted. if so fallow the rooting guides that are posted here. if you need ne help just pm me and i will apply my skills the best i can. i want all to be rooted and experience the true right of freedom. lol. fosho. . . .
Partial hope
When I power it on and hold volume down I can get into fastboot mode and here is what I can see on the screen
Sapphaire pvt 32A eng s-off H
Hboot-1.33.2009(SAPP50000)
CPLD-12
Radio-3.22.20.17
May 6 2009, 00:17:16
Can you please advise me on what I can do next please. Is my phone rooted as it has "s-oof"? and what should my next steps be.
Thanking you
FD
ok ?. did you buy it rooted so you didnt have to do ne thing?? does it have RAv recovery or cm's recovery??
Thank you rocking_mod I was able to restore my phone. Here is what I did
1. downloaded HoFo mod to renamed it to update.zip and copied it to SD card
2. used a recovery img and did a fast boot and loaded the img
3. after the reboot did a clean wipe
4. loaded the HoFo rom from the recovery mode.
And finally now the phone works again. Enough of action for one day.
Thanks again.
freedonkey said:
Thank you rocking_mod I was able to restore my phone. Here is what I did
1. downloaded HoFo mod to renamed it to update.zip and copied it to SD card
2. used a recovery img and did a fast boot and loaded the img
3. after the reboot did a clean wipe
4. loaded the HoFo rom from the recovery mode.
And finally now the phone works again. Enough of action for one day.
Thanks again.
Click to expand...
Click to collapse
Congrats!
Always great to see when someone bring his mobile back to live
I'm guessing the ROM you downloaded was not compatible with your phone. As a side note, do NOT apply the Rogers update ontheir web site. It will upgrade your SPL to the dreaded perfect version.
I got the same error when I first apply the hofoion108.zip. I happened to press apply again somehow, and it had no errors at the second time. My phone can start with that rom later on.
I need help, i am in same situation as you freedonkey, but i don't know where to get the files you reffer to:
1. downloaded HoFo mod to renamed it to update.zip and copied it to SD card
2. used a recovery img and did a fast boot and loaded the img
3. after the reboot did a clean wipe
4. loaded the HoFo rom from the recovery mode.
The HoFo mod and which recovery image should i use and where to get it ?
My phone specs so far are:
Sapphaire pvt 32A eng s-off H
Hboot-1.33.2005(SAPP50000)
CPLD-12
Radio-6.35.08.29
Apr 20 2009, 15:30:43
ps: I am not sure, but i dont know what model is mine (i am kind of a newbie :/) i think it should be Rogers, but not sure, bought it in Portugal blocked to TMN phone company.
I also "soft-bricked" my Magic when installing a new ROM. I had wrong radio and didn't wipe before trying to install - all I was left was the HTC boot splash.
I was then, after a few days of reading & thinking, able to restore the device! I had bought it used so I had no warranty.
I used ADB to check out if the device was alive or dead. I wiped everything that was left (kernel, boot, system and userdata) and flashed new radio that would work with CM5/6. After that I flashed Amon_RA 1.71 Recovery, a 1.6 Donut ROM, gapps and new kernel. It worked! After that (for a month) I've been playing with CM6 nightlies and RC's.
If you don't want root capablities, just the original ROM, there should be good info on that. But if you do, I would recommend to follow CyanogenMod instructions from their wiki - they're helpful and easy to follow.
NaDaBrAvItChKa said:
I need help, i am in same situation as you freedonkey, but i don't know where to get the files you reffer to:
1. downloaded HoFo mod to renamed it to update.zip and copied it to SD card
2. used a recovery img and did a fast boot and loaded the img
3. after the reboot did a clean wipe
4. loaded the HoFo rom from the recovery mode.
The HoFo mod and which recovery image should i use and where to get it ?
My phone specs so far are:
Sapphaire pvt 32A eng s-off H
Hboot-1.33.2005(SAPP50000)
CPLD-12
Radio-6.35.08.29
Apr 20 2009, 15:30:43
ps: I am not sure, but i dont know what model is mine (i am kind of a newbie :/) i think it should be Rogers, but not sure, bought it in Portugal blocked to TMN phone company.
Click to expand...
Click to collapse
Can anyone give me any tip?? i don't know which file should i get for my phone :| or even where to get it .. any help would be really appreciated
kanttii said:
I also "soft-bricked" my Magic when installing a new ROM. I had wrong radio and didn't wipe before trying to install - all I was left was the HTC boot splash.
I was then, after a few days of reading & thinking, able to restore the device! I had bought it used so I had no warranty.
I used ADB to check out if the device was alive or dead. I wiped everything that was left (kernel, boot, system and userdata) and flashed new radio that would work with CM5/6. After that I flashed Amon_RA 1.71 Recovery, a 1.6 Donut ROM, gapps and new kernel. It worked! After that (for a month) I've been playing with CM6 nightlies and RC's.
If you don't want root capablities, just the original ROM, there should be good info on that. But if you do, I would recommend to follow CyanogenMod instructions from their wiki - they're helpful and easy to follow.
Click to expand...
Click to collapse
Thanks for the help kantiii, i will see what i can doo tonight when i get back home
Hey again Kantii,
I am sorry i am bit newbie, I figure out my phone is still alive sthoughout ADB as u did, but i don't know for sure how to:
1- I wiped everything that was left (kernel, boot, system and userdata)
- I actuall wiped it after i turned the phone on with Home+off buton, does that inclued kernel and system wipe ?
2- flashed new radio that would work with CM5/6
- CM = Cyanogen Mod ??? which of these files u recomend to me ? (Both radio and CM5/6 ?)
3- I flashed Amon_RA 1.71 Recovery, a 1.6 Donut ROM, gapps and new kernel
- Is Amon_RA 1.71 Recovery compatible with any HTC MAgic ???
I am really newbie about all this so I would appreciate all details! :|
thanks a lot for everything so far anyway
Sorry for long time no reply! I had not checked my mailbox!
You should wipe them in fastboot:
1. Turn your phone on by pressing back + power until you are in fastboot & see the skating droids. Another method to do this is turning the phone on by pressing volume down + power and then the back key.
2. Connect the device to your pc (make sure you see FASTBOOT USB on the phone display) and run CMD
3. type "fastboot devices" and check if your phone is plugged in correctly and you see the device ID.
4. Now you can wipe them correctly with fastboot:
4.1 type "fastboot erase [system/cache/userdata/boot/kernel/recovery all separately]" (without brackets etc, they are here to make reading easier)
4.2 Download:radio http://www.theandroidkitchen.com/fi...es/?download=Radio_HTC_PVT_32A_3.22.20.17.img
SPL http://briancrook.ca/android/3.22/hboot-1.33.2005.img
recovery http://rapidshare.com/files/387932922/recovery-RA-sapphire-v1.7.0H-cyan.img4.3. Move the downloaded files to C:\ (and if you want, rename to Radio.img and Hboot.img and Recovery.img) so it is easier to use them. After that type "cd.." in cmd repeatedly until you are in C:\
5. Now you should be able to flash the radio, SPL and recovery images:
5.1 Type "fastboot flash radio Radio.img"
5.2 Type "fastboot flash hboot Hboot.img"
5.3 Type "fastboot flash recovery Recovery.img"
5.4 In each step wait until fastboot says it has finished - if you won't, you have to start everything again or may brick your device.
6. Now in your phone press menu to power down it. Then boot again to fastboot to confirm you flashed correctly:SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005
RADIO-3.22.20.177. Now power down the device again and boot to recovery by pressing home + power.
7.1 In recovery, check that it works correctly (no lag, no crashes, functions work properly)
8. Now you can install CyanogenMod 6 and enjoy fast FroYo on your Magic
http://wiki.cyanogenmod.com/index.php?title=Upgrading_from_CyanogenMod_4.2_to_CyanogenMod_5/6
Good luck and hopefully you can restore your device!
kanttii said:
Sorry for long time no reply! I had not checked my mailbox!
You should wipe them in fastboot:
1. Turn your phone on by pressing back + power until you are in fastboot & see the skating droids. Another method to do this is turning the phone on by pressing volume down + power and then the back key.
2. Connect the device to your pc (make sure you see FASTBOOT USB on the phone display) and run CMD
3. type "fastboot devices" and check if your phone is plugged in correctly and you see the device ID.
4. Now you can wipe them correctly with fastboot:
4.1 type "fastboot erase [system/cache/userdata/boot/kernel/recovery all separately]" (without brackets etc, they are here to make reading easier)
Click to expand...
Click to collapse
Not to thread hijack, but these instructions look well suited to my situation. At step 4.1 I get the error "FAILED (remote: not allow)". How to solve?
These instructions are only for Magic, but..
Post your fastboot details, please.
Hi my magic 32b is stuck on vodaphone splash screen.no fastbiot or recovery.but chargeable via usb and has blue light too.can u show me steps to softunbrick
Sent from my HTC Desire using XDA App
Sorry, but 32b is out of my area
Try this http://forum.xda-developers.com/showthread.php?t=755903
After that, test if you can get to fastboot or hboot (fastboot: back + power, hboot vol down + power). Then report back and search the forum for further help on restoring your device with new SPL & radio & recovery & ROM
Otherwise, if these won't work you could try JTAG.
Hope this helps,
kanttii
Hi guys, I'm a newbie. I wanted to know, how can I flash my os from 2.1 to 2.2 .
The main problem is - I dont understand how does the fastboot works. there are img. files. What should I do with them ?
THANK YOU VERY MUCH FOR YOUR USEFUL REPLIES!
do you have rom with fastboot?
do you have fastboot already installed to your pc ?
when yes ,then run these command on androidSDK :
Code:
fastboot.exe flash system system.img
fastboot.exe flash boot boot.img
fastboot.exe reboot
but when not :
you have install AndroidSDK and fastboot items and gt540 drivers.
how can I install fastboot rom ?
I read some information, got the links, but I dont understand how to get that rom on my phone.
I understood, that i will have to reflash my rom, cause I have 2.1B baltic, and there's no fastboot on it. Is there any chance that I can install fastboot seperatly?
Look when you reflash with another 2.1 you wont notice anythings changed. It keeps your data. When done just turn phone off then switch on with power and camera held together until a blank screen. Thats fastboot.
Plug phone in whilst on black screen then follow the fastboot instructions in 2nd post
Sent from my GT540 using XDA App
Which rom do you suggest ?
And it would be very great, if you would link the download. Cause I don't wanna **** up system.
pashinator said:
When done just turn phone off then switch on with power and camera held together until a blank screen.
Click to expand...
Click to collapse
I installed a fastboot ROM, then installed the openswift 2.2 ROM last night, and fastboot mode was hold volume up + search while powering on on my gt540f. Camera went into download mode for me.
hey i accidently flashed 2.22.23.02 on to my rogers htc dream which i figured out needed a different radio now when i turn on my phone it just gets stuck on the rogers screen and i cant boot into recovery or to the bootloader so is my phone now useless or can i fix it
Re-flash it with the correct one according to your ROM. Then you will be good to go.
well he cant get to recovery or bootloader so how will he flash anything? lol jtag? pretty sure you might be out of luck... unless somehow you can get the orange.nbh to flash to your device...
Oops, missed that. I thought I read that he can.
is there any way i can flash it using my computer
thanojan10 said:
is there any way i can flash it using my computer
Click to expand...
Click to collapse
Only if you can get into fastboot or adb..
From the sound of it you had a 3.22.* radio and used recovery to flash a 2.22.* radio.. while both radios work on the phone if you switch them by recovery like that you prob. Have a brick requiring JTAG..
Before giving up hope:
Pull battery + any USB/power wire, replace battery and while holding camera press power..
If you are in hboot, you can restore the phone by fastboot if its an engenering SPL, otherwise a Rogers dreaimg.nbh
If not plug in the USB wire and run on your computer 'fastboot devices' if the phone is found or fastboot USB is on the screen you lucked out (and somthing is wrong with recovery making it fail to load), and can use fastboot to install a valid radio+spl+recovery (make sure you flash all 3 before restarting)
If this isn't working and you can't get into the rom or recovery, you have an ebi0 radio (2.22) with a kernel (recovery) compiled for ebi1 (3.22) and are in boot mode 3 to force the phone to boot into recovery.. Due to the mismatch between the radio and recovery your phone is not able to boot and clear the boot flag to allow normal operation.. Thus without jtag its not possible to enter a useful state.
This is why its recommended to flash radios and SPLs via fastboot when possible since fastboot won't set the boot mode thus allow you at least access to the bootloader in most cases to correct any mistakes.
Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?
ADB and fastboot drivers are different.
Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....
http://bit.ly/Zqk7pm
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....
Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.
oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck
bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...
In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes
SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them