Develop Bugs

back to stock

I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks

No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452

And actually it might even be a safer approach to revert to stock from a stock like rom http://forum.xda-developers.com/showthread.php?t=1439916

Bricked beyond all recognition baby!
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.

putney1477 said:
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
Click to expand...
Click to collapse
Even if you want to go back to pure stock, keeping/reinstalling both TWRP and FFF are the safest and smartest things to do.

Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2

putney1477 said:
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).

Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2

tamaker said:
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
Click to expand...
Click to collapse
I have the same problem, but my battery was 100% when flashing back. Is this good night for the kindle then?
It boots in to the 6.2.2 software, but these errors pop up and force close then eventually does a restart. Dammit!

putney1477 said:
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.

Dasanko said:
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Click to expand...
Click to collapse
oh ok, thanks

Just a side note after restoring to stock you need to then perform a factory restore as well which will wipe your sd card if all goes well it should smooth out from there

Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?

putney1477 said:
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
Click to expand...
Click to collapse
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).

Dasanko said:
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Click to expand...
Click to collapse
OMG! I can't thank you enought for taking the time to answer all of my questions!!! It worked!!!! I am back to stock! (I had no doubt, thanks to you!) THANK YOU!!!
Heather

[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus

[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus
OVERVIEW
I have created an all-in-one script that will revert your Verizon Galaxy Nexus to stock ICS (Build IMM76K). I have found some of the 'toolkits' to be awesome resources, but a bit flaky when trying to return to stock. This tool is a self-contained EXE and can be run offline as it does not need the internet during the process to download any supplemental files.
!WARNING!
This process WILL WIPE ALL DATA on your phone! You must manually backup all user data, documents and media before performing this process. I take no responsibility for any loss of data to your phone. This script is clean and has been tested, but as with all online guides, this is done at your own risk. Make sure your phone has at least 75% battery before continuing.
WHAT THIS WILL DO
Reset radio, bootloader, and software to factory versions. Unroot your phone. Remove all settings and accounts. Delete all data/apps and replace system apps with old original ones.
WHAT THIS WILL NOT DO
Relock your bootloader or make you coffee.
INSTRUCTIONS
STEP 1: Make sure your phone is UNPLUGGED from your computer, then download and install the Samsung Galaxy Nexus drivers (VZW)
STEP 2: Download/extract my Revert To Stock Tool for the VZW Galaxy Nexus
STEP 3: Power off your phone, then boot into 'Fastboot mode' by holding down both volume buttons and then the power button until you see the screen with the green "Start" arrow (shown below).
NOTE: If your phone boots up normally into your Android OS, then you did not press the buttons correctly. Power off your phone again, and repeat the process until you see the correct screen.
STEP 4: Plug your phone into your computer and let Windows install any necessary device drivers that it detects.
STEP 5: Once it is finished, run the tool (filename: VZW-GNex-RevertToStock.exe), and follow the on-screen prompts to revert your phone to stock ICS (Build IMM76K)
CONCLUSION
Let me know if you have any questions or run into any hiccups along the way. I am always willing to modify the script or the guide to make it more user-friendly.
NOTE: If you receive any virus alert notifications when extracting or running my tool, then know that they are false positives. My executable is clean.

Thread Updates:
2012-02-23:
Added verbiage describing what this script will/will not do.

crobs808 said:
**reserved for thread updates**
Click to expand...
Click to collapse
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!

CorkyRogers said:
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
Click to expand...
Click to collapse
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.

crobs808 said:
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
Click to expand...
Click to collapse
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?

CorkyRogers said:
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
Click to expand...
Click to collapse
If you wanted to lock the bootloader, just boot into the bootloader and run fastboot oem lock. Don't rely on toolkits.
Edit: HA! I just realized what thread I'm in.

Cilraaz said:
Edit: HA! I just realized what thread I'm in.
Click to expand...
Click to collapse
oops?

Zepius said:
oops?
Click to expand...
Click to collapse
Hopefully this is the last question. When I unlocked/rooted I was on build IMM76Q. Would that affect returning to stock?

Zepius said:
oops?
Click to expand...
Click to collapse
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).

Cilraaz said:
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Click to expand...
Click to collapse
Good thing this isn't a ToolKIT then, just a tool
Not sure why someone arbitrarily rated this thread with "1" star. Kinda uncool, since this will help people.

not working
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.

harshybar said:
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
Click to expand...
Click to collapse
Try a different port, or a different computer. Or spin up a VM if you've got one.

Not restarting
Hi! I found this thread linked in the GNex Toolkit 7.8 thread when I was looking for a solution because it failed to flash the stock image & unroot. I followed all the instructions, and pressed enter after fastboot restarted twice, and got to where it says "Flashing stock rom/system". I have now waited 20mins (the tool estimates 5mins), and my phone isn't restarting out of fastboot mode. It has a blue highlighted line on the bottom that says "Fastboot Status - Okay1515.FA02".
Should I keep waiting? re-run the tool? just try restarting my phone manually?
Please help!
Thanks!
Oh! Was running LiquidSmooth 1.5MR1 prior to starting this...no idea if that would still be working or not if I restart now...
EDIT: I got brave - restarting from fastboot manually just restarted Liquid, so it didn't rewrite the system. Some more searching, and I found a different dl link to try for the system image, put it in the right folder, and the GNex Toolkit worked like it was supposed to. I have to say, though, this tool is much less intimidating haha! Thanks!

So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!

mwreeves said:
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
Click to expand...
Click to collapse
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.

crobs808 said:
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
Click to expand...
Click to collapse
I thought that too. I tried 3 computers and 6 cables: nothing worked. It hasn't been able to connect to a computer for a month now and it stopped charging 2 weeks ago. I have looked at replacing the port with a new mic/usb module but the phone still won't boot so it wouldn't really be worth it.

i just did this and it saved my phone!!!! thank you so much

DadamsJR said:
i just did this and it saved my phone!!!! thank you so much
Click to expand...
Click to collapse
You're welcome

crobs808 said:
You're welcome
Click to expand...
Click to collapse
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.

charlie.sears said:
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
Click to expand...
Click to collapse
Asks mods to sticky it

[Q] Recover to stock

Currently my phone cannot boot up, get's stuck at the HTC white screen. I am trying to follow the directions here but I'm having some trouble. I can get into the recovery screen and by doing so it automatically starts loading the PG32IMG.zip file but does not do anything after that and I am unsure how to proceed. So far I have tried installing the .zip using the ClockworkMod Recovery but when I attempt to do so it says it can't open and just says (bad), installation aborted. Currently it is S-ON and I do not know if I can change it to S-OFF if I cannot boot it up. Right now I am waiting for the download to finish for this guide and I will hopefully be able to switch it but in the meantime if anyone has any ideas I would certainly like to hear from you.

Zook024 said:
Currently my phone cannot boot up, get's stuck at the HTC white screen. I am trying to follow the directions here but I'm having some trouble. I can get into the recovery screen and by doing so it automatically starts loading the PG32IMG.zip file but does not do anything after that and I am unsure how to proceed. So far I have tried installing the .zip using the ClockworkMod Recovery but when I attempt to do so it says it can't open and just says (bad), installation aborted. Currently it is S-ON and I do not know if I can change it to S-OFF if I cannot boot it up. Right now I am waiting for the download to finish for this guide and I will hopefully be able to switch it but in the meantime if anyone has any ideas I would certainly like to hear from you.
Click to expand...
Click to collapse
What happened before it got stuck at the white screen? Were you trying to flash a rom?

gtdtm said:
What happened before it got stuck at the white screen? Were you trying to flash a rom?
Click to expand...
Click to collapse
yes. I managed to root it last night and was attempting to add this rom this morning. I don't remember what steps I took exactly (I knew I should have written it down!) and now it refuses to boot up. I am able to get into the recovery mode and access the SD card by mounting it to my PC but that's it.

Zook024 said:
yes. I managed to root it last night and was attempting to add this rom this morning. I don't remember what steps I took exactly (I knew I should have written it down!) and now it refuses to boot up. I am able to get into the recovery mode and access the SD card by mounting it to my PC but that's it.
Click to expand...
Click to collapse
So you are HTC dev unlocked but not s-off if I'm understanding correctly. The flashing steps are a little different. You need to look around for flashing instructions for dev unlocked phones. I believe the Viper rom thread has the instructions, and they work for any rom.

gtdtm said:
So you are HTC dev unlocked but not s-off if I'm understanding correctly. The flashing steps are a little different. You need to look around for flashing instructions for dev unlocked phones. I believe the Viper rom thread has the instructions, and they work for any rom.
Click to expand...
Click to collapse
yes you would be correct in that understanding, is this the one you are talking about?

Zook024 said:
yes you would be correct in that understanding, is this the one you are talking about?
Click to expand...
Click to collapse
Yes, his install instructions from that OP are:
Be s-off (or dev unlock)
Install a custom recovery (twrp/4ext)
Download the ROM and place it on your external SD card.
Do a nandroid backup!
Start rom install process and make sure you select to wipe data in aroma
Select your desired setup in aroma, and finish
Reboot the device and enjoy!
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
I'm not dev unlock, so I've never actually done this, which is why I'm not being more specific. The boot.img is already in the zip you downloaded for the rom.
If you look in this thread, the phone is different, but the flash steps should be identical according to my understanding:
http://forum.xda-developers.com/showpost.php?p=28301167&postcount=1

gtdtm said:
Yes, his install instructions from that OP are:
Be s-off (or dev unlock)
Install a custom recovery (twrp/4ext)
Download the ROM and place it on your external SD card.
Do a nandroid backup!
Start rom install process and make sure you select to wipe data in aroma
Select your desired setup in aroma, and finish
Reboot the device and enjoy!
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
I'm not dev unlock, so I've never actually done this, which is why I'm not being more specific. The boot.img is already in the zip you downloaded for the rom.
If you look in this thread, the phone is different, but the flash steps should be identical according to my understanding:
http://forum.xda-developers.com/showpost.php?p=28301167&postcount=1
Click to expand...
Click to collapse
well I managed to install the ROM successfully but it still refuses to boot up, I've run out of ideas at this point, no idea why it refuses to boot up.

Zook024 said:
well I managed to install the ROM successfully but it still refuses to boot up, I've run out of ideas at this point, no idea why it refuses to boot up.
Click to expand...
Click to collapse
More details will be very helpful to any of us that might be able to help you.
What rom are you trying to install?
What do you mean by won't boot up. Are you getting past the HTC screen now?

gtdtm said:
More details will be very helpful to any of us that might be able to help you.
What rom are you trying to install?
What do you mean by won't boot up. Are you getting past the HTC screen now?
Click to expand...
Click to collapse
my apologies, I had originally attempted to install this ROM. I thought I had followed the directions to the letter, obviously I screwed up somewhere. I then attempted to perform a factory reset from the ClockworkMod Recovery which yielded no results. I then attempted the Viper ROM, again wiping the data and that said installation was successful. Still it refused to boot. I then tried this return to stock and with that, the .zip folder is automatically loaded but then does nothing. As of right now I cannot get past the HTC screen.

Zook024 said:
my apologies, I had originally attempted to install this ROM. I thought I had followed the directions to the letter, obviously I screwed up somewhere. I then attempted to perform a factory reset from the ClockworkMod Recovery which yielded no results. I then attempted the Viper ROM, again wiping the data and that said installation was successful. Still it refused to boot. I then tried this return to stock and with that, the .zip folder is automatically loaded but then does nothing. As of right now I cannot get past the HTC screen.
Click to expand...
Click to collapse
Well don't panic first of all. It's not super easy for me to figure out what's going on because your setup is quite different from mine, but I'm willing to offer any knowledge I have gleaned from reading these forums (a lot).
When you tried to go to stock, you went to the bootloader and it found the PG32IMG? Or it just stayed on the options screen of reboot, recovery, factory reset, etc?
If it found the PG32IMG did it give you any messages? Did you check the md5 sum before trying to load it?

gtdtm said:
Well don't panic first of all. It's not super easy for me to figure out what's going on because your setup is quite different from mine, but I'm willing to offer any knowledge I have gleaned from reading these forums (a lot).
When you tried to go to stock, you went to the bootloader and it found the PG32IMG? Or it just stayed on the options screen of reboot, recovery, factory reset, etc?
If it found the PG32IMG did it give you any messages? Did you check the md5 sum before trying to load it?
Click to expand...
Click to collapse
haha too late for that, I'm already freaking out. It does find the PG32IMG automatically as I said and proceeds to load it. I was able to catch the message it flashes before it goes back to the default list, "wrong zipped image!" That doesn't sound good. I had not checked the md5sum prior to this, just did so now, says the codes do not match. Pardon my utter cluelessness but what on earth does that mean?

Zook024 said:
haha too late for that, I'm already freaking out. It does find the PG32IMG automatically as I said and proceeds to load it. I was able to catch the message it flashes before it goes back to the default list, "wrong zipped image!" That doesn't sound good. I had not checked the md5sum prior to this, just did so now, says the codes do not match. Pardon my utter cluelessness but what on earth does that mean?
Click to expand...
Click to collapse
You need to post the md5 sum from the return to stock thread, it is right below the download. If it doesn't match after that, you have a bad download and need to download it again on a good connection. I can't see the md5 very well in your screenshot, but it looks like it is correct. Then the other thing to check is that windows didn't add an extra .zip to the file name. You'll have to go into folder options and make it show known file types then see if it says it is PG32IMG.zip.zip or something. I'll keep looking around to help, but I'd suggest reading through a lot or all of that return to stock thread.
Is the file in the root of your microsd or in a different folder like downloads?

gtdtm said:
You need to post the md5 sum from the return to stock thread, it is right below the download. If it doesn't match after that, you have a bad download and need to download it again on a good connection. I can't see the md5 very well in your screenshot, but it looks like it is correct. Then the other thing to check is that windows didn't add an extra .zip to the file name. You'll have to go into folder options and make it show known file types then see if it says it is PG32IMG.zip.zip or something. I'll keep looking around to help, but I'd suggest reading through a lot or all of that return to stock thread.
Is the file in the root of your microsd or in a different folder like downloads?
Click to expand...
Click to collapse
Ok I corrected myself with the md5sum checker and now it confirms the codes match. I then doubled checked the file extension and it looks good as far as I can tell, I did not see a double .zip.zip anywhere, even after I selected "show file extensions of known files". I just tried again and got the same message,
"Checking....[PG32IMG.zip]
Wrong zipped image!
Loading...[PG32IMG.nbh]
No image or wrong image!"

Zook024 said:
Ok I corrected myself with the md5sum checker and now it confirms the codes match. I then doubled checked the file extension and it looks good as far as I can tell, I did not see a double .zip.zip anywhere, even after I selected "show file extensions of known files". I just tried again and got the same message,
"Checking....[PG32IMG.zip]
Wrong zipped image!
Loading...[PG32IMG.nbh]
No image or wrong image!"
Click to expand...
Click to collapse
Well, I'm running out of ideas. Hopefully someone else can chime in. I'd try downloading again and make sure the md5 is good, put it on the root of the microsd, and try one more time. Other than that my knowledge is spent.
Sent from my Incredible 2 using xda app-developers app

gtdtm said:
Well, I'm running out of ideas. Hopefully someone else can chime in. I'd try downloading again and make sure the md5 is good, put it on the root of the microsd, and try one more time. Other than that my knowledge is spent.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
well I certainly appreciate you trying to help anyways. just on a hunch I tried running through the steps of the HTCdev bootloader which I had originally done and after doing so, it now says the following,
"Main Version is older!
Update Fail!
Press <POWER> to reboot."
that is interesting, should I try the VIPER ROM again and see what happens now?

Well I am happy to report now I have figured it out! I managed to find this video and by following his steps, I was immediately able to get the Viper ROM up and running. So I guess that is what I was doing wrong, trying to follow the S-Off Method when I had already gone halfway with the HTCDev method. Very glad I was able to get it done tonight, another case of "if I can break it, I can fix it!" case closed.

Zook024 said:
Well I am happy to report now I have figured it out! I managed to find this video and by following his steps, I was immediately able to get the Viper ROM up and running. So I guess that is what I was doing wrong, trying to follow the S-Off Method when I had already gone halfway with the HTCDev method. Very glad I was able to get it done tonight, another case of "if I can break it, I can fix it!" case closed.
Click to expand...
Click to collapse
Awesome. I'm glad you figured it out.
Sent from my Incredible 2 using xda app-developers app

Stuck at boot.. can get into bootloader but not sure what to do next...

Hi everyone, this all started when I tried to flash a patched boot image for root and seemed to get worse from there. There's no data on the phone that I care about so just wiping it and getting it to boot would be preferable.
I've tried using the skipsoft toolkit (I have the ultimate version if that helps any) to try and get it to flash a freshly downloaded stock image, but for whatever reason after answering all the questions it extracts everything, does all the checks, then says "device is not set" and just jumps back to the main menu.
I've tried downloading the factory image right and running the flash-all script, it goes through the entire process which looks promising, but then just reboots the phone, I get the nice "your device is corrupt" message, press the power button to continue, but then it just hangs at the white "Google" splash screen with the little unlocked icon at the bottom, and doesn't move past that.
I know the version that I had on here prior to the problems was 8.0.0 (OPD1.170816.010, Sep 2017), so that's the one I've been trying to work with.
Not really sure where to go next, hoping someone has some advice for me.
Thanks everyone.

how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again

Never use a toolkit, they can hide error messages and displays that can help diagnose some issues. Always try the step by step methods to rescue provided by the excellent guides available here.

uicnren said:
how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again
Click to expand...
Click to collapse
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..

krash2k said:
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..
Click to expand...
Click to collapse
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.

uicnren said:
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.
Click to expand...
Click to collapse
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.

krash2k said:
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.
Click to expand...
Click to collapse
:good:

uicnren said:
:good:
Click to expand...
Click to collapse
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)

krash2k said:
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)
Click to expand...
Click to collapse
honestly, Im not sure. But I also didnt think it would make a difference when flashing the stock images back, but it does. I guess anything is possible.

Yep.. it definitely did. I guess this is a lesson for knuckleheads like me who start messing around before properly updating everything.
I just did all of the same things I did earlier, and it booted fine, with root. Lots of wasted hours over a dummy move.
Thanks again for all the help!

I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?

State.of.mind said:
I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?
Click to expand...
Click to collapse
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:

Badger50 said:
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:
Click to expand...
Click to collapse
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command

State.of.mind said:
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command
Click to expand...
Click to collapse
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.

v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
On second thought I think that it didn't work because I didn't have the factory image unzipped inside of the platform tools folder? The good news is that I'm up and running

v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?

nickmilla15 said:
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?
Click to expand...
Click to collapse
Go back to the basics. Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december). Add that folder to your path statement/environment. Download the FULL image (not OTA). Open that zip file and extract into the same ADB/fastboot folder. Do not unzip the included, nested zip file! Open flash-all.bat and remove the -w switch and SAVE. Boot your phone to the bootloader, and then run the script either way (clicking or fastboot window). There are SO MANY better guides/tutorials out there to follow step-by-step. Maybe read/post in those if you have any further issues. Best of luck.

v12xke said:
Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december).
Click to expand...
Click to collapse
This was my mistake when I was having all of those problems. I was using older versions of adb/fastboot. Everything looked like it was installing alright but then it would just keep bootlooping.. was very frustrating. It was a relief when replacing those binaries with the updated ones worked flawlessly.

if you have managed to get it work then have fun otherwise just use deuces script as per the instructions provided in op.

Pixel 2 xl bricked i think so..

Hey guys i have a serious problem..i tried to unlock bootloader and install another rom but my phone i think so its dead... :crying: I unlocked it succesfully,installed twrp,then rom by recovery mode,i made reboot the device,and the rom wasnt installed,so i made again reboot device in twrp by the tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and then it was like everything was deleted..no partitions nowhere,like everything had gone..and now i cant even reboot on twrp just on fastboot and i can only lock/unlock my bootloader.When i lock i take the message "Cant find vaild operating system,The device will not start....:crying: The case is that i didnt made any kind of wipe...how its possible this to happen?Can any professional guy help me here because i tried so much to bring it back to the normal condition but i dont see any solution anymore..

You have a Pixel/Nexus device. Download and flash the factory image the correct way from Google and start over.

Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..

Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Good instructions at top of this page, then the download for your phone model is below.
If you do not understand any step, Google it, then read and understand completely
before proceeding. Be sure you have most current version of Android Tools.
https://developers.google.com/android/images#taimen

Don't panic and make it worse. Make sure you have adb/fastboot environment and drivers on your computer and follow the directions for reinstalling stock.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!

Yeah as others above have said, don't panic. I've been flashing/ rooting/modding since the way back and one thing I've learned is, it's VERY hard to brick a phone completely. Especially with newer ones, there's almost always a way to recover your phone, and especially since you have fastboot, you're not bricked either. Flash the stock rom through fastboot and you should be all set!

also make sure that your cable is good. i had major problems with many cables. finally one cable actually worked. took me hours to realize tha the cables were the culprits.

I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.

mac796 said:
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
Click to expand...
Click to collapse
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!

thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
Az Biker said:
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Click to expand...
Click to collapse
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)

Jinthegodstyle said:
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Click to expand...
Click to collapse
Dude. Start from scratch. Can you get in fastboot and is your bootloader unlocked? Are you doing this all with a tool or are you manually putting in commands It's hard to tell you what to do without all the info.
Edit.... Just saw you used a tool.... I don't care for tools. because of stuff like this. The tool should have installed the adb folder on your computer. Find that folder and open it. Download the Google zip file with stock os and Unzip into your adb foldee or SDK folder . Open the file from Google. While in there open a terminal. Have phone in fastboot mode and plugged in. Type "fastboot devices"
If it shows a number, you are connected.
Now run the bat file and it should install the os
Read all the way through then reread it .
Carefully follow steps. Forget about twrp for now.
https://developers.google.com/android/images
Don't forget to open terminal as administrator

Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!

Jinthegodstyle said:
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Click to expand...
Click to collapse
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches ?

Badger50 said:
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches
Click to expand...
Click to collapse
Thx for advice mate!! Finally after yesterdays adventure with my new toy,today i flashed without any issues in 5 minutes the rom i wanted and it was more easy than i imagined..you see after many xiaomi phones i was confused and couldnt imagine how easy could be on google phones..Now i wont touch nothing since evertything works preety good!! Thx again!!

CyberpodS2 said:
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
Click to expand...
Click to collapse
when rma'ing it, one should defo go with locking bootloader though, i reckon.

xflowy said:
when rma'ing it, one should defo go with locking bootloader though, i reckon.
Click to expand...
Click to collapse
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?

I always always always make sure the device boots before i ever lock the bootloader. I've read to many horror stories.

With this kind of phone, i think anyone should refrain from using any kind of so called "tool", aside from the basic adb n fastboot itself.

Badger50 said:
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
Click to expand...
Click to collapse
does this also apply to the critical unlock method or do i, at least, have to lock critical?