Related
I just got a Kindle Fire from a relative that wanted root access, and have performed several in the past without incident. When I was trying to use KFU to root with Superuser ("#2 option"), I accidentally bumped my booby-trapped keyboard's sleep mode button which shut off the monitor. When I turned it back on, I didn't realize my wifi disconnected and I entered option #2 to root (I'm not even sure internet access is relevant to the process). I immediately got errors which caused my Kindle Fire to get stuck at the splash screen. Using KFU, I changed the boot back to normal with option #1. Upon resuming root w/ superuser (that is, after selecting #2), it started rebooting and whatnot but got hung up at a point. KFU says "Attempt to remove root checker. / mv: can't rename 'system/bin/check_rooted': No such file or directory. / Please wait..." and never finishes. Meanwhile, my Kindle is stuck on the TWRP screen with Install, backup, etc. and won't move past. I have never experienced this screen before with the other roots that I have done; it just moves right into normal display after KFU does it's thing. Being the self-proclaimed techy that I erroneously think I am, I rolled up my sleeves and immediately googled a bootloop fix that seemed to be common with TWRP (command prompt > "adb shell" > changing boot to 4000), but I couldn't get the results the original poster got (I switched my environmental variables to allow for it, but still nothing). Against my better judgement, I will include that I got TWRP to let me into normal Kindle Fire operations and I factory reset it (which is fine, because it was factory to begin with) but TWRP is still showing up. I would have just played it safe and handed it back to my relative without root, but I'm not sure they could get past TWRP boot, and I wouldn't even want to do that to them if it was unavoidable. I have included everything I think was relevant to my troubles, and would be greatly appreciative if someone can glean from what I've done my level of understanding and guide me through this BS. A routine magic trick that I share with my less-tech-savvy family and friends has turned into a headache. To be clear, my question is how do I either A) get rid of TWRP (which seems like taboo from what I've read so far), or B) get back to a condition where I can start the whole rooting process over without interruptions, as I feel that is why I am in this mess. The goal is to get the Kindle Fire to a point where all my relative has to do is turn it on and go (no TWRP screens, bootloops, etc.) I can handle what follows after KFU rooting (namely, installing google market.....nothing like CM7 and the like.) Thank you.:good:
Whewww that a lot k well your best bet is to flash fff in twrp from this link only http://forum.xda-developers.com/showthread.php?t=1632375 by simply mounting the sdcard and transferring fff to it and flashing then power off get back into recovery by pressing the button a few times when you see the white kindle blue fire logo select recovery then mount SD again and transfer this rom in zip form of course http://forum.xda-developers.com/showthread.php?t=1439916 not the alt version that's for dual boot then wipe factory reset , wipe cache , wipe dalvik , wipe system then return to home screen of twrp select install flash rom when done reboot then system if prompted that's it.. wait for boot pass off the beautifully rooted kindle fire to your family member..
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
Google android market will be located in apps no more tampering needed modaco is nothing but rooted stock with Google play
Yeah, sorry. I just wanted to be complete, and I wasn't sure how much information would end up being useful. I'll let you know how it goes, and thanks for the reply!
Try this...
Acquire FireFireFire 1.4.zip and transfer it to your sdcard. Boot into twrp and install FireFireFire1.4.zip. Search the FFF thread for information on how to use it. I think that will either fix most of your problems or set it up to fix them easily
Sent from my Galaxy Nexus using Tapatalk 2
Thepooch said:
Whewww that a lot k well your best bet is to flash fff in twrp from this link only http://forum.xda-developers.com/showthread.php?t=1632375 by simply mounting the sdcard and transferring fff to it and flashing then power off get back into recovery by pressing the button a few times when you see the white kindle blue fire logo select recovery then mount SD again and transfer this rom in zip form of course http://forum.xda-developers.com/showthread.php?t=1439916 not the alt version that's for dual boot then wipe factory reset , wipe cache , wipe dalvik , wipe system then return to home screen of twrp select install flash rom when done reboot then system if prompted that's it.. wait for boot pass off the beautifully rooted kindle fire to your family member..
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
Google android market will be located in apps no more tampering needed modaco is nothing but rooted stock with Google play
Click to expand...
Click to collapse
At the risk of coming off ignorant, I am going to clarify what I need to do so I don't dig my hole even deeper. Please excuse me
I used the first link to download FFF. It came with the folders "cache" and "META-INF" and the single file "padfile". I assume mounting the SD card needs to be done through the TWRP screen, or do you mean on the Kindle Fire itself? Which part of the FFF download needs to be transferred to the SD card; the contents of "cache" or "META-INF", the padfile, or all of it? Do I just drop it onto the SD card, or does it have to be put somewhere special?
I understand how to get into Recovery mode on TWRP, and I will again assume that I need to mount the sd card in TWRP. What contents from the second link (Modaco) do I need to put on sd card, and where (if somewhere special)? It downloaded as a .zip, so should I just leave it that way and drop it onto the sd card?
I saw on TWRP where to wipe everything you mentioned, so I think I got it covered there. Also how to install flash rom.
You mentioned that Modaco already has google play, so I am going to also assume that this will conclude the fix, unless something unexpected pops up. I will try to work through your suggestion, but if you can let me know if any of my understanding is incorrect, I would be very much obliged!
I see that the SD mounting will probably come from within TWRP itself, since I will need to use "Install" for the rom flash, but I am still confused as to how to transfer it over and where it needs to go inside of SD card if there are any special rules for it.
Do not unzip the file! Place the .zip file on your sdcard as is and install it with twrp as you would a rom...no wipes
Sent from my Galaxy Nexus using Tapatalk 2
soupmagnet said:
Do not unzip the file! Place the .zip file on your sdcard as is and install it with twrp as you would a rom...no wipes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Are you referring to your own suggestion soupmagnet, or my question about what to do with the FFF or Modaco .zip? If it's a reply to my question, should I just leave both of them zipped, or just the Modaco one, or what? How do I place them on my SD card for that matter? Through TWRP (which I don't think I know how to do) or onto the Kindle Fire directory on My Computer? I've never installed anything with TWRP; in the past, I've never had to use the screen that I'm seeing now ;p Should I not use any wipes as the first reply suggested? I am confusing myself at this point.
fff you flash in zip form you don't unzip it no wipes needed a rom you wipe prior and then flash in zip form as well
I am seeing on the Modaco website that wipe is not required.
Not for you ... you must wipe...
Thepooch said:
Whewww that a lot k well your best bet is to flash fff in twrp from this link only http://forum.xda-developers.com/showthread.php?t=1632375 by simply mounting the sdcard and transferring fff to it and flashing then power off get back into recovery by pressing the button a few times when you see the white kindle blue fire logo select recovery then mount SD again and transfer this rom in zip form of course http://forum.xda-developers.com/showthread.php?t=1439916 not the alt version that's for dual boot then wipe factory reset , wipe cache , wipe dalvik , wipe system then return to home screen of twrp select install flash rom when done reboot then system if prompted that's it.. wait for boot pass off the beautifully rooted kindle fire to your family member..
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
Google android market will be located in apps no more tampering needed modaco is nothing but rooted stock with Google play
Click to expand...
Click to collapse
This is what I'm about to do as succinct as I can be (as per Thepooch's instructions):
1. Download FFF from the first link. Keep it .zip
2. Transfer FFF by mounting SD within TWRP menu.
3. Flash fff
4. Power off.
5. Enter Recovery TWRP.
6. Mount SD again, then transfer .zip Modaco (not the alt version)
7. Wipe factory reset, wipe cache, wipe dalvik, wipe system.
8. Install Modaco rom
9. Reboot
10. Give to family member and refuse all other requests
Flash fff before powering off.. flash fff before powering off or rebooting guess that better
Crap we made it to thread page 2. I really didn't mean to make this harder than it had to be, I just wanted to be sure of what needed to be done. Thanks again gents for all the input
Mmm, incredible Everything appears to be in order. No TWRP screen and Google Play is included. Thank you so much for the fix. Not completely sure what went wrong, but glad you knew how to get around it. Omne ignotum pro magnifico!
Solved.:highfive:
OK now try to access recovery again to make sure the bootloader works as it should
---------- Post added at 11:02 PM ---------- Previous post was at 10:58 PM ----------
Also now create a backup something you could not do before because I believe the system was broken
Entered recovery without any problems. Created a backup, as well. Every boot since has gone straight to Kindle Fire; no TWRP menu Excellent, because it would have been a pain to explain that whole process to my relative. Great stuff!
Glad it worked everyone's happy no harm done
Help!
Hi, I am hoping someone can help me. I came across this thread because I was having and identical problem, but unfortunately, I am not having the same result. If anyone can help me I would greatly appreciate it. These are the steps I carried out based on what I got from this thread.
1. Downloaded fff-u-boot_v1.4a and Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5 zip, placed it on the root of the SD card
2. In TWRP, I entered install and selected the zip.
3. From that screen I hit reboot.
4. I went to Reboot->Recovery
5. Wiped factory reset, cache, dalvik, system.
6. Installed Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5-569fe6550cfcfba68dabc3d088324a46.zip file
8. Rebooted...
But after all this it went right back into TWRP. I am sure I am just missing something obvious, please help.
WasabiPeanut said:
Hi, I am hoping someone can help me. I came across this thread because I was having and identical problem, but unfortunately, I am not having the same result. If anyone can help me I would greatly appreciate it. These are the steps I carried out based on what I got from this thread.
1. Downloaded fff-u-boot_v1.4a and Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5 zip, placed it on the root of the SD card
2. In TWRP, I entered install and selected the zip.
3. From that screen I hit reboot.
4. I went to Reboot->Recovery
5. Wiped factory reset, cache, dalvik, system.
6. Installed Gr9.2-update-modacocustomrom-kindlefire-unsigned-MD5-569fe6550cfcfba68dabc3d088324a46.zip file
8. Rebooted...
But after all this it went right back into TWRP. I am sure I am just missing something obvious, please help.
Click to expand...
Click to collapse
You almost got it. When you install a ROM and want to boot to it from recovery, select "reboot system". You can still change your bootmode on the fly with FFF1.4 by holding the power button when you see the Kindle Fire logo until you see the boot options appear at the bottom.
I really, REALLY have tried going through the threads and tried to figure this out on my own but I'm just stuck. A while back I got stuck in the boot loop (I guess). It was after a few factory resets. It had been rooted. Now, I can get into twrp but once there I can't seem to find any of the files that I need to flash to get it going again. When I launch the KFU it says the device is "online" and device manager reads "Android Composite ADB Interface". I'm sorry if this isn't enough info but can someone give me a push in the right direction? :silly:
Still vague bro but hey you have twrp do you have fff? If you have those things select mount in twrp transfer ROM zip and a gapps zip to your sdcard but don't place them inside a folder... leave them in the open this is considered the root of your sdcard then select unmount go to install see if you can navigate to the files you put on the kindle if so select wipe, wipe factory reset, wipe cache wipe dalvik, wipe system, select install tap on the ROM zip flash it when done use the back button upper right... flash gapps then select reboot and system if prompted let it boot.. I suggest this ROM or a cm7 flavored variety.. http://forum.xda-developers.com/showthread.php?t=1778010
fff is the kindle logo with the blue (fire) lettering, right? v1.4a in the upper right corner. Let's me go into normal, recovery and reset boot mode? The only option that let's me make any progress is the recovery option and that loads me into twrp. The "mount" option in twrp gives me 4 choices, mount system, mount data, unmount cache, and unmount sdCard. Mount system and mount data are unchecked. And if I click the "mount usb storage" button it takes me to a screen that says "USB Storage Mounted -- Be sure to safely remove your device from your computer before unmounting!" and there's an "unmount" button underneath. That's all I'm seeing. I'm not trying to be vague. I just don't know what specifically is the relevant info to give. But thanks for helping out those who can't help themselves
Ok plug to your computer select mount make sure there are no checks in the boxes of data and system then hit the big button this will mount your sdcard transfer zips select unmount follow my instructions above...
hey man, it worked!:victory: But I'm sure you knew it would. So, is it a bad idea or is it even possible at this point to revert to the factory reset? You know, have it be totally stock? And is it just tricky or dangerous to do factory resets a few times? I like using just the stock kindle version. The kindle app is just a little funky. Or it was the last time I used it. But obviously I love the google suite. I hadn't made a back-up the last time because it was just as easy to download a few of the things at a time from the cloud. So, making a back up would be a good habit and help in a situation like this? Do you know of any good threads re: backups? And superuser is something I don't know anything about but how does it work and where should I learn more about that? Mega MEGA thanks again dude! :highfive:
Yeah if you want the best of both worlds go with rooted stock all the wipes I suggested after backing up first then flash this http://forum.xda-developers.com/showthread.php?t=1439916 the standard version not the altrom thats for dualboot your miles from that
What's the process to get to rooted stock? I just made a back up
akaFoxMulder said:
What's the process to get to rooted stock? I just made a back up
Click to expand...
Click to collapse
just put this on your sdcard wipe every thing but your external storage and flash it http://loadbalancing.modaco.com/dow...gned-MD5-569fe6550cfcfba68dabc3d088324a46.zip your external storage is your sd card you dont wanna wipe that
its nothing but rooted stock with playstore and it wont wipe out your recovery and fff in the process
when installing the modaco custom rom, what boxes do I want to have checked? Zip file sig is checked by default and Force MD5 check on all zips is unchecked. Good?
akaFoxMulder said:
when installing the modaco custom rom, what boxes do I want to have checked? Zip file sig is checked by default and Force MD5 check on all zips is unchecked. Good?
Click to expand...
Click to collapse
Just leave them all unchecked
thanks again for all your help thePooch. I've tried installing the rom a couple of times and it either freezes or I've got the following message.
Writing Data - Writing System - Writing Boot then E:Error in /sdcard/Gr9.2-altrom-update-.....
(Status 0)
*Verifying filesystems...
*verifying partition sizes...
Error flashing zip ‘/sdcard/Gr9.2xxx
do I need to just stay with the cm10 rom at this point? what other kind of fun stuff can I do to get this working:fingers-crossed:
I believe Thepooch told you earlier NOT to download the altrom. Check your download and try again.
no doubt. Funny how this stuff works the way that it's supposed to
soupmagnet said:
I believe Thepooch told you earlier NOT to download the altrom. Check your download and try again.
Click to expand...
Click to collapse
Thanks soupmagnet yes the altrom version will fail everytime because it needs extra partitions to work which do not and very likely will not ever exist on your device.... Intructions well it helps if they are read I gave very clear ones and I definatly said not to use the altrom........
ありがとうございました。 I think I'm done.
your welcome
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
I wanted to update my phone from Software version/Baseband version PF4 to the latest Software and Baseband version PG1, but I wanted to KEEP EVERYTHING ELSE. All my apps, my ROM and my Kernel. I was able to do this in less than one hour by following these steps.
Necessary files first:
1) ODIN file. You want to have a folder with the Odin .exe and other files somewhere convenient, your desktop is fine.
2) Latest TAR file available. Currently, that is PF4. The file should end in .md5.
3) Latest CF-Auto-Root. The file should end in .md5.
4) Latest Recovery (TWRP) TAR file. The file should end in .tar.
All of these are available from thread here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
All Put the PF4, the CF-Auto-Root and the TWRP file in the folder where Odin is.
For convenience, I also recommend installing Minimal ADB. Grab that here: http://forum.xda-developers.com/showthread.php?t=2317790
Install the Minimal ADB. Run that and make sure that it sees your phone. Plug your phone in and type "ADB devices." Look at your phone and accept the security prompt if that comes up.
Once you have Minimal ADB installed the commands that you will use are "ADB Reboot Download" and "ADB Reboot Recovery." These just simplify things.
Is your phone Rooted with TWRP Recovery? Great, we can get started! If not, open ODIN. Flash CF-Auto-Root to get your phone rooted. Then flash the TWRP TAR file. And then you are ready to begin.
Make sure that you have Developer options selected and OEM unlock selected. Really. Make sure. Otherwise you will get the FRP lock.
1) From ADB, type "ADB Reboot Recovery." This should take you to TWRP. If it doesn't read up ^^^^ because you missed a step.
2) In TWRP, go to Backup. This should be the default but if not select Boot, System and Data. Make that backup, which will get stored in TWRP/Backups on your phone. Within that folder, you will see a folder with a long name with lots of numbers and letters that identifies that this backup is for your phone. I generally copy the whole Backup folder to my PC, just in case my phone gets totally wiped I can still restore it. It takes a few minutes and better safe than sorry. Backup done, you can go to the next step.
3) In ADB, type the command to put your file into Download mode. ("ADB reboot download.") Start ODIN. Click on the AP button and select the PF4 file. Let it load, it takes a while. Then click start. This will take few minutes, maybe 10, then your phone will restart back to stock. Again you are going to have to wait for a bit.
4) Let your phone finish rebooting. Once done, you can go to Settings -> System Update -> Download updates manually. You should have an update to PG1 available. Install that and again, your phone will reboot. Once that is done, check your Software version/Baseband version and they should both say PG1.
5) Again, use ADB to send your phone back to download mode and back to Odin. Select the CF-Auto-Root and Start. This should go much faster.
6) Back to Download mode and Odin one last time. Select the TWRP file and start.
7) In ADB, type "ADB reboot recovery".If you have done everything right, you should now be in TWRP.
8) I like to get rid of any bloat that may have been installed with the Stock. I go into Wipe and do both a Factory reset and then in Advanced wipe Caches, System and Data. Then go back to the TWRP main screen WITHOUT REBOOTING.
9) Click Restore and restore the backup that you did at the beginning.
Your phone is now updated to the latest Software and Baseband versions but with all your apps and data as it was before you started.
This literally took me 45 minutes today and that only because of the long rebooting times.
Have fun!
So I always have a space issue with this. I don't have enough free space on my device to hold a backup.
Do you know if there's any way to backup to an external/usb device. I have one of the micro USB to female USB adapters...and I can see the USB drive connected while in the phone, but I don't see an option to use that as a backup destination from TWRP.
Is there a way to backup off the device?
Sent from my SM-G920P using XDA-Developers mobile app
Saafir said:
Mount the USB OTG then you should be able to backup too it
Click to expand...
Click to collapse
I thought I tried that. Ill try again.
Going off the top of my head, if I remember right, it said that the external drive was non-writable.
Is there a specific partition type the USB drive had to be (fat32, ext4, etc) or is there a specific process that I need to follow to mount the drive in TWRP?
Sent from my SM-G920P using XDA-Developers mobile app
Alright. I tried again this morning. The problem is, when I go into mount the USB in TWRP, it does nothing. I can't check it off. I've tried with 2 different USB sticks and I cant get it to work. When the phone is booted to system, I can see the USB, read/write without any problems.
hotwired34 said:
Alright. I tried again this morning. The problem is, when I go into mount the USB in TWRP, it does nothing. I can't check it off. I've tried with 2 different USB sticks and I cant get it to work. When the phone is booted to system, I can see the USB, read/write without any problems.
Click to expand...
Click to collapse
I just tested and OTG seems to be working fine for me.
I went into TWRP, selected Mount, selected USB Storage. Tapped on Select Storage (same screen) and selected USB Storage. (Did you miss this last step?)
I don't know what to tell you beyond the old "It works on my computer/phone."
Are you sure that you are using the right version of TWRP? From here: https://dl.twrp.me/zerofltespr/
koop1955 said:
I just tested and OTG seems to be working fine for me.
I went into TWRP, selected Mount, selected USB Storage. Tapped on Select Storage (same screen) and selected USB Storage. (Did you miss this last step?)
I don't know what to tell you beyond the old "It works on my computer/phone."
Are you sure that you are using the right version of TWRP? From here: https://dl.twrp.me/zerofltespr/
Click to expand...
Click to collapse
I have the right version of TWRP. It might be my otg cable. It's one of the cheap ones. I think I got a 3 pack for something like $0.99.
I was able to use the cable from within the phone and do a full Titanium backup. It's not going to be 100% like your method, but at least my apps and data will be preserved (for the most part). I probably have enough space to do the backup of system and boot, then just restore the apps with data.
Thanks for your help!
I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.
tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions
tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.
AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM