How to recover if G-Tab will not enter recovery... - G Tablet General

I have a G-Tab behaving oddly.... The unit will not enter a recovery mode under any circumstance. I can push images all day long via APX and boot immediately after restore. The problem is when the unit powers back down it automatically enters APX mode and will not reboot. The only way to reboot is to push another image via APX and boot it again.
Anyone have a full factory image I can push to see if it fixes whatever is borked on this thing?

I do need to add that I have some CWM recoveries I pulled off but without being able to boot Clockwork Mod I can't use them that way. Anyone know how to push some Clockwork Mod recovery images manually via APX in the proper format?

cahiatt said:
I do need to add that I have some CWM recoveries I pulled off but without being able to boot Clockwork Mod I can't use them that way. Anyone know how to push some Clockwork Mod recovery images manually via APX in the proper format?
Click to expand...
Click to collapse
Grab the nvflash version of tnt 2.02 from development install nvidia sdk, use the syntax listed in rebeets thread.
When you reboot make sure the tablet. Is plugged in and hold down volume down and press power this puts the tab in apx mode so you can use nvflash
http://forum.tegratab.com/viewtopic.php?f=13&t=21&sid=961900616f4569a5e7b0e37311ee4a39

I was doing that and it was restoring fine. It would even boot normally the first time. If I shut it down or tried to reboot it would not come back on and go into APX automatically.
I just got it restored though. I did another restore. With it back on I pushed the bootloader and recovery via ADB the forced to reboot the recovery via ADB. Am back up and running now.

cahiatt said:
I was doing that and it was restoring fine. It would even boot normally the first time. If I shut it down or tried to reboot it would not come back on and go into APX automatically.
I just got it restored though. I did another restore. With it back on I pushed the bootloader and recovery via ADB the forced to reboot the recovery via ADB. Am back up and running now.
Click to expand...
Click to collapse
Sweet
Glad to hear it

cahiatt said:
I was doing that and it was restoring fine. It would even boot normally the first time. If I shut it down or tried to reboot it would not come back on and go into APX automatically.
I just got it restored though. I did another restore. With it back on I pushed the bootloader and recovery via ADB the forced to reboot the recovery via ADB. Am back up and running now.
Click to expand...
Click to collapse
Hi, I just got my g tab and did the same thing you did and now it is going into APX automatically at boot up. Was wondering if you could help me out on how to use ADB to push the bootloader and recovery and force it to reboot the recovery.
I would really appreciate it.
Thanks.
Thanks to Roebeet I got it out of APX. flashed using his nvflash_gtablet_46 from dropbox and then updated with the stock 3588-update that usually comes up at the top right (after bootup is complete and shows the home screen).

Related

[Q] Unable to boot G-Tab after updating ClockworkMod inside of ROM Manager.

I have a new G-Tab. I was able to install ClockworkMod and update to the latest version of TnT Lite without an issue.
I stupidly installed ROM Manager and allowed it to install the new ClockworkMod Recovery. I realize now that I should not have allowed it to do that, as cwm 0.8 works better than cwm 0.12.
Now, I am unable to boot my tablet, specifically every time I shut the tablet off it goes into APX mode.
I have installed the APX drivers, the NVidia Tegra SDK, and have used NVflash. Using NVflash I am able to flash back to stock. I have tried using NVflash to flash clockworkmod back to recovery. Despite this, whenever I reboot the tablet, I am right back into APX mode. The only way to get my tablet back to working is to flash back to stock and allow NVflash to boot directly into the stock image. Once I turn off the tablet, I am unable to do anything except run NVflash again to get myself back into stock TnT.
I did not use NVflash with anything other than "nvflash_gtablet_2010110500". I did not use --odmdata. I have tried both Power+Vol(-), Power+Vol(+), Power+both Vols. With any of these methods I am unable to tell any difference in the power state of the tablet. The NVflash batch file is able to reflash the device without issue.
The battery is fully charged and I did not flash without using AC power.
Please excuse my verbosity but I am trying to answer all possible questions and be as specific as possible.
I am unable to boot my GTab after updating ClockworkMod to the newest version through ROM Manager. I have tried every recovery method I have found, and am unable to do anything but boot the stock image. Once I power down the tablet, I am unable to do anything except flash the stock image again. What are your suggestions?
There is an option to install bekit08 from the ROM Manager I think. Down towards the bottom. Once you nvflash into the stock OS have you tried installing ROM manager and letting it reflash the 08 CWM?
Join the limited club
You can nvflash the recovery.img from Bekit, just hold the Volume + when you push enter on your computer's keyboard.
ie...(recovery named bekit.img in this example)
have tablet attached via USB, have tablet in APX mode..
nvflash --bl bootloader.bin --download 9 bekit.img --go
press and hold Volume + on the tablet and immediately press ENTER on the computer to execute the above line.
This will push clockworkmod to the tablet and then boot into recovery. Use recovery to mount USB so you can copy whichever ROM you want to the device....
dismount USB, wipe system (factory reset option in recovery) then install ROM from sdcard.
When completed....and you reboot....of course it won't do anything...
So....while attached and in APX mode...
nvflash --bl bootloader.bin --download 9 bekit.img --go [ENTER]
This reflashes the recovery and boots the tablet.
Voila....VEGAn or TnT-lite installed. Configure, use....never reboot or power off.
If you must power off.....use nvflash to "force boot" the tablet again.
I have to do this on one of mine.
See this post...
http://forum.xda-developers.com/showthread.php?t=903684
muqali said:
There is an option to install bekit08 from the ROM Manager I think. Down towards the bottom. Once you nvflash into the stock OS have you tried installing ROM manager and letting it reflash the 08 CWM?
Click to expand...
Click to collapse
I will try this.
[Edit]
ROM Manager installed, but the only option now is Advent Vega. I understand they are similar but I am not going to try flashing the Advent Vega CM image, especially considering I don't think it will fix the issue. (I have no problem flashing CMW, I can just never get into recovery.) Thank you for the suggestion though!
[Edit #2]
I tried it anyways, despite my reasoning against it. I had options to change to CMW 2.5.1.0, 2.5.1.1, 2.5.1.3, 2.5.1.4 (curiously no 2.5.1.2, which is what caused this all). I was unable to change to these other CMW recoveries, it gave me an error.
tcrews said:
Join the limited club
...
See this post...
http://forum.xda-developers.com/showthread.php?t=903684
Click to expand...
Click to collapse
This is exactly the symptoms I'm experiencing. That's disappointing. I hope the latest two posts or so end up working!
Are you able to boot into the version of CWM that was installed?
My suggestion....if it's within the return period of wherever you purchased.....take it back and swap it out.
NMCBR600 said:
Are you able to boot into the version of CWM that was installed?
Click to expand...
Click to collapse
Nope.
tcrews said:
My suggestion....if it's within the return period of wherever you purchased.....take it back and swap it out.
Click to expand...
Click to collapse
Yessir, these are the words I was expecting to hear. Gonna do that today...
I believe this is easier
I had issues with mine when I first started as well. I found that by using my sd card and renaming the sdcard in the "command" file I was able to recover. I still have issues but I am able to recover. I also still rely heavily on nvflash but I can install crm without forcing it. I am also able to use the power option on the device.
dcom222 original post: http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7

[Q] Apx bootloop after NVflash

I ran nvflash to restore the gtablet to stock.
The flash completed successfully and Tapntap booted, however all my luanchers and old apps were still there. When I reboot the device goes directly into Apx. Powering with power button no volume, vol- or vol+ gives same result. If I repeat the flash It boots into tapntap bet debits into apx. Do I need to do a factory reset here or somthing else. I am going to try a data wipe and factory reset tonight at the first boot. I want to install TNTllite 5.00 a cordinto.the install post can't install clockworkmod but some post seem to indi ate install with clo kwor works Any Help appreciated.
Im having the exact issue any help would be greatly apreciated. I flashed to stock and all went well but when i power off it gets stuck in apx mode.. The only way I even know it's on is because when I plug the usb into the comp I get the connected notification. PLEASE HELP
Just a complete guess but did you check to see if the vol - was stuck?
Gentlemen:
When I nvflashed both of my tablets, it went through the process -- then it rebooted and started up the version being loaded right up to the main screen all by itself.
I never had to do a thing after starting the .bat file to flash except watch.
I don't know how this will help, but maybe it will stimulated and idea!!
Rev
Thanks to Roebeet I have a working gtablet again! The newer belkit img in his dropbox caused the APX bootloop, I dont know why. As instructed I used the older img and that worked. Did a factory reset and now have a clean install, ready for TNTlite 5.01!
got mine working last night had to use nvflash_gtablet_46 and nvflash_windows_20100500.zip instead of the nvflash_gtablet_2010110500.zip and it worked great for some reason that nvflash_gtablet_2010110500.zip would make my tab get stuck in a bootloop stuck in apx mode!!! Hope this helps it worked for me!
Can you guys please help me? i am in a similar issue. I tried using the 3588 stock .zip to get ready to install tnt 5/ ttx.9 and well it started to boot loop so to NVflash i went. I have tried
nvflash_gtablet_46 and nvflash_windows_20100500.zip and nvflash_gtablet_2010110500.zip and gtab.spx.stock.3588.zip and NONE of them work for me. I am able to sucessfully NVflash them but when the tablet restarts it goes to the tapntap screen the flashes back and forth between that screen and a black blank screen before it goes completely black... The tablet remains on though just with a blank screen and i must hold the power button for 10 seconds to power it off. i have tried every combination of flashing i can think of but no dice.. please help?
ddarvish said:
Can you guys please help me? i am in a similar issue. I tried using the 3588 stock .zip to get ready to install tnt 5/ ttx.9 and well it started to boot loop so to NVflash i went. I have tried
nvflash_gtablet_46 and nvflash_windows_20100500.zip and nvflash_gtablet_2010110500.zip and gtab.spx.stock.3588.zip and NONE of them work for me. I am able to sucessfully NVflash them but when the tablet restarts it goes to the tapntap screen the flashes back and forth between that screen and a black blank screen before it goes completely black... The tablet remains on though just with a blank screen and i must hold the power button for 10 seconds to power it off. i have tried every combination of flashing i can think of but no dice.. please help?
Click to expand...
Click to collapse
You might need a data wipe - if you can get past the birds but get stuck at some point after the "GTablet" screen, a data wipe would be my first suggestion.
The problem is that 1105 bekit nvflash (and mine) doesn't have clockworkmod embedded in it to fix that. But, as a workaround, you can replace "part9.img" in the bekit 1105 with clockworkmod's "recovery.img" (just rename part9.img to part9.img.org and then rename recovery.img to part9.img). Redo the nvflash, the reboot into recovery when you are stuck again and wipe data. Once "fixed", then you can undo the change and reflash one more time to get back to full stock, or OTA update to 3588 to get 3588 stock.
I know this is a bit of a PITN due to all the steps, but it does work.
robeet u are absolutely correct and i posted that as my solution in the other thread i started. It finally occured to me when i was reading and there was a line that said NVflash will keep ur /data untouched. I was like OH ****.. hah. I though NVFlash wiped EVERYTHING!!!. Anyway replacing the .img with CWM.img and then wiping and then redoing the 3588 apx update worked.
Please help, can't get win7 to detect the device. When u say usb, is it mini usb on your device or is it full size usb? I was be able to run TNTL 5.0, due to afew crashes, i decide to revert back to 4.2. Since then, my viewsonic g tablet never boot again.
Thanks in advance.
khem1288,
Look at the following thread on USB for nvflashing.
http://forum.xda-developers.com/showthread.php?t=989320
There also are a couple of "Windows" nvflash links in the middle of roebeet's TwoTapX thread.
Rev
butchconner said:
khem1288,
Look at the following thread on USB for nvflashing.
http://forum.xda-developers.com/showthread.php?t=989320
There also are a couple of "Windows" nvflash links in the middle of roebeet's TwoTapX thread.
Rev
Click to expand...
Click to collapse
Thank you for your response,
Got mine to work, just want to clarify for those who use win7x64. download three files from thread... nvflash_win, nvflash_gtablet, and usb driver. Turn on device in APX mod, plug in ur tablet via mini usb. Go to windows device manager, making sure it sees APX has proper driver. Go back to nvflash folder and double click on nvflash_gtablet.bat, and relax. Once it's done flash, reboot and enjoy.
thank you all for your hard work.
roebeet said:
You might need a data wipe - if you can get past the birds but get stuck at some point after the "GTablet" screen, a data wipe would be my first suggestion.
The problem is that 1105 bekit nvflash (and mine) doesn't have clockworkmod embedded in it to fix that. But, as a workaround, you can replace "part9.img" in the bekit 1105 with clockworkmod's "recovery.img" (just rename part9.img to part9.img.org and then rename recovery.img to part9.img). Redo the nvflash, the reboot into recovery when you are stuck again and wipe data. Once "fixed", then you can undo the change and reflash one more time to get back to full stock, or OTA update to 3588 to get 3588 stock.
I know this is a bit of a PITN due to all the steps, but it does work.
Click to expand...
Click to collapse
Thanks a lot Roebeet. Saved my life too! I formatted the tablet with the format tool that is supposed to erase the BCT and then did an NVflash for the rest and was stuck in a bootloop. Tried both the 1105 and the other bekit, and ended up renaming part9.img, getting CWM to wipe data and working from there. It's TnTlite 4.4 from here on out. Thanks again.
roebeet said:
You might need a data wipe - if you can get past the birds but get stuck at some point after the "GTablet" screen, a data wipe would be my first suggestion.
The problem is that 1105 bekit nvflash (and mine) doesn't have clockworkmod embedded in it to fix that. But, as a workaround, you can replace "part9.img" in the bekit 1105 with clockworkmod's "recovery.img" (just rename part9.img to part9.img.org and then rename recovery.img to part9.img). Redo the nvflash, the reboot into recovery when you are stuck again and wipe data. Once "fixed", then you can undo the change and reflash one more time to get back to full stock, or OTA update to 3588 to get 3588 stock.
I know this is a bit of a PITN due to all the steps, but it does work.
Click to expand...
Click to collapse
so after you re-nvflash with cwm as partition 9, how do you get into cwm? after i flash to the stock ROM, i can't get to anything other than apx on shutdown/reboot.
williec30 said:
so after you re-nvflash with cwm as partition 9, how do you get into cwm? after i flash to the stock ROM, i can't get to anything other than apx on shutdown/reboot.
Click to expand...
Click to collapse
You restart while holding down the Volume Up key. If it doesn't appear to be shutting down properly then hold down the power key for 30 - 45 seconds and try it again.
K J Rad said:
You restart while holding down the Volume Up key. If it doesn't appear to be shutting down properly then hold down the power key for 30 - 45 seconds and try it again.
Click to expand...
Click to collapse
it's doesn't do anything but boot into APX mode... holding power and volume up doesn't do anything other than enter / exit that mode. that is, unless i'm missing something else...
The only thing I can recommend is to try the nvflash again. Make sure you're using bekit's 1105 image and you're following the instructions on this thread...
http://forum.xda-developers.com/showthread.php?t=861950
It does work.
K J Rad said:
The only thing I can recommend is to try the nvflash again. Make sure you're using bekit's 1105 image and you're following the instructions on this thread...
http://forum.xda-developers.com/showthread.php?t=861950
It does work.
Click to expand...
Click to collapse
the first post doesn't talk about *how* to execute the CWM install, only the nvflash. other posts in the thread talk about the CWM piece, but there is no step by step to get out of APX and into clockwork... that's what i need because something in my config is definitely out of whack.
If your nvflash worked then there is no need for a step by step other than what has been said.
1) Make sure you are using befit's 1105 image
2) Make sure you are using ClockworkMod .8
3) Make sure you've modified the gtablet.cfg file properly.
4) Make sure you didn't get any errors reported from your nvflash.
5) When it is done it should reboot.
If it boots normally, then do a factory reset from within the system settings. Then reboot while holding the volume up key and you should get CWM.
If it doesn't then try to shut it down and restart while holding the volume up key and you should get CWM.
If you're still stuck in an APX loop then I would try nvflashing just the bekit 1105. If that will boot at all you can try to load CWM from an SD card.
If you'd like to post or PM your config file, the result from your nvflash and any other files you've changed I'll be happy to look at them.
Same situation here.... tried everything that was mention but still not working.
As soon I turned on, goes a black screen (apx mode) that's it!!! Power and vol + don't do anything. the only way to boot completely is nvflashing again.... tried to reset data factory but as soon the tablet turn off (restart turn on) black screen.
Can anybody help me.... it has been 12 days already.... I had posted for help before and I already did everything that was suggested..... I don't know what to do anymore.
PLEASE HELP!!!!

Bricked

My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? I CAN get into APX mode.
Yes, wiping the data will brick your device if you don't have a working recovery.
sparky28000 said:
Yes, wiping the data will brick your device if you don't have a working recovery.
Click to expand...
Click to collapse
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
jrfaulkin said:
Actually, I just discovered that I do have access to APX. Is there a way to push a working recovery through APX?
Click to expand...
Click to collapse
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
jeroen.wit said:
I did exactly the same thing.
I have exact same problem.
Tried it via APX mode via NVflash but no luck so far.:crying:
need the correct SBK version.
SBKv1 and SBKv2 doesn't work for the TF300t.
I send my tf300t for repair.
Lets hope that they can fix my TF300t.
Click to expand...
Click to collapse
Unfortunately, APX and nvflash is not available for the TF300T currently. As I understand it, you're required to record some information and your Secure Boot Keys (SBK) prior to bricking to be able to access APX. Otherwise, your only recourse is to contact Asus and start the RMA process.
I'm recording my developments over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=2 (my post is at the bottom)
I think I'm going to hold out until someone figures out the NvFlash process as described here:
http://androidroot.mobi/technical/tf-secure-boot-key/
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
gypsyshaw said:
I had the same issue. wiped my data after the JB update as my device froze halfway through the update, so I forced a reboot and it hang at the Asus screen, so not thinking I wiped data to go do a fresh update... I wiped the update and all my data/system/recovery.
I found that in the boot loader screen (Wipe Data, Fastboot, ETC....) I was able to navigate to fastboot select it and then it would hang from there. - my computer wouldnt recognize it either however, i tried flashing a copy of TWRP anyway while in my hanging fastboot just to see what happened.
It didnt work first few times but it did eventually flash. so I had a recovery to work with. via a MicroSD put a fresh copy of the JB update on it and re-flash through the recovery via External SD Card.
It did remove my root access, TWRP and all the data on my device after flashing the JB update but it "un-bricked" me and got me booted again.
Don't know if I was just lucky or if it will work for you.
Click to expand...
Click to collapse
The difference in your situation is that you were able to access the boot loader. My boot loader is wiped. I don't get the option to select Wipe Data/Fastboot, etc. I'm stuck in a mode where I think the only option is to low-level flash the bootloader after re-initializing all of the partitions.
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.

Is my Xoom bricked?

Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.
Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again
Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?
^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.
but, how can I overwrite it? it seems like they are read only...
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:
No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.

[Q][SOLVED] Help!

[Q] Help!
Okay. So i just rooted my phone yesterday and i flashed a ROM. Well I forgot to backup all my apps and such. So I went back into CWM and I cleared data and flashed my nandroid recovery file. That completed successfully, so I push restart system at the top. Well now it is just stuck in the boot screen and won't do anything. How do I fix this! HELP!
atech087 said:
Okay. So i just rooted my phone yesterday and i flashed a ROM. Well I forgot to backup all my apps and such. So I went back into CWM and I cleared data and flashed my nandroid recovery file. That completed successfully, so I push restart system at the top. Well now it is just stuck in the boot screen and won't do anything. How do I fix this! HELP!
Click to expand...
Click to collapse
I can't get into CWM either. It just keeps rebooting and getting stuck on the boot screen.
For getting back to CWM, pull the battery (USB unplugged) so it turns off fully, put the battery back in, hold the volume up and down both on the left, and turn it on (hold power until you see something, let go of power but keep holding the volume keys). Once you see CWM come on, you can let go of the volume keys.
You flashed what from what? If what you flashed isn't the same major OS version, the nandroid backup is probably only going to be helpful through Titanium Backup or some other program since you won't be able to flash it successfully.
Theraze said:
For getting back to CWM, pull the battery (USB unplugged) so it turns off fully, put the battery back in, hold the volume up and down both on the left, and turn it on (hold power until you see something, let go of power but keep holding the volume keys). Once you see CWM come on, you can let go of the volume keys.
You flashed what from what? If what you flashed isn't the same major OS version, the nandroid backup is probably only going to be helpful through Titanium Backup or some other program since you won't be able to flash it successfully.
Click to expand...
Click to collapse
Ok so I tried to get back into CWM and it was unsuccessful. It just gets stuck on the boot screen still. I flashed my 2.3.6 stock rooted nandroid backup from this custom rom: http://forum.xda-developers.com/showthread.php?t=1404863 . I can still get to recovery mode just not CWM. Any ideas?
Okay... recovery mode but not CWM... what does that mean?
CWM IS recovery mode. Are you trying to get into download mode instead? For that, battery pull, battery in, plug in USB to computer, hold volume... up (I think), turn on (power button until the screen lights up), let go of power, should be in download mode.
Theraze said:
Okay... recovery mode but not CWM... what does that mean?
CWM IS recovery mode. Are you trying to get into download mode instead? For that, battery pull, battery in, plug in USB to computer, hold volume... up (I think), turn on (power button until the screen lights up), let go of power, should be in download mode.
Click to expand...
Click to collapse
Yeah.. I meant i couldn't get into recovery mode but I can get into download mode. Do you think this would get my phone working again? http://forum.xda-developers.com/showthread.php?t=1358498
Working as a phone, yes. If you can get into download mode, you should be able to flash stuff. If you flashed from Froyo to GB-custom, use the one-click twice... first to get the basic ROM over, then tell it to do bootloaders as well. If you flashed from GB to GB-custom, then you only need to flash once.
I'd suggest using the second link, BWaT+stock. Basically, from here:
http://forum.xda-developers.com/showthread.php?t=1822626
If you have any problems, make sure you're following the guide fully:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
After you get it booting up with root, you can extract apps from the nandroid using Titanium Backup or something else similar.
Theraze said:
Working as a phone, yes. If you can get into download mode, you should be able to flash stuff. If you flashed from Froyo to GB-custom, use the one-click twice... first to get the basic ROM over, then tell it to do bootloaders as well. If you flashed from GB to GB-custom, then you only need to flash once.
I'd suggest using the second link, BWaT+stock. Basically, from here:
http://forum.xda-developers.com/showthread.php?t=1822626
If you have any problems, make sure you're following the guide fully:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
After you get it booting up with root, you can extract apps from the nandroid using Titanium Backup or something else similar.
Click to expand...
Click to collapse
Thanks. I used http://forum.xda-developers.com/showthread.php?t=1358498 this and am just going to reboot and everything all over again using this guide http://forum.xda-developers.com/showthread.php?t=1470716 and hope I don't have this problem again. Thanks for your help!!!!!

Categories

Resources