Yes, I think I just need to stop trying to mess with this thing.
After using a sideload with a working update for Kindle Fire, the device now boots to the logo, stays the for a while, goes to a blue screen for a while, then shuts off.
What have I done wrong? There's no way for me to get a warranty, this was pre-owned, and I got it from a GameStop.
Alex311360 said:
Yes, I think I just need to stop trying to mess with this thing.
After using a sideload with a working update for Kindle Fire, the device now boots to the logo, stays the for a while, goes to a blue screen for a while, then shuts off.
What have I done wrong? There's no way for me to get a warranty, this was pre-owned, and I got it from a GameStop.
Click to expand...
Click to collapse
If you have root and have not done a factory reset, like I did, than there may be hope.. What version of FireOS did you have?
XxD34THxX said:
If you have root and have not done a factory reset, like I did, than there may be hope.. What version of FireOS did you have?
Click to expand...
Click to collapse
Sadly, I factory resetted. I had 13.3.2.4, and I was trying to get to 2.3.2 so I could get CM-12 and unlock the bootloader. Sadly, this happened.
Something weird is happening though. It stays on the blue screen when plugged in, and it takes ADB commands.
Do I still have hope?
If you still have ADB access, try this: http://forum.xda-developers.com/showthread.php?t=2793253
XxD34THxX said:
If you have root and have not done a factory reset, like I did, than there may be hope.. What version of FireOS did you have?
Click to expand...
Click to collapse
EncryptedCurse said:
If you still have ADB access, try this: http://forum.xda-developers.com/showthread.php?t=2793253
Click to expand...
Click to collapse
It's saying that some commands are denied. I may be screwed. su command does nothing.
Alex311360 said:
It's saying that some commands are denied. I may be screwed. su command does nothing.
Click to expand...
Click to collapse
Are you rooted?
If not, draxie's approach with ghettoroot may work: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
EncryptedCurse said:
Are you rooted?
If not, draxie's approach with ghettoroot may work: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Click to expand...
Click to collapse
EDIT: I forgot that I should have used the code supplied instead of the install.cmd, lol.
Either way, at the point where you push the kindle update, hopefully this works
EDIT2: And now I can't get past pushing because it's denied. How do I get ghettoroot to work outside of adb shell?
Bump, still kinda stuck.
If you're on 3.2.4, then try the old HDX Toolkit to get root since I believe the old method used in this case just does it's job using ADB. Choose the root method for your tablet in in the menu of the toolkit. No need to use the towelroot one, choose option 6 or 7 depending on which tablet you have.
http://forum.xda-developers.com/showthread.php?t=2665683
icedtrip said:
If you're on 3.2.4, then try the old HDX Toolkit to get root since I believe the old method used in this case just does it's job using ADB. Choose the root method for your tablet in in the menu of the toolkit. No need to use the towelroot one, choose option 6 or 7 depending on which tablet you have.
http://forum.xda-developers.com/showthread.php?t=2665683
Click to expand...
Click to collapse
Does not appear to work.
Bump, still in need of help.
Still in need of help. Am I just doomed?
Alex311360 said:
Still in need of help. Am I just doomed?
Click to expand...
Click to collapse
Sorry, mate. I think the lack of recent responses speaks for itself. Some very talented individuals have already weighed in with their suggestions.
Ok, so I actually have some pretty important news. I'm using MobileGo by Wondershare to actually control it.
My screen is blue, however, through the app I'm using, the screen is actually working OK.
What the hell's going on with my screen? It locks normally and everything, except it's just blue.
Related
ok. ive used the one click root... ive used the script root method... downloaded the correct files. but i can't seem to get root.... both methods says i have root and its good to go but no superuser icon and i even tried using the one on the market just incase i need to... nothing still and ive tried over hours and hours... i don't know what else to do... anyone?
Use the fixed superuser posted on these forums.
Sent from my ADR6400L using XDA App
i can't even get root permission to log into cwk. to flash it.
dadsterflip said:
i can't even get root permission to log into cwk. to flash it.
Click to expand...
Click to collapse
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
nosympathy said:
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
Click to expand...
Click to collapse
Hope that works for them. I wonder if fastboot, where it doesnt shut the phone down 100% and suspends the phone in memory, could be an issue or no?
nosympathy said:
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
Click to expand...
Click to collapse
ill redo it and do this. thx
the only problems root wise i ran into (and i did it the adb way) was super user wouldnt initially give rights. I solved this each and everytime by one reboot. (clockwork i didnt have rights) restarted phone superuser came up with the box for me to give cw rights. Then i installed Tit backup form the market. No rights again, a restart and problem solved. Dont know why it was buggy but try that.
is it normal to see. usb device not recognized? while its on the hboot loading the update through? it only says that while its updating the hboot or loading the PG05IMG.zip. otherwise i have all the right drivers for it.
update.... still not luck. i used the script root... at the end i have s-on.... on the first downgrade i have s-off but at the very end of the script to add the other update ppg05img, it turns the s-on back... sooooo whats wrong with it or what am i doing wrong?
if your having that many issues with the quick root method (ill be honest I havent looked at the instructions for it) i really would suggest doing it manually (the method that was first released). I wanted to post the links for you but i dont have enough posts yet to do so. The instructions i used are on droid-life . com. Once your there go to search and type in thunderbolt root. Another one click root method will be the first topic. Go there and youll see two hyperlinks (here) and (here) in the first paragraph.Click the second one and youll see the list of instructions and a link to a video, showing you how to do it. The original video is very fast but once it starts playing it will give you step one and step two links. This video is very helpful and very detailed. Anyway hope that helps.
Any questions leave a post.
update. finally got root... manual way. thx for the help guys.
dadsterflip said:
update. finally got root... manual way. thx for the help guys.
Click to expand...
Click to collapse
no problem man hope i was a help.
dadsterflip said:
update. finally got root... manual way. thx for the help guys.
Click to expand...
Click to collapse
now you can rest easy that in the future if you screw up your tbolt you understand how adb works enough to probably fix it comfortably.
Amen to that.
Sent from my ADR6400L using XDA Premium App
Hello, I've tried rooting my tablet at first with the sourceforge androidroot thing]. Afterwards I turned on the tablet and the "Android" sign at start up had changed and so did my background,Now I get a system UI error and it restarts every time. Preferabbly I would not like to do a hard reset but I would like to take guides if so, So far nothing I've found on google has helped me.
(I've tried to unroot with SuperoneClick and DoomLord
a500 tablet
DarkLoves said:
Hello, I've tried rooting my tablet at first with the sourceforge androidroot thing]. Afterwards I turned on the tablet and the "Android" sign at start up had changed and so did my background,Now I get a system UI error and it restarts every time. Preferabbly I would not like to do a hard reset but I would like to take guides if so, So far nothing I've found on google has helped me.
(I've tried to unroot with SuperoneClick and DoomLord
Click to expand...
Click to collapse
Which tablet is it? I have an a500 and may be able to help you.
dibblebill said:
Which tablet is it? I have an a500 and may be able to help you.
Click to expand...
Click to collapse
It may be an a500, My tablet is Grey and has the "Acer" on the back. I'm not too sure though. :/
DarkLoves said:
It may be an a500, My tablet is Grey and has the "Acer" on the back. I'm not too sure though. :/
Click to expand...
Click to collapse
Help...please?
Definitely an a500
-bump-
DarkLoves said:
Definitely an a500
-bump-
Click to expand...
Click to collapse
Okay. Which rooting tool did you use? Was it also supposed to install a custom recovery, ROM, etc? I know I'm not on my desktop atm, but i found one for ICS which installed a partition mounter and such.
dibblebill said:
Okay. Which rooting tool did you use? Was it also supposed to install a custom recovery, ROM, etc? I know I'm not on my desktop atm, but i found one for ICS which installed a partition mounter and such.
Click to expand...
Click to collapse
Google "source forge android root" and it should be the first thing that pops up,
I cannot post links yet ;/
DarkLoves said:
Google "source forge android root" and it should be the first thing that pops up,
I cannot post links yet ;/
Click to expand...
Click to collapse
Ah, did find it.
Didn't use that script. Once I'm at my desktop, I can tell you the script I used. Do you have a description of what your boot screen looked like? It could have been the recovery screen.
"Had to run the script manually. After the line files\adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" and reboot the screen went black after boot android logo. Thought the tablet was bootlooping but this was not the case. Could still connect with adb and USB so after I continued to run all the script file the tablet was booting as expected with root access."
This was posted in the comments on that script. As far as hard reset, I'm not sure, beyond finding something that can push a new recovery or ROM straight to the tablet.
dibblebill said:
Ah, did find it.
Didn't use that script. Once I'm at my desktop, I can tell you the script I used. Do you have a description of what your boot screen looked like? It could have been the recovery screen.
"Had to run the script manually. After the line files\adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" and reboot the screen went black after boot android logo. Thought the tablet was bootlooping but this was not the case. Could still connect with adb and USB so after I continued to run all the script file the tablet was booting as expected with root access."
This was posted in the comments on that script. As far as hard reset, I'm not sure, beyond finding something that can push a new recovery or ROM straight to the tablet.
Click to expand...
Click to collapse
"bootlooping"; I might have the same problem this person is having. It seems to be "bootlooping" but as this comment says it might not be the problem.a
DarkLoves said:
"bootlooping"; I might have the same problem this person is having. It seems to be "bootlooping" but as this comment says it might not be the problem.a
Click to expand...
Click to collapse
Try reconnecting it to the computer if you still have the script working, and getting back to that step. Unfortunately, I'm drawing a blank right now on doing a hard reset without OS access.
dibblebill said:
Try reconnecting it to the computer if you still have the script working, and getting back to that step. Unfortunately, I'm drawing a blank right now on doing a hard reset without OS access.
Click to expand...
Click to collapse
Well I still have the script, only thing I would be able to do is to try and re-root it or something, the only option is to press enter for it to root.
DarkLoves said:
Well I still have the script, only thing I would be able to do is to try and re-root it or something, the only option is to press enter for it to root.
Click to expand...
Click to collapse
Try that and leave it connected.
dibblebill said:
Try that and leave it connected.
Click to expand...
Click to collapse
I would have to do it while it was turned off.
DarkLoves said:
I would have to do it while it was turned off.
Click to expand...
Click to collapse
Er, well I dont have to but, I'm not sure if I should turn it on.
Should I do it while its on is the question.
DarkLoves said:
Er, well I dont have to but, I'm not sure if I should turn it on.
Should I do it while its on is the question.
Click to expand...
Click to collapse
I'd say yes. If the tablet's powered off, it can't connect at all. :S
dibblebill said:
I'd say yes. If the tablet's powered off, it can't connect at all. :S
Click to expand...
Click to collapse
Failed to copy files/su to /system/xbin/su' : Read-only file system
rm failed for /data/local.prop No such file or directory
Installing superuser....
failed to copy 'files/superuser.apk' to '/system/;app/superuser.apk' : Read-only file system
It didn't work, uh, Still same problem.
re-edit Everything is alright. Thanks sorry for the trouble.
I'm going to check if its rooted, it should be.
DarkLoves said:
Failed to copy files/su to /system/xbin/su' : Read-only file system
rm failed for /data/local.prop No such file or directory
Installing superuser....
failed to copy 'files/superuser.apk' to '/system/;app/superuser.apk' : Read-only file system
It didn't work, uh, Still same problem.
re-edit Everything is alright. Thanks sorry for the trouble.
I'm going to check if its rooted, it should be.
Click to expand...
Click to collapse
Not Rooted
DarkLoves said:
Not Rooted
Click to expand...
Click to collapse
Okay. I hate to make you wait, but I have to- when I get home today, I'll log onto my desktop PC and check all the rooting tools (I keep every tool for every phone/tablet I root). It'll be about 8-10 hours (I'm at work right now), but I'll get the names of the rooting tools I used. You're on the stock Android 4.0.3 OS, right?
DarkLoves said:
Not Rooted
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520469
Try this thread. ITs what I used to root.
Did it work?
I just got this in the mail today. Does anyone have any insights on how to unlock the bootloader and inject root? I had assumed 'fastboot' would work, but this has ODIN. I'm sure I could follow the steps on the original S4, but I don't know what the downstream effects will be.
Thanks!
----------------------------------------------------------------------------------
Edit: Please see this post: http://forum.xda-developers.com/showpost.php?p=44322019&postcount=70
Ok, just got done rooting my gs4 vzw dev edition. It was really pretty simple.
Steps from my win8 laptop were...
Install samsung drivers,
get adb working (android sdk doesn't seem to work on win8.. but just the adb files are all you need, google adb platform-tools or just use win7)
dl and push your superuser zip to the sdcard or external sdcard
dl odin 3.07 and extract to pc
dl and make tar.md5 of your favorite recovery. ( i personally like cwm )
Then all I did was... reboot phone in to odin mode... while phone is powered off, hold vol down + power
Start odin.exe
uncheck auto-reboot
click pda button, select the recovery file.md5
press start and let it finish, only takes a few secs...
once done.. reboot in to recovery, and flash the superuser.zip u pushed over to it.
Vol up + power to boot in to recovery. for me i just booted the phone normally... used "adb reboot recovery" then flashed superuser.zip.
reboot your phone and done.
good idea to make a backup while ur in recovery
If someone has hosting, i can send the files needed.
-r4ph
Click to expand...
Click to collapse
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
equake said:
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
It became available yesterday, and I got overnight shipping.
tithefug said:
It became available yesterday, and I got overnight shipping.
Click to expand...
Click to collapse
Is it full of VW blot ware?
rcb929 said:
Is it full of VW blot ware?
Click to expand...
Click to collapse
Yes. The only difference is that this has an unlocked bootloader by default.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
markwebb said:
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
Click to expand...
Click to collapse
Probably. But, I knew that would work.
tithefug said:
Probably. But, I knew that would work.
Click to expand...
Click to collapse
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
markwebb said:
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
The boot message you see when you power on your device means your device is rooted. I have the same exact thing when I rooted mine. I got mine from a Verizon store.
Sent from my SCH-I545 using xda app-developers app
tithefug said:
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
Click to expand...
Click to collapse
What backup method are you using: CWM or TWRP?
cmmelton2 said:
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
Click to expand...
Click to collapse
Search for the phrase used in the notification. It had to so with SEAndroid. You have to delete/rename KNOXAgent.apk, KNOXAgent.odex from /system and com.sec.knox.seandroid from /data/data
Have fun!
markwebb said:
What backup method are you using: CWM or TWRP?
Click to expand...
Click to collapse
TWRP. I installed it using the GooManager app.
tithefug said:
TWRP. I installed it using the GooManager app.
Click to expand...
Click to collapse
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
markwebb said:
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
Click to expand...
Click to collapse
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
tithefug said:
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
Click to expand...
Click to collapse
Was just wondering if you tried CM yet?
markwebb said:
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
I would also like to see the best/correct way to root the Developer Edition.
markwebb said:
Was just wondering if you tried CM yet?
Click to expand...
Click to collapse
Not yet. It's going to have to wait until tomorrow. Sorry.
UPDATE: http://forum.xda-developers.com/showthread.php?t=2461483
this thread can be closed.
i don't know how any one is getting any of this done. i've been able to root, several times, install CWM, several times, but i can not seem to figure out how to boot into the fastboot, or into the bootloader so that i can use fastboot, so that i can unlock my bootloader. is there some magical secret that every one else in the world knows, except me???
i'm running v20d. i've got fastboot and adb installed on linux (debian), and i can shell into the phone via adb, and then substitute user* as root and delete bloat ware and every thing else - but i can't figure out how to boot into bootloader... i've tried "adb reboot bootloader" and "adb reboot-bootloader" (yes, the 2nd one is valid), but both just reboot the phone, then i see the CWM flashing lights, then it continues to boot as normal - a few times i got the dead droid icon.
i can do all this http://forum.xda-developers.com/showthread.php?p=43401184 but i can't get into the danged bootloader... this can't be just me, but it seems like i'm the only one that has no clue how to get this right
bleh! thanks in advance.
* "su -" does not stand for superuser - that's a misgnomer, and since most of the mobile hackers are windows users, they never know that little detail - and you should include the dash after su, so that the shell assumes the root user's home directory and reads the root user's .bashrc env vars, etc
LG prevents rebooting in bootloader on most phones, including this one. Entering fast boot with the script and running the command fails BC its not an official fastboot its user compiled.
Sent from my LG-P769 using xda app-developers app
i've been rooting and putting CWM onto it before i bother with the bootloader, but i wonder if you have to unlock the bootloader FIRST, because CWM or rooting wipes out some thing that's needed to get the bootloader to allow fastboot??? i dunno, just taking stabs in the dark now...
I didn't have recovery or radio installed when I unlocked my bootloader
leolawliet said:
I didn't have recovery or radio installed when I unlocked my bootloader
Click to expand...
Click to collapse
that might be the "1 little detail" i've been missing - i'm going to try to convert mine back to stock, without windows...
sentientsystem said:
that might be the "1 little detail" i've been missing - i'm going to try to convert mine back to stock, without windows...
Click to expand...
Click to collapse
Dude, check my last post on the unlocking bootloader guide thread, I think step 13 that I posted might be the missing key,if it is please let me know because I haven't seen anyone try this at all.
leolawliet said:
Dude, check my last post on the unlocking bootloader guide thread, I think step 13 that I posted might be the missing key,if it is please let me know because I haven't seen anyone try this at all.
Click to expand...
Click to collapse
yeah, that was one of the other things i was going to keep in mind (i actually had seen it as soon as you posted it, and thought you might be correct on that detail).
sentientsystem said:
yeah, that was one of the other things i was going to keep in mind (i actually had seen it as soon as you posted it, and thought you might be correct on that detail).
Click to expand...
Click to collapse
*crosses fingers* good luck, if I find more suggestions I'll let you know. For now let's hope I'm right on this.
You're not the only one. I am also unable to unlock. I agree with omgbossis21 when he mentions that LG blocked access to fastboot. I tried several key combinations but none worked.
The bootloader is on this thing, though. The hidden menu shows the status. Has anyone tried asking LG tech support how to access official fastboot? It must exist in order for the techs to recover the damn thing.
Sent from my LG-P769 using XDA Premium 4 mobile app
peanut butter jelly time! http://forum.xda-developers.com/showthread.php?p=43401184 - now that it's unlocked, i don't know what to do next
sentientsystem said:
peanut butter jelly time! http://forum.xda-developers.com/showthread.php?p=43401184 - now that it's unlocked, i don't know what to do next
Click to expand...
Click to collapse
Wait so you managed to unlock it??
unlocked, flashed cyanogenmod tried to fix the inverted / screwed up screen, bricked it again, trying to unlock again...
LaDY Vengeance said:
You're not the only one. I am also unable to unlock. I agree with omgbossis21 when he mentions that LG blocked access to fastboot. I tried several key combinations but none worked.
The bootloader is on this thing, though. The hidden menu shows the status. Has anyone tried asking LG tech support how to access official fastboot? It must exist in order for the techs to recover the damn thing.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Usually phones that don't have a key combo for fastboot you can delete main system partitions and it would start in official fastboot like my LG motion. Not on this phone though
Sent from my LG-P769 using xda app-developers app
Have you tried holding down the vol down button when the lights flash on boot?
villan.co said:
UPDATE: http://forum.xda-developers.com/showthread.php?t=2461483
i don't know how any one is getting any of this done. i've been able to root, several times, install CWM, several times, but i can not seem to figure out how to boot into the fastboot, or into the bootloader so that i can use fastboot, so that i can unlock my bootloader. is there some magical secret that every one else in the world knows, except me???
i'm running v20d. i've got fastboot and adb installed on linux (debian), and i can shell into the phone via adb, and then substitute user* as root and delete bloat ware and every thing else - but i can't figure out how to boot into bootloader... i've tried "adb reboot bootloader" and "adb reboot-bootloader" (yes, the 2nd one is valid), but both just reboot the phone, then i see the CWM flashing lights, then it continues to boot as normal - a few times i got the dead droid icon.
i can do all this http://forum.xda-developers.com/showthread.php?p=43401184 but i can't get into the danged bootloader... this can't be just me, but it seems like i'm the only one that has no clue how to get this right
bleh! thanks in advance.
* "su -" does not stand for superuser - that's a misgnomer, and since most of the mobile hackers are windows users, they never know that little detail - and you should include the dash after su, so that the shell assumes the root user's home directory and reads the root user's .bashrc env vars, etc
Click to expand...
Click to collapse
Have you tried holding down the vol down button when the lights flash on boot? Works for me to get into CWM recovery.
thanks man, but, i'm way past that point. this thread should actually be closed: http://forum.xda-developers.com/showthread.php?t=2461483
HI guys,
I had a successful root of my Fire HD 6. I tried to do a factory reset and somehow I think I wiped necessary files from the device. I can still get to TWRP, but looking through the files I dont see anything. I see the structure but no files. Is there anyway I can get a flashable stock rom or another rom for this? I searched a bit but could not find anything.
Any help will be much appreciated!
Thanks,
Jesse
EDIT: Just looked ar it hooked to my computer and the only directory is TWRP
EDIT: I tried flashing 5.2.0_stock_recovery_only.zip" and now I lost TWRP
JesseHammil said:
...
EDIT: Just looked ar it hooked to my computer and the only directory is TWRP
EDIT: I tried flashing 5.2.0_stock_recovery_only.zip" and now I lost TWRP
Click to expand...
Click to collapse
Awesome! This should keep you in straight jacket before you do some more damage
With 5.2.0 recovery working (?), you are all set to sideload 4.5.3 and root it again:
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
bibikalka said:
Awesome! This should keep you in straight jacket before you do some more damage
With 5.2.0 recovery working (?), you are all set to sideload 4.5.3 and root it again:
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Click to expand...
Click to collapse
Should have been clear. After I tried the recovery, I lost TWRP but I am still stuck at the amazon logo. I think I might be screwed now... haha
EDIT: I tried a 4.5.2 bin that I had but it wont pass verification. Downloading the one you referenced and will try to side load that. Am I going down the wrong path? Seems like I should be able to get a stock package and sideload it over adb right?
UPDATE:Just sideloaded the one you lined. Seems like it worked. As soon as I started it, it forced an update though. Thank you! I think I am in a good spot to root again.
JesseHammil said:
UPDATE:Just sideloaded the one you lined. Seems like it worked. As soon as I started it, it forced an update though. Thank you! I think I am in a good spot to root again.
Click to expand...
Click to collapse
Well, you have to make sure that you disable OTAs right after you sideload 4.5.3, or it will immediately replace 4.5.3 with 4.5.5 which is not rootable directly !
bibikalka said:
Well, you have to make sure that you disable OTAs right after you sideload 4.5.3, or it will immediately replace 4.5.3 with 4.5.5 which is not rootable directly !
Click to expand...
Click to collapse
Makes sense. I actually ended up on 5.0 and I should still be able to downgrade from there I think. Thanks for the help