I was happily running CM7 7.0.2 when I decided to load up .3.
it bootlooped. I tried all kinds of stuff within bootloader...factory reset, cache wipe, delv cache wipe...nothing...then I repartitioned my card and I was screwed.
So I tried nvflash FULL restore, using bekit's original image
This seemed to run...but when the puffins came up...it still bootlooped.
and I lost recovery....it's now just a triangle with an exclamation point for 2 seconds then the puffin bootloop again.
i tried Flashing UPDATE.ZIP the old fashioned way
exclamation point for 2 seconds then the puffin bootloop
I am really at a loss here...not sure what I can do.
Any ideas?
Update....I used NVFlash CWM to get recovery back
when I tried to do a data/factory reset I get this:
e: Can't mount /dev/block/mmcblk3p2
(Invalid Argument)
Error mounting /data/
looks bad
Update2 : OK I tried to load an image.zip file from CWM....after three boot loops I'm stuck on the g-tablet tab.
tried to get back into recovery....didn't go...got some sort of cardboard box....now I'm stuck in g-tablet screen again.
Update 3 : the cardboard box was from "update the old fashion way"....so I followed the instructions and got the image.zip to load up again.....but I'm still stuck on g-tablet.
1) nvflash bekit's 1105 with CWM in place of part9.
2) Repartition 2048 and 0
3) Wipe everything
Then you should be ready to flash a new ROM.
First of all....thanks for your efforts.. however.....
No joy....I did just what you suggested....nvflash...part9
was able to get into CWR
wiped.
installed 3588...seemed to go ok, but now I'm just looking at a g-tablet logo for 10 minutes now....no bootloop at all...
When I tried to clear Delvic cache I got :
e: Can't mount /dev/block/mmcblk3p2
Invalid argument
I get the same error when I try to mount data....
Is my SD Card screwed up somehow? I repartitioned per your instructions.
Try it again but before doing step three nvflash back to bekit's 1105 and leave the stock recovery in then upgrade to 3588 (I prefer manually upgrading but OTA should work also).
K J Rad said:
Try it again but before doing step three nvflash back to bekit's 1105 and leave the stock recovery in then upgrade to 3588 (I prefer manually upgrading but OTA should work also).
Click to expand...
Click to collapse
I'll try it tonight. Thanks so much for your help...I'm getting a little worried.
sudermatt said:
I'll try it tonight. Thanks so much for your help...I'm getting a little worried.
Click to expand...
Click to collapse
Also try (Can't find the exact post) the utility that does a quick deletion/format for your GTAB. THEN try popping in a NVFLASH. Should shake out all the bad demons.
Have you re-downloaded the nvflash image in case the one you have is corrupted? Also another good starting point there.
UPDATE: Post for erasing/formatting your Gtab.
http://forum.xda-developers.com/showthread.php?t=974422
Related
I have no idea what went wrong, this morning I tried turning my gtablet on and suddenly it went into a boot loop!! I have no idea what I did with it except turn it on this morning. I kept seeing the same TnT Lite boot animation over and over again. All day I have been trying to get it out of the loop, but nothing has worked, I tried what Roebeet posted in that huge thread on his firmware, didnt work, went to try the droidpirate method and it brought me back to the Stock TnT boot animation, however, its looped there now too! Im running on TnT Lite 3.1.3, and Im really scared, someone please help!!!! :O
If there is anything, any of you can do for me i would be greatly appreciative!!! Thank you
I don't know what method droidpirate suggested but.
Install Clockwork recovery from here
http://forum.xda-developers.com/showthread.php?t=865245
clockwork 0.8 not the one from the market
Read this if your confused about installing
http://forum.xda-developers.com/showthread.php?t=892090
Boot into clockwork recovery using Power/Vol+
Go to the advance menu in clockwork and repartition your sdcard to 2048 and 0
If you boot using Power/vol+ and you don't get clockwork recovery then it is not installed. Check your recovery/command file and make sure its there and is pointing to the right sdcard
Thank you so much! All is well, now just to restore all my apps and stuff... but thank you!! It worked exceptionally
thebadfrog said:
I don't know what method droidpirate suggested but.
Install Clockwork recovery from here
http://forum.xda-developers.com/showthread.php?t=865245
clockwork 0.8 not the one from the market
Read this if your confused about installing
http://forum.xda-developers.com/showthread.php?t=892090
Boot into clockwork recovery using Power/Vol+
Go to the advance menu in clockwork and repartition your sdcard to 2048 and 0
If you boot using Power/vol+ and you don't get clockwork recovery then it is not installed. Check your recovery/command file and make sure its there and is pointing to the right sdcard
Click to expand...
Click to collapse
I am having the same problem. I have tried formating, and clearing cache, also tried factory restore. Still no luck. Just get flashing TNT screen, and then blank screen. Anything you can offer would be great.
**Update: I used the NVFlash process and that worked.
Hey,
I have had the same problem with my Samsung Galaxy SL-i9003 , Every morning when i wake up i founds the phone gets into boot loop and after removing the battery and starting it again all the data losts.
The solution i have got from Samsung Service Center is that they have changed PBA(Mother Board) of the phone as well as the Sim tray.
So, I've been running GummyCharged FE 1.9.1 with voodoo lagfix enabled for the past few months and the phone has been awesome. Two days ago, however, the phone went into a boot loop. I was listening to sirius on it when it locked up, restarted itself, then would lock up again when loading the homescreen widgets. This progressively got worse until it got down to a boot loop at the Samsung screen. I booted to CWM Recovery to try a wipe but it couldn't mount most of the partitions. So, I tried to reflash GCFE 1.9.1, which failed.
I worked on it for the better part of yesterday, trying everything I could find. I tried flashing stock ED1, ED2, EE4, in both Odin and PST, with and without repartitioning with the PIT file, trying different usb cables and ports, battery in, out, and they all fail when they get to the movinand.bin file. I also replaced the SD card as a last resort, but no dice.
The only thing I CAN get to successfully flash is a build of GCFE 1.9 that didn't have movinand.bin and a few other files in it.
After all that, here is the current state my phone is in:
-It boots directly (after Samsung logo) to CWM Voodoo Lagfix Recovery v4.0.0.8 without holding down any of the recovery mode keys.
-I was able to get the lagfix disabled by creating the disable-lagfix file on my sd card (or at least, it went through the process with the voice without any errors & voodoo recovery shows it disabled)
-CWM recovery gives an error when trying to mount /cache, /data, and /sdcard
Does anyone have any ideas on this?
Are you leaving the battery in when you flash?
Sent from my Droid Charge running Infinity Beta
Yep...battery out to connect to computer, then I pop it in once its in download mode.
can you flash a recovery? try flashing the newer 8/17 orange 4.0.1.4 version, I believe that's the one that will allow you to mount partitions correctly
Ok, I got CWM recovery 4.0.1.4 flashed. I still can only mount the /datadata and /system partitions, BUT when I rebooted from CWM, it booted all the way up to the Droid eye, then looped there for a while. (didn't fully reboot, just went back to where DROID flashes on the screen, then the eye is shown). I let it go a few times and it showed the status bar at the top of the screen, but the rest was black.
enf108 said:
Ok, I got CWM recovery 4.0.1.4 flashed. I still can only mount the /datadata and /system partitions, BUT when I rebooted from CWM, it booted all the way up to the Droid eye, then looped there for a while. (didn't fully reboot, just went back to where DROID flashes on the screen, then the eye is shown). I let it go a few times and it showed the status bar at the top of the screen, but the rest was black.
Click to expand...
Click to collapse
sounds like progress.. does anything flash? like Gummy GBE 2.0 final for example, only because I know that rom is one you can flash over anything
blazing through on my 4G Droid Charge
Is there an odin file available for GBE 2.0? I looked for a while and couldn't find one, and I can't do a CWM flash since it won't mount the sd card.
I tried flashing stock EP1W and ED1 again, and even tried it from another computer, but both failed at movinand.bin. I can mount /cache now, though, so something's happening.
enf108 said:
Is there an odin file available for GBE 2.0? I looked for a while and couldn't find one, and I can't do a CWM flash since it won't mount the sd card.
I tried flashing stock EP1W and ED1 again, and even tried it from another computer, but both failed at movinand.bin. I can mount /cache now, though, so something's happening.
Click to expand...
Click to collapse
Nope. It is only available as a CWM.
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to restore my phone. After trying different tars and making tar with nandroid images I found a tar file of {EI20} 2.3.5. I tried it an it boot up well. I install a voodoo CWM and let me restore! Though the phone is not activated on the cdma network, at least its on factory state with the own carrier's software. Its only a matter of them activating the phone back.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
lilizblack said:
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
Click to expand...
Click to collapse
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
I already tried it and get the invalid argument error. no boot image and straight to recovery
lilizblack said:
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
Click to expand...
Click to collapse
When you flash the verizon odin tar file, are you using an .pit file, and checking repartition? This will get you converted back to BML. The tar file must be a full flash for the repartition to work.
So I am probably breaking a rule but you need help go over to www.rootwiki.com . Go to there forums and look there they have a bunch of people over there developing for the showcase.
Sent from my SCH-I500 using Xparent Blue Tapatalk 2
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
MidniteKitten said:
I waited 2 nights to register so I could wade through fixes and tips and have seem to come up with little to nothing. I have CWM flashed on my phone through ROM Manager with the recovery file replaced in the system/bin and the update zip in the root of the SD card.
When I access CWM and click on Wipe Data/Factory reset it breezes through the first few steps pretty quickly and then gives me this error:
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
It continues past this and then goes on to "formatting sd_card" and then just freezes. I left it on for 30mins and there was absolutely no progress. I've tried battery pulls and re-attempting the wipe with the same result. Have re-flashed CWM, ODIN'ed back to stock, etc etc and still run into the same snag. I'm beyond frustrated because since it never gets past this part I can't install the custom ROM I'm eying and it wipes enough data to have to ODIN every single time and re-root all over again. Just to be clear this error is NOT popping up on bootup but only during Data Wipe/Factory Reset and the only way out of the freeze is to do a battery pull which results in a soft brick.
If it helps any here is what I did prior to ever having run into this problem.
Rooted with SuperOneClick V.2.3.3
Installed ROM Manager
Installed RootBrowser Lite
Downloaded recovery and update zip
Placed both into root of SD card
Used RootBrowser Lite to move recovery file into system/bin
Booted into recovery mode
Attempted to Wipe Data/Factory Reset
Ran into snag on first try and every try thereafter
Can someone please tell me what I'm doing wrong, how to fix it or a workaround?
If possible a very detailed walk through would be appreciated as this is my first ROM flashing. Your help is greatly appreciated!
Click to expand...
Click to collapse
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
No, actually, I didn't. I haven't seen a guide point it out or a video that went through this step. Lemme' give this a shot and see if that helps with the problem I'm running into Thanks for the quick response, hoping this is what I was missing!
azcledel said:
Did you hit apply update.zip after booting into recovery the first time I don't see that listed in your steps
Sent from my Team Nightmare Amaze4G with Sense 4.0
Click to expand...
Click to collapse
Unfortunately this didn't seem to fix my problem. Still encountering:
E:format_volume: make_ext4fs failed on /dev/block/mmblk0p2
Formatting /sdcard/ .android_secure...
And frozen again -_- It's bad enough that the sidekick sucks as stock (took me this long to finally want to do something about it) and that it's being difficult and resisting change.
Hmmm was your phone stock before you did anything to it? Or did you get the phone used or something?
My advice would be Odin to stock and start over try redownloading the recovery.zip to make sure it wasn't a bad download. And try again go slow and tripple check to make sure your following the instructions word for word. I've messed them up a few times cuz I got cocky but I got everything down from doing it so much and checking my work. The first time I rooted my sk4g I did it with adb not superoneclick and it was my first android phone it took me 2 hours of reading and following steps perfectly.
Sent from my Team Nightmare Amaze4G with Sense 4.0
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
ultraprimeomega said:
go back to stock with odin,
Then root http://forum.xda-developers.com/showthread.php?t=1100513
Flash cwm http://forum.xda-developers.com/showthread.php?t=1124453
And them flash this kernel http://forum.xda-developers.com/showthread.php?t=1663622 (dont freak out with the first boot with this kernel let it convert the partitions to ext4 and a loud voice will tell you what is going on)
Ive had that problem from flashing recovery from rom manager, and when it comes up i just return to stock. try to save and remove the update.zip from the sd card and see if you can get into recovery again and just flash the kernel(if cwm come up)
Click to expand...
Click to collapse
You are my saviour! I seriously love you! This worked PERFECTLY! I'm now running Glorious Overdos v3.3 and loving every single second of it. Because of you my phone is no longer a nightmare. You deserve a thanks
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?