Related
I was so excited to update to Ice Cream Sandwich but my wifi xoom is stock rooted on 3.2.1 and so I booted into clockworkmod recovery readying my nandroid backup before I set it to stock and it stays frozen on the backing up data portion. I don't think I had enough free space for a full back up so I force reset and now I'm stuck in a boot loop. I can't get my tablet to mount on the computer and the external sd card has never worked correctly. I have pictures and movies of my baby when he was first born and I don't wanna lose this data forever. How the HELL do I fix this? Any way to transfer the contents of my xoom or am I completely f*****? I should've gotten an Ipad. I'm obviously not smart enough to handle Android.
Let's see. You can't brick these things first of all, I tried its almost impossible.
Reboot the sucker with volume+ and power and go into the dev forum and read the rest of the instructions.
Sent from my Xoom using Tapatalk
I appreciate the quick reply but I've reset the xoom several times. It'll stay on the honeycomb boot animation forever or until the battery dies. I don't know what to do.
If you flash a recovery you should then be able to get
into the recovery stage, from there you can mount the
Xoom and hopefully back up your photographs onto
your computer. Search forums for the recovery to use,
the info already on the site is much better than I can
hope to provide... good luck and I hope you save your
pictures
jessman1988 said:
I appreciate the quick reply but I've reset the xoom several times. It'll stay on the honeycomb boot animation forever or until the battery dies. I don't know what to do.
Click to expand...
Click to collapse
Boot to recovery and make sure that still works. Then let's go from there.
Do you have ADB running on your computer? We can use that to fix things.
It's nearly impossible to totally brick a XOOM. I've brought mine back from exactly the same boot issue you are talking about.
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
Cut and Pasted from NearDood's thread about 3 or 4 down:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
athletex2 said:
Boot to recovery and make sure that still works. Then let's go from there.
Do you have ADB running on your computer? We can use that to fix things.
It's nearly impossible to totally brick a XOOM. I've brought mine back from exactly the same boot issue you are talking about.
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
Cut and Pasted from NearDood's thread about 3 or 4 down:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Click to expand...
Click to collapse
U realize this will wipe the entire xoom right
Hello. Thanks for posting the tutorial. I have the SDK and everything set up from when I rooted my Xoom but I realize that I should back things up more often and I might as well just format and start fresh. I'm pretty damn depressed but then I could update to ICS and I just want the headache to be over. Any way to copy the contents of the xoom on my pc, or would I have to be booted up properly first?
Okay. I directions and even relocked the xoom. Now it's stuck on the dual core motorola screen without a boot animation. I even repeated the directions again to try and fix it. What do I do now? This is so stupid...It made it worse.
athletex2 said:
Boot to recovery and make sure that still works. Then let's go from there.
Do you have ADB running on your computer? We can use that to fix things.
It's nearly impossible to totally brick a XOOM. I've brought mine back from exactly the same boot issue you are talking about.
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
Cut and Pasted from NearDood's thread about 3 or 4 down:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Click to expand...
Click to collapse
Never try that because it will erase everything!!!
I was already aware of that but I really just want my stupid Xoom to start up again and even after erasing everything and flashing everything it won't even grant me with a simple boot-up. What the hell do I do to fix my Xoom now that everything's gone and I have nothing to lose?
jessman1988 said:
Okay. I directions and even relocked the xoom. Now it's stuck on the dual core motorola screen without a boot animation. I even repeated the directions again to try and fix it. What do I do now? This is so stupid...It made it worse.
Click to expand...
Click to collapse
since you have relock your device, you have already lost all your data, there is no way back. (you shouldn't relock it in the first place)
and right now, you want to "unbrick" your xoom and that's simple:
1) go to fastboot
2) unlock the bootloader again
3) go to http://developer.motorola.com/products/software/
4) download the right image for your device
5) extract the zip file
6) flash the images with fastboot using the instructions shown on the website
7) (optional) lock the bootload again, or you can leave it unlocked
I downloaded the second from the top like I was told to but it stays stuck at the motorola screen. Everything says it was successful in fastboot but I just can't get it to boot up. What else is there to try? I have I wifi US xoom. Did I download the wrong rom?
I know this should not matter, but when you did all of this did you still have your SD card in the Xoom? If so take it out and try again. I was having some issues flashing my Xoom and after I took the SD card out everything worked fine.
I actually took my SD card out before I did anything with fastboot. I've never been able to get recovery to read my sd either. Basically, I need some magic cure all through fast boot or I'm gonna have to chuck my Xoom in the closet with all my other "broken devices".
Okay. In an act of desperation I've unlocked my device again and have some version 3 clockworkmod recovery installed and I got Team EOS nightly 36 of ICS installed. I wanted the official 4.0.3 but seeing as how my xoom can somewhat function again, what is the best firmware, hands down to be running on and can i get a tutorial on how to get there? Thanks again for helping a poor n00b out, but I don't know where to go from here. I want a stable OS, and the nightlies kinda make me feel unsure. Thank you so much.
jessman1988 said:
Okay. In an act of desperation I've unlocked my device again and have some version 3 clockworkmod recovery installed and I got Team EOS nightly 36 of ICS installed. I wanted the official 4.0.3 but seeing as how my xoom can somewhat function again, what is the best firmware, hands down to be running on and can i get a tutorial on how to get there? Thanks again for helping a poor n00b out, but I don't know where to go from here. I want a stable OS, and the nightlies kinda make me feel unsure. Thank you so much.
Click to expand...
Click to collapse
The Eos nightlys are absolutely stable and on #37 for wingray, is quite complete. You will need to flash the Eos GApps v10.2, then once you set everything up, just stick with that until Eos releases their final version.
You have nothing to gain from going to the "official" stock ICS rom. Take some time to get to know the Xoom and hows/whys of flashing before going on another adventure...that's my advice!
Hey thanks. I'm glad I picked a decent one. I just can't get some of my game,es working. Even ones that say they're compatible with ice cream sandwich and my Xoom. Is this normal for a test build? I'm gonna be freaking out if I can't play my modern combat 3. Lol'
jessman1988 said:
Hey thanks. I'm glad I picked a decent one. I just can't get some of my game,es working. Even ones that say they're compatible with ice cream sandwich and my Xoom. Is this normal for a test build? I'm gonna be freaking out if I can't play my modern combat 3. Lol'
Click to expand...
Click to collapse
just in case you want to flash to stock so you can have the soak test ICS you need to go back to stock using this
Build HWI69 for US Retail from this section MZ604 - XOOM with Wi-Fi
a few boxes down
Thanks a bunch. Is there a link or further instruction because I messed up because I didn't have clear direction. I got modern combat 3 working by installing EOS nightly 37 but its very choppy and grand theft auto 3 freezes whenever it goes in game. I would very much like to use the official version if its more stable.
It's not an issue of stability; it's how the build, which I think is now a debugging build, is recognized by the game app. If the games are the most important for you, then happy flashing!
MOD EDIT: Ronjoe requested i put the link to droidstyle's guide in here:
http://forum.xda-developers.com/showthread.php?t=1238070
Foreword:
After scouring these forums for a guide for getting CM7 on the Fascinate, I found myself a bit confused and lost. I set out to create a new guide using what I learned from the others, and this is what came out of that.
Anyways, let me start this thing...
*clears throat*
Oops! It seems you've gotten into a bit of trouble! You may have been trying to stick a square peg in a round hole, fly too close to the sun, or perhaps run with a plasma sword. In any case, you've bricked your phone, and you have resorted to seeking help on the interwebz. Well look no further! Uncle Ronjoe can solve all of your Fascinate-ing problems!
Let us begin...
0. Gather everything we need:
i. Obviously, your phone and its USB cable.
ii. Download the files for this guide and extract them to a convenient place on your computer.
Please take note of some important information about this guide:
You must use an OEM cable for the Fascinate.
Regardless of whether your phone is bricked, on another ROM, or doing this for the first time, the steps are the same. Just follow along with the instructions.
If anything goes wrong, you've just bricked the phone again. It's not a big deal: just start over from the beginning of the guide.
Once you have installed CWM, NEVER use the "three-finger salute" (Volume Up, Volume Down, and Power) to enter recovery. This will remove CWM and replace it with stock recovery. Instead, use ADB, terminal, or an app to reboot into recovery.
Real men index their lists at 0. Just sayin'.
1. Make sure you have the official Samsung drivers installed.
NOTE: If you have used Heimdall in the past, you need to uninstall that driver (read its readme) and reinstall the official Samsung ones. If not, don't worry about it.
2. Put your phone in download mode:
i. Turn off the phone and remove the battery.
ii. Press and hold the Volume Down button.
iii. While holding Volume Down, plug the USB cable into the phone.
iv. If you now see a yellow "Download Mode" screen, you're in download mode.
3. Extract the zip and open Odin.
4. If Odin recognizes the phone, a yellow bar will appear under the top left square, and it should say "Added!" in the message box on the bottom left. If Odin does not see the phone, go back to Step 0 and double check everything.
If you are starting with stock firmware for the phone and just want CM7, feel free to skip ahead to step 9.
5. Place Atlas_v2.2.pit in the PIT section.
6. Place the EH03 image in the PDA section (NOT PHONE!!!).
7. Click "Start" and go grab a Snickers. This will take a while.
8. When you see "PASS" in the box, the phone will shut down. Reinsert the battery.
If all you want is stock, you can stop here. But if you want CM7, then follow the rest of this guide.
9. Reboot the phone.
10. Put the zips for CM7 and Google Apps on your SD card.
11. Put the phone in download mode and open Odin again.
12. Put the fixed CWM4 in the PDA section. Hit "Start."
13. Boot the phone into recovery. It should do it automatically the first boot. If it doesn't and it boots completely to stock Android, use terminal or adb to reboot it in recovery. (DO NOT use the three-finger salute)
It should be CWM v 4.0.1.0.
14. Now in CWM, Flash CM7:
i. Wipe data, cache partition, and Dalvik cache (under Advanced)
ii. Still in CWM, go to "Install .zip from sdcard." Select the CM7 zip and install it (You may want to get another Snickers). The screen might go blank a few times. This is normal.
iii. Reboot the phone.
15. After the phone boots up to CM7 completely, reboot to recovery. (either perform step 13, or long-press the power button, select reboot, and choose recovery). At this point, if your touchscreen does not work, just reboot CM7 by pulling the battery. (DO NOT do a three-finger salute)
It should be CWM v 5.0.2.6.
16. Once again in CWM, wipe cache and Dalvik (but NOT DATA) and go to "Install .zip from sdcard." Choose the GApps zip and install it.
17. Reboot. The GApps installer should now run.
18. (Optional) Go back into CWM and make a backup, so you don't brick the phone again.
19. ???
20. PROFIT! I told you there would be profit, didn't I?
Comments, questions, or suggestions? Feel free to speak your mind! If your question isn't obvious or answered already, I might even respond! If it is, well, you'll figure it out soon enough.
suggestion: dont knock others contributions to the community...makes you look like a....well ill let you fill in the blank.
Well sir, although I appreciate your attempted contribution to the community, I must strongly disagree with your "reasons" for thinking "THE GUIDE" is in some odd way " inadequate ". Many in this community have used, and referred many new users seeking help and advice, to this Guide with great success. Also, as mentioned by above OP, don't knock the hard work and contributions by other Devs. It really does make you look like a......well you know.
Sent from my SCH-I500 using XDA App
Sorry, I was in the wrong frame of mind when making the guide. I didn't mean to offend. Rather, I hoped that the comment would prompt the other guidemakers to fix their mistakes.
All I can say is that droidstyles guide has been my flash bible and has never failed me. If there were any errors, why not simply PM him with suggestions? He has always seemed to appreciate and incorporate feedback.
Ronjoe said:
Sorry, I was in the wrong frame of mind when making the guide. I didn't mean to offend. Rather, I hoped that the comment would prompt the other guidemakers to fix their mistakes.
Click to expand...
Click to collapse
Let's see......You've been a member since January 2011 and in a little over a year you've only managed to contribute 7 posts to these forums. You haven't been helping people, answering questions, and providing guidance on a daily basis like the members you are disparaging and insulting first with your OP "oh look these other people are morons and have made completely confusing guides so I'm making one that is so much moar better", and second after your insulting demeanor is pointed out to you, you say you weren't in the right frame of mind then go right back to insulting by pointing out that the other guide makers need to "fix their mistakes." Pretty much confirms you are a........well you know.
--snip--
EDIT: Sometimes saying nothing is better for eveyone involved.
Ronjoe said:
--snip--
EDIT: Sometimes saying nothing is better for eveyone involved.
Click to expand...
Click to collapse
I guess I can see your side of it too. However a simple search would have landed you on droidstyles guide. But some of the comments have gone a bit too far. Its not like your an 11 year old named twinkie
Sent from my SCH-I500 using XDA App
This guide is a slightly modified step-by-step write-up of m.sabra’s one click root guide found at http://forum.xda-developers.com/showthread.php?t=1589251, so please head over to his thread and thank him! I thought making a step-by-step guide would be helpful in case anyone wanted to see how exactly rooting this phone happens.
This guide is for rooting your Nexus S [works with NS4G, I9020T, I9023, and I9020A variants]. By the end of this guide, your device will have an unlocked bootloader, a custom recovery, root access and Superuser app, and the ability to flash ROMs and kernels.
[Disclaimer! Your warranty is now void. I am not responsible for bricked or damaged devices! You are choosing to follow this guide]
Step 0: Download and extract the file found here http://d-h.st/gcZ to your C:/ drive (for simplicity’s sake).
Plug in your phone and put it into USB Debugging Mode, found by going to Settings>Applications>Development (in Gingerbread) or Settings >Developer Options (in Ice Cream Sandwich).
Extract and install the drivers included if you don’t already have them installed.
Step 1: Turn your phone off.
Then, press both the volume up and power button.
You should now be in the Android Bootloader Interface (with a green Android and the options for Reboot, Recovery, Reboot Recovery, and Power off)
Step 2: Now, we have to open a command prompt and change the directory to the location where we have extracted the files (which, if you followed step 0, should be in the C:/ drive).
Open a command prompt and type “cd C:\Nexus S One Click Root.”
We should now be in the correct directory for using fastboot commands.
Step 3: Type the command “fastboot oem unlock” and press enter.
A screen should pop up on your Nexus S.
Use the volume buttons to scroll and the power button to select “Yes” (as the screen says, picking yes WILL wipe everything on your device).
Step 4: Type the command “fastboot flash recovery cwm.img”.
Press enter.
Then type “fastboot boot cwm.img”.
Press enter.
Step 5: Now we have to mount USB storage to copy over the Su.zip file and install it.
Tap or use the volume keys to scroll and select “Mounts and Storage” > “Mount USB Storage” [you have to scroll down to get to it].
Copy the su.zip file to your Nexus S.
Press “Go Back” twice to return to the main menu.
Step 6: Press “install zip from SD card” [you can also use the volume buttons to scroll and the power/lock button to select].
Press “choose zip from SD”.
Press the “su.zip” file you placed on the SD card earlier.
Press “Yes.”
Congratulations! Your phone is now rooted! Select “Reboot System Now” and enjoy!
Thanks for this, the other guide was a bit out of date and hard to follow.
However, is there any way to root without erasing everything? I know there is a method to root without unlocking the bootloader and saving the SD card contents, but will that also keep all the apps and settings? Don't really want to redownload the programs and set the phone up again.
Ashhong said:
Thanks for this, the other guide was a bit out of date and hard to follow.
However, is there any way to root without erasing everything? I know there is a method to root without unlocking the bootloader and saving the SD card contents, but will that also keep all the apps and settings? Don't really want to redownload the programs and set the phone up again.
Click to expand...
Click to collapse
Sorry, if there is a way to this without wiping the device I don't know it. Google backs up your contacts and wireless networks and keys and the Play Store remembers your apps (not their data), but that's it. :-(
I'm already unlocked from rooting 2.3.7. I then did an OTA update to ICS. I checked that bootloader still says lock status is unlocked. Can I just start with step 4? I don't want to wipe anything as some data still needs to be backed up and I need superuser installed to do that.
Moritzio said:
I'm already unlocked from rooting 2.3.7. I then did an OTA update to ICS. I checked that bootloader still says lock status is unlocked. Can I just start with step 4? I don't want to wipe anything as some data still needs to be backed up and I need superuser installed to do that.
Click to expand...
Click to collapse
Sorry for the late reply.
Yeah you should be able to do that with no problem.
Sent from my Nexus S 4G
When I type in "fastbook oem unlock" , the command window stops at "< waiting for device >" and it's been a couple of hours and nothing has popped up on the phone screen, how can I get past this? I'm on stock ics 4.0.4
danshuynh said:
When I type in "fastbook oem unlock" , the command window stops at "< waiting for device >" and it's been a couple of hours and nothing has popped up on the phone screen, how can I get past this? I'm on stock ics 4.0.4
Click to expand...
Click to collapse
Make sure you have the phone drivers installed properly.
Does this work on Jelly Bean??
Can I replace the SU.zip file with the latest chainfire release or is the one included in the download ok?
Yes, it should work with Jellybean. Just remember to enable USB Debugging.
You can either use the SU in the download and update it via the play store after you're done rooting or just use the latest one from the start. Whichever one you prefer.
Sent from my Galaxy Nexus using xda app-developers app
Awesome thanks!
Do you think I should wait for the OTA 4.1.2. then unlock and root? I take it that it will boot me back into a factory reset 4.1.2.? Can I then flash a custom kernel??
I'm not really into trying different ROM's, I really just want Voodoo sound on my Nexus S.
What about the clockwork mod in the folder? Will that version be ok?
Cheers.
So I got my phone back (see http://forum.xda-developers.com/showthread.php?t=1874402 ) and it seemed to have been left unlocked by the guys who fixed it. Anyway, I followed these instructions and it seemed to work except for the fact that I don't actually seem to have root access.
For example, the superuser app sees the su binary installed from su.zip...
View attachment 1416322
... but fails when it tries to update it:
View attachment 1416323
Any suggestions for what to do next?
Thanks this one is pretty neat. I just rooted a while back but I think this is way better than others.
there are so many ways to root now. this one is pretty straight forward.
and thanks for adding the line "USB Debugging Mode":good: I missed that part on faq links.
so thats great.
Regards
[Nexus S i9020a .. CM10 Nightly + Slim gaaps dark (inverted) 2.7a]
Many thanks!
Step by step very easy for n00b like me, impossible to fail
Installed on 4.1.2 stock with TWRP recovery intsead of CMW.
All the best.
1024k said:
Many thanks!
Step by step very easy for n00b like me, impossible to fail
Installed on 4.1.2 stock with TWRP recovery intsead of CMW.
All the best.
Click to expand...
Click to collapse
Glad to help
Sent from my Galaxy Nexus using xda app-developers app
Also flashed gapps 4.2 , don't know why I waited so long....the phone is very responsive and CM10, for what i read, is not the fastest rom.
Thanks!!
You're welcome!
Sent from my Galaxy Nexus using xda app-developers app
ohh bugger I have lost root.
I unlocked and rooted many months ago and have only been using stock with Thalamus kernel. Now root has gone.
How do I enable it again?
I have tried re flashing su.zip (an old version) but didn't work.
Will I have to go through this guide again?
Cheers.
---------- Post added at 12:27 PM ---------- Previous post was at 11:55 AM ----------
My phone is unlocked so I have tried doing the guide from step 4 but it still says I'm unrooted.
Damn.
Warren_Orange said:
ohh bugger I have lost root.
I unlocked and rooted many months ago and have only been using stock with Thalamus kernel. Now root has gone.
How do I enable it again?
I have tried re flashing su.zip (an old version) but didn't work.
Will I have to go through this guide again?
Cheers.
---------- Post added at 12:27 PM ---------- Previous post was at 11:55 AM ----------
My phone is unlocked so I have tried doing the guide from step 4 but it still says I'm unrooted.
Damn.
Click to expand...
Click to collapse
You're sure your phone's boot loader is unlocked? Try booting into recovery. If that works (ie, you are able to boot into cwm try looking for SuperSu.zip and flashing that or try the su.zip from this thread (Step 5). Let me know if you need clearer instructions (Curious: did you do install something that made you lose root or what? )
Sent from my R2-D2 unit on the far side of the moon
Warren_Orange said:
ohh bugger I have lost root.
I unlocked and rooted many months ago and have only been using stock with Thalamus kernel. Now root has gone.
How do I enable it again?
I have tried re flashing su.zip (an old version) but didn't work.
Will I have to go through this guide again?
Cheers.
---------- Post added at 12:27 PM ---------- Previous post was at 11:55 AM ----------
My phone is unlocked so I have tried doing the guide from step 4 but it still says I'm unrooted.
Damn.
Click to expand...
Click to collapse
Try a newer version of su.zip - that was my problem when at first I couldn't root.
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
If you know how to use fast boot try this command:
fastboot -i 0x1949 oem idme bootmode 4000
That should get you out of the twrp loop.
Sent from my Amazon Kindle Fire using XDA
gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.
kinfauns said:
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.
Click to expand...
Click to collapse
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in
gdr425 said:
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in
Click to expand...
Click to collapse
Just having it show up isn't good enough. With TWRP open... you need to have it show up exactly as "Android Phone -> Android Composite ADB Interface" and "Composite" must be in there.
If it does that... Go to your Kindle Fire Utility folder, open the tools folder inside there. Once you have that open, shift-right-click inside the folder and select "Open command window here" to get to the command line. Then inside that enter these two commands... one after the other....
Code:
adb shell idme bootmode 4000
adb reboot
Your KF should restart back into a normal boot and get you to your system.
EDIT: I guess I should mention that the "shift-right-click" inside a folder works in Windows 7, but I'm not sure that it does in previous versions.
When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?
gdr425 said:
When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?
Click to expand...
Click to collapse
If it's able to reboot with the "adb reboot" command, I'm guessing your drivers are working fine, but just to verify... What device is shown in the device manager when you have it booted into TWRP?
It's possible that you have a broken ROM flashed onto your device right now and it can't complete a normal boot. You might want to try flashing a new ROM...
If it's rebooting after issuing the commands, then you shouldn't have to press the power button once the yellow triangle comes up. Just give it a few seconds to get past that part and to the KF screen.
I was having the same issues yesterday after flashing, but resolved once I realized I could issue the commands.
if I dont press the power button it just shuts down, I actually figured out a fix for this brick that worked for me I'll post it in a thread today because i've seen a lot of people having the same problem without much success, THANKS to EVERYONE who helped me with this!
http://forum.xda-developers.com/showthread.php?t=1576675
should take care of your problem
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N
So is this usable in all situations? If yes then should download it & store it safely
Interesting thing, can this update bypass factory reset protection?
iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.
This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you
Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?
holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.
TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939
just want to ask would this method work if the phone has not been authorized to a specific PC ?
iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...