Database Info

[I9020A] Nexus S, Master Clear?

Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...

Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.

Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?

Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do

Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)

Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that

Stuck in bootloop

Now first off I'd like to start saying that I've seen a few threads from a search with this issue but none of them matched my case perfectly or solved the issue.
I have an AT&T HTC One X and was running CleanRom DE 1.0
I saw there was an upgrade out and tried installing the upgrade. I tried running the RUU but it gave me an error 155 (Unknown error). Thinking that it did not matter to much, I tried to install the new version anyway. This got me stuck in a boot loop of the boot animation for about 1 second, then rebooting. I have CWM recovery installed and can adb/fastboot but I cannot do much else. I pushed a 1.7 rom to my sdcard but CWM gives me the message, "Error: Cannot mount /sdcard/"
My phone is unlocked but locking it did not change anything, still could not load anything or use the RUU.
I've seen other threads saying to Lock the phone, then flash the ruu and I guess I'm a little confused on that. By saying "flash the ruu" do you mean just running the .exe file or doing something with fastboot flash? I'm stuck without a phone right now and any help would be appreciated.

In my situation, I deleted the user memory and dalvik cache. I then did some research on my phone's exact stock ROM. I flashed the ROM and basically started off fresh. It may not be the most convenient. But, it may be what is needed. It sounds as if your phone is 'soft-bricked' so this should work as the last ditch effort.
Best of luck!
Sent from my MB865 using xda premium

Thankyou for your reply, I'm new to android and I'm wondering what exact steps went into flashing the stock rom onto your phone? Let's assume I already have that stock rom. Are you just using fastboot flash boot rom.zip ? or using CWM?
EDIT: My phone is now booting! I kept launching the RUU and after about four times it decided to work. Back to the stock AT&T rom, and right now I'm great with that.

[Q] How do I unbrick my phone?

So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.

Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)

WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.

Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel

What went wrong?

I was pulling my hair out for a few hours last night trying to get my phone back to a functional state. Fortunately I was able to do so, but I have no idea what caused all of my problems. Here's what happened:
I was running CM10 on my HOX (from this thread) for awhile now. I was having a few issues with it that were annoying but I didn't want to change the ROM and have to restore everything. I then got a notification for an update to CM10.1 so I downloaded that and installed it. During this process I decided to do a Factory Reset in TWRP.
Once I was booted back into CM10.1 I was having all sorts of strange issues, but the biggest one was that I was unable to connect to my cell network and it kept prompting me to restart. I decided I would just install another ROM so I downloaded CleanROM JL Beta 1 (here) and the Bulletproof-1.0 kernel (here).
I booted into TWPR and proceeded to wipe everything (i.e. clicked all of the buttons under the 'Wipe' menu). I've done this before and haven't had any problems. I then proceeded to install the kernel. It went through the installer fine without any issues. When I tried to install CleanROM JL Beta 1 in TWRP it just kept giving me an error and wouldn't bring up the installer.
I went back and forth trying to install multiple ROMs and every single one would give me an error. I thought I was screwed because I couldn't install an OS on the phone. I also went ahead and installed the stock kernel hoping that would fix the problem but it didn't. I eventually decided on finding the RUU to get me back to bone stock.
I downloaded the 2.20 RUU and relocked my bootloader. I went through the RUU process and everything is fine now, except the fact that I have a stock, bloated phone again.
Was it the kernel that messed me up? I installed it after I wiped everything and I'm not sure if I was supposed to do it that way. I'd like to get back to something stable again but I am not sure if I am able to since I relocked my bootloader and installed the 2.20 RUU. Any help is much appreciated, thanks!
NEW ISSUE #1: I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?
NEW ISSUE #2: I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?

redpoint73 said:
If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?
Click to expand...
Click to collapse
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.

afrat said:
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.
Click to expand...
Click to collapse
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine. I then tried installing CleanROM JL Beta immediately after and it would just give me the zip error.
What I mean by "after the ROM wouldn't install" was after it wouldn't install via TWRP. I then went back and extracted the boot.img, flashed it with fastboot, then went back into TWRP to try and install it again. That didn't work.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.

eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.
Click to expand...
Click to collapse
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.

afrat said:
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine.
Click to expand...
Click to collapse
If you keep reading on the Bulletproof instructions, you will see:
hboot 1.14+ and S-ON:
The installer includes a method to flash the boot.img for S-ON devices using hboot 1.14 or higher;
however, some people still have difficulties. If it doesn't work:
1. extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img​
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have?
Click to expand...
Click to collapse
With hboot<1.14, or with S-on yes. But in his case no. For hboot 1.14 and higher and S-on, you can flash the kernel before or after the ROM, it doesn't matter since the kernel can't be flashed from recovery.
---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------
afrat said:
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.
Click to expand...
Click to collapse
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.

redpoint73 said:
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.
Click to expand...
Click to collapse
I'm not sure. If I did the RUU, does that mean I lost the custom recovery (TWRP) that I've installed as well?

I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?

I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

afrat said:
I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
Click to expand...
Click to collapse
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw

eraste said:
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw
Click to expand...
Click to collapse
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!

afrat said:
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!
Click to expand...
Click to collapse
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?

eraste said:
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?
Click to expand...
Click to collapse
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.

afrat said:
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.
Click to expand...
Click to collapse
Strange. Really strange.

eraste said:
Strange. Really strange.
Click to expand...
Click to collapse
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.

I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.

afrat said:
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.
Click to expand...
Click to collapse
Yes ruu would have put you back to stock with the exception of supercid that would have stayed.
iElvis said:
I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.
Click to expand...
Click to collapse
Me to this was my initial thought super cid was the culprit!

eraste said:
Me too this was my initial thought super cid was the culprit!
Click to expand...
Click to collapse
But some others insisted that it couldn't have been the issue. SuperCID is supposed to allow flashing of any updates regardless of CID restrictions.

No operating system left after GPE flash fail - plz help!

After literally two weeks of reading thread after thread attempting to understand this , I tried to go from a sense ROM to a GPE ROM and I tried to flash the GPE firmware following Digital high's instructions here..
Things did not work out as instructed I'm afraid and that is probably due to my not understanding enough....nevertheless following DH instructions left me with repeated flash failures. Finally the following flashes got me from firmware 5.0.1- the firmware I was already on- to this:
fastboot flash zip VZWm8LfirmwareTWRP.zip - success; followed by the same ' flush" flash - again, success:
then:
fastboot flash zip 5.1_6_firmware+hboot.zip - and again another "flush" flash with success
From the way I read it we are then to reboot to bootloader and proceed further with recovery flashing the rom, blah, blah.... , however, my little android guy is overlaid with a black screen (instead of white) and he is dead. I rebooted to recovery to see if I could flash the sinless GPE ROM which is my goal in the first place (yes I realize it is a 4.4.4 but NOTHING flashes in recovery now) but now I m out of ideas. I have no workable phone and I have to get my ass to a new job in the afternoon. Can anyone help with either finishing my goal to install the sinless ROM or restore back to the adrenaline ROM I was running? I don't want to restore as I am afraid I may have altered the firmware and thus brick if I do restore...PLEASE HELP!!!! PLEASE!
right now my phone is sitting on the charger on the dead android screen. i don' dare touch it. What should i do?
Update: I am flashing digital highs GPE_5.1-multi_dh_051215.zip and I am getting a bootloader remote 24 "parsing android info fail". Does anyone know what that means or how to fix?
Update again: Figured out this needs to be flashed in recovery and not fastboot. Now I have been booting for about five minutes now. Hope I'm not bootlooped. ....

Figured it out
Got it figured out.
Mods, could you please close the thread. thanks!

kerryh said:
Got it figured out.
Mods, could you please close the thread. thanks!
Click to expand...
Click to collapse
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.

cntryby429 said:
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
Click to expand...
Click to collapse
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?

kerryh said:
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
Click to expand...
Click to collapse
When compared to the steps I took to flash the 6/15 build as cleanly as I could manage, here's what jumps out to me as strange or unnecessary:
-I don't know what the '5.0.1 firmware' is but I suspect it's the same as the 'VZWm8Lfirmware.zip' you flashed next. I chose to run the 5.0.1 RUU and considered that as complete of verizon 5.0.1 firmware as there is.
-I don't think that superCID has been necessary for DHs GPE for some time. I don't know that it would necessarily cause a problem but I've never gone to superCID and have had no problems
-flashing DH's carrier-agnostic 5.1 firmware is stated as optional in his OP and I think DH himself admitted a little while back that it may actually be the cause of some folks' wi-fi issues
Regarding restoring old nandroids to a system with updated firmware, I can say that each time a new official software has been released, I've flashed tigerstown's firmware-only zips alongside whatever custom rom I was running at the time with no issues. This points to a trend of successfully running roms on top of newer firmwares without issues. I know of many 5.x roms saying that you must update firmware but I've never read about a 4.x rom having issues with 5.x firmware. I don't think there's much risk of flashing a custom rom (or restoring a nandroid) from recovery that doesn't match the firmware beyond a possible bootloop.