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??
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
Model: GT-I9250T
Original Android version 4.04.
Root method: Gained root without having to unlock or overwrite the vanilla boot-loader and used OTA RootKeeper to backup su.
Long story short: My phone recently updated to 4.2.1 OTA. I restored root using OTA RootKeeper without issue. However when I went to restore The LBE Privacy app service, it caused my Nexus to enter a loop the moment it finishes booting and the lock screen appears.
Behavior:
After booting to the lock screen, the screen flashes and goes black then gets back to desktop and starts all over again in a loop. Once it does that about 3 or 4 times, it'll eventually get to a totally black screen except for the Android robot guy lying down with his belly open and an exclamation mark coming out. It'll then sit like that for about a minute and then the phone will reboot from scratch and the whole process repeats.
Apparently i'm not the only one either: url = badappreviews.com/apps/23315
From the linked site it looks like someone fixed it by using clockworkmod. However I don't see how that's possible as there is no way to enable usb debugging or copy any files to the sdcard as you can't boot the phone properly in the first place. I also noticed that I can no longer get into fastboot using the volume up and power button. However I can get into Odin mode.
Any ideas???
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
.DCCXVIII said:
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
Click to expand...
Click to collapse
Just flash the android stock image through adb and go from there. You don't need debugging access when you're in fast boot
Have I helped? Don't forget to make love to that "Thanks" button!
Download stock images and flash em via fastboot, but you will lose everything. Its the freshest start you can get.
Sent from my Nexus Prime
Seriously, do you need to 'enable debugging' to be able to use adb in recovery?? It's a completely different and independent partition.
And fastboot doesn't need any enabling at all.
So, boot to recovery
mounts and storage
mount sd card
open up a DOS box (or terminal if you're on a mac or linux)
<path to adb>/adb shell
...
profit
The ... is where you go and uninstall the app/service, like the example you found mentioned above.
Usually this would be removing a .apk from either /system/app or /data/app
Thanks for all the help, however i am unable to get the adb drivers installed. I tried both Samsung's and Google's and they both fail (Windows doesn't even recongise a driver even after pointing it to: \sdk\extras\google\usb_driver. Anyone got any other sources for a working driver? Win7 64bit.
Edit: Managed to connect it using the pdanet drivers. Then proceeded to try to load CWM using: "fastboot flash recovery *file name*.img", but just got an error: "FAILED (remote: invalid argument)". I noticed that on my fastboot menu, it says lock state: Locked. Is this why it's failing? The boot loader is still locked? Because I tried "fastboot oem unlock" and that didn't work: "FAILED (unknown status code)".
Edit: Looks like my phone just needed a reboot. Because once I did, I was able to use the fastboot oem unlock command with success! However, before I proceed with unlocking the bootloader, can someone please confirm for me that I need to do so in order to install CWM? Many thanks.
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
m.is.for.michael said:
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
Click to expand...
Click to collapse
OK, i've managed to successfully unlock the bootloader, flash CWM and used the "fix permissions" function. I lost all my data/apps etc but I now have a working phone! Many thanks to all that helped!
hello people,
about this guide http://forum.xda-developers.com/showthread.php?t=2128175
steps 3 and 4 do not work.
Where should I put the files that I download?
whitesalt said:
hello people,
about this guide http://forum.xda-developers.com/showthread.php?t=2128175
steps 3 and 4 do not work.
Where should I put the files that I download?
Click to expand...
Click to collapse
correct the question
fastboot does not respond.
the command adb devices yes
why???
whitesalt said:
correct the question
fastboot does not respond.
the command adb devices yes
why???
Click to expand...
Click to collapse
The device has to be in fastboot mode to show up via fastboot.exe
Regarding your issues flashing the bootloader/TWRP, try using FireFlash, an apk that automates the process of flashing the exploitable bootloader and TWRP, using the freedom boot.img and TWRP files from the thread you mentioned in your post They can be anywhere on the device storage.
Stick the FireFlash apk on the device storage, install it with ES File Manager, plug in the freedom boot.img into the boot slot and the TWRP img into the recovery slot, check the box to flash 8.1.4 bootloader if you aren't already using it (red letters will warn you if you aren't) and check apply stack override. also check disable auto recovery update. execute the flash, and you're done.You can also use FireFlash to easily update TWRP later on if you like.
humpster said:
The device has to be in fastboot mode to show up via fastboot.exe
Regarding your issues flashing the bootloader/TWRP, try using FireFlash, an apk that automates the process of flashing the exploitable bootloader and TWRP, using the freedom boot.img and TWRP files from the thread you mentioned in your post They can be anywhere on the device storage.
Stick the FireFlash apk on the device storage, install it with ES File Manager, plug in the freedom boot.img into the boot slot and the TWRP img into the recovery slot, check the box to flash 8.1.4 bootloader if you aren't already using it (red letters will warn you if you aren't) and check apply stack override. also check disable auto recovery update. execute the flash, and you're done.You can also use FireFlash to easily update TWRP later on if you like.
Click to expand...
Click to collapse
found within the forum
I open Fireflash and find the inscription: warning: current bootloader not kfhd8-u-boot-prod-8.1.4.bin.
Can I switch back?
FlashBoot I click to go into the "flash install script" or "reboot into recovery"?
I can also directly follow the program? reliable?
thanks
is stuck to the initial written "kindle fire" orange. help!
If you are not seeing the blue logo, then the 2nd-bootloader / freedom boot / twrp img is not installed correctly.
I will post a small set of instructions in a few mins. But they require you have a working fastboot connection.
Sent from my XT926 using Tapatalk 2
Hashcode said:
If you are not seeing the blue logo, then the 2nd-bootloader / freedom boot / twrp img is not installed correctly.
I will post a small set of instructions in a few mins. But they require you have a working fastboot connection.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
apparently neither do fastboot adb recognizes the device!
how can I check better?
I remember that already fastboot did not work before, so I installed Fireflash and finally brick
whitesalt said:
I remember that already fastboot did not work before, so I installed Fireflash and finally brick
Click to expand...
Click to collapse
Have you tried using KFFA found here:
http://forum.xda-developers.com/showthread.php?t=2096888
It has MANY options for fixing USB drivers, installing 2nd-bootloader, etc.
Hashcode said:
Have you tried using KFFA found here:
http://forum.xda-developers.com/showthread.php?t=2096888
It has MANY options for fixing USB drivers, installing 2nd-bootloader, etc.
Click to expand...
Click to collapse
nothing happens! the program fails to work because it waits for the device that does not find! I ask amazon replacement?
whitesalt said:
nothing happens! the program fails to work because it waits for the device that does not find! I ask amazon replacement?
Click to expand...
Click to collapse
What operating system are you using on your computer?
If using Windows 7 or 8: are your Kindle HD 8.9 drivers up to date? Check this thread out to uninstall and reinstall the proper drivers: http://forum.xda-developers.com/showthread.php?t=2069117 (it references another thread that helps uninstall "phantom" device drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361)
We need a bit more information in order to help you out.
GenghisKhan67 said:
What operating system are you using on your computer?
If using Windows 7 or 8: are your Kindle HD 8.9 drivers up to date? Check this thread out to uninstall and reinstall the proper drivers: http://forum.xda-developers.com/showthread.php?t=2069117 (it references another thread that helps uninstall "phantom" device drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361)
We need a bit more information in order to help you out.
Click to expand...
Click to collapse
hello,
I use windows xp and windows 7, the guide can not use it because the kindle is blocked! the day after tomorrow comes the new kindle you help me not to make mistakes? I listed exactly what is right to do? remember that the error was born from the fastboot that did not work! thanks
whitesalt said:
hello,
I use windows xp and windows 7, the guide can not use it because the kindle is blocked! the day after tomorrow comes the new kindle you help me not to make mistakes? I listed exactly what is right to do? remember that the error was born from the fastboot that did not work! thanks
Click to expand...
Click to collapse
My point is that it is crucial to have proper drivers present and working BEFORE you even get into fastboot mode.
I would recommend you go back and re-read Hashcode's thread. Back up your system files before modifying anything, so you can go back if anything goes wrong.
GenghisKhan67 said:
My point is that it is crucial to have proper drivers present and working BEFORE you even get into fastboot mode.
I would recommend you go back and re-read Hashcode's thread. Back up your system files before modifying anything, so you can go back if anything goes wrong.
Click to expand...
Click to collapse
but if something goes wrong, without the fastboot mode you can not recover anything the same right?
Surely my mistake was not to test the fastboot. Why can not I work in the device?? for drivers?
I think my kindle volume button is broken. Every time I reboot the device it always enter safe mode.
I reflash the device to stock but the problem still appear, now I want to back to custom rom but I cannot get in to TWRP (the volume up button not working) so I stuck at blue logo.
Fastboot and ADB still working.
Is there any way to install CM10.1 using fastboot/adb only without TWRP?
You can still get into twrp without using volume button, you just need to run adb on your PC with your kindle connected and adb enabled as follows:
adb reboot recovery
Or try
adb shell "su -c 'reboot recovery'"
If it is the second one u can run it from a mobile terminal app on the kindle, just take off the adb shell part.
Once you have cm installed I know for a fact you can reboot into recovery from the shutdown menu, but u have to enabled developer stuff on cm after u flash it. You can tell I'm half asleep when I can't remember the proper term and say "stuff"... Anyways if you want feel free to try what I suggested or search around for what I suggested. I am going to bed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
TWRP problem
Hello people
First of all thanks Hashcode for putting so much effort into it
I ran into a little bit of problem
First off regarding the BLUE LOGO
I first get ORANGE then BLUE n then ORANGE again with the animation
Second regarding TWRP
I can't seem to get into recovery while pressing the volume up button
It gives me a bad boot kinda error n then takes me to Fastboot mode
I hope you guys can help me out with this
Thanks
EDIT
Thanks to the above post i was able to enter recovery
Now it gives me two options
1 reboot kindle
2 reset to factory defaults
Question : How do i install CM 10.1 from there
You apparently didn't follow the instructions in the 2nd bootloader thread very well because you seem to have skipped a step.
To further explain what soupmagnet means, you didn't flash twrp to your recovery, that's the stock amazon recovery and is completely useless.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To further explain what soupmagnet means, you didn't flash twrp to your recovery, that's the stock amazon recovery and is completely useless.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I entered every command perfectly
Do i need to re flash TWRP????
If so , HOW???
Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.