Related
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
jesusgi said:
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
Click to expand...
Click to collapse
nvflash to the version included in the tntlite post there is an apk file link there
Do you mean 3588 stock?
jesusgi said:
Do you mean 3588 stock?
Click to expand...
Click to collapse
yes check the first post in the lite thread. It is linked as APK 3588
I downloaded it, but I am not sure how to use it with nvflash as compared to the restore which was relatively simple using the included bat file. Am I missing something or am I just a hopeless Noob?
jesusgi said:
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
Click to expand...
Click to collapse
Hmm?.. Seems there are a lot of users trying to prove the GTAB is in fact Brickable..*lol*
It is NOT!
Go here:
http://forum.xda-developers.com/showthread.php?t=861950
Yes I feel dumb about it. I did read that thread before posting. I did the restore. I can get the gtab to boot up and it is usable.......until I power down, then the only way to use it again is to reflash the restore again. I mean its usable. Not really bricked, really, but I am frustrated because it seems like I am missing the solution.
I used the nvflash from http://forum.xda-developers.com/showthread.php?t=861950 to prep my gtab for 5.0. Once it flashed and booted to the OS, I had it join wireless, then it prompted to start the update to 3588 immediately. Have you tried this?
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
jesusgi said:
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
Click to expand...
Click to collapse
Been there.......months later the tablet is still there. I can not power it off or reboot it. I bought another tablet and use "the unbootable" one at home where it sits in a dock until needed.
I have tried every nvflash recommendation out there...
There are about 4 or 5 tablets like this. Most have either been returned/swapped out or set aside and no longer used (from my reading of others with the same problem).
I can get it to boot by formatting partition 2 so if it ever goes off or I need to "update" it I turn it off.....connect it and nvflash it...holding volume + if I need to get to recovery. If not...once nvflash sends the bootloader over and formats partition 2, the device boots.
Something on mine is preventing the bootloader from booting.....the nvflash sending it over executes it and the tablet runs......
redundant - double posted
jesusgi said:
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
Click to expand...
Click to collapse
I got the same problem. I can only power my gtab by doing nvflash, and if i reboot, it only goes into apx mode.
Ouch. That has stopped me in my tracks. It's really bad news.
"Something on mine is preventing the bootloader from booting.....the nvflash sending it over executes it and the tablet runs......"
That's my problem exactly. My wife is going to be very upset. I thought I could keep her gtab updated without bricking it. Oh jeez that's exactly what I've done..........
Suggestion? don't do the update after you nvflash.. let the device boot up normally and put a different ROM zip file on the SD via USB.
Calkulins new ROM is based in TnT is super smooth.
http://forum.xda-developers.com/showthread.php?t=985705
From there try to reboot into recovery mode with an app like quick boot AniReboot and flash the different rom.
It may be the ROM you're trying to flash is corrupt.
I did the same too. . An didn't read the fine print. After getting the info
on how to fix my bricked gtab. Also, I had to do some Googling on apx
USB drivers for windows 7.
Long story short.. had a few pints. .. got it back to stock and installed tntl 5
The next day.. I'm using it now and I'm happy. Time for another pint.
I thought I bricked my GTab, after several hours of tweaking I was
able to flash it and run TnT Lite 5.0 now. Here is the procedure I did:
a. nvflash to stock rom. download the usb driver for windows 7 here and install (link from post by syntrix) : http://developer.download.nvidia.com/tegra/files/os/tegra_ventana_froyo_20110207.msi
b. grab the stock rom from the post by roebeet, choose "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip": http://db.tt/Wm25t7U
c. following roebeet's instruction, put Gtab to APX mode (volume down + power on), run nvflash_gtablet.bat, should flash the rom fine.
d. boot the Gtab after flashing, should be able to run the original stock rom.
e. download the 3588 stock rom from this thread:http://forum.xda-developers.com/showthread.php?t=842000
f. run recovery (volume up + power on) to upgrade to 3588 rom, remember to make a "recovery" folder with "command" (check the prefix and see if is name "sdcard") and rename the downloaded 3588 rom to "update.zip". Put both to the root of the sdcard.
g. now you should have 3588 rom after the recovery
h. download tnt lite 5.0 rom and run a recovery. you will get stuck at a black screen. Just reboot and enter recovery mode again (volume up + power on). do a "wipe data" and reboot. Then you will be able to run TnT lite 5.0. In the recovery mode, the "power" button is "enter", not the "home" button in CWM 0.8. Anyway, just follow the instruction on screen for button layout.
Thanks. I have actually done those and would do them all but G-Tab will only boot once after flash (step d) after that if I power down, I gotta black screened brick until reflashing original ROM again. It is impossible for me to do step "F" from Gaspra post
and with that I give up. I ordered another G-Tab, and I'm using the old one as a plant stand. Who said this can't be bricked? I managed to do it.
Send it to me. I'll pay shipping.
jesusgi said:
Thanks. I have actually done those and would do them all but G-Tab will only boot once after flash (step d) after that if I power down, I gotta black screened brick until reflashing original ROM again. It is impossible for me to do step "F" from Gaspra post
Click to expand...
Click to collapse
did you try to erase the rom? try this before flashing to the stock rom:
http://forum.xda-developers.com/showthread.php?t=974422
Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!
Charles Angus said:
Hey there,
Was on Dexter's Froyo 1.2b. Phone froze up, had to pull battery.
After pulling the battery, it won't reboot. Just stays on the Moto logo forever.
Will not go into recovery mode, but will go into bootloader.
Tried flashing a few different ROMs onto it with RSD, no luck.
Any thoughts?
Thanks!
Click to expand...
Click to collapse
try this
remove your sdcard and just leave sim card in our phone and boot..wait for it ..if after 10 minutes moto logo still there..pull out your battery and put it back into phone
press power button , press the Vol + button for 30 seconds as soon as the Moto Logo shows up
if you see the recovery option select the wipe data/ factory reset option and then reboot..
I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......
pajo985 said:
I had exactly the same problem (and a few people too)
sorry...but you can't do anything!
I tried to flash my phone numerous time, and can't get into recovery!
only solution is to send phone to motorola service
PS. this is 100% connected with dexter's froyo...so it would be nice that we collect some info why is this happening on some phones......
Click to expand...
Click to collapse
Did you end up sending yours out to motorola service? Were they able to fix your phone? I think resar also had a similar problem. http://forum.xda-developers.com/showthread.php?t=821210 (before Dexter's ROM)
It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged up ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge up your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charging up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the battery does not charge up anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just ask if you don't understand anything
Did you get into RSD Lite & bootloader mode?
Knoedelkopf said:
It is wrong that there is no way to deal with that problem. I also had it a few weeks ago.
Method 1: http://forum.xda-developers.com/showthread.php?t=892026
Method 2: Get a second battery that is charged ( at least 40 % or so..) and then get into the bootloader and reflash your custom ROM.
Method 3: Charge your phone ( do not connect it to PC ) with the wall charger. When the phone wants to boot automatically, pull out the battery and set it in again. When the phone tries again to boot, pull the battery out and set it in again. My XT720 wanted to boot after 5-10 minutes or so when it was charged up. You should do that until your phone has enough battery to get into the bootloader.
In my opinion the problem is that the phone does not charge anyway?
It worked for me with a second battery that was charged up for 50 % and then I reflashed custom ROM with RSD Lite.
Just keep asking questions if you don't understand anything
Did you get into RSD Lite & bootloader mode?
Click to expand...
Click to collapse
Interesting! So, the idea is that when battery power is too low the flash is either ineffective or perhaps disabled by some low-level hardware check? It does seem plausible. I hope I don't ever have to try this.
battery is not a problem (at least in my case)
I have original milestone which have the same battery as xt, so I always charged battery at 100%...
motorola did repair my phone, but now I am afraid of flashing 2.2 back, because it will surely stuck at M logo again (I tried it two times already )
PS. tried flashing ALL available flashes (even original korean 2.2), and nothing happened..
I just couldn't boot into recovery
So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?
Knoedelkopf said:
So when you got into the bootloader mode, was there shown something like "battery low cannot program"?
Or what do you mean exactly with "I just couldn't boot into recovery "?
Click to expand...
Click to collapse
We tried everything we could to save pajo's phone but nothing worked. resar is also extremely knowledgeable and had to send the phone to Motorola for repair. Pajo's thread has been merged into this mega thread, unfortunately:
http://forum.xda-developers.com/showthread.php?t=962744&page=1
Mine bricked today also using Dexter 1.3. This was my replacement phone (other one had audio jack issue, hardware not software). My battery died and couldn't get it to reboot, would just cycle the moto logo then sometime the dex froyo logo. I'm flashing back to stock right now,then reverting ti 1.2b was a more stable build.
This is for the people who got a new captivate through return or purchase or how ever you obtained it. If you tried flashing a new rom and now are stuck at the att boot loop or the battery loop and your phone will not boot up here is help.
1. See if your phone will do the 3 button recovery to get into download mode.
2. If you cant get into download mode you might need a Jig or do the resistor technique to get into download mode.
3. See if this odin (I897UCJF6-final-OCD-REV0.exe) will flash your phone back to the stock 2.1.
4. If after flashing the 2.1 odin and your phone still has boot loop then try the 2.2 stock odin
5. Next do the same as previous but try with this odin (I897UCJI6-OCD-REV02-Low-designgears_1_.exe) which is the 2.2 stock odin.
Note all of these flashes require you to be in download mode and have odin fired up on your pc the plug in your phone so odin can recognize it so
a. be in download mode (not connected to PC)
b. have odin open on pc
c. Plug in phone to pc and start odin.
odin likes to stop flashing when setting pit file so if it freezes give a sec and if nothing try it again.
if odin freezes on the set pit file your phone will have the dreaded phone to pc icon during boot but dont panic set your phone into download mode and try again.
If any questions should arise PM me or leave a comment and others and i will try and help.
Took me two days to fix my phone after flashing to stock to root it but i hope this helps you turn your 400 dollar paper weight back into a phone.
umm thanks but we know how to use odin there are a million guides in every ginerflash and captivate sticky.
and the 2.2 odin is actually an internal samsung beta 2.2 not official.
returning it with the designgears 2.2 will be an obvious warranty breach if they notice.
and your Step 4 and 5 seem to say the same thing... "flash 2.2 odin" (which isnt official)
and THE REAL FIX FOR THE BOOTLOOP:
reboot into RECOVERY > (not download)
wipe cache and data! (or factory reset)...
DONE!
reboot into the rom that you were trying to use!
takes 20 seconds and no reflashing anything.
i ran into this a few days ago while trying to root a friends captivate(1008) purchased from walmart recently. after trying to flash back to stock i was stuck on att boot loop and could not get into download mode via button combo to save my life. tried everthing minus a jig....after getting fed up with it, i sat it aside. to my amazment, after about 10-15 minutes the mf booted up. i had to use adb to reboot into download mode. flashed with odin(from aio toolkit) back to 2.1. everything worked fine, no problems except for one thing...sometimes it will still loop for a few minutes before it boots...sometimes it boots right away. Im still investigating the whole ordeal but my point here is: if you think your phone is stuck on att screen, just let it sit for a while....maybe a long while. and it should boot. then use adb to get back to download mode. i read every forum post on the web about this issue...just found this thread and thought id give ppl a heads up. hope it helps
I'm stuck in a bootloop right now on the Galaxy S animation screen and this wipe cache and data method doesn't seem to work for me.
so i recently tried flashing a darky rom theme onto my captivate running mosaic 8.
it worked the first time. then i tried another theme didnt like it, so flashed the darky rom one, and now, bootloop....
i can get my cappy into download mode, but odin doesn't recognize it.
i cannot get it into recovery mode with holding down the volume up and down and power button.
i need help
--edit--
fixed!
biggest help i have EVER had in custom roms/rooting etc..
http://forum.xda-developers.com/showthread.php?t=1351224
TRusselo said:
umm thanks but we know how to use odin there are a million guides in every ginerflash and captivate sticky.
and the 2.2 odin is actually an internal samsung beta 2.2 not official.
returning it with the designgears 2.2 will be an obvious warranty breach if they notice.
and your Step 4 and 5 seem to say the same thing... "flash 2.2 odin" (which isnt official)
and THE REAL FIX FOR THE BOOTLOOP:
reboot into RECOVERY > (not download)
wipe cache and data! (or factory reset)...
DONE!
reboot into the rom that you were trying to use!
takes 20 seconds and no reflashing anything.
Click to expand...
Click to collapse
ok cmw is not mounting cache or anything else any other ideas
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
So I power it back up after a few mins of charging.....the LG screen comes on.....then the Ultimate 1.0 Rom loading logo comes up..after that every 10-15 seconds it turns on the screen, shuts it off, turns it on, off, etc. It keeps turning on and off...even after I left it there for 5 mins.
I'm going to flash back my Froyo stock rooted rom that I made a back up. The Ultimate 1.0 isn't the only rom I've flashed in the past. CM7 as well..many of the builds.
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
That happened to me. I had to reset - battery pull alone wouldn't work. That phone is now on its way to T-Mobile, and its warranty replacement is going to be soon due to really bad screen bleed (affects my watching video and game play).
flexnix said:
Argh.
I have my nandroid froyo backup on my SDcard and it says it can't find it.
This whole internal sd and external sd storage is a pain in the ass. The good old G1 days. Sigh. I went ahead with formatting the card as well and copying back the nandroid backup onto the card. Nothing.
Click to expand...
Click to collapse
What was "it says" - ROM Manager?
If so, it looks for a androids on the internal SD. If you had used the easy recovery install tool, you would have been able to select internal or external to use with Recovery - NOT ROM Manager.
Based on your choice, you should be able to access you nandroid in the place you chose in RECOVERY MODE.
Since you fully drained you battery, you might want to erase battery specs in recovery, turn it off, and fully charge with it turned off for 8 hours. It is not recommended that you fully drain the battery and that may be your problem.
Then you could try wiping cache, dalvek, and format /system - and reflash your ROM. Save flashing the nandroid for last.
flexnix said:
I haven't done any flashing in about a week. Everything was working fine. And just today I ran the battery completely dry (which I usually do and it keeps my battery happy).
Click to expand...
Click to collapse
have you tried a different battery?
According to the experts at Popular Mechanics running your battery dry is very bad for it. It greatly reduces the life according to them. There was a post about it last week. There are physics involved that apply to all.
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
You need to NVflash your Recovery
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You boot the phone holding Volume Up & Power buttons until recovery screen appears.
Recovery, if you flashed it using the NVflash tool, will be accessible by booting your phone while holding Vol Up & Power. You will go into Recovery. If you have never done this or do not get recovery its because you did not flash the Recovery onto your phone.
Basically, if all you did was download ROM Manager and start flashing the G2x you are playing with fire. You need to flash the Recovery onto the phone using NVflash tool. ( Follow Step2 in the following link: http://forum.xda-developers.com/showthread.php?t=1060715 )
I would recommend anyone with the same problem or the same question to go thru the link above and you will find answers to most of your problems.
EmceeGeek said:
when this phone crashes and won't reboot, how do we even get into recovery without rom manager??
Click to expand...
Click to collapse
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
flexnix said:
You need to properly install Clockworkmod recovery with NVflash. Its a process but well worth it. Rom manager is a no no with out phones.
Click to expand...
Click to collapse
Did you rename your nandroid backup?
If you did that would be the problem. if you want to rename it, don't leave any spaces.
Sent from my G2x
Hi all, I was planning to flash the ParanoidAndroid Jellybean ROM but wanted to go back to GB stock first from Legend 3 ICS. So I used Heimdall 1-click (on a Mac). The first time flashing it, it rebooted to the AT&T boot screen but it was showing intermittent rainbow screens as well. So I went back to Download mode and flashed with the bootloader checked off. However, it's telling me:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Rinse and repeat from step 1 flashing. Except now it won't even get me to the AT&T screen and just keeps me at rainbow screens. It does not show the Samsung logo, just rainbows. I've tried some more Flash, then Flash with Bootloader, same results. :crying: What should be my next step? Any help is greatly appreciated!
BTW: Got sick of doing this tonight so will continue tomorrow. Will it still charge my phone if I plug it in? Or do I not need to since the battery is pulled out? It was at 96% when I started flashing...
Yakusoya said:
Hi all, I was planning to flash the ParanoidAndroid Jellybean ROM but wanted to go back to GB stock first from Legend 3 ICS. So I used Heimdall 1-click (on a Mac). The first time flashing it, it rebooted to the AT&T boot screen but it was showing intermittent rainbow screens as well. So I went back to Download mode and flashed with the bootloader checked off. However, it's telling me:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Rinse and repeat from step 1 flashing. Except now it won't even get me to the AT&T screen and just keeps me at rainbow screens. It does not show the Samsung logo, just rainbows. I've tried some more Flash, then Flash with Bootloader, same results. :crying: What should be my next step? Any help is greatly appreciated!
BTW: Got sick of doing this tonight so will continue tomorrow. Will it still charge my phone if I plug it in? Or do I not need to since the battery is pulled out? It was at 96% when I started flashing...
Click to expand...
Click to collapse
There may be some issues with Heimdall not completing a flash on Macintosh.
I've seen several reports in the past. If you go back 4-5 months in the Q/A, you will find some.
Try a PC - or see if you can get a different OS on your mac..idk
Thanks, it worked on my PC!