A customer (I kinda do this for work) brought to me about 8 months ago a MZ604 full stock. I rooted, enabled BigPart, flashed CM11, customer happy. Yesterday he called me because the tablet boots to Android and immediately reboots. Easy, wipe, reflash, done.
Nope. Wiped data, rebooted. All the same. Wiped SYSTEM, I mean, deleting the ROM, all the same. It's like the memory is freezed (like on Windows when you reboot and everything you did in that session resets).
Tried RSD, stock ICS. No avail. RSD reports the flashing was succesful, but everytime I boot I get the same CyanogenMod animation. ROM boots, works for a few secs, and then reboots again.
I HAVE NOT A CLUE. Whatever I do, no change. Noting happens.
Also, when trying to change the recovery via fastboot, it reports it flashed correctly, but the recovery stays the same version.
Related
Installed cm920130120p505.zip and gapps-ics-20120429-signed.zip
The cm9 install went well. Rebooted well. Everythings appears to work fine, make and receive calls, WIFI & G3 works. Turned off the phone and it would not reboot. Just a blank screen. Tried to reboot into recovery. Won't work. Removed battery and waited. Tried recovery again. Won't work. Tried again, this time it rebooted into recovery! I then went ahead and flashed gapps thinking maybe it needed gapps. Turned off phone and it will not reboot. I sweet talked the phone into recovery and went back to Gingerbread 2.3.4.
I did the normal procedure for flashing. Wiped and formated, cleared the cache and wiped battery stats. Flashed the rom, rebooted. Everything looked great. Turned off the phone and tried to reboot into recovery and got the blank screen. You have to try rebooting into recovery by removing the battery and reinserting it and try the boot process maybe 2 or 3 times before it will work.
My Phone Stats: LG-P505, Android version 2.3.4, Kernel version 2.6.35.7-perf, Build number GRJ22, Software or Base Band version LG-P505-V20f - I am unlocked and rooted.
I did install the wrong gapps at first but I figured I could just reflash the correct one afterward and it would get rid of the old gapps. To make sure, I cleared the ROM of everything and started over from scratch 2x. Same result.
Ok, so my OPO got into a boot loop. I was running latest SlimKat weekly when suddenly during web browsing session the device rebooted itself and got into a boot loop. Well then I booted into TWRP recovery and wiped all the caches (cache, dalvik) and still no use. Then I did a factory reset and still I got a boot loop. Next thing I installed latest 3 SlimKat weeklys (had them on sd card) with factory resets between them and still the boot loop was there. Then the next few hours I spent installing stock roms from fastboot (22R, 25R, 30O, 33R) and still all I got was the boot loop.
Next morning I booted the device to recovery and did a factory reset and restarted (with 30O rom inside this time). Suddenly the device booted all the way to the Android and I was able to install few apps. Then I installed Whatsapp and launched the app. After the SMS confirmation the device rebooted again and proceeded to a boot loop. I turned the device off and let it settle for about 10 minutes. Then I booted in to the recovery and did the factory reset again and was able to boot all the way to the home screen again! Then after some more app installations came the reboot and boot loop.
Since then I haven't got past the boot animation.
In short terms:
- Was running latest SlimKat weekly
- Reboot and boot loop during normal web browsing
- Did factory reset, didn't help
- Installed stock roms from fastboot (22R, 25R, 30O, 33R), didn't help
What is your opinion? Could there be some hardware issue causing the reboot?
Video: https://www.youtube.com/watch?v=ChC58GHbSW4&list=UUHbkAIAVULcCb2pGa2lKIiQ
Sometimes device reboots before the actual CM boot animation, sometimes it reboots during the CM boot animation (usually straight after factory reset or flash from fastboot).
I think the hardware is faulty. I got my device to boot with the official AOSP rom and I even managed to install few apps. The device always reboots or completely shuts down when there is something more intensive going on, like downloading file from web site and installing app at the same time. I will try to investigate cpu and battery temperatures after work today.
Last week I manually flashed 5.1 on my Nexus 5, because it was rooted an OTA update didn't work. It was working just fine, till yesterday. It's not rooted and it doesn't have custom recovery installed. My battery died and phone turned off. I charged it over night and turned it on in the morning. The phone was booting longer than usual so I left it and came back 2 hours later. It was still displaying boot animation. It's not restarting or anything, it just shows boot animation. I restarted it to bootloader, flashed 5.1 with Nexus Root Toolkit, the phone again stopped at boot animation. Then I went to cmd, used fastboot and erased partitions, flashed it again, it still didn't work. Then I flashed 5.0.1, it still stopped at boot animation. Then I flashed 4.4.4, it booted, play store didn't work, but I managed to install 5.0.1, this time over OTA. After it rebooted, guess what happened. It still stopped at boot animation. After that I installed TWRP, went to recovery, wiped ALL partitions and used TWRP partition repair function, rebooted to bootloader, manually flashed 5.1 AGAIN and my Nexus is still stuck at boot animation. I even tried erasing partitions, still didn't work. All flashings were done without any error reported. Any ideas what might be wrong? Bootloader and Recovery are fine, It boots without problems on KitKat. But I was using Lolipop without any problems for a few months now. Suggestions?
This is a strange issue. I did not found any solutions for that. What I have in mind is that backing up modemst1, modemst2, persist and misc partition then erase the whole emmc with boarddiag tool. This is a bit risky because if this error caused by a faulty emmc we may cannot reflash the bootloader after the emmc is erased because it will fail on some I/O error.
Last night, I downloaded the 6.0 update, copied the .zip to external storage, rebooted to CWM, and flashed it (successfully), then flashed SuperSU over it, cleared dalvik, and rebooted.
Since then, I'm stuck with the Nvidia boot screen. I can use Power/Vol Up to get in to fastboot, but when I try to boot back into recovery, the screen goes black, but goes back to the Nvidia boot screen instead of booting to recovery, even after flashing a recovery image to it via fastboot.
I can probably fix this with enough time and tinkering, but I just came back from a two week from vacation at work and don't have the time to futz around with this. Posting here in case someone already has an idea on what the problem is/how to fix this.
Update: I was able to get back into recovery using TWRP referenced in http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541. Direct link is https://www.androidfilehost.com/?fid=24345424848487676.
I'm thinking this is a kernel issue.
This was a kernel issue. Flashing a older OTA (http://ota.nvidia.com/ota/data/post...wf-full_ota-36442_589.1541.20150826095201.zip) and booting normally, then rebooting to bootloader and fastbooting the CWM image worked. I'm restoring from a backup I took before flashing the update last night, then flashing TWRP, backing up, and trying this all over again.
Thank you, I was having the same issue :good:
Have the exact same issue, except that now, for some reason, I can't even get the device to turn on!
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.