Related
OK, so I just got my Nexus S4G two days ago, and I'm ready to root. My phone out of the box has 2.3.4 on it.
I follow this tutorial: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ the link to which was provided by a good XDA'er. I get the bootloader unlocked and install CWR (recovery-clockwork-3.0.2.4-crespo.img) and that goes fine.
That's when things stop going fine.
First, I try to create a Nandroid backup, and that process seemingly completes fine until i note that the process says it couldn't mount /data. I don't worry about it.
So, I go to Mounts and Storage to prepare to push SuperUser.zip and I tell CWR to "Mount USB Storage" and I wait as directed, but the USB storage never mounts. I try mounting USB Storage and mounting /sdcard, neither of which work, so I can't push SuperUser.zip.
Figuring I did something wrong, I decide to restore from Nandroid, only to have CWR tell me that the MD5 checksum is incorrect and now I have no clean, base Nandroid to restore to.
Then I do some digging, and discover that there's a new CWR for the NS4G at Koush's site and I download the file (recovery-clockwork-3.1.0.0-crespo4g.img) from there, push it to my phone using fastboot's recovery command and start it up.
It doesn't work.
Clicking any of the options (like mounting partitions, or restarting/powering down the phone) causes the screen to go blank and just display the CWR logo in the middle of the screen. The only solution to get out of those loops is to pull battery and restart.
So, now, I'm wondering what to do.
I go back into fastboot, relock the bootloader and I now wait for a reliable root method to root a 2.3.4 NS4G on a Mac.
My questions are:
Where can I get a stock ROM to completely start over from scratch and even remove the recovery I've installed <-- found a base ROM here: http://forum.xda-developers.com/showthread.php?t=1078213
Is there a fully reliable way to root the NS4G on a Mac, and if so how? (I've looked at this thread: http://forum.xda-developers.com/showthread.php?t=878446 and it looks problematic as well).
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
herbthehammer said:
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
Click to expand...
Click to collapse
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
My first nandroid choked. After root and final recovery install, I cleared all the caches it was *****ing about the first time, went in normally to make sure everything was okay, then went back and nandroid and no errors the second time. I probably will just stay with rooted stock but I would not flash other stuff until the dust settles and many of the bugs are worked out of the roms and kernels before jumping in.
TonyArmstrong said:
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
Click to expand...
Click to collapse
If cwm mount won't work then boot into the phone normally and copy over the file like usual is the only other quick and easy way to do it that I could think of at the moment the snafu happened. Yeah the way I did it might not have been the most efficient way but it got me past the hurdle that cwm made quickly. In the end, the result is the same so no big deal.
I don't know if cwm backs up wimax keys so I did it manually. There's a post on how to do it, I don't know if it's in this section. It might be dev?
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
veroby said:
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
Click to expand...
Click to collapse
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
RMarkwald said:
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
Click to expand...
Click to collapse
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
veroby said:
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
Click to expand...
Click to collapse
I've had no issues flashing 4.1.1/4.1.2 ROMs to 4.2.1 and vice versa...but again I'm using TWRP Recovery.
The file is in the stock images from Google, and it's there to reload stock Android recovery at boot...other than that I'm not sure of the exact reasoning.
I know that Android 4.2 has multi-user support, and that has been the cause for many issues with 4.2 in general due to it creating a folder /sdcard/0...so flashing multiple 4.2 ROMs without the latest CWM Recovery version 6.0.1.9 would cause another folder created there at /sdcard/0/0...and so on. If you created another user, they would have their own folder at /sdcard/1...and so on.
I would make sure that you have the latest CWM Recovery flashed to your device, then put your backup in the correct folder. From what I remember when using RM and CWM, there's the folder for your backup and then one level up from that there's the blobs folder, you'll need BOTH of those in order to restore things, as the blobs folder is the backup.
i have a rooted nexus 7 32gb 3G model running 4.2.2. rooted using nexus 7 toolbox and was running stock rom and kernel with TWRP RECOVERY and unlocked bootloader
last night i got the update for 4.3 and i agreed to reboot n install the update. it booted into twrp recovery and installed the update n after finishing it did not boot rather it came bak to the menu of twrp i manually pressed boot system n it asked to swipe to fix permissions for su binary i swiped the button and it just booted and and came to the nexus logo and was stuck there. i thought first time it might take time left it for half an hour was just stuck there and I switched it off n put it bak on after sometime still doesnt go any further from the logo.
if i had a backup i would hav just restored it but the update started off directly i didnt get an option to backup n i didnt backup before doing it=|
please tell me how to fix it. i dont mind going back to 4.2.2 but i need my data i dont want to factory reset
thanks in advance!
Have the same problem here..
please someone help soon=(
Same here.
How can i get a new Custom Rom on my Nexus 7 if it doesn't start?
i have similar problem when flashed bad radio to my phone but i can start recovery/
but nexus start very fast and i can not enter to recovery
so sad, my device only 2 weeks old and i crack the void.
sambistt said:
i have similar problem when flashed bad radio to my phone but i can start recovery/
but nexus start very fast and i can not enter to recovery
so sad, my device only 2 weeks old and i crack the void.
Click to expand...
Click to collapse
if ur able to boot to recovery u can get it bak dont worry! just hold down power button and volume down till the device comes into fast boot. and if ur stuck at the logo and not able to shut down (by removing the battery on other phones) just hold down power button and volume down button for a while i think its 5 seconds but it could be a little more not sure. hold it down till u boot into fast boot and in fast boot u can shut it down or enter the recovery.
and since u say ur device is new n if u dont hav much data then u will be able to simple flash the stock rom and hav a fresh new device.
use this toolbox it'll help u do everything. but im not very sure u might loose all the data on it
http://forum.xda-developers.com/showthread.php?t=1809195
i can not enter fastboot - if i held power button and volume - it only wake up and show Google logo - and after 15 SECOND OF HELDING - GO TO apx MODE
google nexus toolkit cAN NOT help - the device start to logo and ADB or FASTBOOT can not detect device
shoaib30 said:
i have a rooted nexus 7 32gb 3G model running 4.2.2. rooted using nexus 7 toolbox and was running stock rom and kernel with TWRP RECOVERY and unlocked bootloader
last night i got the update for 4.3 and i agreed to reboot n install the update. it booted into twrp recovery and installed the update n after finishing it did not boot rather it came bak to the menu of twrp i manually pressed boot system n it asked to swipe to fix permissions for su binary i swiped the button and it just booted and and came to the nexus logo and was stuck there. i thought first time it might take time left it for half an hour was just stuck there and I switched it off n put it bak on after sometime still doesnt go any further from the logo.
if i had a backup i would hav just restored it but the update started off directly i didnt get an option to backup n i didnt backup before doing it=|
please tell me how to fix it. i dont mind going back to 4.2.2 but i need my data i dont want to factory reset
thanks in advance!
Click to expand...
Click to collapse
If you can go into the bootloader, go to recovery and flash CleanROM or CM10.2 or even a 4.2.2 ROM. Seems to be your only option now. Also flash an appropriate kernel for the ROM right after the flash.
Try a dirty flash at first.
i can - it freeze on logo and reboot after pressing on power and volume
sgt. meow said:
If you can go into the bootloader, go to recovery and flash CleanROM or CM10.2 or even a 4.2.2 ROM. Seems to be your only option now. Also flash an appropriate kernel for the ROM right after the flash.
Try a dirty flash at first.
Click to expand...
Click to collapse
yes i can get into bootloader and recovery. and i hav a few questions...
1. if i flash another rom will my files on the virtual sd in the internal memory get wiped?
2. there is option for backup in TWRP recovery i can backup DATA SYSTEM CACHE and usb otg.
after flashing a new rom can i restore the backup for DATA and get bak the apps?
3. is there any way i can copy the files in the internal memory saved in the virtual SD to my comp or anywhere else through recovery or bootloader? 4. there is an option for factory reset in TWRP recovery which says it will clear data and wipe cache and will not clear internal data. i just want to be sure if the files in the virtual sd wont get deleted if i do this? and by using this factory reset option will i be able to fix the problem?
sambistt said:
i can not enter fastboot - if i held power button and volume - it only wake up and show Google logo - and after 15 SECOND OF HELDING - GO TO apx MODE
google nexus toolkit cAN NOT help - the device start to logo and ADB or FASTBOOT can not detect device
Click to expand...
Click to collapse
oh im so sorry=| i didnt know wat apx mode was just read abt it. try giving it to google and check if theyll fix it? they might charge for it though?
shoaib30 said:
yes i can get into bootloader and recovery. and i hav a few questions...
1. if i flash another rom will my files on the virtual sd in the internal memory get wiped?
2. there is option for backup in TWRP recovery i can backup DATA SYSTEM CACHE and usb otg.
after flashing a new rom can i restore the backup for DATA and get bak the apps?
3. is there any way i can copy the files in the internal memory saved in the virtual SD to my comp or anywhere else through recovery or bootloader? 4. there is an option for factory reset in TWRP recovery which says it will clear data and wipe cache and will not clear internal data. i just want to be sure if the files in the virtual sd wont get deleted if i do this? and by using this factory reset option will i be able to fix the problem?
Click to expand...
Click to collapse
1. If by virtual sd you mean Internal Storage (the place where you copy files to normally via PC), no. It won't wipe anything there.
2. Although this is possible, it is highly discouraged.
3. From bootloader or recovery you can try adb pull to grab a backup of your sdcard's contents. Don't do this unless you are 100% sure you know what you are doing.
sgt. meow said:
1. If by virtual sd you mean Internal Storage (the place where you copy files to normally via PC), no. It won't wipe anything there.
2. Although this is possible, it is highly discouraged.
3. From bootloader or recovery you can try adb pull to grab a backup of your sdcard's contents. Don't do this unless you are 100% sure you know what you are doing.
Click to expand...
Click to collapse
ok i shall avoid restoring backup of data. so ill factory rest it from twrp recovery? it should fix the problem right?
and by virtual sd i meant the internal storage where we copy files from the comp sorry i didnt know how to descirbe it...
and no im not so good at adb so ill avoid tht since u told nothing in the internal memory gets wiped
Go to TWRP>Wipe. And then just swipe. Don't try Advanced or Internal Storage or whatever there is. Should do the job.
sgt. meow said:
Go to TWRP>Wipe. And then just swipe. Don't try Advanced or Internal Storage or whatever there is. Should do the job.
Click to expand...
Click to collapse
im so sorry one last question. if i factory reset n restore only data to get bak the apps.. if it works well n good if it doesnt ill factory reset again.. but does restoring data cause damage tht could brick my device?
If you factory reset, only stuff in /data will get wiped (game saves etc.) Not your sdcard stuff though.
And restoring a data backup from a different ROM may lead to bootloops.
sgt. meow said:
If you factory reset, only stuff in /data will get wiped (game saves etc.) Not your sdcard stuff though.
And restoring a data backup from a different ROM may lead to bootloops.
Click to expand...
Click to collapse
now im factory restting so rom wont change so restoring data i mean the saved games etc itself should work? its just for info im mostly gonna stick with just factory reset for now... doing it now
factory reset didnt work
i did a factory reset but it still isnt comin on=(still stuck in the logo... anything else i can do? i dont want to flash a custom rom can i flash the stock 4.2.2 rom? n not loose anything from internal storage?
edit: to flash any rom how to copy the zip file into the internal storage?
i checked in the nexus 7 toolbox to flash stock image it tells the internal memory will be erased as well=| any other method to flash stock rom?
i havent tried it but my friend told me tht he can mount his external sd in recovery and hes able to view the files on the comp. is it possible to view files of the internal storage on the comp n copy them onto a comp. ?
shoaib30 said:
i checked in the nexus 7 toolbox to flash stock image it tells the internal memory will be erased as well=| any other method to flash stock rom?
i havent tried it but my friend told me tht he can mount his external sd in recovery and hes able to view the files on the comp. is it possible to view files of the internal storage on the comp n copy them onto a comp. ?
Click to expand...
Click to collapse
how can i add a rom if i cant mount my n7 to my computer, I have twrp and all but i never had a custom rom to begin with and im stuck on the N7 logo screen
This is the first time I'm using a device that doesn't have an external SD card, but I've all along understood that the internal SD card does not get wiped when you do a factory reset, and I'm sure I read that again on another thread just the other day.
My N7 is rooted using Wug's toolkit, with CM10.2 and Bulletproof kernel.
Yesterday I decided to do a factory reset (under Settings, Backup & Reset, Factory Data Reset), but after I did it, all the stuff I had on the internal SD was gone, including my backup files, the ROMs I had transferred there, etc.
Surely this is not meant to be the case, is it??
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
sfhub said:
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
Click to expand...
Click to collapse
Thanks for that! (Thanks coming your way). Well, better to know now than later! The down side is that I lost my CWM backups and my Titanium Backup files, but the good thing is that I think I have a TWRP backup that's on my computer.
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
oohyeah said:
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
Click to expand...
Click to collapse
I am not sure what issue you are having with TWRP, but you can flash it to the recovery partition and boot to it automatically. If that's the only reason you don't like it, I'd work on fixing the install rather than jumping to another recovery.
oohyeah said:
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Click to expand...
Click to collapse
I would probably do it from recovery. I don't know what CWM does on this platform as I've only used it on other platforms.
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Sent from my Nexus 7 using xda app-developers app
geckocavemen said:
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Click to expand...
Click to collapse
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign. I remember doing some searches and it seemed like this was normal. I remember the reason was that the N7 would always rewrite the recovery or something. From your responses, I'm guessing it's not normal?
The only way I could get into recovery was using the Wug toolkit using USB debugging/ADB, which really sucked, cos if it bootlooped and I can't get into the system to turn on USB debugging, then I'm not sure what I would do (though I read there's some way around it or something). I had never encountered any such thing with all my many other devices which all run CWM.
So what's up with all that?
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
User_99 said:
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
Click to expand...
Click to collapse
This will work fine. If you have no aversion to installing apps, Rom Toolbox Lite gives you power widgets you can put on your desktop then go to recovery with one touch. I use Quick Boot PRO, although the free version of that all may do recovery also. One might work for you until you want to play with mods.
Sent from my Nexus 7 using Tapatalk 4
oohyeah said:
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign.
Click to expand...
Click to collapse
That is stock recovery.
You need to get rid of /system/etc/install-recovery.sh
You can get rid of it by hand, or just install SuperSU from TWRP. Then flash TWRP to the recovery partition.
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
oohyeah said:
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
Click to expand...
Click to collapse
None of your blunders has anything to do with TWRP.
khaytsus said:
None of your blunders has anything to do with TWRP.
Click to expand...
Click to collapse
OK let me get something straight.
Obviously, the factory resetting that wiped out all internal storage (the original point of the thread) has nothing to do with TWRP, and I never said it did. On this point though, I'm surprised that it doesn't seem to be more well known that a factory reset would do wipe out all your data (did several searches and only found 'confirmations' that your internal SD data would be left untouched), though I'm glad that I know it now.
The suggestions on different ways to boot into recovery were helpful, though I believe that I would still have encountered the dead android, or would I not have?
What's certainly still not clear to me though is regarding the problem of not being able to boot into recovery and getting the dead android with the exclamation/triangle. After the first few replies, I expected to hear that this was NOT meant to be the case and that I did something wrong in the process or whatever.
However, what I seemed to get was that this is the expected behavior, and what I needed to have done was to "get rid of /system/etc/install-recovery.sh".
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
oohyeah said:
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
Click to expand...
Click to collapse
Dead android = stock recovery, so normal there.
When you flash a custom recovery on a stock ROM, there is a file, /system/etc/install-recovery.sh, or I actually prefer just renaming /system/recovery-from-boot.p, which will automatically verify your recovery image and restore it to stock if it doesn't match. So you must always remove this file, or the ROM will restore the stock recovery on boot.
TWRP makes it easy to remove either file by mounting /system in read-write mode and using its built-in file manager to remove it. You can do the same in CWM using adb.
As for point 3, yes, try to reboot into recovery again. If you didn't remove (either file), you'll find stock recovery again.
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
oohyeah said:
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
Click to expand...
Click to collapse
It really depends on what ordering you do your actions in.
/system/etc/install-recovery.sh doesn't exist on a stock factory shipped system.
It only gets put in place after you install an OTA. If you do all your upgrades using the factory images, you'll never encounter it.
What it does is during your boot process, it will check to see if your recovery is different than what it expects (ie stock). If so, it will install stock recovery by taking the stock kernel and patching it.
If any of the following are true, it will not overwrite your recovery:
/system/etc/install-recovery.sh is missing (or modified to not run as the original file)
/system/recovery-from-boot.p is missing
you are not running the stock kernel
The most common way for install-recovery.sh to be missing is you always used factory images.
The most common way for install-recovery.sh to be modified to not do the original function is if you installed SuperSU. It will overwrite install-recovery.sh with its own.
So in all the back and forth, it is quite possible you got rid of install-recovery.sh or had it modified simply by installing root.
If you then subsequently installed custom recovery, it would stay in place.
Previously you were installing TWRP and flashing it onto the tablet, but upon booting into android, install-recovery.sh realized it wasn't stock recovery, and overwrote TWRP with stock recovery.
That is why whenever you rebooted, you got fallen android (which is stock recovery)
If the way you installed cwm is to use "fastboot flash recovery cwm.img" then the only reason it is around is because something else you did got rid of or modified install-recovery.sh. cwm would be no more immune to install-recovery.sh than twrp was.
oohyeah said:
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
Click to expand...
Click to collapse
Just to clarify, you didn't lose root. You just lost the supersu app, a root permission manager, because it was installed to your /data partition. The su binary was still in /system, all you would have had to do was install supersu from the market.
I'm not sure what else you were expecting from a "factory reset"
creaturemachine said:
I'm not sure what else you were expecting from a "factory reset"
Click to expand...
Click to collapse
Did you read the thread? He explained his reason for expectation quite well.
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Skaziwu said:
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Click to expand...
Click to collapse
Depending on which level you are looking at, it didn't really change the behavior, but rather how your data is organized.
Factory reset has always wiped out /data.
On older devices, they put the /sdcard in a separate partition and formatted fat32.
These are the ones that were surviving a factory reset.
On newer devices, the internal /sdcard is starting to migrate onto a directory in /data and the "sdard" you see is "virtual". Since it is on /data, when you wipe data, the virtual sdcard is also wiped.
Some recoveries try to simulate the previous behavior by doing a "rm" of every directory except the virtual sdard when you choose to wipe, instead of the erase/format that Android is doing.
The advantage of keeping the sdcard as a directory under /data is you don't need to decide how much space to split between the sdcard and your /data. Also permissions on files are more flexible being in an ext4 filesystem. Finally since everything is emulated and accessed via MTP, you don't need to unmount the filesystem, so your PC can access it.
There are also cons with this approach, but that is what Google is going with.
Guys i got my oneplus 5 in the mail yesterday and I like it, but I think i ****ed up...big time. please somebody help me out.
i was following this guide: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
to root my oneplus 5 so i can use Adaway. Ive rooted and installed a custom rom many times on my oneplus one before so I didn't really have any issues.
but then when I got to "Gaining root access" part, I was a little confused because I wasn't sure what step to take, so i Just did the stuff from the top. I think somewhere along the way I ****ed up and for some reason all my folders are gone except for android. (ie downloads, notifications, alarms, ringtones, music, pictures, etc folders are gone)
even when i take a picture, it just disappears because it has nowhere to save to... . when I plug it in with file transfer mode, there is literally only 1 folder, look at this picture: http://imgur.com/a/F49v0
is there anything I can do to fix this? or did i just GG no re 540$? I know i'm a ****ing stupid ass ****ing low life piece of **** dumbass **** head.
If worse comes to worse, I still got like 13 days left to return it if possible? Do u think they'll accept a return or replacement from me?
****
when I go to google and try to download an image, it says It can't be downloaded because of missing SD card. wtf is going on?!
EDIT UPDATE: okay now my phone is stuck on boot screen with the 1+ symbol. any1 know how to help me out?
onepluslover69 said:
Guys i got my oneplus 5 in the mail yesterday and I like it, but I think i ****ed up...big time. please somebody help me out.
i was following this guide: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
to root my oneplus 5 so i can use Adaway. Ive rooted and installed a custom rom many times on my oneplus one before so I didn't really have any issues.
but then when I got to "Gaining root access" part, I was a little confused because I wasn't sure what step to take, so i Just did the stuff from the top. I think somewhere along the way I ****ed up and for some reason all my folders are gone except for android. (ie downloads, notifications, alarms, ringtones, music, pictures, etc folders are gone)
even when i take a picture, it just disappears because it has nowhere to save to... . when I plug it in with file transfer mode, there is literally only 1 folder, look at this picture: http://imgur.com/a/F49v0
is there anything I can do to fix this? or did i just GG no re 540$? I know i'm a ****ing stupid ass ****ing low life piece of **** dumbass **** head.
If worse comes to worse, I still got like 13 days left to return it if possible? Do u think they'll accept a return or replacement from me?
****
when I go to google and try to download an image, it says It can't be downloaded because of missing SD card. wtf is going on?!
EDIT UPDATE: okay now my phone is stuck on boot screen with the 1+ symbol. any1 know how to help me out?
Click to expand...
Click to collapse
Try to reboot into TWRP and format everything, including internal storage. Then flash any ROM and reboot.
If this doesn't work, you'll have to start all over again. Do a complete revert to stock.
Download the stock OP5 OOS 4.5.4 zip.
Download OnePlus stock recovery.
Reboot into fastboot/bootloader mode.
Flash stock recovery.
Boot into stock recovery.
Do a full wipe of /system and /data and /data/media (internal storage).
Sideload the full zip you downloaded in step 1 and flash it via stock recovery.
Reboot your phone.
easy
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
MrKhozam said:
Try to reboot into TWRP and format everything, including internal storage. Then flash any ROM and reboot.
If this doesn't work, you'll have to start all over again. Do a complete revert to stock.
Download the stock OP5 OOS 4.5.4 zip.
Download OnePlus stock recovery.
Reboot into fastboot/bootloader mode.
Flash stock recovery.
Boot into stock recovery.
Do a full wipe of /system and /data and /data/media (internal storage).
Sideload the full zip you downloaded in step 1 and flash it via stock recovery.
Reboot your phone.
Click to expand...
Click to collapse
i'm downloading a rom right now. btw I thought the latest OP5 OOS rom was 4.5.3?
huaiyue said:
easy
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
might I ask what exactly does this zip do?
update: solved everything by following khozam's method! that guys a ****ing beast. saved my ass. cheers
Sideload cannot read zip file
MrKhozam said:
Try to reboot into TWRP and format everything, including internal storage. Then flash any ROM and reboot.
If this doesn't work, you'll have to start all over again. Do a complete revert to stock.
Download the stock OP5 OOS 4.5.4 zip.
Download OnePlus stock recovery.
Reboot into fastboot/bootloader mode.
Flash stock recovery.
Boot into stock recovery.
Do a full wipe of /system and /data and /data/media (internal storage).
Sideload the full zip you downloaded in step 1 and flash it via stock recovery.
Reboot your phone.
Click to expand...
Click to collapse
Followed the steps. Everything works fine until sideload. I constantly get error in CMD prompt: cannot read...
I tried removing the zip file extension, dragging the file into command prompt. What am I doing wrong?
I have the same problem as OP where I foolishly deleted storage and now all I have is the android folder on the phone and cannot save files, nor download certain apps from the play store.
Thank you in advance...
sawihsiwi said:
Followed the steps. Everything works fine until sideload. I constantly get error in CMD prompt: cannot read...
I tried removing the zip file extension, dragging the file into command prompt. What am I doing wrong?
I have the same problem as OP where I foolishly deleted storage and now all I have is the android folder on the phone and cannot save files, nor download certain apps from the play store.
Thank you in advance...
Click to expand...
Click to collapse
Can you try formating first using the flash tool? If you accedentally deleted all folders even those in the root branch of the phone, It will generate the necessary files on your phone i think. Then you can simply flash twrp using the tool and should see the folders in twrp. Otherwise you can flash the full ota to generate them
sawihsiwi said:
Followed the steps. Everything works fine until sideload. I constantly get error in CMD prompt: cannot read...
I tried removing the zip file extension, dragging the file into command prompt. What am I doing wrong?
I have the same problem as OP where I foolishly deleted storage and now all I have is the android folder on the phone and cannot save files, nor download certain apps from the play store.
Thank you in advance...
Click to expand...
Click to collapse
Theoretically you should also be able to issue the following command in Recovery:
Code:
adb push -p [COLOR="Red"]<full zip path>[/COLOR] /sdcard/
Then select the zip from there. If you still get the read error, can you try rebooting into normal mode and issuing the same command?
Thank you for your help. huaiyue's storage fix zip file actually did the trick. I was able to restore everything back to normal. So thank you and thanks to huaiyue.
If anyone ever faces this again, Just follow below mentioned steps..
1: Flash TWRP
2: Got to Wipe and FORMAT data this will Decrypt you... AND let's you access your internal storage again..!
3: Now copy stock rom and FLASH.. This makes you ENCRYPTED again.
4: Now everything should be back to normal, just flash twrp again and enjoy..
Go to TWRP ----> select DATA (check it) ---> DONT swipe to wipe but click on REPAIR OR CHANGE FILE SYSTEM and select EXT 4. After that, reboot to twrp and data is recognized as normal sdcard..
That SD card fix helped but I want to know, what caused this?
---------- Post added at 12:03 AM ---------- Previous post was at 12:00 AM ----------
huaiyue said:
easy
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
thankyou so much dude!