So I bricked my kindle fire by screwing up with the framwork-res.apk. The problem is, no CMD commands will work for me when I follow the stickied unbrick guide. So, can anybody walk me through it?
ON TOPIC
So, since my framework-res.apk won't work-I wonder:
If I make a backup using TWRP on somebody else's kindle, transfer the backup files onto MY kindle, and restore using that backup through TWRP on my Kindle, will that fix the framework-res.apk and therefore unbrick my kindle?
So, in short:
1) Make backup from someone else's kindle with TWRP.
2) Put that backup file into my bricked kindle.
3) Launch TWRP on my bricked kindle and restore using the normal backup from antoehr person's kindle.
Will that fix my problem of my bad framework-res.apk file? Even though I will have the other person's account info? Or does it not work that way?
__________
AND CAN ANYBODY HELP ME? THE CMD commands are just NOT working! It's driving me insane. I keep on getting error after error and I just can't launch "adb shell" or anything else without getting an error. Can somebody PLEASE walk me through? I will gladly pay you afterwards (no lie).
Related
I gained root and installed ClockworkMod Recovery. When I booted every process crashed so I selected wipe data/facory reset. Well now I only have the ClockworkMod Recovery and it will continuously load the 2 slash screens.
Before I cause anymore damage can anyone tell me how to go back to how it was from the factory?
You need to sbf from the bootloader if you didn't hose that by installing clockworkmod because it sounds like you didn't use koush's bootstrap to install it the way the D2 needs to have it installed. Please let me know if I'm wrong.
There are two tutorials for flashing the sbf one in windows and one in Linux but both have information worth knowing. I'd link them but I'm on my D2.
EDIT:
Windows.
Linux.
but you should read through BOTH of them before flashing.
Sent from my DROID2 using XDA App; Edited from a PC
p.s. I don't mean to criticize but a more informative thread title would be nice. If you had "Bootloop after ClockworkMod install" for a thread title that means more to me than "I need help".
Thank you that is a start. I really shouldn't have attempted this...
I got a critical error after I selected the sbf.
http://iamthewalcs.com/SBF Files and Update files/SBF File/Droid 2 Global FULL SBF.zip
I try to download that file but when I try and open it is says invalid.
Problem Solved I had to format everything first then do the steps listed.
i want to root and install recovery using KFU but before i get started i just want to ask a few question.
1. i do i need a wi-fi connection in my kindle fire before using KFU?
2. when connecting my KF to my computer, will i turn off first my KF?
3. when im in KFU what boot mode should i pick before starting to root and install recovery?
i hope someone can answer my questions, i can't do anything about my KF because i don't have a wi-fi, so i'll just install custom roms like CM7 or CM9
trycks said:
i want to root and install recovery using KFU but before i get started i just want to ask a few question.
1. i do i need a wi-fi connection in my kindle fire before using KFU?
2. when connecting my KF to my computer, will i turn off first my KF?
3. when im in KFU what boot mode should i pick before starting to root and install recovery?
i hope someone can answer my questions, i can't do anything about my KF because i don't have a wi-fi, so i'll just install custom roms like CM7 or CM9
Click to expand...
Click to collapse
Hope this helps:
1. Yes as it will download the files needed for TWRP and root for u automatically.
2. Nope you do not need to turn off while you want to connect to the computer.
3. In most cases you do not need to choose what bootmode to use.
P.S. Remember to make use of the install driver function in the KFU before you do anything.
i have successfully rooted my KF without wi-fi then i proceed to installing the twrp also without wi-fi but unfortunately the KFU said file missing and then i was stuck at kindle fire logo
what will i do now?
ok i finally manage to get out of stuck kindle fire logo.
right now my KF is rooted and i want to install the twrp and fire, fire, fire.
if someone can answer my question it would be a big help
1. is there a way i can install the TWRP and Fire,Fire,Fire without kindle fire using wi-fi?
2. what will i install first, the TWRP or the Fire,Fire,Fire?
trycks said:
ok i finally manage to get out of stuck kindle fire logo.
right now my KF is rooted and i want to install the twrp and fire, fire, fire.
if someone can answer my question it would be a big help
1. is there a way i can install the TWRP and Fire,Fire,Fire without kindle fire using wi-fi?
2. what will i install first, the TWRP or the Fire,Fire,Fire?
Click to expand...
Click to collapse
1. kindle fire does not need wifi to install FFF or TWRP
2. Install FFF, then TWRP
but when i tried to install the twrp first it says "missing recovery file" something like that. do i need to download this:
Extras(Will auto download, only for manual install users)
Apps.zip = Click Here (Place in a folder called apps)
TWRP = Click Here (Place in a folder called recovery)
trycks said:
but when i tried to install the twrp first it says "missing recovery file" something like that. do i need to download this:
Extras(Will auto download, only for manual install users)
Apps.zip = Click Here (Place in a folder called apps)
TWRP = Click Here (Place in a folder called recovery)
Click to expand...
Click to collapse
if you are manually installing via adb shell commands then you will need those. If using KFU then the files that are needed are downloaded via your PC's internet connection and sent to your kindle
ok thanks for clarifying at first i thought that the KF will download the files
its still the same it says recovery.img missing
trycks said:
its still the same it says recovery.img missing
Click to expand...
Click to collapse
it's cause the download link was down
now it should work again:
http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
maybe download it manually, rename to recovery.img and place it in the recovery folder of kfu
ty
thanks b63 you helped me again
Hi Everyone,
I've been using these forums for along time and have not really had the opportunity to give back until now. Let me give you all the details to my problem and the solution to help anyone else in the same if not similar situation. Apologies if this thread has any errors just let know and I'll try to fix them. Also I am confident enough to use command line to do the things I talk about below, so you'll have to be as well if you want to use the methods described. I assume you have some level of technical ability to do this.
Phone details:
Nexus 4, bootloader unlocked, twrp custom recovery installed, rooted, running 4.4.2.
Problem:
I managed to drop my phone after having it for a year. The screen on front cracked and i couldn't use the touch. This caused a problem using the custom recovery (I use TWRP) because it was touch as well. Most of the information on my phone was backup up, my whatsapp is set to backup and push to my box account nightly using titanium backup, my pictures get uploaded to dropbox, instagram has my instagram, etc, etc. But, there were a few files I really needed in my downloads folder. I spent the whole weekend looking for articles and forum posts to help get my data off. Many required installing an app of sorts and then remote controlling the device. I could install the apps using the play store, but as couldn't get passed my lock screen, which is a combination of widget locker and the standard pin unlock screen I couldn't authorise or configure anything.
Solution:
Anyway, here is what i did. I already had WUGFresh's Nexus Root Toolkit and used adb to pull the files and fastboot to flash clockworkmod custom recovery with no touch. Here are the details.
I loaded the phone into recovery which allowed me to use adb. To use adb I opened the WUG Fresh Nexus Root Toolkit, clicked launch Advanced utilities (bottom left). Then used Manual Input (Launch CMD Prompt). Here I used the command 'adb pull /sdcard c:/pull' which grabbed all my files and dumped on the c: in a folder called pull. You can probably also use this method to copy other files from the phone, but i didn't try that.
In order to clear all my data (which i needed to do so the insurance company couldn't read it), I needed to flash clockworkmod custom recovery without touch. I got this from the CWM website and downloaded the appropriate img file for my device. I then booted my phone into fastboot. I used the fastboot help command to find out what the command was to flash a new recovery and did it. The command was 'fastbboot flash recovery c:/put/path/to/file.here'. This loaded the CWM recovery so i could wipe all my data. I just loaded into recovery and wiped all my data.
Summary:
I recommend you use a utility like titanium backup to automate a backup of all your important apps and their data on a nightly/weekly basis so if you ever get into a situation like myself you have some data to easily recover.
I hope this helps people going forward.
Arun.
You didn't need wug's, you could have just used adb to pull the files in recovery. You also could have run fastboot -w and it would have wiped your device. No need to put cwm on your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You didn't need wug's, you could have just used adb to pull the files in recovery. You also could have run fastboot -w and it would have wiped your device. No need to put cwm on your device
Click to expand...
Click to collapse
Thanks for the extra information, but I only used WUG's NRT because I already had it installed on my computer. The fastboot note is useful though, I don't think I read through the help list properly otherwise I would've done that. I also wrote this for people with a little amount of technical knowledge, and installing WUG's NRT is really simple to do and has a GUI.
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.
I just want to make sure I am understanding this correctly:
I cannot push supersu.apk to /sdcard and install, I have to use TWRP and/or Magisk and flash them to do this? Or will sideloading work? Assuming I can get TWRP sideload adb to initialize...
And when using TWRP, supersu.apk has to be flashed from an external USB drive?
Is this the case with every .apk I want to install?
And some preemptive follow-up questions:
When using TWRP do I want to allow it to make changes to READ ONLY? Or do I want to keep it as READ ONLY?
This was not exactly clear in the nvidiashieldzone guide (which caused me to brick my previous Shield, gotta love Best Buy's return policy).
Actually, their "flashing stock ROM guide" caused me to APX brick. First time I have ever truly bricked a device.
Edit: answered my own questions. Solved. This thread can be deleted and/or locked.