First, sorry if this does not belong here. I did search here and Google and there were a few posts touching on this, but for the most part they were old and the issues were unresolved.
PLEASE Skip The Following (between ** and **) at first unless you really want to read it. My questions are at the end.
**
1. I say this a lot. Though I have abstained for the past week, since I first received my GTab, I have bricked it in various ways and always recovered (thanks to all the G Masters here and elsewhere).
2. This time I really do not know what happened. I added a new program and next time i rebooted ended up in a loop. No problem: I have been very cautious about making backups in CWMod regularly (and using NVFlash ever week or so).
a. Followed acceptable procedures to restore via CWMod. Nothing. Stuck in bootloop again.
b. Turned to ADB and NvFlash. Batch restored BL and the 11 partitions. Wasn't really paying attention to the screen at the time. No errors, all success. Boot loop again.
c. Went back and tried again, this time paying attention. Though the utility enumerates and formats all 11 partitions, it does not appear to upload the part-2.img and part3.img (Boot Config Table and Partition Table).
d. Those sound important so I tried to use the rawdevicewrite command (NOTE: beokit's NVFlash version does not include this command). It would not let me proceed without installing the bootloader again along with Part-2.img. That worked ... insofar as it did write the img to the partition.
e. Move on to Part-3.img. Tried to use --resume and it told me that the bootloader was bad. Tried to reinstall bootloader with it and it failed also indicating that the bootloader was bad.
f. Reboot--nothing but black. Fortunately I knew that ADB was still there.
g. Tried to use the NVFlash Format utility followed by Stock 3558 recovery followed by NVFlash - CWMod. Best I got was back to boot loop. Various other permutations including replacing Part-9.img with the boot image from CWMod backup.
h. Finally, I broke down and repartitioned the internal SD ... which, for some reason TBD, only took about 2 seconds. Reboot Recovery --> forgot about wiping the SD and decided to flash Vegan 7 right away. Install from SD-->choose file-->flash. Reboot ---> No loop, 30 seconds later fully booted. Second recommended reboot.
i. Wait a minute --- I installed from the SD Card that I just partitioned???? Annoyed that I wasted a good 10 minutes backing up the SDcard to my computer before partitioning, rebooted into CWMod and tried to repartition again. Success in 2 seconds. So Repartitioned again with different values (not 2048/0). Success in 2 seconds. And again back to 2048/0. Reboot recovery.
j. Navigate to SD card in CWMod. Still untouched. Installed Pershoot's kernel and booted in 30 seconds again. Currently in Titanium Back up restoring my 198 items...
**
I have the correct versions of NVFlash and CWmod.
Questions:
I . Why does NVFlash format Partitions 2 and 3 if it doesn't NVFlash then Restore partitions 2 and 3?
II. The only thing that got me out of the boot loop was to repartition my SDCard. Any thoughts on how this fixed the problem even though it did not actually repartition? And maybe why it didn't repartition (or why all my files were intact)?
At this point I would just really like to understand what went on? I am currently attributing success to the supernatural.
Also: This has been said many times before on here: BACKUP and REPARTITION your SD Card when nothing else seems to be working (especially when you are stuck in boot loop or frozen boot and cannot mount DATA partition in CWMod). Maybe it will help even if it doesn't actually repartition it at all...
Thanks!
Related
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Have you tried to reinstall firmware?
Regards.
GReddySetGO said:
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Click to expand...
Click to collapse
No need to panic.
When you rooted, did you install CWM Recovery, and if so, do you have a recent nandroid backup? Have you tried rebooting into recovery?
What steps have you followed to get out of your bootloop?
Yes, I have Clockword Mod Recovery 3.2.0.0 R4c 100611-1150
Upon attempting a restore everything appears to work properly until the end when it gets to restoring data, I get an error, regardless of which restore image I use(I tried all the ones I have). It reads as follows:
"Restoring data...
Error removing /data/data/com.noshufou.android.su/cacheError while formatting /data!"
I also attempted a clean wipe/factory reset with similar unsuccessful results. I get an error during formatting data, which reads:
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheFormatting /cache..."
The rest of the formatting appears to run successful for /sd-ext and /sdcard
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
jerrycycle said:
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Can you please provide me with more detailed instructions?
From the advanced menu I see:
Reboot Recovery
Wipe Dalvik Cache
Wipe Battery Stats
Report Error
Key Test
Partition SD Card
Fix Permissions
Sorry, we're forgot talking about Cwm. It's under mounts and storage.
Still the same result as before... I went to mounts and storage > format /data
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheError formatting /data!"
Try format system first then data and cache.
My suggestion would be to go back to stock and then re-root. You can find the stock download on the Moto Dev home page.
+1. Restocking link. MOTODEV > Produ / Software http:/.ly/sQtpKQ bit cts > Device. Then use universal root method reroot.
Sent from my Xoom using Tapatalk
Thanks everyone! I was hoping I would be able to fix it without going back to stock, but since I was unable to I just went that route.
Going stock worked, and I am back to where I was before, so thank you for the advice! In case anyone else may have this problem, this is what I did:
Went back to stock using this: http://forum.xda-developers.com/showthread.php?t=1049485
Then rooted using this: http://forum.xda-developers.com/showthread.php?t=1242241
Then got back to 3.2.1 using this: http://forum.xda-developers.com/showthread.php?t=1278214
Somehow my phone is bricked, although I still am not sure if it's because I actually did something wrong or it just decided to brick itself out of spite. Here's the rundown of events:
This past August I rooted my phone and installed cm-10.2. I made a backup of the stock rom beforehand (which for some reason is dated from 1970). Since then there have been a bunch of bugs, but nothing super major.
Today I decided to upgrade to cm-11, so I backed up everything important to my PC and used the auto-updater. I got a Status 7 error and the installation didn't complete, and I got stuck in a reboot loop that kept returning me only to the bootloader. I read on another forum that the problem was probably my CWM version (6.0.1.2 instead of 6.0.1.3). Anyway, I tried restoring one of my backups, but the bootloader said the folder was empty and no backups were found. I ended up reinstalling cm-10.2 and gapps from the same zip files I used months ago. This let me properly boot up my phone, but for some reason the google play store still wasn't working. I did a simple reboot and it started working again, so I downloaded rom manager and updated cwm. Rebooted into bootloader, made another rom backup, and tried again to install cm-11. Same error, install aborted. This time, however, my backups magically reappeared (along with an extra mystery backup that had today's timestamp but was ~10 hours in the future), so I restored the original (1970, stock rom). Things boot up fine.
I decide to try installing cm-11 one more time because at this point I assume that if it fails again I can safely restore a backup or at the very least reinstall cm-10.2. It fails again, but this time, when I try restoring any of my cm-10.2 backups I get a DM5 mismatch error and it immediately stops. Restoring 1970 is different, it starts recovering but then halfway through says "error restoring /system" or something like that. So now I'm left with no choice but to reinstall cm-10.2 from the same zip file again. Only this time, booting up only shows the cyanogenmod logo forever. I go back into bootloader and my backups are once again suddenly not recognized. I make a new backup of my broken phone to see if it will make the folder show up. I reboot, and now that new backup is the only one that does show up. Trying to restore gives me a DM5 error. I've now tried reinstalling cm-10.2 several times, but my phone will never get past the cyanogenmod logo. I'm out of ideas for how to get my phone to work.
My questions:
1. Any idea how to unbrick my phone? I have not done any factory resetting because I was worried it would erase my backups and also I don't really see how it would help.
2. Does anyone have a backup image I could use? I don't have mine stored anywhere but on my phone's internal SD, but I could maybe try loading one from my external SD if I had one.
3. What did I do wrong here? From my viewpoint it seems I basically tried the same thing twice and got different results. Is there something I'm missing?
4. If I get a new photon q, how the hell should I go about installing cm-11? I know people have gotten it to work before. Which version are you using?
Thanks for any and all help
I'm guessing you don't have a backup of stock?
Have you tried restoring stock everything using RSD Lite?
Also, how long have you let the phone sit? If the phone requires a 'fsck' (file system check) on you /data partition, you could be waiting for an hour or more at the boot animation.
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
DRH48 said:
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
Click to expand...
Click to collapse
See this thread for information on how to restore stock... always a good idea to know how to reset the phone back to a complete stock configuration
I previously posted in the local Galaxy S3 i747M section with the same problem, but now the issue is worse than before.
Here's my previous thread:
http://forum.xda-developers.com/galaxy-s3-att/help/boot-loop-plugged-to-ac-twrp-wipe-data-t3070064
A note that I'm no stranger to flashing and the inner workings of Android architecture (ROMs and general hardware), . But for the sake of this issue, please feel free to treat me like a noob if you think it would help elaborate any procedures I should follow or troubleshooting steps I should take, or just throw ideas at me like the software dev that I am and expect me to figure it out on my own.
Some background:
Recently (around beginning of April), my phone began to exhibit strange behaviour - reboots when reading/writing from internal memory (not uSD card), unable to wipe /data partition in TWRP or CWM. I would also get bootloops when I was plugged into direct AC charging (no problems if plugged into a computer for charging, though).
When in TWRP, CWM, and Philz, I would not be able to wipe the /data partition or anything in it. Installing anything to /system also caused a crash (though wiping it didn't cause any issues). Doing a factory reset wipe would also cause the recovery to "crash" - the recovery would freeze up and the phone would reboot. I could not restore a NANdroid, I could not install a new custom ROM. In TWRP, if I opened up a terminal window and manually tried to repair the /data and /system partitions with the e2fsck command, it would still freeze up and crash.
At that point, I downloaded the stock 4.4 firmware image (I think it was NF2?) from Sam Mobile and flashed it via Download Mode + Odin. Booted it up and ran the phone stock for probably a week. Then, I carefully used Odin to flash a freshly downloaded (and MD5 verified) TWRP 2.8.6.0 TAR image and SuperSU. Flashed both via Odin just fine. From there, I mounted the microSD card - I didn't want to touch the internal memory for now - and copied over a fresh downloaded copy of a CM12 based ROM (also MD5 verf'd) to it. From there, still in TWRP, I successfully flashed a 4.4.x TouchWiz-based ROM.
Take note that at this point, doing anything to attempt to wipe /data still leads to crashing the recovery. Nothing I have done has resolved this issue. I left that issue alone, just happy to have a working phone.
That above procedure seemed to work. I could then use the phone for about 2 weeks. Then my phone started crashing again, same as before: only when I was doing something that was reading/writing the internal memory. E.g. music, podcasts, etc.
I followed the same procedure with Odin + stock firmware > reboot > Odin + TWRP + SuperSU > flash custom ROM. Worked fine again for 2 more weeks.
Here I am 1 month later, same problem as the last 2 times. This time, however, after flashing the custom ROM, it does not boot up now. My phone is at home because I cannot use it. Last night, upon trying to boot up S3rx and PAC 5.1, I literally let it sit at the boot animation for 1 hour, each, and neither got past the boot animation. I'm familiar with ROMs sometimes taking say 10 minutes upon very first boot on a clean flash, but I gave up after about 1 hour (in fact, 1.5 hours for PAC 5.1, which was my second attempt last night). It's to the point where I'm certain if I left my phone plugged into the AC, it would still be at the boot animation over 12 hours later.
I know of the NAND memory corruption issue that S3's had previously, and I did flash the stock firmware that came out at the time (I think it was an Lxx based bootloader+firmware). But that was years ago, end of 2012 if memory serves me correct.
Thoughts on what I am facing? What I should try and do next? Where to go from here? If this is a hardware issue that is beyond fixing with flashing things in fastboot/ADB/Odin, then I'll face defeat and look for a new phone. But if I can hang on to this phone for just a little bit longer...
Thanks!
Hi there
Please note the following sticky from the top of the Assist section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
As a senior member on XDA, I am quite confident that you know where your device section is (you already asked something there) and where to ask for help.
Thanks for understanding
Good luck
Good day.
I got a Nexus 5 D820 from my mom who dropped it in the river about a year ago at which time the phone was dead. It had indication of power but would not turn on. It was in a drawer powered off until yesterday.
I was able to power the phone on although it would not boot. The Google logo appeared and the android loading animation, but it would always reboot or freeze at different points. From the bootloader the phone seemed stable and I never had an issue pushing/flashing files. At this point I flashed a few different recovery images for the device, but only Philz would work, while TWRP and CWM would only freeze or bootloop.
From Philz I was able to flash a few different ROMS including the latest official one from google and also a few custom roms with/out gapps. None of these would boot and had the same freeze/bootloop at the google logo or android animation with no consistency.
I figured at this point possibly the sdcard had become corrupted/damaged by the water since I was able to flash pretty much anything I wanted. This is where things went downhill.
I followed a guide to use the partition editor from within an ADB shell. The guide assumed I was formatting an external SD card and suggested deleting all partitions. I did make a backup of the configuration of the partitions just in case but followed the instructions and removed everything. I was concerned what would happen once I rebooted the device at this point so I looked around a bit and it was suggested that flashing a google factory image would recreate the missing partitions so I didn't have to do it manually, so I rebooted thinking I could just flash the google package from the bootloader. This was the last time the phone ever showed any indication of working.
Now I have no indication of even power, no LED's, no bootloader.
Please let me know what you think... Thanks.
Before deleting the partitions, did you perform a full factory wipe before or after flashing different ROMs?
Does the phone appear as a device in Windows Device Manager when connected via USB?
If you deleted all of the partitions you deleted the bootloader partition.
EDIT: title is incorrect, model is actually S2109A-F
Hi, I'm pretty novice but have searched a solid 2 days about this topic on this device.
The lenovo a2109a-f I recently got (I know, its like 4-5 years old, but for 40$, not a bad 9+" tablet) was in fine working order, but did have some bloatware. Feeling ballsy, I attempted a root, and now it boot loops, meaning it will constantly reboot and show the animated splash screen, and play the synthetic chime sound. Each loop lasts about 1-2 minutes.
Since I can still access the fastboot and the boot recovery I've tried the following:
1) attempt the install of a new rom (original ICS or JB for this device) from a micro SD card inserted into the slot
- no go, it says it mounts the sd card, but wont read from it
2) attempt factor reset (cache, factory reset etc)
- no change and same root file still shows up in the tablet "/sdcard/"
3) Rerun the flash recovery process
- Tablet seems to accept linux (from windows) commands via cmd (fastboot -i <address/commands go here>), but no change for the boot loop
4) attempted other recovery images in fastboot mode
- thought I actually damaged it more. Since it stopped boot looping but wouldn't even boot to recovery at all. I then flashed the original recovery ("CWM_S2109.img") and was able to get the bootloader back and the bootlooping behavior again.
My question for you all, is there something I need to do via the fastboot method to clear the cache of the bootloader, or the memory of the device and install the bootloader that way and hope it accepts a basic OEM rom? Again, I'm no programmer, but am able to follow instructions and would love to be able to fix my 40$ mistake here sometime. Thanks in advance for all your help. I've used a lot of your tips and resources here over the years and have learned a lot from your skills and experience.