Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
nexus 9020A did rooting, but when i tried to boot up it froze and not booting up look like System.IMG missing what is the solution for that
Thanks in Advance
Lost what ever info you can so that the people you are asking for help from can better help you.
Sent from my Nexus S using XDA App
when i turn the phone on it shows me ( google) and under of it there is a open Lock and as soon as it comes phone freezes . i tried to fastboot System.Img file in it but every time i do it fails.i want to know what should i do from this place? Sorry i spent 10 hours last night to get it fixed and i was bit frustrated .
thanks
can u get into recovery by holding up volme and power button?
yes i can go into bootloader and recovery. i tried to recover it in factory mode didnt work.
any helppppppppppppppppppppp?
Put your phone into fastboot.
Download ClockWorkMod Recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
Flash clockwork mod recovery in fastboot with this command: fastboot flash recovery C:\where\ever\you\put\the\file.img
Then from fastboot select recovery.
Wipe data/factory reset
Install zip from sdcard: http://download.cyanogenmod.com/get/update-cm-7.1.0.1-NS-signed.zip
Do you have a custom recovery?
If yes, then download a Rom to your computer and either a) mount your to computer and transfer the Rom to your phone or b) push it to your phone with adb.
After that is done wipe everything (except sd card) and flash the Rom you just transferred to your sd card. Reboot and enjoy.
If you do not have a custom recovery then download one (search) and place it into the same folder on your computer as fastboot. Then plug your phone into the computer and boot to the bootloader. Run this command ( fastboot flash recovery insertname.Img ). After this do the steps I wrote above.
If you have any questions about the above steps then search you will find the answer. If you unlocked your bootloader than your computer obviously sees your phone and adb works well. If you can get your phone into the bootloader then I don't see any reason how your problem cannot be fixed. This leads me to believe your not quite putting forth the effort to search.
Check the stickies in this section and have fun.
Dueces
Sent from my Kindle Fire using xda premium
weehooherod2 said:
Put your phone into fastboot.
Download ClockWorkMod Recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
Flash clockwork mod recovery in fastboot with this command: fastboot flash recovery C:\where\ever\you\put\the\file.img
Then from fastboot select recovery.
Wipe data/factory reset
Install zip from sdcard: http://download.cyanogenmod.com/get/update-cm-7.1.0.1-NS-signed.zip
Click to expand...
Click to collapse
Beat me to it lol.
Sent from my Kindle Fire using xda premium
How about instead of making a thread with no one helps me in capital letters and bumping it over and over again. You actually put info in your thread. Like what you did. Examples. Unlocked via fastboot with sdk flashed so and so recovery and so on
Or you could have just searched the forum/read another thread about how to fix a phone stuck at google logo because of user error.
Frankly you are lucky anybody even bothered to help you at all.
Hey guys.
Basically:
My brother has a Motorola Xoom 32GB MZ604. He tried to root it but it was unsuccessful. After reboot of the failed root, it will now get stuck on the M boot screen and not move, there's no loop as such, it will literally stay on until it runs out of battery or is turned off by pressing buttons.
Any ideas what's happened and how we can fix it?
He took it back and they want £46 to put new software on.
Thanks
Oli
Can you still enter recovery??
Sent from my Xoom using XDA Premium App
I believe he can but he said he's already wiped it? I'll try again though when he gets home tonight from work.
I had the same issue when I first tried to root my xoom. Here is what you do:
1) take out the external sd card. And thru pc , put on it the new recovery image and put it back into xoom.
2) search my posts on how to root mz601. I know yours is mz604. But it is the same procedure. I will post steps for you soon.
Sent from my MZ601 using Tapatalk 2
There you go. Step by step.
First, download the below and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: get the latest release for mz604 from here. http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot adb
reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Sent from my MZ601 using Tapatalk 2
if it's getting to the splash screen then just as you turn it on, whack it into fastboot then you'll be able to flash new recovery or flash back to stock.
matt4321 said:
if it's getting to the splash screen then just as you turn it on, whack it into fastboot then you'll be able to flash new recovery or flash back to stock.
Click to expand...
Click to collapse
Go here: http://developer.motorola.com/products/software/ to get the stock images to flash in fastboot to get the xoom back to factory conditions. It's normally the last resort, but the most successful. You may need to sign up for an account, but it is free.
Right guys basically i want my xoom to be complete stock what is the best way to do this. can i still use the above steps but by using the default motorola software.. it looked like it was using differnt firmware, and one of the links didnt work. sorry i really dont have a clue what to do and need my xoom back its been away for 3 weeks now
yes you can.. just flash the stock OS for it and you are good to go again.
and whats the best way to do this. sorry im not too sure about rooting on the xooms etc i used that poxy one click root which by the looks of things lots of people have had problems with it.
Rooting is pretty straight forward steps. Use the steps I provided you above if you want. If you are looking to flash stock rom, you still need recovery and stock rom to be flashed.
Sent from my MZ601 using Tapatalk 2
My mz601 is stuck at booting it keeps going off and booting again
My steps to a factory reset Xoom Wingray
My Xoom Wingray also crashed and was stuck in the boot animation. I still use my Xoom as my alarm clock and music player with multimedia dock. I had to put the Xoom in the drawer as there was no way to turn it off, it would just reboot back to the flashing animation. I was surprised that it wasn't dead by morning and it was still in the boot loop. So I wanted to revert back to the stock ROMs so this is what I just did. This is assuming you have nothing installed on your PC so from scratch. I actually just went through this a hour ago so I am still in the very last step.
First download and install the following:
-Minimal Android SDK from http://forum.xda-developers.com/showthread.php?t=2317790
-Motorola drivers from http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Now you need the original images:
You can try to get it from the source here, https://motorola-global-portal.custhelp.com/app/standalone/rom-images , but I had to request access to the files and was impatient.
I found the original images here instead, http://forum.xda-developers.com/showpost.php?p=64412362&postcount=10
You will need to find the original images for your device, the source in the first link should be able to help you.
Flashing Instructions
I would recommend having the power cord attached throughout this, but if your Xoom is fully charged it should be ok.
Assuming you installed the minimal SDK in the default folder, C:\Program Files (x86)\ Minimal ADB and Fastboot, unzip the individual images (boot.img, recovery.img, system.img and userdata.img) into this folder. If you installed into some other folder unzip there instead.
Now you need to put the Xoom into fastboot mode. Press the VOL-UP and Power to reboot, but then keep holding the VOL-UP. You should end up in fastboot mode.
Plug the Xoom into your PC.
Open a CMD window into the fastboot directory. If you installed the Minimal Fastboot from above you can simply go Start>Minimal ADB and Fastboot>Minimal ADB and Fastboot.
Type "fastboot devices"
Type "fastboot flash boot boot.img"
Type "fastboot flash system system.img"
Type "fastboot flash recovery recovery.img"
Type "fastboot flash userdata userdata.img"
Type "fastboot erase cache"
Type "fastboot oem lock"
You can see the responses I got in the attached image. Once complete the Xoom rebooted with the original Honeycomb OS and then I had to wait for all of the OTA updates to be pushed. This has taken several hours and now it is updating all of the stock Google apps.
Help with my MZ601
Please, I need help with my MZ601.
A friend who recently passed willed his MZ601 GSM/Wifi to me. I do not know a thing about it; however, I have read a couple of posts. I gathered from these posts that the MZ601 would need to be flashed with a new ROM, especially as when I powered it on, it stopped at the big 'M' logo.
I have checked so many posts online here and found links to many Roms and Gapps, but none is working.
Please, I would be glad if anyone could help me with the following:
(a) MZ601 GSM/Wifi ROM - whether Stock or Custom ROM.
(b) Also remember that I am a idiot; hence, I will need a step-by-step guide on what to do.
Thank you very much.
oyeniyib
I've been stock for a while again, and feel like going back to having more control. I'm on stock Sprints Nexus S 4g's 4.1 JB...how would I go about rooting this?
Windst said:
I've been stock for a while again, and feel like going back to having more control. I'm on stock Sprints Nexus S 4g's 4.1 JB...how would I go about rooting this?
Click to expand...
Click to collapse
I used "http://forum.xda-developers.com/showthread.php?t=1250583&highlight=one-click-nexus-7+2" by ShabbyPenguin. Works good . . .
Windst said:
I've been stock for a while again, and feel like going back to having more control. I'm on stock Sprints Nexus S 4g's 4.1 JB...how would I go about rooting this?
Click to expand...
Click to collapse
yep shabby's 7.2 tool is the way to go
Thank You both
Download supersu.zip onto phones internal storage.
Fastboot flash or boot custom recovery.
Flash supersu.zip from recovery
Stock rooted.
Easiest way. Best way. Never fails way. The same way the phone was rooted in the first place.....
can't get Shabby's way to work. just searches for devices & on my phone it stays at the bootloader screen. how can I flash something if i'm unable to use ROM manager?
courtesy of my Jelly Bean'd Nexus S 4G using Tapatalk 2.1
Thread Cleaned. Lets stop the arguing.
Deleted my comments
Vs Nexus S4G using tapatalk2
Follow the instructions below to install CWM on your phone and then you can flash super user binaries to get root access.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery
how to root nexus s ? from jb ? more infos ?
To root ANY nexus the process is the same. All that differs is the files used.
1. Unlock bootloader
2. Get the proper su zip on the devices storage. Either boot up and put it there or do it by mounting storage in step 3
3. Boot or flash custom recovery and flash your su.zip.
That's it. If you're already unlocked skip step one. Make sure you got the su.zip on your phone. Use fastboot to flash or boot recovery and boot into it. Flash the zip.
ive tried everything in this post, but i cant unlock or root. Im assuming the drivers are my problem because in Device Manager I can only install ACER ADB or Android Adb Interface.
In shabby's one-click, I get to the step where it says something like "select the unlock option on my phone", but in fastboot i only get 4 options and neither say "unlock"
peopleface said:
ive tried everything in this post, but i cant unlock or root. Im assuming the drivers are my problem because in Device Manager I can only install ACER ADB or Android Adb Interface.
In shabby's one-click, I get to the step where it says something like "select the unlock option on my phone", but in fastboot i only get 4 options and neither say "unlock"
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1623481
Its old but still works. Go into fast boot and type in cmd fastboot oem unlock, its not an option in fadtboot. Don't use one clicks, learn the original way. You will be much better off in the future.
This might help also
http://forum.xda-developers.com/showthread.php?t=1901617
Sent from my Nexus S using xda premium
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?
Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!
I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.
Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)
RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk