I am having a lot of trouble restoring my GSM Galaxy Nexus to it's former glory. I installed CM12 and CWM recovery earlier but CM12 suddenly stopped working. My phone started rebooting over and over so I decided it was to time to flash the stock ROM.
I flashed the stock ROM with WugFresh's root toolkit. And it worked fine besides the fact that writing the system.img took 30 mins, which is very unusual. I rebooted my device and CM12 showed up again... ?!. I tried flashing it by hand with ADB but no luck either. CM12 was still there.
I've been busy 3 days now and suddenly realized that CM12 created new root folders after a factory reset which I did multiple times. So for example, my sdcard contains one root with a folder, named 0, that contains the files on my phone before the factory reset. The problem is that this folders contains the system and CM12 ROM too. So I have like four 0 folders, and the 'deepest' one contains the system and ROM.
Assuming that if you flash a stock ROM, it will install in the root of my SD-card, but doesn't boot because it didn't overwrite the CM12 ROM in the deepest '0' directory [IMG]. If only CM12 was working, I could manualy delete all the unnecessary 0 folders... I really have no idea how to continue from now on and I really need your help [IMG]
Edit: I tried: adb shell rm -r /sdcard/0 and it is gone but if I reboot Recovery and look into my folders everything is there again...
epilogue:
Maybe the fact that system.img took 30 minutes to write has something to do with all those 0 folders [IMG]
I tried flashing multiple recovery's to my device but they only show up if I open them via ADB. Otherwise CWMR shows up again because that one is actually installed in the 'correct' (read:incorrect) folder.
With Skipsoft roolkit I actually received an error while writing userdata.img. It said: remote: write fail. I thought this was due the multiple installation folders and the toolkit not knowing where to place/flash the ROM.
So I need to remove all the 0 folders and place the OS back in the sdcard's root, or I have to somehow tell android to place the stock ROM in the same directory as CM12, or I need to somehow wipe the complete sdcard so I can install a new recovery and flash the stock ROM... I have no idea how however.
Thanks in advance!
Related
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse
xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image
Hello there, I've flashed the new Android Revolution 4.3 Rom, and after restoring a TiBu backup, I rebooted.
Since then I'm stuck in recovery, since no Rom will boot, not even the one I had flashed before.
The good news is that I can still get into recovery, the bad news is that I don't seem to be able to do anything from there.
I tried to push the latest 3.96 PA but adb push command fails saying that
Code:
failed to copy 'pa_maguro-3.96-20130813.zip' to '/sdcard/pa_maguro-3.96-20130813.zip': Read-only file system
This has never happened to me before, what can I do?? Any help is very appreciated!
Edit: seems like a full wipe of internal storage fixed everything
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
I have same problem. When i turn on my phone there is a google screen and then "X" screen. After 30 seconds it reboots again and again. I tried everything that i found on xda forum. Pls help !
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
DR3W5K1 said:
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
Click to expand...
Click to collapse
Erk.... No wonder sometimes when in fastboot mode, when flashing the userdata.img, it will failed with "Read Only Mode" error.
:crying::crying::crying:
But, thanks bro for your information.
Hello, I flashed PA 4.4.4 on my i9250 and now I wanted to go back to 4.3. Unfortunately I have a problem because my 4.3 backup isn't visible anymore, directories are messed up by 4.4.4. Found a way to make it visible (had to put an old backup to /data/media/clockworkmod/backup/) but I get an error while trying to restore it. I even flashed my previous cwm and installed cm 10 (the one that I've got my last backup from) but now all i get is a bootloop... I think it's caused by messed directories. How to get rid of those f***ing 0 emulated location?
1. Download JB factory image for your NExus from here: https://developers.google.com/android/nexus/images
2. In the recovery make swipe data/factory reset
3. power off and boot into fastboot mode...
3. Flash system partition through fastboot. (You need Fastboot drivers for Windows..) (system.img):
fastboot flash system system.img
and flash boot.img :
fastboot flash boot boot.img
4. Boot.
Nb. You have to extract the img files from the zip package.. if you want you can use flash all batch file (.bat) or script file (.sh) (depends of the OS...) but if you use it, then it'll flash everything automatically and wipes everything from the phone.
Hm I hoped that will do without going back to stock. I suppose this operation will relock my bootloader?
casioman1 said:
Hm I hoped that will do without going back to stock. I suppose this operation will relock my bootloader?
Click to expand...
Click to collapse
Only fastboot oem lock command locks your nexus's boot loader.
About "0" and some other directories, these are new on JB 4.2 or 4.3... you can remove them but it's useless... so I recommend to keep them.. 0 is like the current user,, for e.g 3 is the second user (multi user)...
CWM backups: I am not really sure... you can remove md5 stuff and maybe recovery lets you flash the files.. Also use the recovery with what you made the backup if newer CWM recoveries won't flash it
Hell yeah! Finally got it done. This it how:
1. flashed an old recovery (the one that I've got my last backup from) but still got a bootloop with an old cm10.
2. installed the newest working wersion of CM just to put my backup into different directory and make it visible (make sure you copy both folders with a date of your backup AND blobs because without the latter one it won't restore giving you an error)
3. voila, you've got a fully restored system
Thanks Carlos_Manuel for your help
Hi everyone !
I wanted to install the new MIUI 9 rom (9.5.8.0 OCAMIFA) through the recovery, but couldn't find any file in the TWRP recovery. I had an error when mounting the data partition.
I saw the solution was to reformat the data partition, so I wiped and reformated the partition. After that, I coudn't flash the 9.5.8.0 rom. I had an arror telling me that my device was not compatible. Actually the updater script within the ROM zip file looks for a variable called product and it must be set to 'sagit', the name of the MI6. But on mine it is not set, I don't know why. So I modified the updater script and succeded in flashing the ROM, but the phone got stuck at startup, with the Mi logo.
I saw that to get rid of that I had to flash the rom through fastboot. So I downloaded the Mi flash tool and the fastboot version of a rom (9.5.6.0). Once again, I had to modify the bat scripts, since they were looking for this 'product' variable that is not set on my phone. The flash started well but eventually after 30 seconds I had an error (write error) whatever the bat file I used.
But I didn't give up. I still had an old TWRP backup on my hard drive. So I rebooted in recovery mode, and transfered the backup files. But during the transfer, it stops copying ; the progress bar get stuck. I tried to copy file by file, but only the small files are copied. The big ones never make it to the end.
I think I'm cursed. Now I don't know what to do. I think I've tried almost anything I could.
Does anyone have an idea ?
i've also got bootloop after updating from 9.2.2.0 to 9.5.8.0 through TWRP, now i'm hopeless and also looking for help. i've wiped cache,dalvik,and data (exclude internal storage) even i've flashed dm-verity.zip to avoid bootloop after flashing the rom
jeanvalery said:
Hi everyone !
I wanted to install the new MIUI 9 rom (9.5.8.0 OCAMIFA) through the recovery, but couldn't find any file in the TWRP recovery. I had an error when mounting the data partition.
I saw the solution was to reformat the data partition, so I wiped and reformated the partition. After that, I coudn't flash the 9.5.8.0 rom. I had an arror telling me that my device was not compatible. Actually the updater script within the ROM zip file looks for a variable called product and it must be set to 'sagit', the name of the MI6. But on mine it is not set, I don't know why. So I modified the updater script and succeded in flashing the ROM, but the phone got stuck at startup, with the Mi logo.
I saw that to get rid of that I had to flash the rom through fastboot. So I downloaded the Mi flash tool and the fastboot version of a rom (9.5.6.0). Once again, I had to modify the bat scripts, since they were looking for this 'product' variable that is not set on my phone. The flash started well but eventually after 30 seconds I had an error (write error) whatever the bat file I used.
But I didn't give up. I still had an old TWRP backup on my hard drive. So I rebooted in recovery mode, and transfered the backup files. But during the transfer, it stops copying ; the progress bar get stuck. I tried to copy file by file, but only the small files are copied. The big ones never make it to the end.
I think I'm cursed. Now I don't know what to do. I think I've tried almost anything I could.
Does anyone have an idea ?
Click to expand...
Click to collapse
Try to transfer your backup file with adb push maybe, and see if that manages to copy your file over (You need to have adb installed on your computer of course)
I dont have my Xiaomi Mi 6 rooted, so I can't test it on my Mi 6, but I tested this on my rooted Z3 Compact, and it seems to work great there
Reboot into recovery launch a command prompt on your computer and type:
adb devices to see if you can see your device
if that works you can try to adb push to transfer your TWRP-backup
like this:
adb push /home/zteam/adb-backup/backup.zip /