Guys I have a big problem!
For about a month I have on the galaxy nexus rom slimkat + kernel dfk and until tonight I had not any problems, until this evening the phone has rebooted and the disaster happened, the boot animation was jerky and the phone has put more than 5 minutes to power, however going slow, and even after I have booted the phone is super slow, it's all jerky and unusable.
From recovery I tried to wipe system, but even if the message confirming correct operation, it really does not matter because if I reboot the phone loads the system, even if ever so slow and jerky.
I also tried to use the Nexus root toolkit but nothing, when I try to reflash stock hangs the command "writing system" and does not go forward ... I do not know what else to try.
I also tried using fastboot commands, but nothing changes ... not the operations are successful and the changes are not applied.
Please help me! Thank you very much!
Wipe system, cache, data, dalvik cache and internal.. Then flash stock factory image and then install roms
Wipe from recovery do not work.
I tried to flash from toolkit the stock factory image, but hangs on the command "writing system".
There is another way to flash it??
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
h4xx0rr said:
Yes..you can to flash another recovery with nexus root toolkit. Boot into android and enable usb debugging in dev. options, connect gnex with PC and flash recovery (cwm or twrp or philz, not STOCK) and then wipe..
Click to expand...
Click to collapse
I've tried, the procedure seems to be successful but the recovery does not really change.
I also tried to flash the stock rom with odin, well after the half-hour procedure is successful, the phone has rebooted but nothing, everything remained as before, with the old rom.
I do not know what to think anymore, I try recovery, toolkit, fastboot and odin but nothing.
I came to doubt that it may be a hardware problem with the internal memory of the phone, do not you?
Thank you!
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
h4xx0rr said:
Try to boot into recovery temporary with nexus root toolkit if you can't to flash..this can help to wipe all and brick gnex
Click to expand...
Click to collapse
I boot into temporary recovery and i do successfuly all wipe, but when I restarted the system, nothing has changed, loaded the old rom
I do not know what to do!
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
h4xx0rr said:
If you wiped, system can't be rebooted. I really don't have more ideas
Maybe you have problem with hardware.
Click to expand...
Click to collapse
Thanks ... I think like you!
Related
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
Dear All
yes, I am new and I feel exactly as the intro-video when registering was referring to ("noob", "loser",...)
After half a year, thought it was time to root my galaxy nexus. Used the Gnexus Toolkit. Everything worked fine.
So, I wanted to take things a bit further and as I've read interesting things on the franco.kernel, I tried to flash a new kernel using the app's automatic flash tool.
Device restarted, stuck at the Google logo.
I went inro recovery mode and followed some guidelines I found here and on other fora telling me to wipe data, wipe cache, wipe dalvik cache, format data,....
First tried to restore the "recovery"-thing clockworkmod creates for you when first using it. Didn't work.
Tried to wipe/format once again... Nothing helps and now I've even lost the "recovery"-thing.
only option seems to adb sideload... but I do not seem to get that working.
Well... hm. Here I am then. Having no idea to continue...
And, yes,... I have to repeat... I feel exactly as the intro-video of xda is suggesting I should feel
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
joooe said:
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
Thanks: I was indeed able to start in fastboot and used the Gnex Toolkit. I installed the stock image (4.0, then it updated to 4.2.1 later).
Pfffew, everything now works. hehe.
Thanks.
:good: Good result then.
joooe said:
I would probably start all over again.
Download latest version of ClockworkMod Recovery, go to fastboot mode, flash it.
Download rom, push it to the "sdcard" with adb, then go to CWM recovery and flash the rom.
Click to expand...
Click to collapse
That's indeed what I wanted to do.
Need to get some work done now. Will try it in the weekend. Thanks for the help.
Please Help....
I have a GSM galaxy nexus with the latest Slimbean 4.3 custom ROM. Recently my phone randomly started bootlooping. I was reading something on Flipboard when suddenly it rebooted for no apparent reason. When my phone restarted I was waiting for my widgets to load and after about 30s it rebooted again and now for the past two days it doesnt work for for more than 30s before it reboots. I tried to get into Trickster MOD to disable set on boot but I don't have enough time. I've tried everything suggested in all the threads without success.
Here's what I tried so far to fix my phone:
1. I have custom recovery TWRP 2.6.0.0 installed on my phone. I rebooted into recovery and tried to dirty flash Slimbean 4.3 build.1 and GAPPs again. But it continued to boot loop
2. Next I went to the wipe menu and did a factory reset wiping cache, dalvik and data (not data/media) then I reinstalled Slimbean 4.3 and GAPPs. surprisingly when I rebooted it was as if the factory reset did not work. All my apps my widgets and my customizations were still there. I didn't go through the android initial setup process that you normally go through when you do a clean wipe, and my phone again started to boot loop.
3. I decided to forego any data that I have on my phone so I rebooted back into recovery and this time from the TWRP wipe menu I did a Format Data in the hope that it would wipe my phone completely. I expected it to wipe all my data, the ROM, everything except the bootloader and the recovery. Nothing was wiped. Even though I got a message saying success, when I rebooted the phone it booted back into Slimbean and all my apps and widgets and customizations were still there and it started to boot loop again!!
4. so I moved on to the next step. Using Nexus Root Toolkit v1.7.2 by WugFresh I decided to flash a Factory image on my phone first I tried to flash a TAKJU 4.3 JWR66Y factory image in bootloader mode using fastboot. Everything seem to succeed normally... radio.img, recovery.img, boot.img and userdata.img all seemd to proceed normally. After about 10 minutes of going through this I rebooted my phone and still nothing had changed. My phone booted back into Slimbean with all my apps and my widgets and my customization intact and it continued to bootloop again.
5. I repeated the above with a TAKJU 4.2.2 JDQ39 factory image. Again it seemed to complete successfully but when I rebooted it went back into Slimbean and I still had all my apps and my data and my customizations intact. My phone continued to boot loop.
6. I decided to try Odin to flash a factory image. I used ODIN3 v1.87 and loaded the i9250 PIT file to repartition my phone and I loaded a TAKJU 4.3 md5 file under PDA. The process completed successfully showing a bright green pass. When I rebooted my phone keeping my fingers crossed nothing had changed. Slimbean, all my apps, all my widgets, my data and the bootloop were all still there!!
7. I tried the same process with ODIN3 v3.07 however each time halfway through flashing system.img the process would fail and nothing would change.
Right now I'm completely flabbergasted and I don't know what else to try I wish there was a way to completely wipe my phone so that It would have no OS, no partitions, no data, a fresh clean slate that I could repartition and flash a factory image and proceed from there. I'm wondering if there is any tool out there that can do a low level format of the NAND so no trace of any OS or any data remains. Perhaps then I can flash a bootloader and a recovery and factory image. Even if someone could help me softbrick my phone so that it wouldn't boot up, it would be welcome change from this frustration that I'm experiencing. Any suggestions and any help would be much appreciated.
Thanks,
iMethodZ
Have you tried using fastboot?
Sent from my Galaxy Nexus using Tapatalk 4
fried emmc...
try to lock the bootloader, it will still unlocked
Zepius said:
Have you tried using fastboot?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
I have tried fastboot erase userdata
erase system
erase boot
erase recovery
erase cache
format userdata
format system
format cache
all commands succeed but they don't seem to have any effect at all... nothing gets erased... all my data is still there
samersh72 said:
fried emmc...
try to lock the bootloader, it will still unlocked
Click to expand...
Click to collapse
How can I attempt to lock the boot loader?
My phone is still under warranty is there anything I can do to completely brick it so I can get a replacement device?
fastboot oem lock
locks the bootloader. if that fails, your emmc is fried.
Zepius said:
fastboot oem lock
locks the bootloader. if that fails, your emmc is fried.
Click to expand...
Click to collapse
well I tried that and the message says "okay" but the bootloader is still unlocked... I guess that means the emmc is fried
Any ideas on how to fry the phone even further so it wont even turn on ... perhaps I'll be able to get a replacement device LOL
hi, recently i decieded to install CM11 on my samsung galaxy nexus, i downloded it and then i reset facotry my phone, but when i wanted to install it from Bootloader i got an error, then i thohgt it cause of old bootloader so i wanted to update it but THE problem showed up, i cant come into my android it wont be come, please help me out
If all you did was a normal factory reset, it should boot up fine. If you did something like wiped system, then you need to get to a computer and use ADB. If you wiped system then you have nothing to boot to
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
the error is: set_metadata_recursive: some change failed
E:erro in /sdcard/0/0/cm-11-20131130-UNOFFFICAL0maguro.zip
(stat7)
insstalation aborted.
the.farbod said:
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
If you have a backup though, why cant you just restore the backup? Can you not get into the recovery anymore?
kinda curious, OP why didnt you just wipe everything in recovery mode and flash it??
1) adb reboot bootloader
2) fastboot flash recovery ***recovery.img*** (i like to rename the image to "recovery" for the ease of my own useage)
3) press vol rocker to recovery mode and flash away!
I personally use TWRP, but a lot of people prefer CWM, they are both amazingly easy to use.
worst case, you flash the stock 4.3 image from google to get everything back on track.
First of all check out this thread http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835. I had a problem with my phone because i rooted it, and i wanted to apply an ota so i unrooted and applied the ota, but that got me stuck in a bootloop. So i went to the thread above and did what the instructions said. Everything was fine until i started getting force closes on gapps and most apps on my phone, so i decided to reflash the system with the prerooted image from the link above. I did this and i decided to go into recovery from bootloader in order to format data as this stopped the force closes the first time. When i booted into recovery i got the same old android logo that says error, only this time it was blinking and i couldn't get into the recovery; I then force shut off the phone and tried to boot up normally but i got the same error android guy flashing again. So since i couldn't get into the stock recovery then i tried http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063. This cwm recovery booted up fine after a minute or two. Once in there I went down to wipe data/factory reset; It completed the process and i rebooted and there was no error this time, the phone booted up normally.
If anything similar happens to someone try first the guide in the first link, then the second link if you can't get into recovery.
I hope this helped someone with the same circumstances.
@Ratedzelaya, hey, it was good of you to share your experience with all people. Btw, you required CWM to do a factory reset, right? And that factory reset fixed the phone for you, right? Well, if that's the case, you could simply boot to bootloader mode, and then issue these commands to do a factory reset:
fastboot format userdata
fastboot format cache
No need of recovery in this case, and the device should be fine as per your method. Just sharing my opinion! Having CWM recovery isn't bad anyway
itskapil said:
@Ratedzelaya, hey, it was good of you to share your experience with all people. Btw, you required CWM to do a factory reset, right? And that factory reset fixed the phone for you, right? Well, if that's the case, you could simply boot to bootloader mode, and then issue these commands to do a factory reset:
fastboot format userdata
fastboot format cache
No need of recovery in this case, and the device should be fine as per your method. Just sharing my opinion! Having CWM recovery isn't bad anyway
Click to expand...
Click to collapse
That's helpful information in case I ever need it. I'm not the most familiar with fastboot or adb.
Ratedzelaya said:
That's helpful information in case I ever need it. I'm not the most familiar with fastboot or adb.
Click to expand...
Click to collapse
it's full of tutorials here,just search
Bro im not really familiar with bricked devices,
But may i ask again about what happened in your device
are you sure your device it is considered hard bricked not soft?
Just asking )))