Related
My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
If you're using Galaxy Nexus Toolkit v5.4 from mskip, you don't need to extract anything, just copy .tgz file into the appropriate folder and the toolkit will do the rest for you.
Try reflashing the stock image from google again (make sure you choose the one for CDMA version).
After that, use toolkit to flash CWM, and the touch version is fun.
highmoon said:
My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
Click to expand...
Click to collapse
If you're using Windows. You can be saved at this point. The good thing is that your device is being recognized by ADB in recovery.
The toolkit installed the SDK onto your computer
Here is what you do to go save yourself
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
go to C:\Android-sdk-windows\platform-tools and put the ROM and Gapps in there
Now, with your phone plugged into computer and in recovery, open up a command prompt
In recovery, navigate to "Mounts and Storage" and be sure to select MOUNT DATA
type
cd c:\android-sdk-windows\platform-tools
adb push EXACTNAMEOFROM.ZIP /data/media
(depending on the file size, it will take about a minute or two)
adb push EXACTNAMEOFGAPPS.ZIP /data/media
adb reboot recovery
------
Okay, now that you have rebooted recovery , go to "install zip from sd card" and MAKE SURE you see the ROM and Gapps package, but DON'T flash them yet.
Go back,
Wipe data
Wipe Cache
Go to advanced and select Wipe Dalvik Cache (ignore the SD-EXT error that's normal)
Go to Mounts and Storage - and select Format System
Go back
Go to install zip from sd card, flash ROM, then slect install zip from sd card again and flash Gapps
REBOOT
Enjoy
Again...
Samsuck said:
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
Click to expand...
Click to collapse
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Up to you, you can also just flash stock images and start over.
My method should work too, and leave you with root
Your choice
highmoon said:
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Click to expand...
Click to collapse
You could do it either way.
Okay, I found a solution without wiping everything.
(Flashing a stock ROM image, or other ROMs would wipe your everything...)
But thanks people!
For those of you, who would encounter something like this (including me again), I'm leaving a note.
0) This problem happens because your Boot partition, overwritten by ClockworkMod recovery image, is no longer compatible with the rest 4.0.4 image. So you need not only "recovery.img", but also "boot.img". Unfortunately, boot.img is not there in the 4.0.4 ROM. But luckily, someone else extracted it.
1) Get the 4.0.4 stock image from here
(android.clients.google.com/packages/ota/verizon_prime/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip)
2) Extract "recovery.img" from the file above.
3) Get "boot.img" in here (aospdev.com/rhcp/dev/404boot_root.img)
4) Get into FASTBOOT mode
5) fastboot flash boot boot.img (if not renamed, "404boot_root.img" above)
6) fastboot flash recovery recovery.img
6) Enjoy
Yesterday I wanted to flash the new CWM (5.8.4.0) but I accidentally flash using fastboot boot boot.img
Then it kept rebooting into recovery
After panicking a few times, I used Hasoon2000's allinonekit to flash stock recovery, stock kernel, relocked and reunlocked bootloader, factory reset through hboot.
Now im in a bootloop but instead of the usual htc with beats that i usually get, a simple logo featuring the word "android" is all that showed up on my screen. Sometime when I restart it would show a harddisk or something like that with a green refresh logo. In cwm my phone can't detect my sd so I can't flash my nandroid backup.
Can someone help this noob
Boot into fastboot.
First turn on the phone.
Hold both Power and Volume Down until the screen turns black, after two seconds release the power button only, it should boot you into fastboot, you can also try just holding both buttons, not sure about that so if it won't boot into fastboot try both ways!
When it boots into fastboot, open up command prompt and execute the command fastboot erase cache, this should make you able to boot into recovery again.
Good luck!
I can access recovery now. The problem now is the android bootloops
Katang said:
I can access recovery now. The problem now is the android bootloops
Click to expand...
Click to collapse
Do you have any ROMS on your SDCard?
If you do, follow these steps please!
First of all, find the boot.img of the ROM you have on your SDCard, do this by downloading the ROM to your computer again and extracting the boot.img or using franco's or whatever other one there is.
Put the boot.img into the directory where your fastboot.exe is located, boot back into Fastboot and execute the following commands, fastboot flash boot boot.img and then fastboot erase cache.
Boot into recovery from fastboot, Wipe Data -> Wipe Cache, browse for the ROM and flash it, this should fix your phone!
I was running ARHD 6.1.1 before. but like I said in CWM it cant detect my sd,
it says there is no such file. any ideas?
Katang said:
I was running ARHD 6.1.1 before. but like I said in CWM it cant detect my sd,
it says there is no such file. any ideas?
Click to expand...
Click to collapse
Yes, flash this CWM.
http://lh.rs/Zs6RYrc8m7Os
Put phone into Fastboot and run following commands.
fastboot flash recovery r1--recovery-clockwork-touch-endeavoru.img
fastboot erase cache
Boot into recovery see if it recognizes the SD.
flashed that recovery, cleared the cache
when I went into recovery i chose zip from sdcard but then no files found
in Hboot it said SD checking...
failed to open usb master mode
failed to open usb master mode
only then would it show the options:
fastboot
recovery
factory reset
simlock
showbarcode
image crc
Katang said:
flashed that recovery, cleared the cache
when I went into recovery i chose zip from sdcard but then no files found
in Hboot it said SD checking...
failed to open usb master mode
failed to open usb master mode
only then would it show the options:
fastboot
recovery
factory reset
simlock
showbarcode
image crc
Click to expand...
Click to collapse
what is your recovery version? 5.8.4.0?
If you flash the latest recovery 5.8.4.0, then you should be able to view your SD Card and also infact,
if you go to ADVANCED Mode in the latest Recovery, connect the USB, it will detect your PC. Transfer the required files.
You have recovery now, try mounting the SD Card. Make sure you have enough charge ( >50%)
Please do not panic!
I will try that. Although i don't know how much battery I have left cause it suddenly turns on and bootloops after I charge for a particular amount of time
did you fix your phone now? if you fix pls mail [email protected] me cos we have same problem im using HOX stock " android logo "
even i put file on cwm 5.8.4.0 SD failed open master mode
Is there any possible way of accessing the internal storage through TWRP? I made the unfortunate mistake of wiping everything including the OS. I would like to access the internal storage drive so I can put in a ROM and flash. Any help would be greatly appreciated!
olive.knight said:
Is there any possible way of accessing the internal storage through TWRP? I made the unfortunate mistake of wiping everything including the OS. I would like to access the internal storage drive so I can put in a ROM and flash. Any help would be greatly appreciated!
Click to expand...
Click to collapse
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot once, put the files you need on internal and then proceed from there.
cmstlist said:
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot custom recovery directly from fastboot, put the files you need on internal and then proceed from there.
Click to expand...
Click to collapse
+1
Maybe try using an OTG cable and usb stick. I just went from CWM to TWRP and saw that there was an option to use otg. I did did a backup to the usb directly and it works great. The inbuild file explorer was also able to browse all the files on the usb stick as well
bk201doesntexist said:
+1
Click to expand...
Click to collapse
You edited my quote to say "then boot custom recovery directly from fastboot". Please don't edit me. It does NOT work if your data partition is fully wiped.
On the Galaxy Nexus if you do a full userdata partition wipe, it CAN'T be written by any custom recovery until you do one full boot cycle into a ROM. The custom recovery will fail to mount the data partition. Booting into a ROM regenerates that partition.
You can see this after unlocking the bootloader, which does a userdata wipe. If you flash custom recovery and try to go straight into custom recovery, it will simply find no writable partition at all. Notice that when you boot into system after a userdata wipe, it commences the boot cycle and then reboots itself one additional time. I suspect that first boot cycle regenerates the userdata partition, and then the second boot cycle continues as normal.
cmstlist said:
If you can get ADB over recovery working, you can push files to internal storage.
Be aware that if you did a data partition wipe, TWRP may be unable to write anything to the internal storage partition until you've booted a stock ROM at least once. If this is the case, then you are best to flash a stock ROM from fastboot, then boot once, put the files you need on internal and then proceed from there.
Click to expand...
Click to collapse
Thanks for your reply as well as everyone else that has contributed to my thread. I am able to get my device to be in fastboot mode but adb does not detect my device. It states:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If this method does not work, would you suggest me to purchase an OTG usb cable as an alternative?
Adb doesnt work in fastboot mode.
Sent from my i9250
Why don't you just fast boot flash stock and start all over?
Sent from my Nexus 4 using xda premium
olive.knight said:
Thanks for your reply as well as everyone else that has contributed to my thread. I am able to get my device to be in fastboot mode but adb does not detect my device. It states:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If this method does not work, would you suggest me to purchase an OTG usb cable as an alternative?
Click to expand...
Click to collapse
In fastboot mode, you need to use fastboot (not ADB) to flash the stock ROM. Then after regenerating the data partition with one boot cycle, go back into fastboot again and flash custom recovery if you don't still have it.
Never tried it myself, but it should be possible to flash a custom recovery right when you're flashing stock through fastboot. Not through flash-all.sh, but manually flashing system.img, boot.img and userdata.img, unzipped from the update-jop40d.zip file, plus cwm.img or twrp.img, and then boot up normally, or directly to custom recovery to push a rom/root/whatever.
Again, if the device already has the latest bootloader/bb version, there's no need to reflash it. If using flash-all.sh, just comment those out from the script.
Sent from my i9250
bk201doesntexist said:
or directly to custom recovery to push a rom/root/whatever.
Click to expand...
Click to collapse
... except that if the userdata partition was completely wiped, directly to custom recovery will not be able to access the data partition until it's been booted into system once.
cmstlist said:
... except that if the userdata partition was completely wiped, directly to custom recovery will not be able to access the data partition until it's been booted into system once.
Click to expand...
Click to collapse
i stand corrected.
still, how about flashing userdata.img before flashing a custom recovery?
edit: I'm sorry. I must prove you wrong this time. I just finished flashing back to stock with the following steps:
- fastboot erase system
- fastboot erase userdata
- fastboot erase boot
- fastboot erase recovery
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot flash recovery twrp.img
- (manual reboot to recovery on the device)
- adb push ~/workbench/maguro/recovery_flashables/CWM-SuperSU-v0.99.zip /sdcard/
- (flash zip on recovery)
- (reboot system from recovery)
- rooted JOP40D, working fully.
bk201doesntexist said:
i stand corrected.
still, how about flashing userdata.img before flashing a custom recovery?
edit: I'm sorry. I must prove you wrong this time. I just finished flashing back to stock with the following steps:
- fastboot erase system
- fastboot erase userdata
- fastboot erase boot
- fastboot erase recovery
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot flash recovery twrp.img
- (manual reboot to recovery on the device)
- adb push ~/workbench/maguro/recovery_flashables/CWM-SuperSU-v0.99.zip /sdcard/
- (flash zip on recovery)
- (reboot system from recovery)
- rooted JOP40D, working fully.
Click to expand...
Click to collapse
I'm sorry if we have had different experiences, but this is what I have experienced:
- fastboot flash userdata userdata.img
- fastboot flash recovery {CWM or TWRP}
- (manual reboot to recovery on the device)
- Attempt to adb push anything
- Error message (I don't remember exactly what)
- Attempt to mount the data partition from the mounts menu
- Error message
- Boot into the ROM once, then into recovery
- No more error messages
This was my experience both on Galaxy Nexus and Nexus 7 3G.
FWIW, my GNex was bought from WIND Mobile in Canada. I have heard that the Play Store Nexus units are sometimes a bit different (e.g. some have reported that the Play Store Nexus does not wipe userdata after unlocking bootloader).
zephiK said:
Why don't you just fast boot flash stock and start all over?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Oh I definitely want to do this but I don't exactly know how to flash stock in fast boot mode. I don't know how to load the zip file in internal storage. If you could provide me a link or instructions on how to proceed I would gladly appreciate it!
olive.knight said:
Oh I definitely want to do this but I don't exactly know how to flash stock in fast boot mode. I don't know how to load the zip file in internal storage. If you could provide me a link or instructions on how to proceed I would gladly appreciate it!
Click to expand...
Click to collapse
When you flash in fastboot, the files reside on your computer and are flashed over USB to the device.
cmstlist said:
When you flash in fastboot, the files reside on your computer and are flashed over USB to the device.
Click to expand...
Click to collapse
I tried using my computer to command my phone in fastboot mode but my computer keeps stating that the "USB device not recognized" and the cmd continues with < waiting for device >. Are my efforts to revive my phone a lost cause?
Search around for GNex fastboot drivers. And make sure you're using fastboot on the computer, not ADB.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Search around for GNex fastboot drivers. And make sure you're using fastboot on the computer, not ADB.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you and very one else that contributed to my post. With your help and a dash of luck I finally managed to return my phone to working order. Thanks again and happy holidays!!!
Found this question from Googling, and I actually have an easy answer for it:
Load TWRP, connect the phone to your computer (I was on Windows), and you can access your Internal Storage and SD card normally through USB as an attached device.
Hi guys, I have a very big problem. After a crean wipe and install of cm11, my phone started to reboot after maybe 10 seconds from the boot. I tryed to restore factory but the toolkit and odin fail on writing of system.img.Could anybody help me? Thanks so much
lo97 said:
Hi guys, I have a very big problem. After a crean wipe and install of cm11, my phone started to reboot after maybe 10 seconds from the boot. I tryed to restore factory but the toolkit and odin fail on writing of system.img.Could anybody help me? Thanks so much
Click to expand...
Click to collapse
Are you able to get to recovery via the power button and volume button method?
Stupendousman2012 said:
Are you able to get to recovery via the power button and volume button method?
Click to expand...
Click to collapse
Also, is device recognized w/adb?
Yes, I'm able to use the fastboot but it didn't seem to work bacause I'm on cwm and I tryed to flash twrp but It didn't work. Also I'm not able to flash stock because it fails at system writing. No adb, I have only 15-30 seconds befere the FC and the restart
EDIT: Maybe it's a permission error (only R/O) how fix it?
lo97 said:
Yes, I'm able to use the fastboot but it didn't seem to work bacause I'm on cwm and I tryed to flash twrp but It didn't work. Also I'm not able to flash stock because it fails at system writing. No adb, I have only 15-30 seconds befere the FC and the restart
EDIT: Maybe it's a permission error (only R/O) how fix it?
Click to expand...
Click to collapse
Reboot the phone into safe mode by holding power until the reboot menu appears, and then holding your finger on the beboot button until the reboot into safe mode dialogue appears.
When you are in safe mode, see if you are able to navigate around without the phone auto-restarting.
If so, see if you are able to copy the rom and GAPPS to the sdcard/download directory and try to flash again?
Not sure if this will work, but at least you can see if the hardware is failing in safe mode
Stupendousman2012 said:
Reboot the phone into safe mode by holding power until the reboot menu appears, and then holding your finger on the beboot button until the reboot into safe mode dialogue appears.
When you are in safe mode, see if you are able to navigate around without the phone auto-restarting.
If so, see if you are able to copy the rom and GAPPS to the sdcard/download directory and try to flash again?
Not sure if this will work, but at least you can see if the hardware is failing in safe mode
Click to expand...
Click to collapse
Safe mode works only if I presso volume down button because everything I do seems to don't change anything after it reboot = like not saving thing. And It reboots also in safe mode (bu i have like 1-2 minutes...unless i try to delete something or download because them cause a reboot...) (sorry for my english). Every whipes and flash doesn't work...no factory reset, no toolkit reset, no odin reset..they all failed or just don't change anything (I tryed odin download and I pass but after it rebooted like every-time before)
lo97 said:
Safe mode works only if I presso volume down button because everything I do seems to don't change anything after it reboot = like not saving thing. And It reboots also in safe mode (bu i have like 1-2 minutes...unless i try to delete something or download because them cause a reboot...) (sorry for my english). Every whipes and flash doesn't work...no factory reset, no toolkit reset, no odin reset..they all failed or just don't change anything (I tryed odin download and I pass but after it rebooted like every-time before)
Click to expand...
Click to collapse
Fastboot(bootloader) is recovery independent, recovery doesn't even need to be there. I'm pretty sure from what you've said that you've got some corrupted partition(s). I went through the same thing, couldn't flash anything with adb. This is what you gotta do after you've tried to adb pull as much data from your phone as you want to backup. Most people don't know about this for some reason, it's very easy and reliable.
->Bootloader(fastboot mode) --- hold down VOL_UP + VOL_DOWN + POWER until your phone vibrates. There's post information at the bottom and the start, poweroff, boot -recovery, -bootloader options to scroll through.
->Leave your phone in fastboot mode and connect it to your PC/remote terminal. You can look at it once we execute some fastboot commands. A blue bar appears at the bottom of the screen once you send it a fastboot command/signal.
->Open up a command prompt as administrator (su shell with *nix/mac) in the directory where your fastboot(.exe) binary is. Should be the same as where adb binary is -- Don't trust adb executable downloads that don't come with fastboot. Check for connectivity, a serial should print just like with adb after entering:
Code:
fastboot devices
-----NEXT STEPS WILL WIPE && FORMAT YOUR PHONE-----
->We are going to do a fastboot erasure. This is a complete wipe/format. It reconfigures block size, cylinders, etc (default unless specified) and can format all the specified "mmc" image blocks in /dev/block. The most likely place you're gonna see data corruption is in /data and /cache because those are always mounted Writable and pretty much all data writes occur their unless you're flashing a new rom, kernel, modding /system s***, etc. Then you will temporarily be writing to some other partition blocks. So let's do a userdata and cache fastboot format. This will completely erase /data and /cache (including sdcard, it won't take a second glance). I've never heard of this failing btw. It's the gold standard of debugging reliability, and unfortunately Odin is something to definitely avoid. Bury that one away in your suicidal desperation toolbox.
Code:
fastboot -w
Reflash your bootloader, unlock it, flash recovery TWRP, and flash a kernel boot.img that's super stable like FAUX Kern or Fancy. <---- Do all that in fastboot! ---- Check the Galaxy Nexus wiki page for these commands. I'd search "fastboot commands" in xda, there's some cool s*** fastboot can do.
Then you can boot recovery, adb push all sd stuff back over. Flash a new rom with adb sideload. Make sure to download trickster and either set Dynamic Fsync = OFF or set Fsync = ON to avoid data corruption system gangbangs. :good:
7175 said:
Fastboot(bootloader) is recovery independent, recovery doesn't even need to be there. I'm pretty sure from what you've said that you've got some corrupted partition(s). I went through the same thing, couldn't flash anything with adb. This is what you gotta do after you've tried to adb pull as much data from your phone as you want to backup. Most people don't know about this for some reason, it's very easy and reliable.
->Bootloader(fastboot mode) --- hold down VOL_UP + VOL_DOWN + POWER until your phone vibrates. There's post information at the bottom and the start, poweroff, boot -recovery, -bootloader options to scroll through.
->Leave your phone in fastboot mode and connect it to your PC/remote terminal. You can look at it once we execute some fastboot commands. A blue bar appears at the bottom of the screen once you send it a fastboot command/signal.
->Open up a command prompt as administrator (su shell with *nix/mac) in the directory where your fastboot(.exe) binary is. Should be the same as where adb binary is -- Don't trust adb executable downloads that don't come with fastboot. Check for connectivity, a serial should print just like with adb after entering:
Code:
fastboot devices
-----NEXT STEPS WILL WIPE && FORMAT YOUR PHONE-----
->We are going to do a fastboot erasure. This is a complete wipe/format. It reconfigures block size, cylinders, etc (default unless specified) and can format all the specified "mmc" image blocks in /dev/block. The most likely place you're gonna see data corruption is in /data and /cache because those are always mounted Writable and pretty much all data writes occur their unless you're flashing a new rom, kernel, modding /system s***, etc. Then you will temporarily be writing to some other partition blocks. So let's do a userdata and cache fastboot format. This will completely erase /data and /cache (including sdcard, it won't take a second glance). I've never heard of this failing btw. It's the gold standard of debugging reliability, and unfortunately Odin is something to definitely avoid. Bury that one away in your suicidal desperation toolbox.
Code:
fastboot -w
Reflash your bootloader, unlock it, flash recovery TWRP, and flash a kernel boot.img that's super stable like FAUX Kern or Fancy. <---- Do all that in fastboot! ---- Check the Galaxy Nexus wiki page for these commands. I'd search "fastboot commands" in xda, there's some cool s*** fastboot can do.
Then you can boot recovery, adb push all sd stuff back over. Flash a new rom with adb sideload. Make sure to download trickster and either set Dynamic Fsync = OFF or set Fsync = ON to avoid data corruption system gangbangs. :good:
Click to expand...
Click to collapse
It says that wase pass but didn't change anything. Also flash the recovery didn't change anything (I was on CMW and after flashing the TWRP, it opened CWL like always). I'm desperate .
lo97 said:
It says that wase pass but didn't change anything. Also flash the recovery didn't change anything (I was on CMW and after flashing the TWRP, it opened CWL like always). I'm desperate .
Click to expand...
Click to collapse
nothing is changed after flashing, it took long time to flash system then it failed...= fried emmc, need replacement.
samersh72 said:
nothing is changed after flashing, it took long time to flash system then it failed...= fried emmc, need replacement.
Click to expand...
Click to collapse
Also if it works normally for like a cuple of minutes?
lo97 said:
Also if it works normally for like a cuple of minutes?
Click to expand...
Click to collapse
if the emmc is died, phone works fine, but nothing can be deleted or flashed. nothing will stick.
try to lock bootloader with fastboot command, i guess it will still unlocked...
samersh72 said:
if the emmc is died, phone works fine, but nothing can be deleted or flashed. nothing will stick.
try to lock bootloader with fastboot command, i guess it will still unlocked...
Click to expand...
Click to collapse
Ok, thanks ... :'((
samersh72 said:
if the emmc is died, phone works fine, but nothing can be deleted or flashed. nothing will stick.
try to lock bootloader with fastboot command, i guess it will still unlocked...
Click to expand...
Click to collapse
Is this a pretty surefire way to tell if emmc is good or not?
I did a fastboot OEM lock and it seems to have locked ok (reloaded bootloader after command)
bpm2000 said:
Is this a pretty surefire way to tell if emmc is good or not?
I did a fastboot OEM lock and it seems to have locked ok (reloaded bootloader after command)
Click to expand...
Click to collapse
Are you able to adb push, adb sideload, fastboot flash anything over at this point? If you can you get into a recovery and use adb check for any files in data, system, cache that aren't deleted. Then run
Code:
adb shell
/sbin/busybox mount -w -o remount /system /system
/sbin/busybox mount -w -o remount /data /data
/sbin/busybox mount -w -o remount /cache /cache
find / -exec /sbin/busybox chattr -i '{}'\;
. This will make sure you don't have any immutable files; it makes all files mutable so rm -rf works and so installations can replace and delete them.
Hey Guys I've got a problem with an install im trying to build using a Nexus 7 (2103) flo....
So far I've run:
Code:
adb reboot bootloader
fastboot oem unlock
I downloaded openrecovery-twrp-2.8.5.0.img and then ran:
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0.img
I rebooted the Nexus after it finished and I copied supersu.zip to the internal storage area and I ran:
Code:
adb reboot recovery
I then got the red triangle on top of the android robot - it doesnt seem to matter what I do, I cannot get to the recovery area to install the supersu file..
Any ideas what I could try?
ok for some reason it works on the first time after I've installed the recovery however when I reboot the tablet I cannot access the recovery bit until after I've flashed the nexus with a factory image!
Is there something I am doing wrong? Surely I don't need to keep flashing my image just to see the recovery section.
Also, I'm moving some zip files to the internal memory (shown as a device on windows 10 - not an actual drive) however when I'm in recovery I cannot see the files - but go back in to normal android they are there
1. Wrong forum
2. Try: adb boot recovery.img, once in recovery use adb push su.zip /sdcard, flash zip, reboot to bootloader, adb flash recovery recovery.img, then adb reboot recovery