Related
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
Hi. So I consider myself somewhat of an amateur now at ROMing and messing with the Kindle Fire ecosystem, but lately I have been having trouble. I have the latest TWRP (I think) installed. I am using twa_priv's latest builds of Jellybean on a weekly basis, but am switching a bit back and forth between that and the stock 2.3 KF system because that supports a few things that Jellybean hasn't covered yet. My problem is that when I create a backup...it seems to create one just fine. BUT when I try to restore the backup, it "runs" the backup in about 10 seconds, and when I go to reboot the system, it warns me that no OS i installed.
What is my problem?
Josepho1997 said:
Make sure you select all of he options for restore(system, data, cache, ect.)
Android>iOS... Android FTW!
Click to expand...
Click to collapse
Thanks for the advice. However, I have made sure to do that every time. I have messed with all the settings I can think of. Including the md5 file properties. Hopefully this picture of the files from one of my more recent backups helps?
jma9454 said:
Thanks for the advice. However, I have made sure to do that every time. I have messed with all the settings I can think of. Including the md5 file properties. Hopefully this picture of the files from one of my more recent backups helps?
Click to expand...
Click to collapse
Run the restore as you have been. Pull the recovery log...
Code:
adb pull /cache/recovery/last_log recovery_log.txt
Put it up on pastebin and post the URL here.
kinfauns said:
Run the restore as you have been. Pull the recovery log...
Put it up on pastebin and post the URL here.
Click to expand...
Click to collapse
OK. so here is the link. I don't understand it one bit, so hopefully you can make something out of it.
http://pastebin.com/TBVU1Lhu
jma9454 said:
OK. so here is the link. I don't understand it one bit, so hopefully you can make something out of it.
http://pastebin.com/TBVU1Lhu
Click to expand...
Click to collapse
Well, I thought TWRP would write to the log file with some details on its restore operations, but it apparently does not. My bad for making you jump through those hoops needlessly.
I would try deleting or renaming the TWRP folder in /sdcard, rebooting back into TWRP, and trying the backup/restore process again. If that doesn't help, try reflashing TWRP and repating the process with different ROMs, I don't believe this is a known problem with TWRP, so you have to try narrowing down the variables and seeing what helps.
kinfauns said:
Well, I thought TWRP would write to the log file with some details on its restore operations, but it apparently does not. My bad for making you jump through those hoops needlessly.
I would try deleting or renaming the TWRP folder in /sdcard, rebooting back into TWRP, and trying the backup/restore process again. If that doesn't help, try reflashing TWRP and repating the process with different ROMs, I don't believe this is a known problem with TWRP, so you have to try narrowing down the variables and seeing what helps.
Click to expand...
Click to collapse
OK, thanks. I am going to try reinstalling TWRP. I have tried most of the helpful hints that you have given me already, so I figure that maybe my TWRP is bad? I forgot to mention that I came from CWM because I originally had TWRP, switched to CWM, hated it, and reinstalled TWRP through the KFU.
I got a flashable TWRP from this link:
http://forum.xda-developers.com/showthread.php?p=30780737
The only problem is that I don't know the adb command to flash TWRP onto the kindle. Any help?
jma9454 said:
OK, thanks. I am going to try reinstalling TWRP. I have tried most of the helpful hints that you have given me already, so I figure that maybe my TWRP is bad? I forgot to mention that I came from CWM because I originally had TWRP, switched to CWM, hated it, and reinstalled TWRP through the KFU.
I got a flashable TWRP from this link:
http://forum.xda-developers.com/showthread.php?p=30780737
The only problem is that I don't know the adb command to flash TWRP onto the kindle. Any help?
Click to expand...
Click to collapse
That zip archive needs to be installed with TWRP like you would a ROM. I suggest you set that aside and install it the old fashioned way and use fastboot...
http://forum.xda-developers.com/showthread.php?t=1638452
My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!
Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Misread OP.
ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all
thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.
Ok, i have a problem, i make a bakcup of my rom (Lite rom 0.9), the backup doesnt show any problem when i did, but, when i try to restore, the phone stay in black after boot animation, i try to wipe cache, dalvik, reinstall the rom then backup and nothing, i cant restore my backup. Somebody know how to solve? or i lost my backup?
I had this with my back flip. If you backup with a custom boot animation, then the backup won't work.
Sent from my SGH-I927 using xda app-developers app
so, there is no way to recover the backup? (i will loss a lot of savedata of my games haha )
I have successfully restored loads of backups of LiteRom0.9. What version of cwm are you using?
I have always used the tar backup style instead of blob. I don't think that would make the difference, but it's worth a shot.
Sent form my SGH-i927 running dman's cm10.1
I use the touch version of CWM, when i made the backup, there was no problem, but i cant restore, i try a lot of time, but never boot
Ok, are you using tar or blob for the backup format? What do you mean by "won't boot?" Does it freeze at the samsung logo, before that? Or whatever boot animation it has?
When you use cmwr to restore from backup, what does it say? Does it think it worked properly? If you want, you can attach you backup folder (you can use "adb pull /sdcard/clockworkmod/backup/whatever" or something of the sort to pull the folder from your device) and I'll see if there are any problem with the backup itself.
Also, bear in mind that cwm doesn't have official support for the glide. And from what I've read, the touch port isn't that reliable, you might want to try to flash it again/the non-touch version.
Sent form my SGH-i927 running dman's cm10.1
Its restore without errors, but stays a lot of time in the boot animation and then the screen turns black. I dont know too much, i only go to bakcup and resotre an do the backup, and restore from there. i dont change anything
Hmmm... OH!!! I can't believe I didn't think of this!
Try wiping your cache, sometimes wierdness happens with that. Just to get your phone working again, you might also want to try a full wipe. That won't delete your backups, so hopefully we can still recover the data, but that might get your phone working again for the time being.
This might help me determine if the backup is somehow corrupt:
1) boot into recover
2) under "mounts and storage", mount either your internal or external sd.
3) ensure your phone is plugged into your computer and type "adb shell"
4) type "cd /sdcard/clockworkmod/backups"
5) type "ls" That will show all folders in the current directory.
6) the folders are named based of the time and date the backup was created, choose one the type "cd [whichever folder you want]"
7) type "ls" and tell me what it outputs. It might have somehow taken a corrupted image.
Sent form my SGH-i927 running dman's cm10.1
ok, will try that, i already reinstall the rom and install the app, but, i has alot of data from every app (games, settings, etc) that take time to put again, so i want to recover the backup, and i like to try other roms, so i will need to go back with my backups and if not work, will be a problem for me.
i try that, but give me a error, device not found
Your phone was in recovery and it said that? Hmmm....
Ok, go into settings on your phone in normal boot and make sure usb debugging is turned on. You once you've done that, you can actually do the same proccess but starting on step 3.
Sent form my SGH-i927 running dman's cm10.1
scottbot95 said:
Your phone was in recovery and it said that? Hmmm....
Ok, go into settings on your phone in normal boot and make sure usb debugging is turned on. You once you've done that, you can actually do the same proccess but starting on step 3.
Sent form my SGH-i927 running dman's cm10.1
Click to expand...
Click to collapse
The same, it tells me error: device not found
edit: ok, i see a problem, i turned on usb debugging, but when i leave the settins its turn off. it seems that dont turn on :/
Ok.... well, that's bizarre. I guess just stay on that screen for now.
Sent form my SGH-i927 running dman's cm10.1
Still not luck, after a while, the debuggin options stay turned on, butstill cant connect with adb shell
Do you have the proper drivers installed? If you do, try uninstalling then reinstalling them.
Sent form my SGH-i927 running dman's cm10.1
are the same used in odin?
had the exact same problem using .9 lite rom n touch recovery, updated to latest non touch recovery everythings fine now
I was thinking that might be the case, but I hadn't heard about that problem with the touch version. I haven't had any significant problems with the nontouch version.
Sent form my SGH-i927 running dman's cm10.1
the problem is that i cant take the risk to use odin, my phone freeze a lot in the past when i flash the recovery and cost a lot of time to flash without a problem. That why i say that the rogers version has something different.
Well now... that could be a problem. Try to upload a zipped version of you cwmr backup folder. We'll see what we can do.
Sent form my SGH-i927 running dman's cm10.1
The bakcup folder have 1.6gb :/ that can take a lot, dont know why is too big
I have recently updated my HTC one X to the latest CyanogenMod, after I flashed the rom the phone keeps rebooting endlessly
I have been looking for the past few days for a fix, this is my last resort, I've tried the following:
Attempt 1:Install an original ROM
Problem: doesn't go past htc logo, I tried erasing the cache before, as this was a common fix for it, I get "error:remote not allowed" (this happens when I try to erase any file recovery, boot ect.) so I tried a different path...
Attempt 2:use an RUU
Problem: not able to source an RUU that is newer (3.14.980.27) and attempting s-off, from what i could fine, required a working ROM
Attempt 3: load another nandroid backup onto the SD partition, one that is new.
Problem: Using CWM my computer won't detect the SD when mounted nor will adb detect the device whilst in recovery, I then tried TWRP, this resulted in "E: unable to open lunfile: (no such file or directory)" so that was out...
Attempt 4: push the nandroid file to the device using adb and then use CWM or TWRP to install the nandroid backup
Problem: only the file would be transferred and none of the juicy usable bits that I needed.
As you can see I'm a fair bit of a NOOB, and out of ideas so if you think I have done something wrong or have gotten close with one of these steps and just need to do it a bit differently please tell me and I can go into more detail on how I cocked up. I have tried these steps on 2 other computers with a huge range of usb cords as well.
If anyone can help, I would be a very happy person
Did you flash the boot.img
Sent from my One X using XDA Premium 4 mobile app
Full wipe and flash again. Don't forget the boot.IMG which is the kernel.
Sent from my Nexus 7 using xda app-developers app
Also which CM did you flash? The latest nightlys aren't very stable.
I would recommend that you visit CM11's thread which is here: http://forum.xda-developers.com/showthread.php?t=258303
from what I saw, the lastest nightlies aren't the most stable but a few builds before that seems too be quite good :good:
Bobbi lim said:
I would recommend that you visit CM11's thread which is here: http://forum.xda-developers.com/showthread.php?t=258303
from what I saw, the lastest nightlies aren't the most stable but a few builds before that seems too be quite good :good:
Click to expand...
Click to collapse
Now you are really getting freakin annoying ! Reposting 2 times answers that already have been given in 1 thread.....i would almost call it "spamming"