[UTILITY] G-Tablet Format - G Tablet Android Development

This fully erases the ROM but this will NOT affect the internal SD card
You MUST be able to use nvflash to restore the stock firmware.​
You must have already installed nvflash on your computer/have the APX driver
This will completely erase all traces of anything in the G-Tablet's ROM storage space - except the BCT - and user data (use CWM to erase userdata)
Many people with HTC Windows Mobile phones can think of this as a task 29 for the G-Tablet
After doing this, you must nvflash the stock ROM back on to your tablet by following the instructions here: nvflash restore

You may wanna explain what this is a little more fully before you get a ton of posts like " This rom screwed up my tablet completely, how do I fix it"
Just a suggestion

thebadfrog said:
You may wanna explain what this is a little more fully before you get a ton of posts like " This rom screwed up my tablet completely, how do I fix it"
Just a suggestion
Click to expand...
Click to collapse
Added a line I forgot to add.

So this is a "detox" program for our gtablet that we can choose to run prior to NVflash process.
And this process should not be done unless absolutely necessary, right?

xmr405o said:
So this is a "detox" program for our gtablet that we can choose to run prior to NVflash process.
And this process should not be done unless absolutely necessary, right?
Click to expand...
Click to collapse
Yes, exactly. I just felt that I shouldn't keep this to myself.

rr5678 said:
Yes, exactly. I just felt that I shouldn't keep this to myself.
Click to expand...
Click to collapse
Thanks! I would warn people though. Maybe a little disclaimer for yourself.

Very nice. If I ever need to use nvflash (and I absolutely pray I don't) I'll now at least feel better knowing that I'm starting with a clean slate.

Good to know that this tool is available.
You never know when you will need to push the jolly, candy like, history eraser button.
Sent from my Chromatic Magic using XDA Premium App

xmr405o said:
So this is a "detox" program for our gtablet that we can choose to run prior to NVflash process.
And this process should not be done unless absolutely necessary, right?
Click to expand...
Click to collapse
rr5678 said:
Yes, exactly. I just felt that I shouldn't keep this to myself.
Click to expand...
Click to collapse
In addition, if you're selling your G-Tablet, you may want to do this for that extra sense of security, knowing that nobody will have your Google account/password.

My G-Tablet is stuck on a black screen. I can't even tell if I'm stuck booting or if I'm in a ROM. Let the battery go dead overnight. Still can't boot. I was going to dive into the hardware and do a hard reset. But getting into the case is a pain!!!
I was wondering to use nvflash how booted up do I have to be?
Sent from my Droid using Tapatalk

jbirdvegas said:
My G-Tablet is stuck on a black screen. I can't even tell if I'm stuck booting or if I'm in a ROM. Let the battery go dead overnight. Still can't boot. I was going to dive into the hardware and do a hard reset. But getting into the case is a pain!!!
I was wondering to use nvflash how booted up do I have to be?
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
Did you try plugging it into your PC and see if the computer recognizes the tablet? It may even be in APX mode (the mode for nvflash)

I get errors after performing the format, something about a "mismatch" and something about "kernel". The errors are in red font as opposed to the white font. Is there something im doing wrong or is this common, but I doubt it. Anyways after those errors I have to reenter apx mode and I flash nvflash BUT...after successfully restoring it to factory I get into a boot loop at the tap n tap logo crap. Any suggestions? Thanks for the help!
Sent from my HTC Glacier using XDA App

ACis0014 said:
I get errors after performing the format, something about a "mismatch" and something about "kernel". The errors are in red font as opposed to the white font. Is there something im doing wrong or is this common, but I doubt it. Anyways after those errors I have to reenter apx mode and I flash nvflash BUT...after successfully restoring it to factory I get into a boot loop at the tap n tap logo crap. Any suggestions? Thanks for the help!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yes. The mismatch thing is normal. Remember, there is completely no data after you run the format tool. After that, just flash stock. But since it seems that your data partition is unmountable, use nvflash to install ClockworkMod, and while in ClockworkMod, repartition the internal SD card. The options to choose are 2048 and 0

rr5678 said:
Yes. The mismatch thing is normal. Remember, there is completely no data after you run the format tool. After that, just flash stock. But since it seems that your data partition is unmountable, use nvflash to install ClockworkMod, and while in ClockworkMod, repartition the internal SD card. The options to choose are 2048 and 0
Click to expand...
Click to collapse
Thanks for the reply! How would I get around to do that? Do you mean flash cwm through adb?
Sent from my HTC Glacier using XDA App
EDIT: Nvm got it. Turns out you just have to DL cwm 0.8 and replace part9.img with whatever you call your DL of cwm. tHEN just flash stock + YOUR NEW RECOVERY (cwm 0.8) using nvflash

rr5678 said:
Did you try plugging it into your PC and see if the computer recognizes the tablet? It may even be in APX mode (the mode for nvflash)
Click to expand...
Click to collapse
No dice. Computer won't recognize and can't boot into bootloader or custom recovery. Power up just shows blank black screen no kernel logo or boot animation just black. Truely stumped
Sent from my Droid using Tapatalk

rr5678 said:
Yes. The mismatch thing is normal. Remember, there is completely no data after you run the format tool. After that, just flash stock. But since it seems that your data partition is unmountable, use nvflash to install ClockworkMod, and while in ClockworkMod, repartition the internal SD card. The options to choose are 2048 and 0
Click to expand...
Click to collapse
Thanks brother. Got it after a little looking around. Turns out it's pretty darn easy lol

jbirdvegas said:
No dice. Computer won't recognize and can't boot into bootloader or custom recovery. Power up just shows blank black screen no kernel logo or boot animation just black. Truely stumped
Sent from my Droid using Tapatalk
Click to expand...
Click to collapse
You may have to do this
buzzzard said:
If you have managed to find yourself in a situation where APX will not work due to a mangled bootloader, and your battery is dead as well, you can follow the instructions in this guide.
So here are the steps needed to get to a charging state:
1. Disassemble the tablet. Remove the four rubber stoppers on the bottom of the tablet (put them aside). Next, unscrew the screws under them (keep those too). Next we need to get the back half of the tablet off. Put the tablet face down on a piece of paper or another protective material. Gently work one corner of the tablet until the two halves are slightly separated, then use something thin like a business card to keep them slightly parted. You can then use something thin and strong, like a plastic gift card to zip around the edges and break the seal. Prying will only damage your plastics.
2. Disconnect the battery lead (a flat connector with multicolored wires, probably held down with tape. Look near the battery.)
3. Connect the device via USB.
4. Short (connect) the four contacts circled in the photo. (A smallish square of tinfoil works well for this. Be careful.)
5. Press the power button for 2-3 seconds and release.
6. Disconnect the tinfoil shorting tool.
7. The APX device should be detected on your computer.
8. NVFlash a working bootloader.
9. Disconnect the AC adapter.
10. Reconnect your battery.
11. Reconnect the power until your device is charged.
Thanks everyone!
-Buzz
Click to expand...
Click to collapse
the 4 contacts are the switch labbeled K2
ACis0014 said:
Thanks brother. Got it after a little looking around. Turns out it's pretty darn easy lol
Click to expand...
Click to collapse
Glad you got it working. Now if I may suggest a nice flashing of the Vegan-Tab ROM.

Ill give this a try when I get home thanks for all the help so far ill let you know if that works
Sent from my Droid using Tapatalk

curiously after using the format I get the red notice, but once I re-flash with the recovery nvflash my boot animation is back...

P00r said:
curiously after using the format I get the red notice, but once I re-flash with the recovery nvflash my boot animation is back...
Click to expand...
Click to collapse
Well you get the red notice because everything was erased.

Related

Don't Try to Partition with Rom Manager.

If You try to partition with Rom manager it partitions the internal sd and you will brick your phone. Your screen will be black with only the capacative buttons glowing. This brick is possibly the more annoying ones where you have to flash your phone twice. If you have this problem don't panic like i did.
*REMOVING EXTERNAL SD CARD MIGHT IMPROVE ODIN CHANCES OF WORKING*(Thanks Hoey2011 for mentioning this)
Step 1: Download all files from this thread
http://forum.xda-developers.com/showthread.php?t=734475
PUt them in a safe spot you will need them for later.
Step 2: Download files from this thread
http://forum.xda-developers.com/showthread.php?t=740558
Step 3: HAVE ODIN OPENED FIRST!!(This helped it detect my phone for some reason)Get phone into download mode. The easiest way to do this is pull out battery from phone. Then plug phone into usb connected to computer it will have the battery sign. Hold volume keys and power button when the screen goes black let go of power button. You will be in download mode if Odin doesn't detect it unplug usb and replug it.
Step 4: Once Odin has recognized your phone set the pit file and .tar file FROM EUGENE'S 2.2 THREAD. NOT THE FIRST LINK THE SECOND LINK. Then click start. And follow all the directions on his thread.
Step 5: Once you have flashed that rom you put your phone in download mode again and set up the pit and .tar file for Stock 2.1. After you finish flashing it your phone should be saved!
Thanks to Eugene373, justanothercrowd and anomalous3(for being patient and helping me out when I had this problem) And to anyone else that helped me solve this problem.
Thanx for being the guinea pig. Glad you got it back working.
Yea It was a ***** tho. Spent at least 4 hrs fixing it. But glad its working
Wow that sucks well thanks for the write up.
I was in the same boat as you and as I was downloading 2.2 to try I found your thread. Works like a charm! Thanks for the info on this. I guess I shouldn't read threads backwards from now on, huh?
ok so I've been following this method, and got eugene's 2.2 loaded up correctly, and rebooted back into download mode. The 2.2 files loaded just fine through odin, but now that I'm flashing 2.1, it seems hung on the cache.rfs.
I am gonna go smoke a blunt or two and come back and see how it's progressed, but this hang is the same issue I had before, on my windows 7 64bit machine. I figured it was a compatibility problem so I'm using my old busted vista machine. I've gotten further on the vista laptop than the W7 one, but I'm still hung.
How long should the 2nd loadup take??
I am almost at my wits end with this stupid mistake I made and hope is such a far stretch
ok, so i continued my use of the search tool here at xda and found my answer
I had my MicroSD card in my phone, hadn't even thought to remove it. I have moved past the cache.rfs file and am now waiting to see the results....
IT WORKED OMG OMG OMG
Xda forums almost ruined my phone, then brought it back from the dead
god i love equlibrium
Good info thanks for posting it, but one thing I would like to point out and I am not alone in feeling this way people are throwing the.word brick around and far to casually. You did not brick your phone by partitioning it the proof is that you fixed your phone. Bricking a phone is wheb youbrender the phone usless as a brick when it is totally broken and unfixable. I dont mean to nitpick i just hate seeing everyone that makes a mistake in anything crying wolf and claiming to have bricked. But my rant aside thanks for the very usefull info you mightvwanna pass it on to koush so he can fix it.
Sent from my SGH-T959 using XDA App
I did exactly this and I was so frustrated that I sent my phone back to tmobile and just purchased a new one. I don't know about yall but if there are two storage points (internal and external) there should be an option for both in default recovery because when I tried to partition the external sd card *in which i was able to execute on my nexus one* it was very easy but because I use clockwork recovery and did a rom backup, i guess the backup zip wasn't safe because I received the same results as you. There should be 2 options to choose from that says *internal storage, External SD Card* why make things difficult? lol
The manufacturers need to be a little more intuitive.
*this is my opinion*
zDisturbed1 said:
Good info thanks for posting it, but one thing I would like to point out and I am not alone in feeling this way people are throwing the.word brick around and far to casually. You did not brick your phone by partitioning it the proof is that you fixed your phone. Bricking a phone is wheb youbrender the phone usless as a brick when it is totally broken and unfixable. I dont mean to nitpick i just hate seeing everyone that makes a mistake in anything crying wolf and claiming to have bricked. But my rant aside thanks for the very usefull info you mightvwanna pass it on to koush so he can fix it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks for the clarification. I actually had no idea a brick was unfixable. I thought a brick was when your phone messed up and you'd reflash to get it working. Lol sorry again
Sent from my SGH-T959 using XDA App
Ah crap, that's right, /sdcard is mapped to the *internal* sd card on the phone, and that's what is partitioned. I'll disable partitioning on the phone (external SD card is not accessible in recovery).
Koush said:
Ah crap, that's right, /sdcard is mapped to the *internal* sd card on the phone, and that's what is partitioned. I'll disable partitioning on the phone (external SD card is not accessible in recovery).
Click to expand...
Click to collapse
I haven't tried partitioning, but the card's /dev/block/mmcblk1p* entries are there and I can mount them. That's how the dc2ext hack works. It mounts /sd-ext and /data to do the copies and it does it in recovery.
hoey2011 said:
ok so I've been following this method, and got eugene's 2.2 loaded up correctly, and rebooted back into download mode. The 2.2 files loaded just fine through odin, but now that I'm flashing 2.1, it seems hung on the cache.rfs.
I am gonna go smoke a blunt or two and come back and see how it's progressed, but this hang is the same issue I had before, on my windows 7 64bit machine. I figured it was a compatibility problem so I'm using my old busted vista machine. I've gotten further on the vista laptop than the W7 one, but I'm still hung.
How long should the 2nd loadup take??
I am almost at my wits end with this stupid mistake I made and hope is such a far stretch
Click to expand...
Click to collapse
I have had serious issues with Odin hanging on my WIn 7 32bit system. However, I think I was actually doing it wrong. I was booting my phone to download mode then plugging it in to my computer. However, I have had continued success (tried a bunch last night) by doing this:
Open Odin, take out the battery, plug in USB cord to phone and computer, hold vol up+down, put in battery. Whenever I booted into Download Mode this way, Odin worked perfect every time. Turns out after cursing my computer it was user error, whoops .
brandnewsimmy said:
I have had serious issues with Odin hanging on my WIn 7 32bit system. However, I think I was actually doing it wrong. I was booting my phone to download mode then plugging it in to my computer. However, I have had continued success (tried a bunch last night) by doing this:
Open Odin, take out the battery, plug in USB cord to phone and computer, hold vol up+down, put in battery. Whenever I booted into Download Mode this way, Odin worked perfect every time. Turns out after cursing my computer it was user error, whoops .
Click to expand...
Click to collapse
turns out, the system wasn't the finicky piece of equipment, it was the phone and the odin software. I inadvertently left the sd card in the phone, the external one, and that was causing my hangs. Two more tries after pulling the sd card, I had success and was back to my phone again
hoey2011 said:
turns out, the system wasn't the finicky piece of equipment, it was the phone and the odin software. I inadvertently left the sd card in the phone, the external one, and that was causing my hangs. Two more tries after pulling the sd card, I had success and was back to my phone again
Click to expand...
Click to collapse
I forgot to mention to do that. I did that with mine as well. Taking out the sd card increases success. Thanks for mentioning it.
Sent from my SGH-T959 using XDA App
farrisizdaman said:
Thanks for the clarification. I actually had no idea a brick was unfixable. I thought a brick was when your phone messed up and you'd reflash to get it working. Lol sorry again
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
YEa I guessed as much thats why I was trying not to "flame" and to be informative you are a victim of exactly what I am talking about. Because so many people throw around the word brick anytime anything goes wrong not only is it losing its meaning but people are also getting confused.
This does work, it took me about 7 hours last night to fix it.
I will say if it does not work then keep trying.
My flash kept freezing on the froyo rom and would not finish, so I actually had to try and flash the full captivate stock rom (search the captivate forum) it froze but afterwords it let me go throught the whole flash process with Eugenes 2.2 rom, then flashed right back to 2.1 no prob.
I will also say that if you are on a x64 system then go find a x86 (32 bit) system. I dont know why but it just works better.
So if it doesnt work then do this:
1. Make sure you are on a 32 bit system.
2. Flash a Full Rom from the Captivate forum. (It has a more to it I believe, changes the system maybe?)
3. If it freezes that is ok. Flash the 2.2 rom. (might need to do it a couple times)
4. After successful flash then go to stock.
This needs a sticky!!!!!!!!!
I just did this. Wish I would have seen this thread first!
I'm having a really hard time getting to download mode. Read all the threads I could find on it.
Any ideas? Download mode isn't removed when partitioning with rom manager is it?
I'm trying not to freak out...
tsnow247 said:
I'm having a really hard time getting to download mode. Read all the threads I could find on it.
Any ideas? Download mode isn't removed when partitioning with rom manager is it?
I'm trying not to freak out...
Click to expand...
Click to collapse
After fighting with it I found out this worked best for me:
Battery out
Plug in USB cord to the phone and PC
Hold Vol up and down
Put the battery in
Phone should boot right into download mode.
Also, I found you should have Odin open FIRST before you do this. If I didn't I would have constant issues with Odin hanging.

Bricked-Unable to Re-install Packages

greetings...i've read far too many threads on not being able to boot into "recovery" and "download" and haven't found anything to fix me...
i can successfully get into "recovery" but when i try to reinstall the packages it starts to run a recovery with Clockworkmod etc...it stops and reboots into recovery...this will go on and on...
now when i try to boot into "download" i can't, i've tried many methods none work.
any help?
rooted/clockwork recovery/nandroid back up prior to trying the vibrant7
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
The K-Zoo Kid said:
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
Click to expand...
Click to collapse
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
dsuycott said:
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
Click to expand...
Click to collapse
Alright i will doo... and you restored from odin after the problem started...?
I flashed the stock kernel and everything is good... Its in the OP of Eugenes rom.
98classic said:
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
Click to expand...
Click to collapse
thanks for the reply...i've done that a bazillion times...won't go, i even went to the tmobile store in my hood and no go on their end...
The K-Zoo Kid said:
Alright i will doo... and you restored from odin after the problem started...?
Click to expand...
Click to collapse
not after, i had restored from odin about two weeks ago...
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
The K-Zoo Kid said:
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yes(but i'm over saturated right now, i might have missed something) ...i'm dead in the water, i can't get to the point of anything seeing my device...my computer won't see it except as unknown usb device, no partitions show up, adb doesn't recognize it in any way...maybe i'm a [email protected], but i don't see anyway to flash it without at least getting in to download mode, or somehow pushing a .zip at the sd for a recovery??? technically figuring out that stuff is beyond my remaining brain cells...this seems like a dicey way for the phone to rely on when restoring to factory.... it would be nice to have the device look at All available partitions, internal/removable, for a recovery system or have an altogether different sd in the phone for a -R dedicated recovery volume....don't know, i'm a noob at this android stuff sooo....

[Q] Emergency. HELP!

I was adding a new custom ROM to my Droid 2 because I wasn't happy with the Epic ROM so I went with the VZW 2.4.5 Clean ROM, I wanted to add the kangerade blue theme to it but accidently installed the wrong version of it over my ROM and now my phone is in a constant boot loop. sometimes it stays at the droid eye for a while and then load into the lock screen but will go right back into the boot sequence.
When it does boot into the lock screen there is not enough time for me to get into the bootstrapper app to boot into recovery mode.
are there any other ways to get into recovery mode? I've searched high and low on this forum and others as well.
I want my droid back =[
Have you tried to pull the battery and then put it back in. Everytime I do that, I end up at recovery thing.
yup, i've pull the battery many times. i've got it into the android recovery screen but when I to the data/cache format it just brings me to the green android starting screen and goes back into the boot loop, what's weird is that the theme is still applied to the phone
yaooitsbrett said:
yup, i've pull the battery many times. i've got it into the android recovery screen but when I to the data/cache format it just brings me to the green android starting screen and goes back into the boot loop, what's weird is that the theme is still applied to the phone
Click to expand...
Click to collapse
Hmmm. Kind of a roundabout process, but did you make a backup. I'd just restore it to a backup and then go from there.
i can't get into the clockwork recovery, just the stock android recovery. are there any backdoors that i could use with adb?
Try taking the battery out during the boot animation a few times, if that doesn't get you to clockwork recovery you've probably lost your recovery. I've noticed that I sometimes (or always?) Lose clockwork when installing a Rom. If that is the case you may have to sbf unless you can get adb to work from the lockscreen.
Sent from my DROID2 using XDA App
pulptastic said:
Try taking the battery out during the boot animation a few times, if that doesn't get you to clockwork recovery you've probably lost your recovery. I've noticed that I sometimes (or always?) Lose clockwork when installing a Rom. If that is the case you may have to sbf unless you can get adb to work from the lockscreen.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
how would I go about doing an sbf? could you point me in the right direction?
On this forum three posts down is a guide. Follow the guide exactly, except you will have to put your phone in bootloader mode since it will not turn on and stay on. Do do this, hold the up button on the dpad when you turn it on.
It works, i just did it yesterday. First time ive ever had to flash SBF, and i did ALOT of roms and modding on my D1. The bootstrap is nice but not as nice as a full bootloader.
Sent from my DROID2 using XDA App
cool. i think i found the guide. it says backup my sd card to my computer..this doesn't delete everything on the sd card does it?
(not a huge concern since having a working phone is better than losing all my stuff on my memory card)
okay. I tried doing what the tutorial said and I got an error on my bootloader that says
"Critical Error: DEA1"
EDIT:
Well it looks like it was just a simple "I need to update my rsd lite program"
I was using the 4.5 and I read that 4.9 was out so I gave updating RSDLITE a shot and boom, the phone is reflashing as we speak
My sd card is intact... untouched from what I can tell. I had no apps2sd though (with 8 gigs on board why would I?)
Sent from my DROID2 using XDA App
Where is the RSD Lite 4.9? All I come across is 4.7.
Sent from my DROID2 using XDA App
Terri M said:
Where is the RSD Lite 4.9? All I come across is 4.7.
Click to expand...
Click to collapse
Google "RSDLite 4.9" it should be in one of the first results..I found mine in a forum
http://droid2files.com/tools/RSD Lite 4.9.zip
This is RSD Lite 4.9.

Help! Droid 2 stuck in boot loop.(solved.)

Ok, so I was playing around with the new Root Tools app and made a few, what I thought were safe, tweeks to the system and rebooted the phone. It gets past the M screen, runs the boot animation and then starts the boot animation again. No way out except to pull the battery.
How can I get it out of this endless bootloop? If I have to factory reset and start again from scratch, so be it. I would just like to know how.
I've tried holding down different button combinations on boot but haven't come up with the right sequence I guess.
I've also tried pulling the battery as the animation starts, then putting it back in and rebooting which is supposed to call up the recovery mode, but it doesn't. I'm not sure what to try next? I wish these things had a reset button
It's a Droid 2 Rooted with the stock rom running Froyo 2.2. I have the Bootstrap recovery loaded and did a backup with the clockwork recovery. I also have, and use, Titanium Backup Pro for Root.
After bootlooping pull the battery and put it back in. Then plug the droid 2 in with the cable either wall or USB will work. Then turn it on and it should get you recovery. The phone has to be completely off when you plug it in though.
Sent from my DROID2 using XDA App
EDIT: I tested it and USB won't work (at least for me) better off just using the wall plug.
Thanks, but that not working either. When I plug in the cable after the battery pull it starts up automatically and goes to the battery charge screen. I then shut it off and start it back up with no battery but plugged in and it goes right back into the boot loop after the M screen.
The batter charge screen is what you want. Just press the power button after you get the charge screen and you'll be booted into clockwork.
But in order to factory reset from a bootloop you have to flash an .sbf theres a few different tutorials. One in Windows, Another in linux/mac, and another in linux but for windows machines through an Ubuntu livecd(that I made).
Oh, OK I thought it was going to go right into recovery mode. Good to know.
I finally figured out how to get into the stock recovery and bootloader, so I tried to run the stock restore but after it wiped the data, it couldn't find the recovery file! So then I read in another post about using RSDlight 4.9 to do an sdf restore so I used that method. Of course while it was flashing I did come across your Ubuntu method and that does look like it would be a simpler process. I'm going make one of those CD's to have for next time.
Anyway, I was able to get it back to stock. It looks like most of my stuff is still on the SD card, so that's a bonus! I'll have to re-root before I can restore everything via Titanium, but that's going to be tomorrow's project. As for now just happy to to have my phone back. Especially before the wife (who has been telling me for weeks to stop F'in with it) found out .
I really appreciate that you took the time to help, thanks again!
No problem.
Could you change your Thread title to include [SOLVED]. Thanks
Can you please explain to me how you fixed this problem? I am currently having this problem now.
Please do not open/post in multiple threads for the same issue. This is a waste of time as we can see you have an open thread. Please reply to my response in your original thread for further assistance. (http://forum.xda-developers.com/showthread.php?t=824254)
newk8600 said:
Could you change your Thread title to include [SOLVED]. Thanks
Click to expand...
Click to collapse
Ok, your wish is my command! ;-)
Sent from my DROID2 using XDA App
Can I close this?
Yes. This issue has been resolved.
theecho said:
Yes. This issue has been resolved.
Click to expand...
Click to collapse
Ok, thanks

Am i permanently effed?

I tried flashing dorian's redpill v4 (3) on my phone but now when i boot my phone the dual core technology (unlocked) screen pops up... and then after a bit of loading the screen starts flashing non stop. I went back to fastboot and did a restore but the same thing happens afterwards!!.
what do i do?
Can you get into recovery?
alphaguy said:
I tried flashing dorian's redpill v4 (3) on my phone but now when i boot my phone the dual core technology (unlocked) screen pops up... and then after a bit of loading the screen starts flashing non stop. I went back to fastboot and did a restore but the same thing happens afterwards!!.
what do i do?
Click to expand...
Click to collapse
yes i can , currently in atrix 4g recovery v4.0.0.2 GOAPK.com , if that's relevant.
YES i am a noob before you think about throwing difficult words at me D= . im rather panicky tho
I don't even know which recovery that is. If you can boot into fastboot then try to install this recovery on to the phone.
http://forum.xda-developers.com/showthread.php?t=1204500
alphaguy said:
yes i can , currently in atrix 4g recovery v4.0.0.2 GOAPK.com , if that's relevant.
YES i am a noob before you think about throwing difficult words at me D= . im rather panicky tho
Click to expand...
Click to collapse
Did you wipe everything you were supposed to before flashing the ROM? I.e. data wipe/factory rest, wipe cache & dalvik wipe?
Which recovery was that; Rom Racers or Rom Manager.... please don't say Tefnars?
If you have a micro SD card, put a fruitcake on it and flash that, or another ROM.
Sent from my Transformer Prime TF201 using xda premium
i wiped everything before performing the flash, I was pretty sure backing up everything and restoring it would've been poolproof but i guess not. as of right now im unable to do anything cause i gotta be out, however the first moment i get ill try iinstalling that recovery thing, tho if someone can give me an easy step by step guide i'd feel a bit more assured. i hate for this to be my first post, but damn im freaking out.
thank you for the swift replies guys
i reflashed it when I was out with 50% battery life and for some reason it worked. I don't know if I can recover it back to original state, though I rather not give it a try for now. Gonna enjoy my phone. Thanks for the swift replies!!
BTW, today was my first time plugging it in to my HDTV (i never did it prior to flashing) and I tried to watch videos using its own "entertainment center" software, but videos wont show up on the screen. If i watch it through gallery it works, but i cant make it go full screen, instead it just rotates the screen when i do it, while not making it widescreen. Any idea son how to make this work?
If you're using Redpill then I don't know anything about that. I haven't followed that ROM at all, sorry.
alphaguy said:
i reflashed it when I was out with 50% battery life and for some reason it worked. I don't know if I can recover it back to original state, though I rather not give it a try for now. Gonna enjoy my phone. Thanks for the swift replies!!
BTW, today was my first time plugging it in to my HDTV (i never did it prior to flashing) and I tried to watch videos using its own "entertainment center" software, but videos wont show up on the screen. If i watch it through gallery it works, but i cant make it go full screen, instead it just rotates the screen when i do it, while not making it widescreen. Any idea son how to make this work?
Click to expand...
Click to collapse
doesn't matter. get into recovery perform a factory wipe, and then install some OTHER rom just so u can make sure it works. Forget about redpill for one sec
You're using an outdated recovery that doesn't support EXT4, so just update recovery and try to flash the rom again.
Sent from my MB860 using xda premium
alphaguy said:
i wiped everything before performing the flash, I was pretty sure backing up everything and restoring it would've been poolproof but i guess not. as of right now im unable to do anything cause i gotta be out, however the first moment i get ill try iinstalling that recovery thing, tho if someone can give me an easy step by step guide i'd feel a bit more assured. i hate for this to be my first post, but damn im freaking out.
thank you for the swift replies guys
Click to expand...
Click to collapse
1. Download moto-fastboot from here:
http://forum.xda-developers.com/showthread.php?t=1138092
2. Download RomRacer's CWM from here (.img file):
http://forum.xda-developers.com/showthread.php?t=1204500
3. Hit Windows Key + R on your keyboard
4. Type cmd and hit enter
5. Locate the extracted moto-fastboot files on the command prompt window
6. Put your phone in fastboot mode and connect it to the computer via USB
7. type in moto-fastboot devices and hit enter to make sure it's recognized
8. type in moto-fastboot erase recovery and hit enter
9. type in moto-fastboot flash recovery recovery-atrix5.img (or whatever the file name is) and hit enter
10. Type in moto-fastboot reboot, hit enter, and enjoy your new recovery.
take sd card and put it into anoter phone or on a little micro sd adaper put that into your pc download the recover and and the put the sd back on you phone.Then start recover and fastboot and flash the new recover and then flash a new rom or try to trouble shoot yours
Deleted. Sorry.
Sent from my MB860 using XDA App
Were you able to get this up and running?
I had the same issue yesterday... I ran through the steps outlined here and I was good to go.

Categories

Resources