ok. i successfully rooted this kindle with "root with restore by Bin4ry." i am pretty sure i was on version 7.2.1. i made an attempt at installing a second bootloader with TWRP using seokhun's noob-proof tutorial, step by step. bam, brick. maximum bootloop. i then went to use KFHD System.img restore tool, to no avail. KFFA, no-go. i made a factory cable to get it into fastboot, and it works- the only life it shows is fastboot screen or bootloop with the kf logo. only in fastboot with a regular usb does adb recognize a connection. now, my main goal is to just recover from this brick and carry on. i have scoured the forum and got the same thing every time. is it a permanent brick?
i'm not a complete noob, i have plenty of experience rooting and flashing several models of htc androids. this is just super confusing, cuz i can usually fight thru stuff like this. any guidance is appreciated!
Related
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
I am having a brutal time with recovering my rooted, soft bricked Droid Charge. More than a while ago while trying to root it, I bricked it, but followed the step by step tutorial on this site and fixed it with ease. But recently, it magically soft bricked. I tried EVERYTHING to recover it, including all the step by step tutorials on here to recover a Droid Charge. I have it to the point where it boots (which takes forever). It'll boot to the main screen then basically freeze and shut down. I re-flashed the rom, pit, recovery, etc, etc ... and that's about as far as I can get.
Is my phone pretty much shot? Does the usb port matter? All the files were successful in Odin, but I was using Windows on a duel booted Macbook. But either way, it's stressing me out, especially now that I'm stuck with a lag-fest BlackBerry that makes me want to throw myself out the window. Can anyone help?
_Silky said:
I am having a brutal time with recovering my rooted, soft bricked Droid Charge. More than a while ago while trying to root it, I bricked it, but followed the step by step tutorial on this site and fixed it with ease. But recently, it magically soft bricked. I tried EVERYTHING to recover it, including all the step by step tutorials on here to recover a Droid Charge. I have it to the point where it boots (which takes forever). It'll boot to the main screen then basically freeze and shut down. I re-flashed the rom, pit, recovery, etc, etc ... and that's about as far as I can get.
Is my phone pretty much shot? Does the usb port matter? All the files were successful in Odin, but I was using Windows on a duel booted Macbook. But either way, it's stressing me out, especially now that I'm stuck with a lag-fest BlackBerry that makes me want to throw myself out the window. Can anyone help?
Click to expand...
Click to collapse
what is phone model dude?
Any help appreciated. I was trying to install second bootloader to my kfhd7 and HAD twrp working and when trying to complete the process upon reboot when the red triangle recovery screen showed up(i thought nothing of it) and it asked to restore device or something else, i believe i chose the restore option. ever since i have been stuck at the splash screen with orange kindle fire replaying over and over. I made a flimsy fastboot cable(which is now broke, I ordered a skorpn one) and was able to get into fastboot but i absolutely cannot get the device recognized in fastboot or adb. Mind you i had the drivers/adb working previously. I fear that without FB recognition on my pc I will be SOL... running windows 8 and FB cable should be here tomorrow or next day. wanna be prepared when they arrive. In advance thank anyone who helps for your help.
psver the last week im pretty sure i've read almost every kfhd7 post out there and haven't found one exactly like this. do not seem to find anyone else having some much trouble getting ADB/Fastboot to see device as me when in this situation(used to be the easiest part for me).
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
issact said:
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
Click to expand...
Click to collapse
zironia said:
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
Click to expand...
Click to collapse
Hey, it's good to hear I'm not alone in this. lopestom has been friendly enough to correspond with me about it and he suspects it's a new model of the same phone. I sent him a screen cap of the factory settings screen (VOL-/POW)
In the end we might be out of luck until more people get their hands on the new version of the phone.
I would gladly appreciate and donate to anyone who can step-by-step guide Me to reviving My Shield Tablet 32GB LTE US! I had TWRP but somehow cannot make it back into it, all i get is the bootloop or the Fastboot screen. My laptop runs on Win8 and most of the time can't or won't recognize the tablet and when it does, it can never seem to find the files I'm trying to push to it. Someone told Me it can never be truly or permanently bricked and for about 6 months I gave up but I miss having a bigger screen, games, all the storage, etc. I need My tablet back and NOBODY is giving Me a clear way to do it as I AM pretty much a noob at all this. This is the absolute most stressful/tedious root I had ever had to do and shortly after getting TWRP and achieving root access through KingRoot, I accidentally wiped My partition and then locked Myself out of recovery... If ANYONE can help, I would ULTIMATELY appreciate it. Thank You.
Mmmmmmmh your tablet have unlocked bootloader?
If yes probably you can do something with ADB....
if not...i think you can trash your tablet ;_; at least if you don't solder an eprom flasher, but it's out of my possibility and need sort of reverse engeneering
If you can actually get to the fastboot menu, you should be good to go. You'll have to unlock your bootloader, but once you do that you can flash the recovery partition or flash an entire recovery image. Do respond if you're looking to do so.
I unlocking the bootloader was the very first thing I did. Yes, i need to know exactly where to get the image, where to save it, and how to push it thru adb please.
I do have accidental insurance... But i don't want to do that.
If you go to the link in my signature, you will find guides for flashing the recovery partition (among other things) as well as download links for the recovery images.
If you lack installations for adb/fastboot, there's a tool on XDA called Minimal ADB and Fastboot. I'd recommend using it.
can you help me? I have same issue.
My tablet only shows up as APX in device manager.
Cant boot up to NVIDIA logo, Cant boot up to fastboot nothing.
It was unlocked before now.
No bootloader, no luck. Only NVIDIA can help you now.
http://forum.xda-developers.com/shield-tablet/help/help-help-bricked-shield-tablet-original-t3313428
I believe I can get it working again somehow by puting the recovery on the SD card seeing how mine came with a usb adapter
Reflash twrp via fastboot