Related
Just got my workphone, Droid 2 Global. No stranger to flashing droid phones (my personal phone is a Captivate) I just had to flash it. I mucked it up once or twice flashing Droid 2 Roms on it and needed to get it back to stock. I know a few people have asked about recovering the Droid 2 Global but I haven't seen any instructions to that effect, so here goes:
Droid 2 Global Return to Stock
1. Download RSD Lite 4.9 - http://www.mediafire.com/?ufxs9lft9q2xwnu
2. Download DROID2WE_X6_2.4.29_FULL SBF - http://www.megaupload.com/?d=MD5K1YY8
3. Download Motorla Drivers - http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe
4. Install RSD Lite 4.9 and the Motorla Driver software. Unzip DROID2WE_X6_2.4.29_FULL to a convenient location, i.e. Desktop.
5. Shut off your Droid 2 Global, unhook it from USB or the AC adapter charger.
6. With the phone off, slide open the keyboard, hold the UP ARROW key on the keyboard and hold the power button. This puts the phone in Recovery mode. The screen will display white text and say something to this effect: "Bootloader D0.11, Battery OK, OK to Program, Connect USB Data Cable."
7. Start RSD Lite by clicking on the desktop icon, this brings up the GUI. Click the ellipse (...) next to the Filename dialogue box. If you put the DROID2WE_X6_2.4.29_FULL SBF file on the desktop, scroll down and select it and click Open. The File Properties box should populate with information about the SBF file.
8. Hook your USB cable to your phone, the text on the display will change. Click the Start button and have patience, this takes a while. RSD Lite will extract files to your desktop and begin flashing your phone. Do not interrupt the flash at any point or you will most likely have as nice paperweight.It takes roughly 5 minutes to flash the default rom and RSD Lite will reboot your phone.
9. If the Reboot fails and your phone loops through the starting animation. Pull the battery and put it back in.
10. Slide open the keyboard on the phone, hold down X on the keyboard and push the power button. This puts the phone in Recovery mode. You know you're in recovery mode when you see a triangle with a yellow exclamation and the green android logo.
11. Hit the Search magnifying glass key, this brings you in to the actual menu. You use the Volume Up and Down to navigate here and the Camera button for enter. Power button exits. Use Volume down until you get to the entry which reads Wipe Data/Factory Reset, push the Camera button. This will wipe your data and cache, I had to tap the OK button (The four little square button on the touchscreen) While it was running because the progress bar would stop. Your milage may vary. After it finishes, select the first menu option to reboot and push the Camera button.
That's it in a nutshell pretty much, let me know if I missed anything.
I've been trying to do this all day. My husband installed Liberty on my phone last night and forgot that it was a D2G, so of course it's all kinds of buggy. I'm trying to revert back to stock to try to properly install Liberty on the phone, but I can't get past the RSD Lite section. It keeps telling me "Failed Flashing Process 0x7100."
I've read a few forums about this issue and tried everything I could find. I'm running Windows 7, have run RSD lite as administrator, changed compatibility to Windows XP, moved the sbf file to every folder mentioned, moved RSD lite to the desktop, etc etc. I've also rebooted, uninstalled, reinstalled, in every fashion I could think of.
This is what I get when I check the error log:
17:01:30, May 03, 2011
Line: 868
ERROR: \\?\c:\users\user\downloads\droid2we_x6_2.4.29_full.sbfuèá contains an invalid path.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
17:01:30, May 03, 2011
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
I'm not sure what it means because most of the errors I've seen for RSD lite have been "was not found."
Any suggestions?
Also, I don't know if this is connected (I think it probably is), but for some reason when I plug in the phone it tells me MTP USB driver installation has failed. Each and every time.
Should I try to flash Fission over top of Liberty?
Thanks.
At first glance, i'd say to check the filename. There looks to be a space in what you copied from the errorlog, in the word full. Secondly, i'd redownload the SBF file, it's possible your download is corrupt. You can also try uninstalling and reinstalling the Moto software, it should install the drivers properly in recovery mode. I have windows 7 64bit and did not have to do anything other than what's in my directions.
Shorten the name of the SBF. Like - d2g.sbf for example. Put the SBF in c:\ and let RSDLite look for it there. It is known not handle well long paths or spaces in file name.
Is this supposed to put the phone back at original stock settings with no apps and everything? I can't find any videos of this, but the Droid X sbf guid it leads you back to the touch the android new out of the box screen. I followed this guide and when my phone rebooted, it had all my apps and widgets and stuff still, the only thing that was different was the firmware version had gone back down.
Nevermind, I somehow skipped the last few steps, I must be really out of it, ignore me.
i flashed it twice now and updated it. both times while flashing it told me to restart the device manually and when i did no change, so i closed the rsd and hit ok when it warns me of damaging my phone. phone was already on and running at the time.
Now i cant get my wifi to connect, it authenticates, then goes straight ot disconnected and then trys again.....any ideas of why this is happenning?
Did you follow steps 9-11?
What terrigan said. If you didn't do the last steps, then your phone will maintain all of its settings, but it will revert to the old firmware, 2.4.29 which is what I initially did. I believe that firmware has buggy wifi to say the least which might be the cause of your problem. You should do steps 9-11 and then after that go to settings, about phone, and system updates, and update to 2.4.330
Awesome!
Thank you for the post! You are awesome. Like a noob, I messed up my phone wile rooting/bootstrapping it and couldn't download from the marketplace, get updates installed etc. This fixed it all and I'm back up and running!
No prob, Wish there were more ROMs for the D2G though.
Worked like a champ, thanks!
Thanks muchly! Now that D2G Gingerbread is available, I'm reverting in the hopes to get the OTA update. Just waiting for the stock SBF to finish atm, will let you know how it goes..
Were not going to get the update until a couple more weeks...
Sent from my DROID2 GLOBAL using XDA App
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Chenoaem said:
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Click to expand...
Click to collapse
The steps and the RSDLite software will, you will need to find an SBF for your phone.
Droid 2 (Non Global) SBF: http://www.multiupload.com/R6VS5FFISB
I take no responsibility if this bricks your phone.
failed flashing process?
Hey, I was trying to revert my phone back, and while running RSD Lite, it got to 100% then it said that the flashing process failed?
the status came out as:
"Failed flashing process: Failed flashing process: Phone[0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected"
help please?
Is there a reason why this would work on one phone but not another? I keep getting a failed on one phone with RSD lite I get code error FEBE 0047. I search and says not compatible software, doesn't make sense. Phone stays in boot loop.
thanks for any help.
Hey guys,
Here's my story:
Just bought a brand new D2G from a friend who likes to waste money...he tried to root it using a D2 rom, and gets the bootloader error. I bought it off of him for $50.
Flashed back to the SBF file in the first post, and then I got a message saying a new update was available. It downloaded on the phone, installs, the phone reboots and I saw the android green robot logo with a box, and a status bar. Once it hit 100%, the phone rebooted again, and to the bootload error said "code corrupt, insert data cable"
Tried holding X and power button to go into recovery mode like I did before, but it just boots to this screen....
Battery just died too, so I had to take it to a verizon store where they are awfully kind to recharge it for free.
Any help is appreciated, otherwise I'm just re flashing back to the rom in the first post again, and never updating the phone!
Jon
Find the .330 D2G SBF file and that should solve your problem I think....
Sounds like the update corrupted during install or download.. theres a .330 sbf try it like the above post stated make sure its fully charged low battery can cause major issues
My viewpad 7 is boot-looping, it is restarting before reaching the launcher screen, and also stuck while booting into cw recovery mode. I changed font files of the root before this happened. Any way to restore it's rom without using cw recovery mode? Is it possible to boot from sd card?
Can you boot your VPAD7 into CW Recovery Mode ? (Hold down Vol. UP and Vol. Down buttons and press Power at the same time to get into recovery mode)
Anyway, you most likely need to flash a stock ROM first using the SUTL3_v1.7.9 utility available from Viewsonic and then one of the FM6*.nb0 files - it might not recognize or "see" the device, keep trying & reset/reboot and use that small "reset" button on the bottom if necessary.
Check your FTM (Factory Test Mode) for your Hardware & Software build info - and try to match the closest *.nb0 file for flashing. Hold down Vol. Down while pressing Power to start & run FTM, use tiny pin hole to press & reset device/exit this mode.
I haven't done this in a while, but it will most likely change the device back to unrooted, stock form. And, you will lose all your custom app settings - but it should come to life after a successful flash, restart & give it 5 to 10 minutes to complete initial install & setup - and, you should see your original screen again.
Then, follow steps to get it rooted again, do a NAND backup & set it aside for safe keeping, then reflash your choice of custom Rom, etc. Detailed directions are here on XDA - good luck & let us know if we can be of further help ....
I was making the root to my viewpad 7, and during the process, I took out the cable by accident. And now it's impossible for me that the process finish, it always stuck. Some ideas, please?
luisete123 said:
making root .... and during the process .... took out the cable .... And now it's stuck. Some ideas, please?
Click to expand...
Click to collapse
OMG, okay - relax & take a deep breath ....
It should be recoverable, I think - you will just need to flash the "proper" factory stock ROM first, get it working again & then repeat the rooting process.
First, check your hardware/software version in the FTM mode (it's for diagnostic, flash & download to ROM, etc. ....) & safe to do - hold down the left Volume Down key on top while pressing the Power button with the device off. If necessary, get someone to reset the device (use the smallest pin hole on the bottom of the device.) A pin works best but small paper clip will do.
In a few moment, it will show "Enter FTM Mode" and then display the VPAD7's info -
SWVer=3.410 or whatever is on yours
Model: FM6-0001 or whatever yours say
HWVer: 107 (106, 103 or whatever)
What to do with this info - it will help you select the correct or closest factory ROM to flash & restore your Vpad7 to stock condition, unrooted.
You will need one of the SULT3 or for oldest ROM, maybe SULT2 is better - download & save to PC, unzip the SULT* - and follow onscreen prompt & instructions to select your *.nb0 file.
Another suggestions, since you cannot get into Recovery Mode to wipe dalvik, cache & full system/data first, it might help to flash the *.nb0 file twice - it will take a bit of time, maybe 10 minutes or so and a few more minutes to do its initial boot-up configuration. Be patient - and write down any error messages, etc. if you run into problem.
It's best to take out any SIM card and even mSD card from your device, not required but recommended. When you can boot up again & get pass the Android activation wizard/screen, you can power down - put the mSD card back in and reboot again.
http://vsg.viewsonic.com/ViewPad7/
Good luck - there's a wealth of helpful info posted here, please set aside & take time to read it first & refer to those notes. Good Luck & Cheers - let us know if you succeed ....
A thousand of thanks Letitride!!
Before continue making mistakes, I want to ask if there is any problem to use SULT3 (because I read u posted it before) instead of SULT2, because yesterday, before post my question, I already installed SULT3_v1.7.9...
When I enter FTM Mode, the display shows:
SWVer=3.16R
Model: FM6-0001
HWVer: 106
So now I dont understand. I am a little bit lost, but I think I must to download something else from the viewsonic web that u posted (I can't repeat the link because I am new), isn't it?
Thanks again for your help. I know there are lots of help already posted, but about my problem I didnt find anything, that's why I asked. Thanks!!
Ok, I will explain what I tried, and the next error:
As I said, I already installed SUTL3_v1.7.9, so I used it. I downlodes for the viewsonic web that you posted FM6-316Q-0-1008-A01.nb0, and this is the error that the program said me:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
Maybe I need to uninstall SUTL3_v1.7.9 and try with SUTL2.1_v1.8.4? During the process I don't need to select nothing in the ViewPad screen, do I?
Thanks again!
EDIT:
I installed the SUTL2.1_v1.8.4 (without unistall the SUTL3_v1.7.9, and there is the next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
luisete123 said:
Ok, I will explain what I tried, and the next error:
I installed SUTL3_v1.7.9, FM6-316Q-0-1008-A01.nb0, the error:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
EDIT:I installed SUTL2.1_v1.8.4 (without SUTL3_v1.7.9, and next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
Click to expand...
Click to collapse
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Letitride said:
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Click to expand...
Click to collapse
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I think it was a problem while I was downloading yesterday, because I don't know why, the speed was very very low. Otherwise I can't understand, because in this other laptop that I tried, the Windows is not original, and in mine it is...
So now, as I understand, I can root it without any problems, can't I? I will wait untill tomorrow, because I am on hurry now, and I dont wan't to do any more mistake
I am really greatful Letitride, thanks again!
luisete123 said:
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I can root it without any problems, can't I?
Click to expand...
Click to collapse
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Letitride said:
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Click to expand...
Click to collapse
I am again really thank you! But, I still have the same problem... I am trying to use SuperOneClick v1.7 program, and again get stuck...
I will try with GingerBreak, but I was reading here another post about this program and I will need to read it again, in order not to make another stupid mistake!!
Cheers anyways!!
Moon Shadow's Droid X2 Tutorials - HowTo: Perform a SBF, or "factory restore" of your Motorola Droid X2
Please keep in mind that this tutorial is specifically for the Motorola Droid X2. These procedures MIGHT work for other phones, however, I would not recommend taking the risk of bricking, or even soft bricking, your phone.
Standard disclaimer: I, nor XDA Forums, are responsible for what you do to your phone. Just because these tutorials work for me, does not mean that they will work for you.
I make no claims to be the original owner of this process. I am just consolidating the process into an easy to follow (hopefully) guide that will help everyone from noobs to experienced users.
This tutorial has been adapted from the post: [updated][how-to] sbf tutorial [how-to][updated] by DAG425 who compiled a SBF Tutorial from everything he found.
This method uses Windows! (I know, I'm a Linux guy, but...) My Linux system crashed several months ago and I do not have the funds to purchase new hardware. I can try to assist as I am a mixed environment System Administrator, however, I make absolutely no claims of being a guru. I have heard (not substantiated) that people are having success using Virtual Box. I highly recommend Virtual Box as it seems to be the only free virtualizing environment that supports accessing hardware directly, as long as Linux sees the hardware, Virtual Box and use it (for the most part).
I am making some assumptions in this tutorial:
1. You understand and are comfortable with installing software on a Windows computer.
2. You understand and are comfortable with downloading programs.
3. You understand and are comfortable with extracting compressed files (*.zip, *.rar *.7z, etc.) (I recommend 7zip to extract all compress files.)
4. You are willing to read this entire tutorial and ask questions if something is unclear to you, BEFORE you start this process. (Better to be safe than sorry.)
Now, on to the good stuff…
Hints:
Text in green are applications to launch or buttons to push within an application.
Text in red are warnings.
Orange is reserved for text that must be typed or copied. – Specific commands are also listed in code boxes.
This process will revert your phone to any one of three “Verizon factory original” states.
2.2.2 – Froyo (Why anyone would want to go that far back is beyond me, but I’ll include it anyway.)
2.3.3 – Gingerbread
2.3.4 – Gingerbread
Note: There is a KNOWN problem with the battery indicator and the way Android interprets and displays the battery percentages in Gingerbread 2.3.4. Currently, there is no known fix for this. This problem plagues the original build and any custom ROM based on the 2.3.4 kernel. Until the bootloader is unlocked and we have the source code for the kernel, do not expect this to be fixed any time soon.
UPDATE! Peperm1nt has given us a work around that works. See his post: [MOD]GingerBread Battery Fix v0.8 11/25/11 PSA op update! It has worked well for me and has been integrated with the CM7DX2 ROM.
PLEASE make sure you have a backup of your existing system, or at least your data. To back up your data, I recommend Titanium Backup (TiBu). Purchase the TiBu key, it is WELL worth it! To back up your entire system, goto Moon Shadow's Droid X2 Tutorials - How to perform a backup of your Droid X2. I have performed this method of flashing my phone back to stock using the 2.3.4 SBF file from both Windows XP (SP3) and Windows 7 Professional x64. I have not used or tested the 2.2.2 or 2.3.3 files. The process is identical for all three SBF files.
1. First make sure you have the correct Motorola driver installed on your system (you may have to right click and select "Save Link As").
a. Windows universal 32-bit Motorola drivers version 5.2.0
b. Windows universal 64-bit Motorola drivers version 5.2.0
2. Next download the SBF file you want to load to your phone (you may have to right click and select "Save Link As"):
a. Froyo 2.2.2 SBF File (you may have to right click and select "Save Link As")
b. Gingerbread 2.3.3 SBF File (you may have to right click and select "Save Link As")
c. Gingerbread 2.3.4 SBF File (you may have to right click and select "Save Link As")
3. Once you have downloaded the file, use 7zip to extract the file (whether it ends in .gz or .zip, I recommend using 7zip). You CANNOT just remove the .gz from the end of the filename! It is a compressed file. Using 7zip to extract it will ensure the file is intact and will have the extension of .sbf.
4. Next download RSD Lite and install it. I have used both and currently use 5.4.4. (You may have to right click and select "Save Link As"):
a. RSD Lite 5.3.1 and Drivers
b. RSD Lite+ 5.4.4 - Thanks to motcher41 for getting this to me!
5. Once you have installed the software on your computer, REBOOT it.
6. Turn off your phone.
7. While your computer is booting back up, power up your phone by pressing and holding the VOLUME UP BUTTON and then pressing the POWER BUTTON until you see the words STARTING RSD PROTOCOL SUPPORT (in white) at the top of the DX2’s screen. This should only take about 3-5 seconds.
8. Once your computer has come up completely, start RSD Lite.
9. Once RSD Lite has started, click the three dots (…) in the upper half of the window. It is located to the right of the long blank box labeled Filename:.
10. Using the Open dialog box, navigate to the sbf file and click the Open button.
11. If you correctly extracted the file in step 3, you should see information fill the right hand box called File Properties.
12. Plug your factory Motorola USB cable into the DX2, then into an available USB port on your computer.
13. When you plug the DX2 into the USB port, the RSD Lite screen will update the first line in the lower section of the window (Port No. 1.) with the following information:
Model: SE Flash Daytona
Port Type: USB
IMEI / ESN / MEID: N/A
Status: Connected…
14. If it does not have the preceding information, make sure you are not plugged into a USB hub; if problems still persist, restart the process at step 5.
15. Click Start, and WAIT! Laugh at me, but the first time I performed an SBF, I did it on a computer with an Intel Pentium 4, 2.66 GHz processor, and 1 GB of memory. It took OVER AN HOUR for the SBF process to complete! RSD Lite first backs up what is on the DX2, then it proceeds to flash each of the 5 sections (partitions actually).
16. The Progress and Result columns will update with information as the flash progresses. When the flash is complete, the phone will reboot and RSD Lite SHOULD inform you that the process is complete. If not, you might have to do the process over. You may also receive a message to manually reboot your phone, this is normal and seems to happen about 30-40% of the time.
17. Whether or not your phone boot loops at this time, I HIGHLY recommend performing a factory reset from the Android Recovery menu. This is also the process of fixing the boot loop.
a. Pull the battery.
b. Plug the battery back in.
c. Power up your phone by pressing and holding the VOLUME DOWN BUTTON and then pressing the POWER BUTTON until you see the words FASTBOOT (in white) at the top of the DX2’s screen. This should only take about 3-5 seconds.
d. Press the VOLUME DOWN BUTTON 7 times, or until you see the words ANDROID RECOVERY.
e. Press the VOLUME UP BUTTON and the screen will add “Entering Android Recovery” under the words ANDROID RECOVERY.
f. In about 5-7 seconds, you should see a white triangle with a yellow exclamation point in the middle and a little android down and to the right of the triangle.
g. Press both volume buttons at once.
h. The Android system recovery utility (second line of text) will come up.
i. Press the VOLUME DOWN BUTTON until “wipe data/factory reset” is highlighted.
j. Press the power button to start the process.
k. Once the wipe data/factory reset process has completed, press the VOLUME UP BUTTON until reboot is highlighted.
l. Press the power button to reboot your DX2.
18. Congratulations! At this point in time, you have successfully flashed your phone back to “factory stock”. Now you can root your phone, install a custom ROM, or return it.
Note: If you are going to flash a custom ROM, make sure you SBF the correct kernel for the ROM. For example for CyanogenMod 7 ROM (cm7dx2) you must be on Gingerbread 2.3.4. For the Eclipse v2.03 ROM, you must be rooted and on Gingerbread 2.3.5. For the Liberty ROM, you must be on Gingerbread 2.3.4. Please make sure you read all of the posts in the thread for that ROM. Somewhere in there it will tell you what build you need to be on.
For a great video tutorial, following what I have written out here, se UbuntuBrandon's youtube video: http://www.youtube.com/watch?v=6lfkJ2heXos. Thanks, UbuntuBrandon!
Again, if you have any questions, or comments, either post them here, or PM me! Thanks all!
Ciao!
Just want to add that yes 5.4.4 rsdlite works the same and just fine. I JUST used it an hour ago.
Also wanted to add and easier way to get ur phone to "starting rsd protocol "
Just hold power and VOLUME UP buttons for about 8seconds and it starts rsd protocol. U don't have to scan through any other menus or press anything else. Just hold power and VOLUME UP buttons and it will work. I have done it this way EVERY time I sbf.
((A couple times u referred to RSDlite as SBFlite. ..just trying to eliminate any confusion ))
ashclepdia said:
Just want to add that yes 5.4.4 rsdlite works the same and just fine. I JUST used it an hour ago.
Also wanted to add and easier way to get ur phone to "starting rsd protocol "
Just hold power and VOLUME UP buttons for about 8seconds and it starts rsd protocol. U don't have to scan through any other menus or press anything else. Just hold power and VOLUME UP buttons and it will work. I have done it this way EVERY time I sbf.
((A couple times u referred to RSDlite as SBFlite. ..just trying to eliminate any confusion ))
Click to expand...
Click to collapse
Good to know on the RSD Lite 5.4.4. I hadn't used it yet so I put that disclaimer in there. I don't want to put in information that I personally have not verified. At this time, I haven't had a need to SBF, so... I'm stuck with what I have done. I'll update the OP when I have have the opportunity to actually use 5.4.4.
Thanks for catching the typos. I have fixed them. Also, because the volume down method is intuitive (well, okay, not really), and it is easiest for a user to watch what scrolls by, instead of counting out 8 seconds, I think I will leave it in there. However, if people reach the end of my post and get to yours, I will leave the easier method glory to you.
I truly appreciate your feedback! Thank you again!
Moon Shadow - NM said:
Good to know on the RSD Lite 5.4.4. I hadn't used it yet so I put that disclaimer in there. I don't want to put in information that I personally have not verified. At this time, I haven't had a need to SBF, so... I'm stuck with what I have done. I'll update the OP when I have have the opportunity to actually use 5.4.4.
Thanks for catching the typos. I have fixed them. Also, because the volume down method is intuitive (well, okay, not really), and it is easiest for a user to watch what scrolls by, instead of counting out 8 seconds, I think I will leave it in there. However, if people reach the end of my post and get to yours, I will leave the easier method glory to you.
I truly appreciate your feedback! Thank you again!
Click to expand...
Click to collapse
Sounds good bro.
And I will pass that glory on to MikeJ since that's where I learned it in his sbf thread at droidforums.
And it isn't exactly 8seconds. Just a roundabout. Doesn't have to be exact and doesn't matter if u keep holding a little past when it shows up. When u see it pop up u can just hook ur phone up after rsdlite is started. I usually get my phone ready then open rsd and hook up.
Either way works. I just like being able to get my phone to rsd mode in one step that really can't be messed up. Don't have to press anything after u see rsd protocol at top. About the same amount of time it takes just to show fastboot lol. I apologize for rambling here.
Thanks again!
I just used this method with RDSLite 5.5 and it worked fine. Just an FYI for people.
Droid X2 wont boot up!!!!
Okay i was wonderin does this work if the droid x2 wont boot up, im a noob to this cause i have never Bricked a phone. Ive been rooting and flashing roms since my OG droid to my Droid Bionic, in the middle of flashing a rom my mother knocked my DX2 off tha charger and the battery popped out , i tried booting it back up and it says "failed to boot 1" then reads "starting rsd protocol". I was reading how to sbf back to stock and was wondering did this still work while my dx2 is in this state since it seems to be ready to flash sbf. And another thing it keeps saying "battery to low to flash" but wont charge on wall and usb port only seems to work but still only make it come on for a sec then turns back off, PLEASE HELP
U might have to get an external desktop charger or new battery to be able to sbf if battery is too low.
Or.find someone with and x or x2 and charge your battery up then u should be fine to sbf. As long as u have good amount of charge on battery and can get rsd protocol started u should be fine.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
Also. Next time before flashing the rom make sure u do it with full battery. Once you are in system recovery u can take phone off charger and it works fine. That way u can keep ur phone in a safer place
thank you so much bro...... so your saying in this state it should sbf??
I only recommend trying it if u have a full battery to use. U wont be able to sbf with a nearly dead battery and run the risk of.messing up somehow with a low battery.
it should work fine if u have enough battery. "Starting rsd protocol " is where u need to be before u plug phone into computer. Make sure rsdlite is open on the computer FIRST. And have cable plugged into computer only. Then after u see starting rsd protocol hook it up and wait for rsdlite on computer to say device connected or something along those lines. If it does it should work.
Edit: I should have read ash whole post, I got bored and didn't finish and reposted info he already did.
Haha...I got ur original post in my Gmail lol. I was wondering if my post just didn't go thru lol
U didn't have to edit it out can't hurt to repeat good info
lol thanks, thats okay, it dont hurt 4 me to confirm that the info was correct, i guess i will have to wait to get another battery, will post to let you guys know how it went
I know I have seen some 5$ desktop chargers available on eBay with overnight delivery available for free. Might even find a 3battery&desktop charger for around $15 also...then u will always have that fully charged backup foe that "oh ****" moment. This is why I keep TWO fully charged batteries in my wallet lol. That and the fact that I am always on my.phone and I can drain a battery faster than a toilet flush at a train station
the SBF link is dead, someone here had download it
please share... thanks
un1ocked said:
the SBF link is dead, someone here had download it
please share... thanks
Click to expand...
Click to collapse
I just checked and all three SBF images are working. Which one do you need?
I also check the other files and noticed that RSD Lite 5.4.4 is not working. If anyone has this file, PM me and I will host it. Thanks!
I have a question about backing up... I applied the 2.3.4 update without thinking, and my rooted/supercharged X2 is acting all kinds of funny now. It's like half of it think it's rooted, and the other half doesn't. TiBackup won't work because it can't gain root access, yet I still have SuperUser on my phone and can enter that to enable/disable certain apps. I can still get to the nandroid recovery portion which wouldn't work unless it was rooted. Biggest thing is that the backlight stops working often, and I need to figure out if it's hardware related or borked from the update.
So, my question is how can I back my data up? If I do a nandroid backup, isn't that going to just put whatever messed up state my phone is in back once I SBF? If I can't do a TiBackup I don't see any other option.
@berfles SBF'ing to 2.3.4 will remove root, you need to use Pete's One Root tool. Just google it (apparently I can't post links being under 8 posts? ). As far as you're phone acting wonky, is it because the apps didn't have root?
berfles said:
I have a question about backing up... I applied the 2.3.4 update without thinking, and my rooted/supercharged X2 is acting all kinds of funny now. It's like half of it think it's rooted, and the other half doesn't. TiBackup won't work because it can't gain root access, yet I still have SuperUser on my phone and can enter that to enable/disable certain apps. I can still get to the nandroid recovery portion which wouldn't work unless it was rooted. Biggest thing is that the backlight stops working often, and I need to figure out if it's hardware related or borked from the update.
So, my question is how can I back my data up? If I do a nandroid backup, isn't that going to just put whatever messed up state my phone is in back once I SBF? If I can't do a TiBackup I don't see any other option.
Click to expand...
Click to collapse
I have actually seen this issue posted before, I think its an issue with titanium backup. Im too lazy to do it for you, but a search of this forum should find it. Ash will probably log in soon and find the link for you.
Sent from my DROID X2 using XDA App
EvilTim said:
I have actually seen this issue posted before, I think its an issue with titanium backup. Im too lazy to do it for you, but a search of this forum should find it. Ash will probably log in soon and find the link for you.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Nice hahaha...
one thing I don't know much about is titanium backup tho..
and I don't care much to know anything about it. To me it seems like a pointless app. Especially now that eclipse has the app restore function built in. And if I wanna freeze or remove anything I use bloat freezer(which freezes better) and root explorer(which is the best app ever haha )
That made me laugh eviltim. I needed that before I get to work and get reemed out for being late Monday ((where is that "NNNNOOOOOO" BUTTON lol))
Happy to help ash. And remember, if you show up on time today, with a shotgun, no one will say ANYTHING to you, let alone ream you out for being late Monday.
Sent from my DROID X2 using XDA App
I hit a wall with this issue. After rooting and trying to install a new rom, I am getting the security error on the LG logo. I can access updater with vol+ and insert usb, but I am stuck on how to restore anything or access boot menu. Any suggestions? The computer no longer seems to be able to access the phone as a device via command prompt.
Thanks in advance!
See thread above you...
Sent from my LG-P769 using xda app-developers app
I searched but could not decipher a clear way to fix the problem. This is what I did to fix it.
Open LG Mobile Update (Make sure you have internet on)
Input MEID (located behind battery)
Connect phone to computer via USB in S/W upgrade mode (Vol+ then insert USB)
Let LG download and install phone recovery
NOTE: Recovery stopped at 4% install, but just leave it alone, and it will install correctly. It never went past 4%
NOTE: This will return your phone to factory settings like the day you got it, so you will have to re-root if you use this method.
There may be a way to fix this without losing root, but this was the only way I could figure out.
rarsenaux said:
I searched but could not decipher a clear way to fix the problem. This is what I did to fix it.
Open LG Mobile Update (Make sure you have internet on)
Input MEID (located behind battery)
Connect phone to computer via USB in S/W upgrade mode (Vol+ then insert USB)
Let LG download and install phone recovery
NOTE: Recovery stopped at 4% install, but just leave it alone, and it will install correctly. It never went past 4%
NOTE: This will return your phone to factory settings like the day you got it, so you will have to re-root if you use this method.
There may be a way to fix this without losing root, but this was the only way I could figure out.
Click to expand...
Click to collapse
So,,, How long i must waiting for upgrade recovery completed?
arakenzy said:
So,,, How long i must waiting for upgrade recovery completed?
Click to expand...
Click to collapse
less than 10 minute
rarsenaux said:
I searched but could not decipher a clear way to fix the problem. This is what I did to fix it.
Open LG Mobile Update (Make sure you have internet on)
Input MEID (located behind battery)
Connect phone to computer via USB in S/W upgrade mode (Vol+ then insert USB)
Let LG download and install phone recovery
NOTE: Recovery stopped at 4% install, but just leave it alone, and it will install correctly. It never went past 4%
NOTE: This will return your phone to factory settings like the day you got it, so you will have to re-root if you use this method.
There may be a way to fix this without losing root, but this was the only way I could figure out.
Click to expand...
Click to collapse
I opened a Lg Support tools, find my phone, and when start analyzing phone settings, don´t go ahead stoped a long time on this screen
arakenzy said:
So,,, How long i must waiting for upgrade recovery completed?
Click to expand...
Click to collapse
It depends on your internet connection. The process should take about 1 to 3 hours.
Sent from my LGMS769 using XDA Premium 4 mobile app
I'm stuck right at the end of checking phone settings
kuma82 said:
It depends on your internet connection. The process should take about 1 to 3 hours.
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My LG mobile updater stops just at the end of "checking phone settings" the bar at the bottom shows anywhere from 10 to 15 seconds and stops counting. I never see a %. Is it doing anything?
---------- Post added at 07:17 PM ---------- Previous post was at 07:08 PM ----------
rarsenaux said:
I searched but could not decipher a clear way to fix the problem. This is what I did to fix it.
Open LG Mobile Update (Make sure you have internet on)
Input MEID (located behind battery)
Connect phone to computer via USB in S/W upgrade mode (Vol+ then insert USB)
Let LG download and install phone recovery
NOTE: Recovery stopped at 4% install, but just leave it alone, and it will install correctly. It never went past 4%
NOTE: This will return your phone to factory settings like the day you got it, so you will have to re-root if you use this method.
There may be a way to fix this without losing root, but this was the only way I could figure out.
Click to expand...
Click to collapse
Do you have a download link for the updater that asks for the IMEI? My LG Mobile Updater only asks for phone model.
Also, am I supposed to be doing a regular software update or "upgrade recovery" option?
kg4krw said:
...
Also, am I supposed to be doing a regular software update or "upgrade recovery" option?
Click to expand...
Click to collapse
Hi kg4krw, you could try "upgrade recovery" option.
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
I need help. ;(
arakenzy said:
So,,, How long i must waiting for upgrade recovery completed?
Click to expand...
Click to collapse
Help! it says that my lgms769 is up to date, and everytime i get passed the analysis to download the software, it doesnt download anything, and says time elapsed 23 at the bottom ;( please help me ;(
swaggyp said:
Help! it says that my lgms769 is up to date, and everytime i get passed the analysis to download the software, it doesnt download anything, and says time elapsed 23 at the bottom ;( please help me ;(
Click to expand...
Click to collapse
bro make sure you have unlocked bootloader if you haven't
check the android development forum you will get scripts to put phone in fastboot.
unlock the bootloader
flash CWM recovery
download nanadroid back up for your phone model. from general section.
copy it to ext sdcard, and restore your phone via cwm reovery.
LG's flashing software is just pain to use. use CWM to restore your L9/
er.davinder said:
bro make sure you have unlocked bootloader if you haven't
check the android development forum you will get scripts to put phone in fastboot.
unlock the bootloader
flash CWM recovery
download nanadroid back up for your phone model. from general section.
copy it to ext sdcard, and restore your phone via cwm reovery.
LG's flashing software is just pain to use. use CWM to restore your L9/
Click to expand...
Click to collapse
The problem is my phone cant be read, it doesnt appear. Ever since i tried to install a custom rom, my phone shut off and everytime it turns off and says security error then turns back off.
?
rarsenaux said:
I searched but could not decipher a clear way to fix the problem. This is what I did to fix it.
Open LG Mobile Update (Make sure you have internet on)
Input MEID (located behind battery)
Connect phone to computer via USB in S/W upgrade mode (Vol+ then insert USB)
Let LG download and install phone recovery
NOTE: Recovery stopped at 4% install, but just leave it alone, and it will install correctly. It never went past 4%
NOTE: This will return your phone to factory settings like the day you got it, so you will have to re-root if you use this method.
There may be a way to fix this without losing root, but this was the only way I could figure out.
Click to expand...
Click to collapse
Mines doesnt even download, it just says time elapsed 22 on the software section on the lg mobile update
Thanks in advance.
swaggyp said:
The problem is my phone cant be read, it doesnt appear. Ever since i tried to install a custom rom, my phone shut off and everytime it turns off and says security error then turns back off.
Click to expand...
Click to collapse
swaggyp said:
Mines doesnt even download, it just says time elapsed 22 on the software section on the lg mobile update
Thanks in advance.
Click to expand...
Click to collapse
Connect the phone without battery to computer and install fast boot drivers for omap chipset. Again check the dev section " how to install fast boot drivers"
Unlock the darn boot loader
Flash CWM recovery
Restore via nandroid back .
Offline flash method is bit completed and may not work every time
After trying to restore a nandroid backup via CWM, phone is hard-bricked. Sent to service, where they changed (mother)board.
Just for those, who lost their faith (in LG9) - when you see 'security error' on each boot (like I saw yesterday) after flashing CWM on not unlocked bootloader and, after stock ROM flashing, you see dead android with exclamation heart outside - it is normal, and it is still OK - thanks to bootloader being locked
- u can use any good method to flash stock ROM back - I have used this program combined with official LG Mobile Supprt Tool
- I have turned phone off (by battery removing for a moment)
- kept Volume up pressed when connecting to USB - I had no message that any phone is connected - I didn't bother
- flashed stock (20o in my case)
- saw 'dead' android with its exclamation heart outside - bothered for a moment
- removed battery to restart phone
- I have found that all is working :laugh: back
- rooted with Kingo in a minute
- then a step u can omit - I passed the whole procedure again, as I'm faster then smarter
All done with W8/64-bit and my 10cm nokia usb cable, which I found the best in flashing when some longer or 'filtered' cables do not see the phone
I recently switched phones(both same model optimus fuel due to loose heaphone connection) long story short all my info is on 1st phone(important texts/phone numbers) I only have one battery to share between the two phones(wasn't huge deal!) I could just put battery back in my old phone if I needed info from an old text ect! today I put battery back in and tried to turn it on all it does is blink on and off the screen with Lg logo and security error comes up(won't go anywhere else??) can't understand how all of a sudden this happened sitting around with no battery in it nor was it jarred gotten wet ect?? any help appreciated call or text me at(814)493-7199 Jim thanks
How to unbrick P760 and others, how to install cyjangenmod
How to unbrick P760, how to install cyjanogenmod 6.1
after many hours spend i fixed my two phones l9 - p760
how to:
system xp or windows server 2003 - others dont work for me: 7 and 10
insall drivers - most important omap4430
open program lg B2CAppSetup (LGMobile Support Tool)
use "additional function" - emergency retrieve system
next put your imei number (under battery 15 digits)
push vol+, connect usb cable to phone, put battery and wait like 5 sect till s/w upgrade message appear on phone
in lg application press verification button, now start dowlnoading system and installation
thats it, after 30 minutes you have unbricked phone (any case like: security error, blinkin logo, stay on logo etc)
________________________________________
How to instal android 6.01 marshmallow:
Install root, dowload kingo root, set phone in developer mode: usb debugging, click roo - thats it.
next dowload program flashify
install recovery: twrp-3.0.2-0-p760.img
back and install zip from this page (cyajnogenmod 13)
remember to check twrm and wipe partition - check all options, then reboot
system will instaling from your internal memory (if you put move here )
next you need install gapps, several dont working so dowlnoad this one: A-GAPPS_6.0.1_09022016.zip
how to do that, how to reboot in recovery mode - just click five times in: settings, phone information, number of compilation, exit to settings and find developer options, plug in. here you can plug on root, also advanced reboot to recovery mode to install for example gapps
next enable advanced reboot option. click on power button and reboot in recovery mode
install gapps
now you have working play store
to fix gps for Pokemon go - i did all of this for my two boys search in xda:
I hope i help to somebody.
for me was terrible try to install all of this but i cant belive now how l9 is fast compare to 4.1.2 stock system
regards
Pawel
Ps. no links but the names of application / files you can find on xda for sure.
corrinti said:
Just for those, who lost their faith (in LG9) - when you see 'security error' on each boot (like I saw yesterday) after flashing CWM on not unlocked bootloader and, after stock ROM flashing, you see dead android with exclamation heart outside - it is normal, and it is still OK - thanks to bootloader being locked
- u can use any good method to flash stock ROM back - I have used this program combined with official LG Mobile Supprt Tool
- I have turned phone off (by battery removing for a moment)
- kept Volume up pressed when connecting to USB - I had no message that any phone is connected - I didn't bother
- flashed stock (20o in my case)
- saw 'dead' android with its exclamation heart outside - bothered for a moment
- removed battery to restart phone
- I have found that all is working :laugh: back
- rooted with Kingo in a minute
- then a step u can omit - I passed the whole procedure again, as I'm faster then smarter
All done with W8/64-bit and my 10cm nokia usb cable, which I found the best in flashing when some longer or 'filtered' cables do not see the phone
Click to expand...
Click to collapse
Can someone answer what flashing does NOT mean.
1) It does NOT wipe your user data, correct?
2) It means fix the OS to make the phone start up (without affecting user data), correct?
3) I see people give advice to flash or use S/w recovery tool. But I need confirmation that it doesnt factory wipe or delete user data.
4) Or please tell me what method I should do to preserve the internal SD card, or harvest it, or if there is a way to connect the cord in a certain [phone mode] so I can download the data from a phone that wont start (logo loop).
Thanks.
Oh, you cited me and if u mean LG L9 - I do not remember exactly now, it was a short adventure. There is no general answer to your questions 1 - 3, it depends on the data organization in the system. As far as I remember it was OK for the given procedure, but not for sure . maybe someone else can help. And good but too late for you advice is to make copies of all important data and settings before u try to change anything in your system.
t5678 said:
Can someone answer what flashing does NOT mean.
1) It does NOT wipe your user data, correct?
2) It means fix the OS to make the phone start up (without affecting user data), correct?
3) I see people give advice to flash or use S/w recovery tool. But I need confirmation that it doesnt factory wipe or delete user data.
4) Or please tell me what method I should do to preserve the internal SD card, or harvest it, or if there is a way to connect the cord in a certain [phone mode] so I can download the data from a phone that wont start (logo loop).
Thanks.
Click to expand...
Click to collapse
First time poster, but thought I'd share how I managed to fix my problem, in hope that it helps someone else out.
I recently received the OTA Marshmallow update for my Stock Nexus 9 (unrooted and locked bootloader), but unfortunately it didn't work, and threw me into "bootloop" where it continually tried to apply the update but failed. First off I followed instructions to clear the Cache, which only made the problem worse, as all the tablet would do then was boot into the “swirling colour dots” and do nothing else until eventually the battery died.
After reading several forum posts I discovered that the usual solution is to flash via fastboot, however on a Nexus 9 you need to unlock the bootloader by activating "Enable OEM Unlock" from within Android. As I'm running a 100% Stock Nexus 9 I had never done this, so couldn't flash it.
Eventually though, after having an absolute nightmare trying to get it to work again, I found a working solution! Just use "Apply update from ADB" under Recovery, along with the correct update image!
A lot of what's in the steps below is likely to be known to most of the community, but I’ve tried to keep the steps extra simple so anyone can pick this up.
Steps:
1. Reboot into HBOOT (Hold down Volume Down + Power Button).
2. Press Volume Down to highlight Recovery, then press the Power Button to enter it.
3. Wait until the Google logo goes away, and you should see a picture of an Android laying on it’s back. Hold down the Power Button + Volume Up (very important to hold Power FIRST).
4. On the Recovery page it lists a few details about your version at the top. Note down the 6 character identifier for your device (which is in the format of 3 text characters, 2 numeric, and another text char). For me I was running 5.1.1 before the update, so my identifier was LMY48T.
5. Find the OTA update that upgrades from your current version to the next version. For me I was going from 5.1.1 to 6.0.0 on a Nexus 9, so I searched for LMY48T on Google and found that this was the OTA update needed: https://android.googleapis.com/pack...83199e.signed-volantis-MRA58K-from-LMY48T.zip
6. If you don’t have it already, download and install “Minimal ADB and Fastboot”: http://forum.xda-developers.com/showthread.php?t=2317790 – when it’s installed let it run straight away, and leave the command prompt open you’ll need it in a min.
7. If you don’t have it already, download and unzip the Google USB Driver: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
8. Copy the OTA update file you downloaded to the folder that Minimal ADB was installed in (usually C:\Program Files (x86)\Minimal ADB and Fastboot\).
9. Back on your device use Volume down to get to “Wipe Cache Partition”, and press the Power Button to activate it. If you want to be really sure this will work you should do a “Wipe data/factory reset” too, but be aware you will definitely lose your data.
10. Use Volume up to go to “Apply update from ADB”, and press the Power Button to enter it.
11. Plug your tablet into your PC (if it’s not already). You’ll need to go to your Device settings on your PC and you should see a new device named the same as your device or possibly just “Android”. Go to the Properties of the device and force the Driver to be the ADB Google driver from the Google USB Drivers that you downloaded earlier. (There’s plenty of other longer tutorials on how to do this if you’re having issues)
12. On your PC, in the Minimal ADB Command Prompt (that you should still have open from earlier) enter “adb sideload {NAMEOFOTAFILE}” e.g. for me this was “adb sideload ab835e17c874202049463ccd916f86fede83199e.signed-volantis-MRA58K-from-LMY48T.zip”.
13. Let it run. It took less than half hour for it to install for me, and I’m now the proud owner of a working Stock Nexus 9 with Marshmallow!
So why does this work but applying the stock images via fastboot doesn’t? As far as I can see it must be due to the “signing” of the files. The regular stock Google fastboot flash images don’t include signature information (as far as I’m aware) so they’re rejected as unsafe by the locked bootloader, whereas when you run the OTA update files through ADB sideloading signatures are on the OTA update files, and your device determines that these are safe to install.
Yeah, as long as your system partition is intact, "adb sideload" is a good option. I'm not so lucky...
nothint to do with mine, it doesn't show any OS versione unfortunately.
works well
Hi,
I had exactly the same upgrade failure, despite of a clean stock Nexus 9.
I followed the procedure and it works great for me.
Thank you for this post !
FYI - You don't need to go searching for OTA files on Google. They're all conveniently posted here:
http://forum.xda-developers.com/showthread.php?t=2906492
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
gijosh28 said:
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
Click to expand...
Click to collapse
The same situation, maybe have any other solutions?
I wound up calling HTC and getting an return authorization. I have to pay shipping to them. They cover shipping back to me. But the whole thing is going to wind up taking about 2 weeks. Couple days to get there, 7-10 days to fix, couple back. I haven't sent it out yet. I bought mine at BestBuy, so I was going to see if I could swap it out there first.
Josh
it doesnt show any OS version either, what can i do?
Guide works perfectly. Massive thanks.
The trick is finding the latest OTA zip. Here for the moment.
http://apk-bro.blogspot.com/2015/12/download-android-601-marshmallow-ota.html
I got it to work but I'm never buying another HTC product again. I called warranty service in the first guy refused to help me out unless I had the tablet in front of me. The second guy did help me but I'm still waiting for the RMA ticket, it still has not showed up. So when I got these instructions I managed to resurrect for my Nexus 9 which is good. Now I have a working tablet to which I'm talking to the right now, but other than that HTC still sucks ass and I'm never going to buy anything from them again. Done.
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
harishvr9 said:
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
Click to expand...
Click to collapse
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
harishvr9 said:
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
corkiejp said:
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
Click to expand...
Click to collapse
I did a stock image flash using the Nexus Root Toolkit. But the message is still appearing whenever I restart the device. Otherwise the device is working perfectly.
When I get to step 4, I don't see device identifier text. I got text in pink saying
Code:
" *** Device state - LOCKED *** "
What do I do now
Just got it back from 'repair' via HTC, if anything it's got worse, with random freezes, lock screen freeze and bootloop.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.
Many Thanks!!!!
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
1. Share the link where you like, the Original Finder of this is mentioned in the link
Posted here
2. Have you enabled developer options? Or does Android N not have that feature.
Found the developer options!!
Thanks and yes I found it. I had to reboot my tablet to see the Android version. It must be a bug but I will be happy to deal with a small bug like that. Much better than a bricked tablet. The first thing I did was to enable unlocking of the bootloader in case this happens again. Fool me once but not twice..lol