Related
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder
In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.
im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally
drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.
how did you get it too work???
simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2
I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.
nothing is working out for me this is not fun
same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.
yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that
it appears you can use splashes from the M7 and M8 just take splash.565 or splash1.img and rename to splash1.nb0 and place in empty zip
Big thanks to @iElvis for the VZW android-info.txt and zip
to make your own splash use
[APP] Splash Image Converter And Flasher 2.0
http://forum.xda-developers.com/showthread.php?t=2316060
You must have adb installed.
put splash zip in your platform-tools folder
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip ZIP FILE NAME.zip
fastboot reboot
NOT RESPONSIBLE FOR EPIC FAILS
Here is a couple i kanged
awesome job many thanks!
just a FYI the android-info.txt says 1.32.401.15, while the one for VZW is 1.33.605.15.
can prolly just edit it to say the correct number, but not 100%
Looks nice. I need that black one. Thanks for finding this out..
i changed the version in the info and fast flashed it worked but since it doesn't really effect anything and becuz im fat and lazy gonna leave it :silly:
Any chance of more detailed instructions for those of us not familiar with those tools? I would really like to try to make my own.
xgerryx said:
Any chance of more detailed instructions for those of us not familiar with those tools? I would really like to try to make my own.
Click to expand...
Click to collapse
what you need help with
Karl said:
what you need help with
Click to expand...
Click to collapse
Just like, more dumbed down instructions. What is the platform-tools folder, where do those commands get entered specifically. I tried them in ADB shell and nothing was working. The .bat program was giving me an error about the adb program not being installed. So I guess like a more detailed list maybe?
xgerryx said:
Just like, more dumbed down instructions. What is the platform-tools folder, where do those commands get entered specifically. I tried them in ADB shell and nothing was working. The .bat program was giving me an error about the adb program not being installed. So I guess like a more detailed list maybe?
Click to expand...
Click to collapse
hmm i see... platform-tools folder is a folder inside android sdk program folder.. those commands are entered in command prompt ...in adb shell
the big thing is you need to learn how to use adb and install adb give these a look over
http://forum.xda-developers.com/showthread.php?t=2317790
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=2266638
http://forum.xda-developers.com/showthread.php?t=1474956
https://developer.android.com/tools/help/adb.html
Karl said:
hmm i see... platform-tools folder is a folder inside android sdk program folder.. those commands are entered in command prompt ...in adb shell
the big thing is you need to learn how to use adb and install adb give these a look over
http://forum.xda-developers.com/showthread.php?t=2317790
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=2266638
http://forum.xda-developers.com/showthread.php?t=1474956
https://developer.android.com/tools/help/adb.html
Click to expand...
Click to collapse
Thank you so much! That explains why I couldn't find the fastboot part of it too. I'll do my homework and figure it all out
Karl said:
i changed the version in the info and fast flashed it worked but since it doesn't really effect anything and becuz im fat and lazy gonna leave it :silly:
Click to expand...
Click to collapse
nice thanks for testing. I'm OCD and I like the OS to say the correct one in download mode, makes no different though.
I haven't seen this anywhere yet but does anyone know the name (IE: 0P6BIMG.zip) to flash in bootloader like before? is this still an option? I noticed bootloader doesn't look for zips anymore.
Evocm7 said:
I haven't seen this anywhere yet but does anyone know the name (IE: 0P6BIMG.zip) to flash in bootloader like before? is this still an option? I noticed bootloader doesn't look for zips anymore.
Click to expand...
Click to collapse
ive seen this
Karl said:
ive seen this
Click to expand...
Click to collapse
That's download mode (there is no fastboot usb on the M9).
The file name is 0PJAIMG.ZIP.
That's zero p j a i m g.zip
You need to have the right android-info.txt in the file.
hgoldner said:
That's download mode (there is no fastboot usb on the M9).
The file name is 0PJAIMG.ZIP.
That's zero p j a i m g.zip
You need to have the right android-info.txt in the file.
Click to expand...
Click to collapse
:good:thats the only thing ive seen calling for a zip in reference to his question but it was in download not in boot , wasnt sure of its name or if it was still using them
Didn't think of that. Thanks guys
made the black version splash for updated firmware 2.6.605.10
md5: 9f1ffddf81eafd8115360151e10ce3ea
enjoy
good
has anyone been able to go back to stock splash screen after flashing a splash screen? re flashed firmware, reflashed stock aboot (in android development thread), reflashed no red text aboot (in android development thread), and still see first installed black splash screen. can anyone help? just want to go back to completely stock no custom splash screen.
nice didn't know you could do that
magesticschu said:
has anyone been able to go back to stock splash screen after flashing a splash screen? re flashed firmware, reflashed stock aboot (in android development thread), reflashed no red text aboot (in android development thread), and still see first installed black splash screen. can anyone help? just want to go back to completely stock no custom splash screen.
Click to expand...
Click to collapse
If the stock splash isn't in either of the firmware.zips, RUU may be only way. Unless the M8 one works.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!
Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan
jan_ruc said:
Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan
Click to expand...
Click to collapse
Where are you at right now, and what have you all tried besides the skipsoft?
Badger50 said:
Where are you at right now, and what have you all tried besides the skipsoft?
Click to expand...
Click to collapse
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.
jan_ruc said:
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.
Click to expand...
Click to collapse
Try a different USB cable.
ilal2ielli said:
Try a different USB cable.
Click to expand...
Click to collapse
I don't have any other cables. I will ask my friend to lend me his and try that. But what if that doesn't work?
I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.
Ariac Konrel said:
I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.
Click to expand...
Click to collapse
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?
I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.
dabaang_khan said:
I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.
Click to expand...
Click to collapse
Do you mean Deuces? I tried it. Should I try it again on a different computer?
jan_ruc said:
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?
Click to expand...
Click to collapse
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.
Ran into the same issue few days ago, changing cables and ports didn't help but restarting the computer several times did.
Ariac Konrel said:
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.
Click to expand...
Click to collapse
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...
jan_ruc said:
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...
Click to expand...
Click to collapse
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok ?
Badger50 said:
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok
Click to expand...
Click to collapse
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!
jan_ruc said:
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!
Click to expand...
Click to collapse
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface ?
https://developer.android.com/studio/releases/platform-tools
Badger50 said:
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?
jan_ruc said:
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?
Click to expand...
Click to collapse
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.
Badger50 said:
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.
Click to expand...
Click to collapse
Now I have installed Android Studio and selected the SDK tools that weren't selected before and installed them.
Still my question remains... Since the USB cable is the problem, could I flash it from TWRP? I don't mind keeping TWRP installed so if I could just reinstall the OS. That would be lovely.
On the other hand. Tell me what to do, and I'll do it.
Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img
CyberpodS2 said:
Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img
Click to expand...
Click to collapse
At the moment all I really want is to get this phone working...
I just re-ran the flash-all.bat with the same set of folders as you have and got this:
< waiting for any device >
Sending 'bootloader_a' (36380 KB) OKAY [ 0.937s]
Writing 'bootloader_a' FAILED (remote: Flashing is not allowed for Critical Partitions
)
Finished. Total time: 0.947s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.002s
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: unknown command)
fastboot: error: requirements not met!
Press any key to exit...
So I guess that means criticlal is locked?
I ran fastboot flashing unlock_critical:
fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
EDIT*: I rebooted the phone in hopes of you know... Any progress. It seems to be stuck on the "G" loading screen.
From this point could I just flash a custum ROM via TWRP?
I just want it to work.
Hello guys,
I have been trying to get this to work on my own for a while now. I am trying to use deuces script and it is not working for the life of me. I have formatted user data entirely and killed all encryption. I have tried to install the factory image numerous times and numerous ways but nothing seems to be working. I have tried to use deuces script, from fastboot and it isnt working (log attached).
Here is what is currently going on and the current setup. No ROM installed currently (I do not believe). Device is UNLOCKED. TWRP is installed, version 3.3, latest version.
I can get into fastboot and the computer can see fastboot with fastboot devices command.
I can get into recovery from the device, which is TWRP. I can sideload things from there and run any commands that twrp can natively run.
I can NOT get deuces script to run with either the latest android 9 factory image, or the latest android 10 image.
I am putting all of the factory image files, unzipped, in the platform tools folder, along with the deuces script files in the same folder... then running the script. It is kicking back an error, which is attached as an image.
Additionally the log is attached as well.
ANY insight on how to get my phone back to stock would be great. Really getting anything installed on it would be great at this point, currently I can only get to fastboot and recovery.
Thank you so much!
Try a different cable or USB port if you haven't already.
Also you can try putting everything into C:\platform-tools, instead of having everything a few directories deep.
All my files just get extracted into C:\platform-tools
ilal2ielli said:
Try a different cable or USB port if you haven't already.
Also you can try putting everything into C:\platform-tools, instead of having everything a few directories deep.
All my files just get extracted into C:\platform-tools
Click to expand...
Click to collapse
I always do the same thing with good results!
Sent from my Pixel 2 XL using XDA Labs
wdarea51 said:
Hello guys,
I have been trying to get this to work on my own for a while now. I am trying to use deuces script and it is not working for the life of me. I have formatted user data entirely and killed all encryption. I have tried to install the factory image numerous times and numerous ways but nothing seems to be working. I have tried to use deuces script, from fastboot and it isnt working (log attached).
Here is what is currently going on and the current setup. No ROM installed currently (I do not believe). Device is UNLOCKED. TWRP is installed, version 3.3, latest version.
I can get into fastboot and the computer can see fastboot with fastboot devices command.
I can get into recovery from the device, which is TWRP. I can sideload things from there and run any commands that twrp can natively run.
I can NOT get deuces script to run with either the latest android 9 factory image, or the latest android 10 image.
I am putting all of the factory image files, unzipped, in the platform tools folder, along with the deuces script files in the same folder... then running the script. It is kicking back an error, which is attached as an image.
Additionally the log is attached as well.
ANY insight on how to get my phone back to stock would be great. Really getting anything installed on it would be great at this point, currently I can only get to fastboot and recovery.
Thank you so much!
Click to expand...
Click to collapse
Do it without unzipping the factory image. The script unzips it itself and you're causing an error by doing it for it.
Title
Forget about recovery and unzipping files or scripts.
If you xan boot into the bootloader google gives you precise instructions to follow to just flash everything executing flashall.bat here: developers.google(dot)com/android/images.
If you followed the exact steps and it's not working show the full final terminal output to help you.
JuanG2 said:
Forget about recovery and unzipping files or scripts.
If you xan boot into the bootloader google gives you precise instructions to follow to just flash everything executing flashall.bat here: developers.google(dot)com/android/images.
If you followed the exact steps and it's not working show the full final terminal output to help you.
Click to expand...
Click to collapse
Just for reference, dueces script is use 99% of the time AFTER Google's flash-all.bat had failed to give the desired results. Not saying this is the case here but it is a likely reality.
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
Just for reference, dueces script is use 99% of the time AFTER Google's flash-all.bat had failed to give the desired results. Not saying this is the case here but it is a likely reality.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I (myself *my opinion*) really wouldn't use that script becouse it's just an incredibly verbose way of forcing the flashing of the images and it's way more tedious to find errors using it.
If google's flash-all script is not working it should be analized why as it only is running 5 fastboot commands to flash all the images and if the phone can't run fastboot commands it's somewhat worring.
In his case the script can be failing for a million reasons like the script cant create the work directory to unzip the factory zip becouse it's only for admin use, or maybe has conflicts of directories, can also not be using an appropiate file for it as the naming scheme does not make sense. In any case the problem here is with the way the dueces script is decompressing the .zip as it can't find the image.zip when it's allocated to the variable here: $imgzipname = (Get-ChildItem _work/*/*.zip).fullname.
This script code is really not prepared to correct it self and is not great, HOWEVER it should work without much of a problem if no naming scheme of the images, partitions, directories changes or so I understand why people use it when they really screw something up.
---------- Post added at 09:30 AM ---------- Previous post was at 09:06 AM ----------
JuanG2 said:
I (myself *my opinion*) really wouldn't use that script becouse it's just an incredibly verbose way of forcing the flashing of the images and it's way more tedious to find errors using it.
If google's flash-all script is not working it should be analized why as it only is running 5 fastboot commands to flash all the images and if the phone can't run fastboot commands it's somewhat worring.
In his case the script can be failing for a million reasons like the script cant create the work directory to unzip the factory zip becouse it's only for admin use, or maybe has conflicts of directories, can also not be using an appropiate file for it as the naming scheme does not make sense. In any case the problem here is with the way the dueces script is decompressing the .zip as it can't find the image.zip when it's allocated to the variable here: $imgzipname = (Get-ChildItem _work/*/*.zip).fullname.
This script code is really not prepared to correct it self and is not great, HOWEVER it should work without much of a problem if no naming scheme of the images, partitions, directories changes or so I understand why people use it when they really screw something up.
Click to expand...
Click to collapse
Actually I just realized why the script is not working for you. You are running it against the incorrect file. You shouldn't be running it against the images.zip that's inside of the factory.zip but rather to the factory.zip itself don't unzip it, just paste the whole zip downloaded from developers.google.com and run the script against it.