Related
THIS WILL BE USING THE CM 7.1 ROM. IT WORKS WITH OTHER ROMS TOO. JUST FOLLOW SAME PROCEDURE WITH YOUR ROM.
INTRODUCTION AND WARNINGS:
If you have an Evo 4g updated to android 2.3.5 with hboot 2.18.0001 and your wifi always randomly disconnects this guide is for you! The reason the server disconnects is because your router could be incompatible with your HTC phone. If it's just because of some wifi problems and some easy fixes could be made, I would go with that. But for those who have the same problem, not only will you get a cool Cyanogenmod 7.1 look... you'll be able to play PL with wifi.
I'll try to make it as easy to understand as possible... as I'm not good with this stuff either and it took time to understand the guides. Actually I used several guides but I'll kind of combine them.
This guide is for flashing Cyanogenmod 7.1 and what to do before. I am not responsible if there are any problems with your device. Use this guide at your own risk, although there's 99.99999% chance everything will go right if you follow the guide.
PART ONE:
First you'll want to install this file, you need winrar. Just unzip onto desktop so it's easier. You won't actually be using the tool but the root folder. Read the xda first post first though... http://forum.xda-developers.com/show...75&postcount=1
Here's link to download if you've read the post:
http://goo-inside.me/apps/frigid/
Then you'll want to go to www.htcdev.com.
You'll have to register there and use a real email address.
After you register login and click unlock boot loader. Where there's a scroll-down, choose "all other supported models"
Then click get started, the site will guide you through the next steps. Remember, this could void your warranty, I'm pretty sure there is a way to undo this all but remember do this at your own risk.
Tips: If you can't navigate to the right place remember to type "cd [insert name of root folder]"
To get the address, just go to root folder and click copy address at the top. (Right click on where it shows what folder you're in)
After you have successfully unlocked your boot loader you are ready for part 2.
PART TWO:
Enter fast boot on your phone again.
If you closed your command prompt, (which is fine) open it again.
Download this file and save it:
http://files.androidspin.com/downlo...ECOVERY/&file=recovery-RA-supersonic-v2.3.img
The file should appear in downloads.
Move the file into your folder titled root.
If the file is not named recovery rename it to that.
In your command prompt go the the root folder address like you did in part one.
Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)
Once the prompt finishes the command, go back to main boot loader screen. Then use the volume keys to go down to select recovery.
Press the power button to select recovery.
Once the recovery boots on your phone, select use the volume keys to select/highlight USB MS then press the power button.
Take this zip (don't unzip it) and place it into your sd card (just the root, not in any folders).
Zip: http://download.cyanogenmod.com/get/...nic-signed.zip
Press the power button to exit USB MS.
Now go back to main screen of recovery.
Highlight/select the choice flash zip from sd card and press the power button.
Select/highlight the zip you put in your sd card and press the power button to flash.
Press the power button again to confirm.
Once it's done flashing reboot your phone.
If your phone goes into boot loop (keeps rebooting at cyanogen logo thing) then go to your recovery again and select wipe and select wipe all data/factory reset.
OPTIONAL PART 2.5:
If you're looking for Google apps you might want to flash this too, same thing with the Cyanogen ROM, flash it same way.
http://cmw.22aaf3.com/gapps/gapps-gb...828-signed.zip
This working for everyone?
Do people actually read this? Did I post in wrong section?
Guide updated v1.1
Fixed link to Amon Ra Recovery. Last link worked but file was deleted.
Hey man, I have no need for the guide , but much thanks, sincerely. Thanks
sent from AOKP heaven
Ok... I guess...
so does using that htc super tool folder instead of android sdx not wipe everything while unlocking? Or does it still do a factory reset when you unlock?
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
BigPimpin said:
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
Click to expand...
Click to collapse
have to take it out of disk drive mode i believe and put it in charge only
evo4gnoob said:
have to take it out of disk drive mode i believe and put it in charge only
Click to expand...
Click to collapse
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
BigPimpin said:
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
Click to expand...
Click to collapse
when i did it to my phone i had it in charge only
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Tried disk drive on and off a couple times and still getting stuck on the red exclamation.
BigPimpin said:
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Click to expand...
Click to collapse
Recovery just puts a base place where you can flash roms and stuff.
And if you get a bootloop on CM7.1 yes you will have to wipe all.
As for the recovery flash problem, try putting it on charge only and usb debugging. Then power off phone or just take out battery and reboot into bootloader. Go into fastboot again and try to flash recovery on again. Then try it.
Did you rename the recovery img to recovery? Or if it's not saved as recovery.img rename it to that.
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
BigPimpin said:
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
Click to expand...
Click to collapse
When you go to the bootloader it scans for a PC36IMG.zip file. Normally if you were s-off that's how you would flash a recovery. Since your s-on unlocked the only thing that can be flashed in PC36IMG.zip format is a file signed by HTC like a RUU
Sent from my swiper using XDA App
I got a chance to see some of the names of the missing files it lists when going into boot load. The PC36IMG.zip is one of them that says no image. So guessing that file isn't even there at all. I searched for a PC36IMG.zip file and put it in there and got more then I have seeme before on that screen. I had a blue progress meter on the right side. When it got done it said something about being too old and unsuccessful.
Also, I tried starting all over, even going into the htcdev site again. When I did that all the step worked, but when it's supposed to get to the screen where it tells you it will wipe your phone, that screen never comes up. Now I'm wondering if I can just start all the way over. Can I go into my phone and of I select factory reset, will it make the phone a totally stock phone again and change anything I might have changed? Not that I'm sure I have even changed anything at all to this point.
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
BigPimpin said:
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
Click to expand...
Click to collapse
it shouldnt find a PC36IMG.zip file or the other. Only files in that can be flashed in that format is radios hboots splash screen RUUs recoveries. You shouldnt go around just flashing random things in the bootloader you can end up bricking your phone
Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?
Try a different usb port. then rerun step 3.
me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.
Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
I'm on the US variant so I'm not too familiar with yours. I would suggest starting from stock, and downloading MiFlash, and the latest MiFlash edl package for your variant.
Jay_Nz said:
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
Click to expand...
Click to collapse
Okay, couple o' things:
- If your bootloader is unlocked, there should be a screen when your turn on the phone that says 'Your phone can't be checked for corruption. Please lock the bootloader' which is there for around 10 secs. If you use the volume buttons from there you should be able to select recovery or bootloader
-It is possible that you don't even have a working bootloader mode. IN CASE THAT YOU DON'T HAVE THE SCREEN I PREVIOUSLY TALKED ABOUT, try with adb: install adb, enable usb debugging, authenticate in the phone, "adb reboot bootloader". If it reboots into the bootloader (Should say START in green plus some text) then you can unlock the bootloader. But follow a guide before attempting that, or you'll risk a brick
-Having the stock recovery doesn't necessarily mean that the phone is not rooted. If you have the stock recovery it could be because the previous owner simply rooted it, used it, then flashed the stock recovery and sold the phone like that. Which is really weird in itself
-What you should do to recover from this mess is use MiFlash. Find a package called "A2017_NOUGAT_FULL_EDL" (might have a version number somewhere, just use the most recent). Enable OEM unlocking and USB debugging, then issue "adb reboot edl". The phone seems off but it's not. Now unpack the file and install it to the phone with MiFlash.
After you reflash the system you can proceed with a guide. If you get the warning screen when you turn on the phone then your bootloader is already unlocked and you can proceed with installing TWRP (maybe via axon7tool) then flashing Magisk.
Hey,
I have a problem with my OP6T. I want to boot my phone into the recovery mode. Using cmd i typed: fastboot boot twrp-3.3.1-0-fajita.img and now my phones is stuck with showing on screen oneplus logo, and "Fastboot Mode".
I was following yt tutorial: "Install Custom Rom’s on Oneplus 6 & 6T Step by Step guide" by TechiBee and ended at 5:50.
What can I do now?
Fenkk said:
What can I do now?
Click to expand...
Click to collapse
I assume your phone was up to date? (Android 10) If so you used a very old outdated version of TWRP, and that won't work. Turn the phone off. Hold the power button until it restarts. I believe power plus volume down also will force it off.
Then try it again with the correct version of TWRP from this thread . Don't use the official. The P image is for Pie (Android 9), Q for Android 10, the installer is for both, it is universal.
I didn't watch the video so I'm not sure what else is dated or possibly not correct. For this reason I would suggest Funk Wizards Guide. Also note the section on EFS backups this is the one thing unique to your phone. Hopefully you never need them, but if you ever do it will save you. Make them and keep them somewhere safe, not on the phone.
I have a guide for installing Lineage here. It would also work for most other custom ROMs though. The process is the same.