Related
I rooted my kindle fire 6.3.1 using the utility and installed twrp, everything is fine , once i install a custom rom it wont boot. No matter what rom Installed . it will turn on to the black and blue kindle screen then go black and nothing happens. Or the rom will boot but hangs at the boot image.
Did you "factory reset" before flashing the rom?
I'd download the newest version of kfu, then re-flash twrp , then fire fire fire, put the from on the SD card, then factory reset, wipe both caches, then install from and wipe caches again
Sent from my Galaxy Nexus using XDA Premium HD app
chris_m128 said:
I'd download the newest version of kfu, then re-flash twrp , then fire fire fire, put the from on the SD card, then factory reset, wipe both caches, then install from and wipe caches again
Click to expand...
Click to collapse
There is no reason to re-flash twrp and there is definitely no reason to re-flash FireFireFire unless absolutely necessary. Flashing a bootloader is potentially dangerous and shouldn't be done just for the hell of it.
The OP has one post on XDA, this one; which leads me to believe he was unaware of or has overlooked the importance of performing a factory reset before flashing any new rom.
[Edit:] That wasn't intended to sound so brash, but you get the point.
I get the point that you think you know a lot more than you do.
Edit: that was intended to sound exactly like it does
chris_m128 said:
I get the point that you think you know a lot more than you do.
Edit: that was intended to sound exactly like it does
Click to expand...
Click to collapse
I tried to convey to you that my intention was not to be rude, yet you respond with unnecessary hostility. What exactly do you expect to accomplish with this? Change my mind? Hurt my feelings? Cause me to be any different than I am? I'm guessing it's probably not going to happen.
forgive me o' mighty one
i have a droid x2 that i have rooted and switched roms on numerous times, as well as sbfing becoming one of my close friends. not sure what to do with the 3 different pages on rooting applications and methods. does a link to actual step by step instructions on how to root and intall roms exist? last night i rooted and installed twrp using the utility, but could not get it to boot for anything. held power down and all i get is a normal boot . when i went to install AOKP , i used the utility to get into twrp RIGHT after putting FFF on it. i flashed the rom and gapps after wiping data, and i got a blank screen for an hour. i found a tutorial on mounting sd card through twrp and saved it. my question is what is the proper way to root 6.2.2? and will installing roms through working twrp actualy work? if so how do i get twrp to work? thanks in advance guys.
clarity
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Lorenzo VonMatterhorn said:
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
Click to expand...
Click to collapse
Yes, you use adb but it instructs you what to type.
Sent from my Galaxy Nexus using xda premium
pyroscott said:
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Yes the first step should be root... which in my case also installs twrp...
If you're planning to install a custom ROM, there's no point in rooting. FFF and TWRP are more than enough.
aokp
ok well i rooted. and now twrp works flawlessly. but when i try to flash aokp, i wipe data/factory reset, install aokp and then gapps, i get nothing but a black screen after rebooting. after waiting a minute or two, i rebooted into recovery and restored a backup. am i doing something wrong? i started on 6.2.2 if that helps at all.
You should -always- wipe cache and dalvik-cache when flashing ROMs.
When you're upgrading the same ROM from a lower version to a newer one (for example, going from gede 1.65 to 1.7) you may skip factory reset, so long as there isn't a major change (going from normal to linaro, for example).
However, it is good practice to let Titanium Backup handle all of your /data backups and just factory reset every time as well.
You have the two most important steps done.
1. You have TWRP installed and you can boot into it. That is one of the hardest steps it appears.
2. You did a backup before doing anything else.
As Dasanko said you also need to wipe cache and dalvik-cache. When I do a new rom I wipe data, system, cache and dalvik-cache.
Titanium Backup (TiBu) is also awesome to restore your apps. However, you will need to install TiBu to use it to restore other apps. Some ROMS have it installed already and some don't. If you don't have access to TiBu from the Rom your are flashing you will need the GApps installed to get the Play Store. You can then download TiBu be able to restore your chosen apps.
Lorenzo VonMatterhorn said:
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Click to expand...
Click to collapse
Yes, you should get the screen with the triangle. I would try flashing the recovery again
Sent from my Galaxy Nexus using xda premium
also when you are installing a new rom I always wipe system so you dont have any errors because that is where the old rom is located. btw cm9 and aokp are both really nice on this device
I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
vbaros said:
If you are not afraid to loose your data. Enter the recovery and do a factory reset.
Click to expand...
Click to collapse
sfhub said:
There are always a small percentage of installations that won't work with a dirty flash (keeping your user data).
This could be because of the specific apps they have installed, flash memory corruption, etc.
That is why you should always backup before doing a system update.
The solution normally is to just wipe data/factory reset from recovery.
Click to expand...
Click to collapse
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
So wipe the data before flashing the factory image? Because I have tried booting into recovery AFTER doing the update to wipe data and it kept bootlooping still.
Click to expand...
Click to collapse
Sorry, I didn't read your original post closely enough, if you are bootlooping at google, then it is a problem with /system and wiping won't help. If you were looping at the bouncing balls or X, then that is user data related so wiping usually fixes it.
If you are stuck at Google, something went wrong with your flash or your flash memory got corrupted.
I would try reflashing the factory image, making sure to do the -w wipe option (by default that is what flash-all.bat does)
Make sure to pay attention to any errors that might show up.
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
msk said:
I had the same issue. You need to clear your data and cache after flashing the factory image. See my post here: http://forum.xda-developers.com/showpost.php?p=47472320&postcount=35
Click to expand...
Click to collapse
It worked all fine until i wiped data and cache at the end of your process... After rebooting it still bootloops and is now hanging at the Google sign... At this point I have no idea what I'm doing wrong...
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
Bump.. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What method did you use to flash the factory images?
Sent from my Nexus 7
RMarkwald said:
What method did you use to flash the factory images?
Sent from my Nexus 7
Click to expand...
Click to collapse
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
BraddahBoi808 said:
Command prompt through android sdk. Didn't boot, stayed at Google screen. Then tried wugs toolkit and same thing, hung at Google boot screen...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So you did all of the steps listed here? http://forum.xda-developers.com/showthread.php?t=2469508
Yes..
Sent from my Nexus 7 using xda app-developers app
Now sure if this means anything, but when i send the ota update zip through aideload, at the end it gives me
script succeeded: result was [/system]
Does that mean it worked or the system had something wrong??
Not sure on that one.
- Sent from my Galaxy S3
K this stupid thing must hate kit Kat or something cause no matter what ROM I try to flash that's kit kat it still don't boot. I'm tired of this already. Idk what else to do. I thought nexus devices were suppose to be the easiest ones to get updates... /end rant
Sent from my SCH-I545 using xda app-developers app
BraddahBoi808 said:
So my Nexus 7 still has not received the OTA update, and like a bunch of other, I decided to try to put it on myself. I tried both ways too - sideloading the zip and flashing the full factory image from google. Now I'm no newbie in this.. but for some odd reason, my Nexus 7 just wont boot past the Google logo in start up... any ideas? Ive been at it for the past couple days and still can't find anything on it
Click to expand...
Click to collapse
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Zaphodspeaks said:
I would try this, if you can use TWRP to back up your data partition, then use Wugfresh's Rom toolkit to flash to stock KRT160, and then root, and install your recovery again.. Then.. restore just the data partiton.. That should bring your nexus to working order..
This will only work if you can move the TWRP folder off your device, use the TWRP folder via OTG to a Sdcard or thumb drive and then copy it back when your back at stock.. Sounds complicated, but its very simple.. That may work for you
Or if your brave enough, just flash Bootloader.img first, then System.img from Stock image.. That should be the simpler method..
Click to expand...
Click to collapse
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
BraddahBoi808 said:
At the moment I dont really care about my data cause I dont have much on it. All i have are a couple songs and a movie, which is easily transferable because they are from my laptop. I just want this thing updated to kit kat. So, one more time, the methods I've tried using are:
Wug's toolkit to restore to KRT16O
ADB sideload to update manually using the OTA zip obtained from here
factory images obatined from google and flashed using the .bat in their zip
the link Mr. @RMarkwald posted
and through flashing stock KRT16O update from Scrosler's rom
So far, ALL methods will not allow my device to boot past the Google logo...
Click to expand...
Click to collapse
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Zaphodspeaks said:
Then i would suggest possibly restoring your Nexus to 4.3 and see if you can atleast get it working again..
Im thinking your device maybe corrupted, but dont quote me on that.. Can you atleast boot into recovery?
I made a recovery of a Stock 4.4 from TWRP incase I needed it..
If you cant boot into recovery on the device, you can try booting into TWRP via Wugfresh's tookit.. and try and restore your Nexus that way
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip Good luck..
Click to expand...
Click to collapse
I can restore back to JSS15R 4.3 fine and the device works fine, no issues. It's just for some reason it doesnt like anything 4.4, which I find very odd. It still hasn't gotten to OTA update either. After updating to 4.4 and it hanging on the Google screen, it can boot into stock recovery fine. I have wiped data and cache in there too to see if that works but nothing. Thanks for all your quick help by the way. So the method your saying now.. Do I flash that from my stuck 4.4 or from rooted 4.3?
I would try that from 4.3....Dont use the stock recovery.. Flash it from TWRP..
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
eris170 said:
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
Click to expand...
Click to collapse
A factory reset from inside TWRP does NOT wipe internal storage/sdcard. If you want to wipe everything you can either do it from inside TWRP with "advanced wipe" or just do a normal factory reset from Settings/Backup and reset. If you fastboot flash the userdata and cache images that would also be like a factory reset. If you wipe/erase the system you will need to fastboot flash the system image or flash a rom BEFORE you try and reboot.
wantabe said:
A factory reset from inside TWRP does NOT wipe internal storage/sdcard.
Click to expand...
Click to collapse
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else. When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things.
Should I just go find the stock OS image and recovery image and flash them over?
eris170 said:
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else.
Click to expand...
Click to collapse
I'm pretty sure that wiping data from inside advanced wipe will have wiped everything, that should have been enough to get rid of your encryption.
eris170 said:
When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
Click to expand...
Click to collapse
No. The system image I was talking about is from the factory image. You have to extract/unzip the factory image a couple times before you can see the zip folder with all the images ( boot (kernel), cache, recovery, system and userdata). You had mentioned in your first post "erasing userdata, system and cache." If you erase system you will need to replace it otherwise your device does not have an os (operating system) anymore. One of many ways to replace it would be to fastboot flash the system image (fastboot flash system system.img) that is extracted from the factory image.
eris170 said:
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things
Click to expand...
Click to collapse
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
eris170 said:
Should I just go find the stock OS image and recovery image and flash them over?
Click to expand...
Click to collapse
I think in your case the easiest thing to do would be to flash the factory image and start over. You will then need to reinstall TWRP and then use TWRP to install/flash the supersu zip. My advice would be to do lots of research before flashing custom roms and custom kernels. After you get back to the factory rom you really need to use TWRP to do a backup (nandroid) BEFORE you flash any custom roms and kernels, with that done it will be easy as hell to get back to stock after experimenting with whatever! Don't rely on toolkits, install the android sdk and learn adb fastboot commands, it's not hard, hell even I can do it!
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
I've never used this but looks interesting. [TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)
wantabe said:
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
Click to expand...
Click to collapse
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
wantabe said:
I think in your case the easiest thing to do would be to flash the factory image and start over.
Click to expand...
Click to collapse
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
eris170 said:
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
Click to expand...
Click to collapse
One of the great things about android is having the ability to change what you don't like and for the most part it isn't hard to do. I did notice with the update to 4.4 better performance and fluidity on both my N5 and N7 so it might be worth checking out at some point. I didn't care for some of the changes like the ui sounds with the 4.4.1 update but it's all easy to modify. Anyway.. glad you got it sorted out.