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.
Related
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
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
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
@BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.
Be aware, and backup before doing this or everything you're dubious about.
Cheers
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them
RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order
I'm stuck somehow, I don't know what to do. I tried flashing TWRP, it said failed, and nothing is happening. Guys, someone help
IAmNotANerd said:
I'm stuck somehow, I don't know what to do. I tried flashing TWRP, it said failed, and nothing is happening. Guys, someone help
Click to expand...
Click to collapse
Do you have the latest SDK platform-tools??
What OS version were you on before you started this process?
Do you know how to fastboot a factory image?
Badger50 said:
Do you have the latest SDK platform-tools??
What OS version were you on before you started this process?
Do you know how to fastboot a factory image?
Click to expand...
Click to collapse
Yes, have the latest SDK tools
Was on Android 9
Not actually. I follow some youtube tutorials to do so.
IAmNotANerd said:
Yes, have the latest SDK tools
Was on Android 9
Not actually. I follow some youtube tutorials to do so.
Click to expand...
Click to collapse
Use the factory image that coincides with your current system, September I would assume. Then follow the directions here.
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Badger50 said:
Use the factory image that coincides with your current system, September I would assume. Then follow the directions here.
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Click to expand...
Click to collapse
Could you walk me through it? Its kinda greek to me
as of now Im with no TWRP and my system says 'No Command' many times, sometimes just gets stuck on the android loading google logo screen. or sometiems says that 'deivce is corrupted' screen
IAmNotANerd said:
Could you walk me through it? Its kinda greek to me
Click to expand...
Click to collapse
After you download the factory image, extract it.
Place the extracted files in your SDK platform-tools folder.
That will include: Bootloader, Radio, the flash-all.bat file, and the large secondary zip you pulled from the factory image.
Right click the flash-all.bat file with your mouse, and remove the -w toward the end of the script, and leave a single space between the remaining words, then save your edit.
This will not wipe your internal data.
Then, put your phone into bootloader mode manually and connect to your pc.
Open a command prompt on your platform-tools folder and type in...fastboot devices...If you see your phone ID displayed, your good.
Now go back to your platform-tools folder and double click the flash-all.bat file to start the installation process.
Let us know how it goes :good:
Badger50 said:
After you download the factory image, extract it.
Place the extracted files in your SDK platform-tools folder.
That will include: Bootloader, Radio, the flash-all.bat file, and the large secondary zip you pulled from the factory image.
Right click the flash-all.bat file with your mouse, and remove the -w toward the end of the script, and leave a single space between the remaining words, then save your edit.
This will not wipe your internal data.
Then, put your phone into bootloader mode manually and connect to your pc.
Open a command prompt on your platform-tools folder and type in...fastboot devices...If you see your phone ID displayed, your good.
Now go back to your platform-tools folder and double click the flash-all.bat file to start the installation process.
Let us know how it goes :good:
Click to expand...
Click to collapse
This is where I am now. Should I go ahead and factory reset my device? Or is there some error during installation? (Kind of thought as it said some files weee missing as attached in the photo there)
IAmNotANerd said:
This is where I am now.
Click to expand...
Click to collapse
You don't appear to be in bootloader mode. That's recovery. With the phone off, hold the power button and volume down until you see the bootloader screen.
Badger50 said:
You don't appear to be in bootloader mode. That's recovery. With the phone off, hold the power button and volume down until you see the bootloader screen.
Click to expand...
Click to collapse
I did the steps you said to me in that mode, then this opened, all on its own.
Also now it’s giving me two options only. Try again, and factory reset, can do one only I suppose.
IAmNotANerd said:
I did the steps you said to me in that mode, then this opened, all on its own.
Click to expand...
Click to collapse
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Badger50 said:
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Click to expand...
Click to collapse
Yep, repeating procedure and updating you soon.
Badger50 said:
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Click to expand...
Click to collapse
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
IAmNotANerd said:
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
Click to expand...
Click to collapse
Yeah, you may have not done yourself any favors when you incorrectly installed twrp.
I now recommend you use the Dueces script. It has saved a bunch of people in your predicament.
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
IAmNotANerd said:
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
Click to expand...
Click to collapse
You can find it here.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Thanks a ton mate! Job done, back to stock now. I really gotta find a way to get a custom now. The tutorial I followed got me in a weird state.
IAmNotANerd said:
Thanks a ton mate! Job done, back to stock now. I really gotta find a way to get a custom now. The tutorial I followed got me in a weird state.
Click to expand...
Click to collapse
Congrats bruh! Now do some reading before you jump into the fire again :good:
Badger50 said:
Congrats bruh! Now do some reading before you jump into the fire again :good:
Click to expand...
Click to collapse
This needs to be said. Read everything you can before doing anything. Read everything about the problems that you might come across. And, most importantly, read about how to fix things if you aren't successful. I knew nothing, apart from what I'd read, and I've managed seven phones and three tablets, plus my brother's phones and tablets. I have never bricked any device, because I read and follow instructions. The great thing is, you can learn a lot from guides and such, because, if you're paying attention, you get a better understanding of what is going on.
He's right...read everything you can before doing anything you don't know how to do or understand. And, just for good measure, ask before, and not after you get yourself into a bad situation
Just my two cents... Is incredible how people takes risk on a 1000 dollars phone...