Database Info

[HOWTO] GB to ICS OTA for Rooted Stock - Keep your data (Revolutionary hboot only)

Provided you meet the prerequisites, this is an easy way to safely update from 2.11.695.19 Gingerbread to 7.02.605.06 to 7.02.605.10 Ice Cream Sandwich via the new OTA and keep root. I have also modified the stock kernel to allow adb remount so you can push/pull files directly from the command line without needing to drop into adb shell. If you do not have the correct Revolutionary hboot or have modified your Gingerbread system files then skip this guide and flash a rooted stock build from the development forum.
ONLY for users with S-OFF revolutionary hboot and running rooted stock. DO NOT USE THIS GUIDE IF YOU ARE HTCDEV UNLOCKED OR HAVE CHANGED OR DELETED ANY OF THE STOCK SYSTEM FILES. FLASH THE RADIO AND FULL ROM INSTEAD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
REQUIRED Prerequisites:
Revolutionary hboot with S-OFF
Rooted Stock ROM with NONE of the system files missing or changed
Get the files:
- Save the stock recovery image to your fastboot directory: Stock recovery (use the same as your ROM build, 2.11.695.19) or attached below
- Save the custom recovery image of your choice to your fastboot directory: TWRP or CWM
- Optional Superuser or SuperSU recovery flashable .zip package if OTA rootkeeper did not work
- Optional insecure boot.img attached below
Steps:
1) Set your Superuser app for OTA survival mode
2) Reboot into bootloader
If your bootloader does not have "Revolutionary" across the top, STOP immediately. If you take the OTA, you will end up with a locked bootloader.
3) Flash stock recovery
Code:
fastboot flash recovery name_of_stock_recovery.img
4) Reboot, check for the first firmware update and download.
5) Apply update. It should reboot a few times and then reboot back into system when done. Check for the second OTA and download.
6) Apply update. It should reboot a few times and then reboot back into system when done.
7) Reboot into bootloader
8) Flash TWRP or CWM recovery
Code:
fastboot flash recovery name_of_custom_recovery.img
9) Copy the superuser install .zip to the root of your sdcard
10) Reboot into recovery and flash the superuser update package
Optional for insecure boot ie: adb remount works:
1) Download mecha_insecure_boot.img to your fastboot directory
2) Reboot into bootloader
3) Flash:
Code:
fastboot flash boot mecha_insecure_boot.img
Secure boot attached if you want to go back.
Code:
fastboot flash boot mecha_secure_boot.img
Once you are done, your Thunderbolt will have the current ICS rom with data intact, the new radio, working superuser, custom recovery and insecure boot for "adb remount" if wanted.

This looks good, have people had success with it yet? I don't want to lose my data by trying to unroot, but I am already sitting with rooted stock with the 2.11.605.19 recovery installed.

I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?

Looks simple enough. I am going to try this on my wifes tbolt tonight.

Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
Tiezane said:
This looks good, have people had success with it yet? I don't want to lose my data by trying to unroot, but I am already sitting with rooted stock with the 2.11.605.19 recovery installed.
Click to expand...
Click to collapse
So far just me that can confirm this works. I did not wipe at first but ended up doing a factory reset after everything was said and done anyway. There are always bits and pieces of old data that are not quite right going between major versions like this.
KidJoe said:
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Click to expand...
Click to collapse
I can only confirm this worked for me on the Revolutionary hboot. Not going to speculate on others. If the version number in the OTA is higher, it probably will replace what you currently have.

Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.

Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
A CWM flashable zip would have been nice to have last night! This goat rope is pretty much the same process I used on the G2 and MyTouch. No patience so went with what I know and sharing how I did it.

kpetrie77 said:
A CWM flashable zip would have been nice to have last night! This goat rope is pretty much the same process I used on the G2 and MyTouch. No patience so went with what I know and sharing how I did it.
Click to expand...
Click to collapse
Haha yeah I agree, however I spent last night getting it made up.
Didn't finish till this am.
But truly thank you for sharing this alternate method of keeping root and updating.
I'm sure it's much appreciated by many.
Upload is about halfway...

santod040 said:
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Click to expand...
Click to collapse
Call me timid.....
Thanks in advance santid040.

santod040 said:
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Click to expand...
Click to collapse
At the risk of sounding like a complete n00b (which I feel like anyway)... will the version you are uploading be run as an update, and therefore maintain data on the phone, or is it going to wipe what I have there now?

Tiezane said:
At the risk of sounding like a complete n00b (which I feel like anyway)... will the version you are uploading be run as an update, and therefore maintain data on the phone, or is it going to wipe what I have there now?
Click to expand...
Click to collapse
It's a full rom install.
But I did not set it up to wipe data.
That doesn't mean it will play well if you don't format first, but you can try.
It's posted HERE

KidJoe said:
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Click to expand...
Click to collapse
Apparently I had an OLD "permanent hboot with S-OFF that was made to not be overwritten.
I chickened out on trying to update. Instead, I reverted from the OLD "permanent" hboot to the old eng 1.40.2000 s-off hboot which could be over written. Then flashed with the 2.11.605.5 RUU to get back to S-ON, and Used Revolutionary to get S-OFF & Root.
So I now have the Revolutionary S-OFF hboot 6.04.1002 and will be upgrading from here.

santod040 said:
It's a full rom install.
But I did not set it up to wipe data.
That doesn't mean it will play well if you don't format first, but you can try.
It's posted HERE
Click to expand...
Click to collapse
I read this post while installing and wiped data/factory reset after installing (without booting first). Will this have the same effect as doing so before installing? Or should I wipe and install again?

Dropbox temporarily suspended... Oops.

lukesed said:
I read this post while installing and wiped data/factory reset after installing (without booting first). Will this have the same effect as doing so before installing? Or should I wipe and install again?
Click to expand...
Click to collapse
As an answer to my own question... I wasn't able to log in to my google account. I did a full wipe and installed again, and now it does work.

I have come to the conclusion that rooting is for people much smarter and with much more time than me. I'm hopelessly confused. I will never root my phone again becasue I simply don't enjoy spending my whole damn night figuring this stuff out... but since my current phone IS rooted and I want the ICS update I have to deal with this migrane.
I appreciate this OP ... but the first thing it says to do is to get the mecha android 3e recovery rom or whatever it is... and when I click that link it takes me to another forum with files all over the place, none of which are called that. What exactly am I supposed to download?
Thanks!

Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
Good point, updated the OP. Use the stock recovery from Scotty's thread (linked) that matches the ROM version your are on.
Settings > About phone > Software
If on 2.11.605.09 then use the matching 2.11.605.09 recovery. If running 2.11.605.19 rom use 2.11.605.19 recovery.

jdport said:
I have come to the conclusion that rooting is for people much smarter and with much more time than me. I'm hopelessly confused. I will never root my phone again becasue I simply don't enjoy spending my whole damn night figuring this stuff out... but since my current phone IS rooted and I want the ICS update I have to deal with this migrane.
I appreciate this OP ... but the first thing it says to do is to get the mecha android 3e recovery rom or whatever it is... and when I click that link it takes me to another forum with files all over the place, none of which are called that. What exactly am I supposed to download?
Thanks!
Click to expand...
Click to collapse
If you are rooted, why not flash the stock rooted ICS rom?

santod040 said:
If you are rooted, why not flash the stock rooted ICS rom?
Click to expand...
Click to collapse
Because I have no idea how. I'm a complete newbie to this. I got through the rooting process because the nice scripts that were written were easy for even me to follow.... the only reason I rooted at all was so that I could get a proper backup with titanium. I wish now I had not rooted because I am absolutely clueless on how this stuff works. Of course if I unroot, it wipes my phone and I can't restore... without rooting again. lol. I just want to get the update installed without screwing up my phone.... whatever it is I have to do to do that. Unfortunately I really can't seem to find a resource that explains all of this. I've been reading all night and at this point my head is starting to hurt and i'm not much closer to the solution than when I started.

jdport said:
Because I have no idea how. I'm a complete newbie to this. I got through the rooting process because the nice scripts that were written were easy for even me to follow.... the only reason I rooted at all was so that I could get a proper backup with titanium. I wish now I had not rooted because I am absolutely clueless on how this stuff works. Of course if I unroot, it wipes my phone and I can't restore... without rooting again. lol. I just want to get the update installed without screwing up my phone.... whatever it is I have to do to do that. Unfortunately I really can't seem to find a resource that explains all of this. I've been reading all night and at this point my head is starting to hurt and i'm not much closer to the solution than when I started.
Click to expand...
Click to collapse
If you are already rooted, go to my thread, click the link.
Sign into the InfectedROM forums, and grab the stock rom, full or debloated, your choice.
Flash it in Recovery like any other custom rom and reboot.
DONE! Stock ICS rooted... :good:

[Q] Desire S stuck at HTC logo after Cyanogen - once again

Hello,
as you can read in the title, my Desire S gets stuck at the htc logo while booting, after installing Cyanogen.
A common problem, I read loads of threads, but could not find a solution to my problem, which actually works. That's why I'm asking here.
I am sorry if the solutiuon is already somewhere out there, I could not find it, even after several hours of google.
Anyway, I'll explain what I have done, step by step:
I updated my saga some time ago to 4.0.4 with the official htcdev RUU. Later i unlocked it using the htcdev bootloader-unlocker, which worked fine.
Used it a while with the old 4.0.4 RUU, but with root permissions. It still tells me to be S-ON, I think the htc bootloader lets the phone in this state (?). For the root permissions I used the clockworkmod to install superuser. Worked fine.
Today I decided to install cyanogen 10.2, I think (not sure about the version, the latest nightly, however).
So I installed the .zip of the ROM using the clockworkmod and flashed the boot.img of the mod with the PC (fastboot).
It all seemed to work, so far, so I cleared all the caches with the clockworkmod and started my phone for the first time - it stuck at the logo.
So I tried again and again, reinstalled the mod, the boot.img and so on, nothing seemed to work. I decided to restore the phone to my old 4.0.4 using clockworkmod (I have made a backup, of course) but that gets stuck at the htc logo too.
The htc RUU utility can find my phone (when in USB fastboot mode) and tries to update it, but it shows me an error message after completing the sending of the data to the phone.
Now the facts about my phone:
Bootloader-message:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
(I don't think that the other stuff is important, can write it too,m of course, if you need it).
Clockworkmod: 5.0.2.0
Can anyone tell me what I should do? I don't really care if you can help me to get my old 4.0.4 backup working or the cyanogen.
I would like the last option better, of course, but as long as my phone works again, I'll be happy.
Again: Sorry if the information on how to fix my phone is somewhere out there. I did not find anything useful for my problem.
Especially the S-ON is confusing me a bit. Is that the problem?
Is the old backup not working anymore because I have already flashed the boot.img of the cyanogen? I once tried to flash the cyanogen, some weeks ago, but found out at half the way that I needed my phone right now working again (I had not flashed the boot.img yet), so I used the backup. It worked, then. Now it isn't working anymore.
I hope, someone can help me. I really like my phone and don't want to buy a new one.
If I bought a new one, I want the One, and that's way too expensive for me...
With kind regards,
Moritz

elektrobastler said:
Hello,
as you can read in the title, my Desire S gets stuck at the htc logo while booting, after installing Cyanogen.
A common problem, I read loads of threads, but could not find a solution to my problem, which actually works. That's why I'm asking here.
I am sorry if the solutiuon is already somewhere out there, I could not find it, even after several hours of google.
Anyway, I'll explain what I have done, step by step:
I updated my saga some time ago to 4.0.4 with the official htcdev RUU. Later i unlocked it using the htcdev bootloader-unlocker, which worked fine.
Used it a while with the old 4.0.4 RUU, but with root permissions. It still tells me to be S-ON, I think the htc bootloader lets the phone in this state (?). For the root permissions I used the clockworkmod to install superuser. Worked fine.
Today I decided to install cyanogen 10.2, I think (not sure about the version, the latest nightly, however).
So I installed the .zip of the ROM using the clockworkmod and flashed the boot.img of the mod with the PC (fastboot).
It all seemed to work, so far, so I cleared all the caches with the clockworkmod and started my phone for the first time - it stuck at the logo.
So I tried again and again, reinstalled the mod, the boot.img and so on, nothing seemed to work. I decided to restore the phone to my old 4.0.4 using clockworkmod (I have made a backup, of course) but that gets stuck at the htc logo too.
The htc RUU utility can find my phone (when in USB fastboot mode) and tries to update it, but it shows me an error message after completing the sending of the data to the phone.
Now the facts about my phone:
Bootloader-message:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
(I don't think that the other stuff is important, can write it too,m of course, if you need it).
Clockworkmod: 5.0.2.0
Can anyone tell me what I should do? I don't really care if you can help me to get my old 4.0.4 backup working or the cyanogen.
I would like the last option better, of course, but as long as my phone works again, I'll be happy.
Again: Sorry if the information on how to fix my phone is somewhere out there. I did not find anything useful for my problem.
Especially the S-ON is confusing me a bit. Is that the problem?
Is the old backup not working anymore because I have already flashed the boot.img of the cyanogen? I once tried to flash the cyanogen, some weeks ago, but found out at half the way that I needed my phone right now working again (I had not flashed the boot.img yet), so I used the backup. It worked, then. Now it isn't working anymore.
I hope, someone can help me. I really like my phone and don't want to buy a new one.
If I bought a new one, I want the One, and that's way too expensive for me...
With kind regards,
Moritz
Click to expand...
Click to collapse
Hi
S- on : in short means you have to flash boot.img each time you flash a new rom
or backup from different base than your current...
If you restore stock 4.0.4 you have to flash boot.img from that backup as well...
Because now you have kernel from cyanogenmod...-
sense rom would not boot

asgardr said:
Hi
S- on :means you have to flash boot.img each time you flash a new rom
or backup from different base than your current...
If you restore stock 4.0.4 you have to flash boot.img as well
because now you have kernel from cyanogenmod...
Click to expand...
Click to collapse
Thanks, this tells me at least, what the problem was, but not, how to solve it (well, I don't understand how to solve it).
I have no idea, how to find the kernel for the stock 4.0.4, from htc i have only got a .zip with a .exe and a pdf in it. The exe is doing everything from the PC, no idea how the extract any useful data from this. Is it someweher in my backup, maybe?
Do you have any idea, why the cyanogen didn't work? I actually flashed the right boot.img using fastboot...

elektrobastler said:
Thanks, this tells me at least, what the problem was, but not, how to solve it (well, I don't understand how to solve it).
I have no idea, how to find the kernel for the stock 4.0.4, from htc i have only got a .zip with a .exe and a pdf in it. The exe is doing everything from the PC, no idea how the extract any useful data from this. Is it someweher in my backup, maybe?
Do you have any idea, why the cyanogen didn't work? I actually flashed the right boot.img using fastboot...
Click to expand...
Click to collapse
Just open your 4.0.4 backup and there it is- boot img that belongs to your backup
flash through fastboot before you boot the phone ,
and all should be well..
As for the other rom- may be a bad download- corrupted, check md5 sum
It is always strongly recommended to perform a full wipe before changing roms,
especially when comming from sense to aosp, cyanogenmod or any of their derratives...

asgardr said:
Just open your 4.0.4 backup and there it is- boot img that belongs to your backup
flash through fastboot before you boot the phone ,
and all should be well..
As for the other rom- may be a bad download- corrupted, check md5 sum
Click to expand...
Click to collapse
Thank you very much, you saved my day
I'll instantly try to flash my old boot.img again, I'll tell you in a few minutes if it worked!!

elektrobastler said:
Thank you very much, you saved my day
I'll instantly try to flash my old boot.img again, I'll tell you in a few minutes if it worked!!
Click to expand...
Click to collapse
Once, i was there too- mate

Thank you, thank you, thank you!!
You saved my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

elektrobastler said:
Thank you, thank you, thank you!!
You saved my phone
Click to expand...
Click to collapse
While s- on it is good to take in to habit:
Flashing kernel each time when flashing the rom
Full wipe before any full rom flash- especially when changing base
( even an update can sometimes be based on different structure)

Desire S is dead!!!
asgardr said:
While s- on it is good to take in to habit:
Flashing kernel each time when flashing the rom
Full wipe before any full rom flash- especially when changing base
( even an update can sometimes be based on different structure)
Click to expand...
Click to collapse
Hi I would like to also add my problem to this thread. I have :
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
I wanted to install SABA ROM, but at the end my phone is dead!!!
I unblocked bootloger according to HTCdev guidelines, I installed 4EXT recovery, made gold card.
Finally by mistake I used SuperOneClick, which blocked my phone.
Now I can only enter to bootloger menu, but when I start my Desire S normally, it gets stuck on black screen after white htc logo while booting.
The problem is that I do not have backup boot.img file from my phone, so I cannot follow @asgardr advice
Please advise what I should do? I am totally lost now.
PLEASE HELP!!! Thanks in advance!!!
PS. Please forgive not proffesional language as I am newbe!

continiven said:
Hi I would like to also add my problem to this thread. I have :
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
I wanted to install SABA ROM, but at the end my phone is dead!!!
I unblocked bootloger according to HTCdev guidelines, I installed 4EXT recovery, made gold card.
Finally by mistake I used SuperOneClick, which blocked my phone.
Now I can only enter to bootloger menu, but when I start my Desire S normally, it gets stuck on black screen after white htc logo while booting.
The problem is that I do not have backup boot.img file from my phone, so I cannot follow @asgardr advice
Please advise what I should do? I am totally lost now.
PLEASE HELP!!! Thanks in advance!!!
PS. Please forgive not proffesional language as I am newbe!
Click to expand...
Click to collapse
You mean- Sabsa prime rom
Any ,( or most ) roms you flash contain boot.img file in the .zip ( full roms not updates or ota`s)
so you only have to:
1. open the rom zip
2. find boot.img
3. reboot to bootloader
4. < fastboot devices >( without arrows )
5. < fastboot flash boot boot.img
6. reboot
before flashing a rom- full wipe - ( all except sd card ) very often saves you the headache...
edit: if it turns out to be a big trouble with the rooting method you`ve used,
you may start from scratch:
1. relock bootloader (must be for flashing RUU ) but keep unlock_token from htc- you`ll need it
fastboot oem lock
2. flash RUU you were previously having installed
3. unlock bootloader again
4. flash recovery- via fastboot
5. flash superuser and its binary- zip--- from recovery, and you are rooted
6. fully wipe your device
7. flash rom ( recovery )
8. flash boot.img of the newly flashed rom ( fastboot )
9. reboot device
10. done

[Q] Problem with preparing HTC Sensation for Custom Rom installation

Hello,
Call me a noob but for starting I do not understand half of therms being used on most of the threads I've read even tho I spent days reading and trying to figure out everything by myself before opening a new thread and being pointed as a noob by everyone but I don't care about that anyways.
Alright, so I have some sort of an unusual HTC Sensation because every time I try to do a step forward I get stuck because of my particular phone and have to go back 2 steps. That lead me to a 3-days frustrations even tho I'm reading everywhere that people with no experience whatsoever are rooting and installing custom roms in less than 10 minutes.
So, first some software data about this little prick who seems different than most of the others Sensations I've seen around.
Phone name: HTC Sensation Z710e
Android version: 4.0.3 (official update)
HTC Sense version: 3.6
Software number: 3.32.771.51
Kernel version: 3.0.16-gda3fdfc
[email protected] #1
SMP PREEMPT Fri Feb 17 19:24:03 CST 2012
Baseband version: 11.69A.3504.00U_11.23.3504.07_M2
Build numver: 3.32.771.51 CL360734 release-keys
Browser version: WebKit/534.30
*** UNLOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
Okay. So or the last few days I managed to UNLOCKED the phone and make it S-OFF even tho it was not easy at all for me, especially with my HBOOT version which forced me to do some silly wire tricks that actually worked at the end. (but probably messed up my WiFi)
What I'm trying to do and what I need your help for is... installing Android Revolution HD Custom Rom from here: http://forum.xda-developers.com/showpost.php?p=14191938&postcount=1.
So, in order to do that first I had to make my phone S-OFF and unlock it which I did successfully after a lot of struggling.
It also says that I need to update the firmwire: "t's necessary to flash new firmware package before flashing this ROM" which should be found on this thread: http://forum.xda-developers.com/showthread.php?t=1412618 but... ONCE AGAIN I encountered a problem because I don't see my version listed anywhere.
My CID: H3G_106
My MID: PG813000
So that's my first problem. Then in order to install that particular ROM I need to wipe all my data. I have no problem with the data itself but I've tried doing it in AROMA but I didn't see anywhere the option to SuperWipe everything. Yes, a real noob here, huh? I guess I have to somehow install a SuperWipe script but I didn't manage to do that yet.
One PROBLEM that I got after unlocking the phone, making it S-OFF and trying to wipe it (only did the factory reset) was losing WiFi. That's limiting my phone A LOT as you would guess and I don't seem to find a solution. Many said that it will 'return' once I istall the Custom Rom but I'm not sure about that and I'd kinda like to get that resolved ASAP. It's a 'standard' problem where it says 'ERROR' and cannot be turned on at all. I tried some WiFix from WiFi Manager and similar 'tricks' but nothing worked. I assume it was after doing the 'wire trick' in order to S-OFF my phone but that's just my guess that might be irrelevant for the solution of the problem.
Well, that's all from me in the first post.
I hope somebody will skip the noob introduction and will actually help me with the problem because I do need help regarding this and it's not like I came here for the first time after buying a phone. I tried sorting all this out by myself for the last few days but I just gave up and decided to seek help from the more experienced ones.
Thanks a lot in advance,
Fidel

1. Since you are s-off, get superCID.
2. Firmware: http://forum.xda-developers.com/showthread.php?p=21711154
3. Flash a custom recovery (4EXT is probably your best choice)
4. Make a nandroid backup via recovery
5. Format all partitions in recovery
6. Flash the ROM you want
If WiFi still does not work, then I would try a kernel that is compatible with the ROM you want.
Your super wipe problem can be easily fixed by flashing a custom recovery.
On step two, you can flash 3.33 universal firmware if you want. It will allow you to flash a custom recovery
Here's 4EXT: http://forum.xda-developers.com/showthread.php?p=20015407
Take a look at this thread as well: http://forum.xda-developers.com/showthread.php?p=16125079
Sent from my Ouya

AndroidSupporter318 said:
1. Since you are s-off, get superCID.
2. Firmware: http://forum.xda-developers.com/showthread.php?p=21711154
3. Flash a custom recovery (4EXT is probably your best choice)
4. Make a nandroid backup via recovery
5. Format all partitions in recovery
6. Flash the ROM you want
If WiFi still does not work, then I would try a kernel that is compatible with the ROM you want.
Your super wipe problem can be easily fixed by flashing a custom recovery.
On step two, you can flash 3.33 universal firmware if you want. It will allow you to flash a custom recovery
Here's 4EXT: http://forum.xda-developers.com/showthread.php?p=20015407
Take a look at this thread as well: http://forum.xda-developers.com/showthread.php?p=16125079
Sent from my Ouya
Click to expand...
Click to collapse
I changed my CID to 11111111. Now which firmware should I get? There are too many and I don't wanna choose the wrong one.
Thanks.

Fidel Castro said:
I changed my CID to 11111111. Now which firmware should I get? There are too many and I don't wanna choose the wrong one.
Thanks.
Click to expand...
Click to collapse
3.33 is the latest firmware. Use the link posted by Androidsupporter318 in point 2 above and follow the instructions on that thread. Remember to check the MD5 sum of the firmware before flashing.

3484jacks said:
3.33 is the latest firmware. Use the link posted by Androidsupporter318 in point 2 above and follow the instructions on that thread. Remember to check the MD5 sum of the firmware before flashing.
Click to expand...
Click to collapse
I saw that about checking the MD5 but I still don't understand it. I download some MD5 checkers and I got the MD5 number but I have no idea what I have to compare it to? It says that MD5 should match. Match with what?
Plus, I cannot use the 4EXT Recovery because it requires INTERNET and as I said already I don't have it due to the ERROR with my WiFi.

MD5 is a long string of characters and numbers. It is used to check whether the file you downloaded was done correctly (not corrupted). After you check the downloaded file's MD5 sum, there should be an MD5 sum on the website where you got the file. Make sure the file's MD5 sum matches with the one on the website to ensure that the file is not corrupted.
About 4EXT, it does not require internet access. I am talking about the recovery image you have to flash via PC. Internet access in required only to download the recovery image
Sent from my Ouya
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
The 4EXT link is in the second post. Make sure you read all the directions
Sent from my Ouya

does he actually need to update his FW. He got OTA ICS so his FW should be okay right?
I don't see you mentioning anywhere in your post that you installed a custom recovery like 4EXT. A custom recovery is neccesay to flash a ROM and other files like superwipe script.
I think the only thing you need to do is install 4EXT, download superwipe and ARHD and flash those. New ROM should fix your wifi problem.
just to be clear; you download the 4EXT recovery file from this site. you place the file in the same folder from where you use fastboot and then flash it on your phone with fastboot. You don't need internet for that. I can't think of a case other then downloading that you need internet for 4EXT.
If it's installed you can acces the recovery by turning off your phone, remove battery for 3 sec, boot by holding volume down + power button, in bootloader(hboot) scroll to recovery with volume buttons and select with power button. If not in bootloader, but in fasboot mode then scroll to bootloader and select it to enter bootloader(hboot). If you installed 4EXT correctly you would recognize the interface of the custom recovery. If not, you'll end up in the custom HTC recovery which is useless for flashing ROMs, and 4EXT is not installed.
you don't need internet for any of this.

onemanshow85 said:
does he actually need to update his FW. He got OTA ICS so his FW should be okay right?
I don't see you mentioning anywhere in your post that you installed a custom recovery like 4EXT. A custom recovery is neccesay to flash a ROM and other files like superwipe script.
I think the only thing you need to do is install 4EXT, download superwipe and ARHD and flash those. New ROM should fix your wifi problem.
just to be clear; you download the 4EXT recovery file from this site. you place the file in the same folder from where you use fastboot and then flash it on your phone with fastboot. You don't need internet for that. I can't think of a case other then downloading that you need internet for 4EXT.
If it's installed you can acces the recovery by turning off your phone, remove battery for 3 sec, boot by holding volume down + power button, in bootloader(hboot) scroll to recovery with volume buttons and select with power button. If not in bootloader, but in fasboot mode then scroll to bootloader and select it to enter bootloader(hboot). If you installed 4EXT correctly you would recognize the interface of the custom recovery. If not, you'll end up in the custom HTC recovery which is useless for flashing ROMs, and 4EXT is not installed.
you don't need internet for any of this.
Click to expand...
Click to collapse
probably he didn't see the link for the recovery.img
also there is no need for superwipe script
format all partittions except sdcard from 4ext is fine

rzr86 said:
probably he didn't see the link for the recovery.img
also there is no need for superwipe script
format all partittions except sdcard from 4ext is fine
Click to expand...
Click to collapse
probably not, but it's recommended if he's going to ARHD since he's comming from stock. precautions never hurt

آm recovery to install a new ROM, I did not prepare a backup, now the phone is not recognized by the laptop, so I can flash a new custom recovery and install a ROM. Friends, can someone help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hard brick? Soft brick? I need help

Please treat a newb gently...
I rooted my phone earlier tonight, followed all the instructions here, and everything went well. I flashed cwm recovery (I was most comfortable with it from an old phone.)
The first thing I did was back up my stock configuration for future use.
I then rebooted and started removing some bloatware. (The real reason I wanted to root.) I got a little overanxious and removed one app I decided I wanted back, so I rebooted to recovery and restored my backup with no problem.
Then, my phone wouldn't boot up out of recovery. So, I removed the battery and tried a simple boot - no luck. To make a long story short, I've booted to recovery multiple times. I've wiped and restored multiple times. No matter what I do though, the phone will not boot to anything but recovery.
Help!

Sounds a bit like the bootloader didn't unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]

How can I fix it?

butch50 said:
How can I fix it?
Click to expand...
Click to collapse
Ezunlock 1.2... Do you still have root?
Sent from my SCH-I535 using xda premium

Correct me if I'm wrong, but Ezunlock requires me to boot to the ROM. I can only boot to cwm recovery.
And yes, I rooted before trying to unlock the bootloader.

Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I've been away from a computer for a couple of days, but that's what I did. Worked like a charm, thanks.

Followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2, cannot mount sdcard to get .tar
blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.

boldred said:
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.
Click to expand...
Click to collapse
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
shimp208 said:
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.
Click to expand...
Click to collapse
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.

boldred said:
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.
Click to expand...
Click to collapse
To use Odin I would first download the latest version of Odin from here. Then I would extract the contents of the .zip file that contains Odin to a folder on your computer. Also I would recommend downloading the I535VRBMF1 firmware from here. Once you have done this click on the Odin .exe file. Now that you have launched Odin I would recommend taking a look at this guide on how to flash the firmware. After you have flashed the firmware to your device and have a clean slate then I would go ahead and use the 1-click by beanstown106 to root, unlock bootloader, and install custom recovery. Feel free to keep asking questions if you need as I'll be happy to answer them.

Here is a list of all .img files in the newest update. Which ones should I NOT flash?

OK so this is going to be a unique question for some reason. I can't find what a lot of these .img files do, and no sites really break it down.
Basically I am rooted/unlocked bootloader on my Google Pixel (from the Google store) and I want to flash everything possible except .imgs that will mess with my bootloader or ones that will wipe my phone.
I understand that flashing all of these are not necessary, as no guides even mention modem.img, but I want to make sure I have the most up to date everything, plus I want to learn what all these imgs are for.
Anyway, here is the complete list:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is pmic.img? hosd? apdp? rpm?
A lot of guides and sites make no mention on a lot of these, and a lot of them seem important, especially in regards to getting the best signal on my phone, battery, wifi reception, and things like that.
So for argument's sake, say I want to manually flash as many of those img files as possible, but without loosing root, without locking my bootloader, and without losing my data, which ones am I free to flash? Everything but boot.img and bootlocker.img? I have no clue!
Thank you very much in advance for any info!

This won't exactly answer your question but first, nothing but you specifically locking your bootloader will lock it. Flashing an updated bootloader doesn't lock it.
I'm running the completely stock ROM but rooted and with TWRP. When the July update came out, I extracted the full update zip, modified the flash-all.bat to remove the "-w" wipe command from the one fastboot command that includes it so I didn't lose any app data. Then flashed the entire stock ROM and made a TWRP backup of the boot.img.
Then redid the fastboot boot TWRP.img, flashed the full TWRP RC2 zip, rebooted recovery, re-flashed SuperSU v2.82 and everything is golden. Note that I downgrade TWRP to RC1 for back up and restore, and use RC2 for all flashing.
I also did a full Titanium Backup to Google drive and also a full TWRP backup before any of this and copied to a flash drive as things happen.
The TWRP backup of the current correct unmodified boot.img has saved me a couple of times when I was away from the computer and did something to cause the phone to only boot to recovery. After restoring the backup just flash SuperSU again.

roirraW "edor" ehT said:
This won't exactly answer your question but first, nothing but you specifically locking your bootloader will lock it. Flashing an updated bootloader doesn't lock it.
I'm running the completely stock ROM but rooted and with TWRP. When the July update came out, I extracted the full update zip, modified the flash-all.bat to remove the "-w" wipe command from the one fastboot command that includes it so I didn't lose any app data. Then flashed the entire stock ROM and made a TWRP backup of the boot.img.
Then redid the fastboot boot TWRP.img, flashed the full TWRP RC2 zip, rebooted recovery, re-flashed SuperSU v2.82 and everything is golden. Note that I downgrade TWRP to RC1 for back up and restore, and use RC2 for all flashing.
I also did a full Titanium Backup to Google drive and also a full TWRP backup before any of this and copied to a flash drive as things happen.
The TWRP backup of the current correct unmodified boot.img has saved me a couple of times when I was away from the computer and did something to cause the phone to only boot to recovery. After restoring the backup just flash SuperSU again.
Click to expand...
Click to collapse
Thanks! I don't want to flash just the update though; I want to flash the entire release as I am going to be using the t-mobile version from now on. I think the only difference is it fixed the t-mobile glitch where wifi calls don't ring.
I do appreciate all the other advice though!
Anyone with any ideas to me original post, please keep them coming because I am desperate to learn!

daddylonglegs said:
Thanks! I don't want to flash just the update though; I want to flash the entire release as I am going to be using the t-mobile version from now on. I think the only difference is it fixed the t-mobile glitch where wifi calls don't ring.
I do appreciate all the other advice though!
Anyone with any ideas to me original post, please keep them coming because I am desperate to learn!
Click to expand...
Click to collapse
I just want to make sure I was clear. I flash the entire "release", if by release you mean not the OTA but the full large firmware.

Not sure why you want to do it this way, maybe I am missing something. Just download the full factory image for t mobile and use the flash all bat file. If you want to save your data and apps edit it and remove the -w from it.
That flashes everything and does it correctly.

TonikJDK said:
Not sure why you want to do it this way, maybe I am missing something. Just download the full factory image for t mobile and use the flash all bat file. If you want to save your data and apps edit it and remove the -w from it.
That flashes everything and does it correctly.
Click to expand...
Click to collapse
Well I looked inside the text files and it doesn't look like the command flashes literally everything. But maybe I'm wrong?
Also I don't want to lose root or lock my bootloader.

daddylonglegs said:
Well I looked inside the text files and it doesn't look like the command flashes literally everything. But maybe I'm wrong?
Also I don't want to lose root or lock my bootloader.
Click to expand...
Click to collapse
It does everything. You wont relock it unless you yourself issue the fastboot command to lock it. Yea, you will loose root which takes two minutes to do.
If you just want to update use FlashFire from Chainfire and use it to install the ota file feom Google. Me, I just flashall after removing the -w from the flashall bat file and the reroot.