First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
soulman1980 said:
First off, this forum rocks. First post but have read a tremendous amount since learning to root and rom my Thunderbolt.
I upgraded to the Galaxy Nexus (CDMA), and decided to try the "one-click root" which left me with the followign problem.
It seemed to work ok, however when I booted into recovery, recovery failed to load and I got the android w/ exclamation.
I tried a few other things to no avail, at one point I hit a volume up and down and got a limited clockwork menu on the screen, one which was factory wipe (as I was intending to install a ROM).
The wipe hung, so I pulled the battery and was left in a loop.
I booted back into fastboot, and it shows as unlocked, but I can't get it to show as a device in ADB.
I'm assuming this may be a driver issue. I did re-download the Android SDK but this didn't seem to make a difference.
I get the USB connection, but the phone displays "Fastboot Command Read Error -2147483647". I did try to kill server and try again as I saw suggested in some other posts but no luck.
In device manager it shows as "SAMSUNG Android ADB Interface" for the driver 2.9.310.1125.
I'm thinking fastboot should be a non-samsung branded driver?
Anyhelp is appreicated.
thanks!
Click to expand...
Click to collapse
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
badassirocz said:
When you boot back into fastboot look under device manager on your computer and you will probably find a yellow question mark by your device. You will need to download the Samsung driver and manually install it at that screen. Then you can fastboot oem lock and then fastboot oem unlock and that should fix your boot loop issue. The android with exclamation point is the factory recovery, if you rooted and still have root download rom manager in the market and flash clockworkmod through it.
Click to expand...
Click to collapse
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up.
also, if you can get into clockwork recovery, look at your device manager again for yellow errors....often there is another driver that doesn't install itself properly; the one that allows you to use adb while in CWM.
cancerouspete said:
definitely check for any drivers, but i haven't heard anybody needing to re-lock & unlock before. once you have the drivers you should be able to use 'fastboot' from the fastboot screen. not adb. after your drivers, type 'fastboot devices' and see if anything comes up
Click to expand...
Click to collapse
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
badassirocz said:
Fastboot OEM lock and the Fastboot OEM unlock is a known fix to correct a loop soft brick issue that he noted
Click to expand...
Click to collapse
which is because it is just doing a factory wipe correct? if he fixes his drivers & fastboot issue, he should be able to just flash an image without wiping the whole phone
I guess in some aspect yes but if the phone is not softbricked anymore that he should be fine not doing it. Most of the time the ADB issue is like you stated that when you boot into fastboot the driver is not recognized so you need to do a manual install to fix it. If his battery pull left the phone stuck in a boot loop he will have to re-lock and then unlock to fix it.
You guys really are a godsend.
So, the drivers all seemed good and installed properly (no exclamation or question mark in Device Manager).
Ultimately, I knew there was a driver issue so I just went to a different computer (running win7 64). Coulnd't get that to work, then found drivers arn't supported. I also found the PDANET work around.
This allowed me to install the driver and fastboot WAS able to detect the device.
Following some advice and some other posts I tried "fastboot oem lock", which worked successfully.
I then rebooted, was still in a loop, then pulled the battery.
I ran "fastboot oem unlock", then rebooted.
This time I got past the "google" screen and got the graphic screen.
This sat for awhile (3-4 minutes)??
Then it rebooted again (I almost cried) and I was back to the google logo. Again, it went past this point and displayed the graphical animation again.
Than, on the second time around came the "Welcome!" screen!!!!!!
As well as a rush of relief that is indescribable....
I spent 5 minutes living as Phillip Seymour Hoffman in Boogie Nights sitting in his car outside the party - then did a human xanax reboot and am happy to go to bed!
I'm only posting all of this in detail as an update, and so it is available for anyone else who may come into this problem.
It seems there are many ways to get stuck into this boot-loop besides what I did.
NOW - the next problem....
I'm in my phone, everything works. HOWEVER, I apparantly have a corrupt or bad install of Clockworkmod on my phone.
Do I just try everything again from scratch, or is there something I should do differently to reinstall CWM Recovery?
Thanks again!
glad you got booted. drivers are supported for windows 7 64x, using them currently btw.
i would download a new copy of cwm, confirm its md5 checksum first, and flash it again if you think its corrupt, or if you have rom manager you should be able to do it from there.
good luck
Glad you got it fixed. The lock and unlock fixes the boot loop issues as you found out. I would root your phone with cf-root using adb which you can find here on xda. Then install clockworkmod through rom manager which you can download free in the market.
Thanks again guys, all is good in the hood.
I followed the instructions to re-install CWM here:
http://forum.xda-developers.com/showthread.php?t=1392336
I picked up where I had left off (I already had phone unlocked).
All is perfect!
can't thank you all enough
Related
>>GUIDE<<
This guide will work to root the stock ROM. None of that automated stuff where you don't know what's going on. This guide will explain it step by step and you will actually know what's going on when you root a ROM
If you want to boot into a recovery image, simple use:
fastboot boot recovery.img
Note: You'll have to find the correct recovery.img file for your phone!!
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
your drivers probably arent installed properly. download PDA net and use it on your computer and it should install the drivers for you
Can't gain root after unlocking bootloader
xx
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Same here. And I did install PDAnet prior to attemping this so that I would have the correct drivers.
I have tried this on 2 different computers and I keep getting the same error. When I try to do "adb root" it will start daemon and then it will fail.
It keeps saying "Error: Device Not Found"
same error as everyone else..
"adbd cannot run as root in production builds"
I noticed my bootloader says unlocked...is that good?
DenzelChurchill said:
Hey guys,
I can't seem to boot straight into boot.cdma.img. Soon after this command, the phone boots (doesn't make it to the ROM boot animation), then reboots, then goes into the ROM. When I try "adb root" I get the "production" error message. I have a Verizon CDMA/LTE Galaxy Nexus and I'm connecting it to Mac OS X. Thoughts?
Detailed explanation below for those curious...
Thanks everyone!
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
EDIT: Added phone / computer details.
Click to expand...
Click to collapse
remember, that command is supposed to be
fastboot boot boot.cmda.img
xx
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Seaman24 said:
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Click to expand...
Click to collapse
I know their network was down from around 6am EST to Noon EST. And last night on some cities on the west coast.
I actually lost 3g data for that time as well.
DenzelChurchill said:
Hey guys,
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
Click to expand...
Click to collapse
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
---------- Post added 22nd December 2011 at 12:05 AM ---------- Previous post was 21st December 2011 at 11:59 PM ----------
aznxk3vi17 said:
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
Click to expand...
Click to collapse
I can confirm this. You need to be in bootloader to see the device driver error. It will show a Android 1.0 with an exclamation mark over it. I believe the device is a labeled as a storage drive or something similar (its not under "Android Phone")
Follow the above instructions to apply the SAMSUNG drivers
Just wanted to say thanks for this. I am fairly new to this but this seemed a lot less complicated.
Just one thing, I couldn't figure out why I couldn't run the adb root command until reading some more and finding that I had to enable USB debugging then reboot again. Hope that helps someone.
Thanks again all.
Also, how do you unroot the phone after using this method?
How to do on mac
I am new to doing this on Mac. I know that it is kind of the same but what is different when I am doing this on a Mac as apposed to a PC?
numbskill said:
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
Click to expand...
Click to collapse
any idea why this happens? I rooted 3 phones with this method. The first one went smoothly. The second two went through the reboots. In one case, I actually loaded an odin to get it back to the boot animation, otherwise I was stuck on the unlocked Google screen. Would be nice to know what I might be doing before I root someone else's phone.
xx
Does following this guide erase your phone? When it says boot the CDMA.img, I'm thinking it's going to replace the already installed image with a stock version that has root.
Or am I completely missing the mark here? I read what the guide wrote, but it doesn't really say if it's going to replace my stock image or what's going to happen.
BUMP?
The file linked on that thread is 404'd. Also, does this work on 4.0.4? I want to root but learn at the same time so I want to avoid using the toolkit. Does the toolkit work on 4.0.4? Thanks.
i ran into a little problem idk what it is this is the first time i run into this problem. i enter the first command prompt into terminal i think its
./fastboot-mac oem unlock and all it says is:
./fastboot-mac: operation not permitted
i don't know what I'm doing wrong help??
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
asanz00 said:
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
Click to expand...
Click to collapse
Usually that happens when the device isn't at the bootloader. Did you run "adb reboot bootloader" to get to the bootloader?
Sent from my Nexus 7 using xda premium
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
MIght be a driver issue. On mine the first time I booted into fastboot mode I had to go into device manager, found the android device with a yellow triangle, and had to install the drivers manually with "have disk". Hope this helps.
asanz00 said:
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
Click to expand...
Click to collapse
Same thing happened to me, I never saw anything until I fastbooted the .img. And then I had to try it on 3 displays before one would show CWM. However after I flashed the .zip I have since tried all the displays and they all have worked every time.
Wow problem solved!
In devices administrator, there was one small called "fastboot" with yellow triangle.
I manually installed a driver called "android bootloader interface" and now it is working
thanks a lot!!!
No problem, always glad to help.
Now im fighting to get multi usb support via using a 5 ports usb-hub, i will write if i can ge througt
Can you post about that in the USB thread ? I just bought an active USB cable and 4 port hub, I hope they weren't a waste. I'll still get some use on my laptop, but not enough to justify the purchase.
Sent from my GT-P3113 using Tapatalk 4 Beta
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...
Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).
I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?
Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.
That's the bootloader. What procedure are you using for fastboot?
Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere
You cannot run a RUU from adb. Only fastboot.
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.
Have you tried booting into bootloader and choosing fastboot before trying the RUU?
Yep. Same USB connection error despite having 'FASTBOOT USB' showing....
Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?
Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
My nexus 7 lte is in the exact same state(that's why I've posted here instead of starting new thread)...by using nrt to try updating to marshmellow as per site's instructions...wondering if anyone can offer a solution???
(bought at google play almost 2 years ago and they already sent me a free refurb replacement...but I still wanna try getting the old one going before sending it back if possible...worth a try before buying a replacement mobo)
here some details of my situation:
ran this on my nexus 7 2013 lte...failed on the first try...tried again..it wiped everything and then failed on install...now I have bootloader (accessible by volume down and power button simultaneously) only and no functional recovery(get the android with red triangle and asterisk when I select Recovery)...the only Android device listed in Device manager is Android Bootloader Interface.
If I start from fastboot mode:
gives a driver failed to load error from windows" and also, now in Device Manager my Android Device Listed changed from "Android Bootloader Interface" to "Android Composite ADB Interface", as well, there is now a Portable Device listed also but it's the driver that failed to load I guess "MTP USB Device" with a yellow asterisk.
If I run the flash-all.bat in the image download that the NRT got on the first attempt, everything goes fine until I get to "sending system"...this fails with unknown data transfer error...
when I download the latest image from developers google.com and extract it I get just one big file with no extension...shouldn't there be a bunch of files including a flashhall.bat file?
^Yes, inside the main image zip is the bootloader (+ radio in your case) and another zip of the actual partition images.
Run fastboot devices from the bootloader just to be sure it's detected. If not uninstall all traces from your pc and start fresh.
Flash the new bootloader, reboot bootloader, flash the radio, reboot bootloader then flash each .img individually with fastboot. Don't use any toolkits.
You should get the "OKAY" after flashing each image. Is it only system that fails? Do you get the okay with boot and recovery? If system only I don't know.
ronf1011 said:
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
Click to expand...
Click to collapse
The android with the red triangle with exclamation is what happens with stock recovery, you need to press power, volume up and down quickly all at the same time to get in. Usually takes a few tries. If you can get into recovery you could factory reset. It could be another problem though. You have to describe what you previously did to it if you really wan't help.
rma
Thanks for the reply...was never able to get the system image to load...google play is supposed to reemburse me once they receive my original nexus 7 (already got a pristine refurb from them..updated to marshmellow..will be staying away from NRT with this one...)
Thanks again for the reply and suggestions!
system image can't be written
Exactly the same happened to me. After a successful update to MM with Wugfresh's NRT 2.0.5 (with no root) I tried to root my device with 2.0.6 which was released in the meantime.
But that failed because NRT thinks my bootloader is locked, while in fastboot mode I can see that it is unlocked. With fastboot commands I can relock and re-unlock but for NRT it makes no difference.
It seemed to me that a manual reflash of bootloader (FLO-04.05), kernel, cache, system and data should solve this, but no way. The flashall. bat reports a write error of the system.img. A direct fastboot flash system system.img command leads to FAILED (remote: unknown chunk type).
I couldn't find any information about chunk types. I am afraid that somewhere in the process the partitioning was affected. Is that a possibility and can anything be done to fix this? Or are there other solutions for the chunk type error?
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now. I cannot get anything to flash through fastboot to the phone no matter what I try. At one point I even said screw it and tried flashing the stock boot image back over to re-lock my bootloader, but no luck, still won't flash.
I was originally following this tutorial here but during the flashing of the boot image it kept failing. Then I tried following the "foolproof" guide found here
I either ended up with the error of "no such file or directory" or "too many links" or "unable to identify current slot". Did a ton of Googling but ultimately came up with no solutions.
I have Android SDK and development studio installed. I have the google drivers installed. I have the Razer phone drivers installed and I have ADB and Fastboot installed.
I have all the files I need on the SD card, and when I'm flashing everything I have the files I need placed in the same folder as the ADB\Fastboot files.
I have my bootloader unlocked, developer mode on and USB debugging enabled. I am using a USB Type A to Type C cable as recommended (made by Anker if it matters). I've tried all 3 USB ports on my laptop. I've even disabled Antivirus.
I have flashed many Android devices in the past and none have given me such a headache as this one. I'm even more ticked off that I can't even get the factory boot image back over to re-lock the bootloader after now realizing that I can't install Netflix anymore because they wen't and blocked installations for Rooted android users (for whatever ridiculous reason).
I will say that for whatever reason that when I go to open command prompt by using the shift+right click I only get the option to use Windows Powershell, not Command Prompt. I also have to put a .\ in front of every command I send. I'm unsure why, but I found no work around for it.
I'd like to try to get the TWRP and Magisk installed. I'm sure I can force Netflix to install over to the phone using another method.
Open to any suggestions!
FireGuy0723 said:
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now.
Click to expand...
Click to collapse
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Munk0 said:
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Click to expand...
Click to collapse
I've been messing with it today a bunch. I am back to following the "foolproof" guide and this time I have completely uninstalled all my old drivers for anything android or USB or ADB related and reinstalled everything.
All commands work, I am using command prompt now.
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
I've double checked the file names numerous times. I have no idea what I am doing wrong now. I have tried the command "fastboot boot twrp-3.2.1-0-cheryl.img" as stated in the other tutorial and it bounces back with "failed to identify current slot".
So I'm making progress at least. I'm trying to follow the first set of instructions listed in the fool proof guide but still no luck. I also tried the "clean method" listed below on that guide and that one doesn't work either. Apparently the Fool Proof guide thinks I'm a fool!
FireGuy0723 said:
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
Click to expand...
Click to collapse
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Munk0 said:
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Click to expand...
Click to collapse
I was finally able to get the phone to accept a flash! I ended up saying screw it and dug a old laptop out, fresh install of windows and installed all the proper drivers onto it.
It worked almost flawlessly. It was able to correctly send the twrp.img file and the phone was able to boot into twrp which is about as far as I got. As it was attempting to load twrp it would "crash" the screen would flash twice and try rebooting back to TWRP.
What ended up happening was it got stuck in a boot loop trying to boot into TWRP. (I haven't even installed TWRP.zip yet, just tried booting the .img file).
I couldn't get the phone to boot to the system anymore. I thought I had a nice $600 paperweight on my hands.
I finally got the phone to go back into the boot loader and flashed all the factory stuff back on and relocked the bootloader. So right now I'm 100% back to stock.
I'm not sure what went wrong in the boot up of the twrp.img file. I'd like to try again but I'm kinda getting sick of wiping the phone Everytime something goes wrong.
Sent from my Phone using Tapatalk
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
chris5s said:
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
Click to expand...
Click to collapse
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
FireGuy0723 said:
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
In my case I actually had to flash the stock boot.img from the May 2018 stock OS. Then I was able to use Razers guide to flash stock again. I haven't locked my bootloader since I still want to give it a try again. But I want to find a reliable way of rooting and then unrooting in case I want to do so in the feature.
So far I haven't found said documentation.
Installed Magisk v17.1 via TWRP loaded in fastboot boot (not fastboot flash boot ie not permanently installed) and so far all seems well. No boot loops when restarting...
Peace