So anyone figure out why some ROMs fail to flash on to some devices?
I have a theory, I think it has something to do with "fastboot flash partition gpt_main0.bin" failing to flash on certain devices depending on which rom it's sourced from, also depending on which the device currently has already flashed successfully..
Although this is beyond my comprehension, I don't know the reasoning and or the correct wording. Perhaps someone with more knowledge could shed some insight..
I.E. I can successfully "fastboot flash partition gpt_main0.bin" on my device using MX retail, Bell and AT&T versions/copies will fail to flash on my device and I think it is because the last complete successful flash I was able to do with RSDlite was MX retail.
Anyone got any ideas?
The Atrix HD can be a pain
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
TheJeremyWhite said:
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
Click to expand...
Click to collapse
Fails to downgrade.
clockcycle said:
Fails to downgrade.
Click to expand...
Click to collapse
Haha, you're absolutely right. Thanks for pointing that out.
Sent from my MB886 using XDA Premium 4 mobile app
Related
Hi all. I haven't been able to boot my Nexus One for months now. It all started with the random reboot problems that many have reported, but now it won't boot at all. I never rooted it or flashed it with a non-stock Android. It's always run stock OS. If I remember well, the last build installed was FRF91.
I've read dozens of threads, tried hard resetting, Recovery, and the latest thing I tried was a restore with the PASSIMG.zip method explained here http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
It does not seem to have gone well, because step [2]Radio_V2 showed error message "Fail-UZ" and [6] System "Fail-PU". Then it got stuck at the screen attached.
I'm starting to think I've got a faulty battery along with a software problem: when I've got a full charge, I can only perform one operation (power on, recovery, hard reset, whatever), and it usually freezes in the middle of it, usually with that three time vibration. Then, I've got to wait a long time before it can even charge and show the charging LED again.
Any help in getting my agonizing Nexus back will be highly appreciated. Thanks a lot.
Am I seeing what I'm seeing?
You have SHIP S-OFF Nexus, which means - no security. And you're still locked???
Unlock your bootloader, and execute "Unroot/restore" guide from Wiki, for unlocked bootloader. Which means - direct flash to partitions using "fastboot flash" command.
Thanks a lot, Jack. I'll give it a try this weekend. I've got my Nexus as a present at an Android event at Mobile World Congress 2010, that might explain unusual factory settings.
Unlock bootloader OK, but still no restore
I unlocked the bootloader, but still couldn't restore with PASSIMG.zip method. It still gives out radio fail, and restoring the system got frozen at "unzipping". After a long while, it vibrated 7 times, but is still frozen there.
Should I try older stock versions for the PASSIMG.zip restore? I'm using FRG33 right now. Hopefully I didn't brick it.
Thanks again in advance. Best.
Read my suggestion above again, please.
I didn't suggest you to use PASSIMG method. I suggested something else.
Got it
I see what I did wrong, thanks for the response again and putting up with a novice. I somehow missed the link to the Fastboot flash method, thought I was doing the right thing. I'll try fastboot when and if my N1 wakes up from one of it's long slumbers. Best
Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron
first try reinstalling the drivers and try again. if you can get download mode, should be repaired.
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.
Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien
Hey guys, first post. And well, as the video said, I'm a noob!
So I've tried two different guides, but am currently trying to implement this one in different ways.
Now, I do all the steps in order to get the phone connected, which it finds and is successful. I was trying to install the firmware as a single package. Which on the program(odin) side. All goes well.
Now the issue is, which I can't find on the forums or with google. Once the phone boots itself up during the process and the firmware is sent to it. On the screen for a moment I see some debug looking text scroll. It shows 2 folders system/ something. But I can't quite make out the rest as it does this very quick. Regardless, I think it has something to do with access is not allowed? So it quickly skips that and the phone boots up normally. So nothing is installed, and the normal firmware with all the bloatware is just loaded back up.
Odin then just waits a few more minutes and passes it. But obviously nothing happens.
I tried rooting the phone, which was successful. But it didn't help me in attempting the above method again.
I've attempted with odin as well doing what the above guide states as well here "If archive contains only <filename>.tar.md5 select it as PDA and OPS as OPS, leave other fields EMPTY". But in doing so, adding the file to the PDA section, odin reports it's an invalid image type. Then seems all good, but I'm worried in doing it this way, in case I end up bricking the phone.
I been trying to install the firmware "S5830XWKT7_S5830OPPKS6_S5830XWKT3_HOME.tar.md5" Which is the 2.3.6 Australian one.
Any help would be appreciated as to why it's failing on the phone end of things. As the program does seem to issue to use, as it does successfully transfer everything in the first place.
Thanks guys,
Myth.
Im posting here because I am not sure this is phone specific issue, but if you guys could help me that would be great.
Long story short i screwed up my phone, cant recover with rsd so used fastboot...blah blah blah Its up and running except one thing.
WHen the phone boots I see the motorola Logo....but thats it, I hear the droid doing the weird machine startup,,,i plug the phone in to the computer and it recognizes it, i even called from another phone and it rings...
I just cant see anything it black, I also get haptic feedback on the buttons.
I fxz'd with the latest update from verizon...I boot into recovery and i see the little android man, i Islo see the white letters on bootloader, its just when the rom actually loads its a black screen?
If anybody could help i would appreciate it.
Phone is a bionic
Reinstall your android. Your os must hav corrupted. Flash it again.
i have re-installed over 20 times, i think maybe the phone is done??? i accidentally tried flashing a GB fxz before the JB one.....the phone s running but soon as the bootanimation starts for the phone i get nothing on the screen only sound.
SomebodyPleaseHelp said:
i have re-installed over 20 times, i think maybe the phone is done??? i accidentally tried flashing a GB fxz before the JB one.....the phone s running but soon as the bootanimation starts for the phone i get nothing on the screen only sound.
Click to expand...
Click to collapse
from my understanding once you go to JB there is no going back.. Were you getting any errors when you fxz? mine would get an error at step 5 and stop. their was a separate image file for that error which I used and it worked fine. It's on the page. I have bricked mine 3 or 4 times and it always came back to life. I really like this phone. wish it wasn't nearing the end of it's life for support. Times I thought mine was a gonner but it always came back. try redownloading the fxz file.