[Q] Option 3 brick? - Asus Eee Pad Transformer Prime

Hello all, I have what appears to be an option 3 brick, but after having searched through the Unbrick posts, I haven't been able to find a definitive answer to how to resolve this (or if it is even an option 3 brick). What happened:
1) Installed ROM Manager on the latest stock ROM (.28?)
2) Installed CWM 5.8.3.4 via ROM Manager
3) Downloaded CM10 via ROM Manager and attempted to flash
4) Realized that this required unlocking
5) Unlocked device
6) Rebooted into CWM
7) Flashed CM10
8) Reboot
9) Passes EeePad boot screen, but stays on CM10 splash screen forever
10) adb pushed a CM9 ROM on instead
11) tried flashing CM9, but same thing
From the posts in the Unbrick thread, a brick 3 isn't quite the same thing because it's a boot loop into CWM instead? I'm not sure. At any rate, it seems to have something to do with not unmounting /staging or something, but there has been no single post with a method to unbrick this. In the Unbrick thread, there are references to fixing this but those references seem to have been removed since it no longer works; a new method was hinted at in several threads, with no definitive procedure. I was also not allowed to post into the Unbrick thread as I haven't reached 10 posts yet.
Any ideas? Thanks.
li Arc

li Arc said:
Hello all, I have what appears to be an option 3 brick, but after having searched through the Unbrick posts, I haven't been able to find a definitive answer to how to resolve this (or if it is even an option 3 brick). What happened:
1) Installed ROM Manager on the latest stock ROM (.28?)
2) Installed CWM 5.8.3.4 via ROM Manager
3) Downloaded CM10 via ROM Manager and attempted to flash
4) Realized that this required unlocking
5) Unlocked device
6) Rebooted into CWM
7) Flashed CM10
8) Reboot
9) Passes EeePad boot screen, but stays on CM10 splash screen forever
10) adb pushed a CM9 ROM on instead
11) tried flashing CM9, but same thing
From the posts in the Unbrick thread, a brick 3 isn't quite the same thing because it's a boot loop into CWM instead? I'm not sure. At any rate, it seems to have something to do with not unmounting /staging or something, but there has been no single post with a method to unbrick this. In the Unbrick thread, there are references to fixing this but those references seem to have been removed since it no longer works; a new method was hinted at in several threads, with no definitive procedure. I was also not allowed to post into the Unbrick thread as I haven't reached 10 posts yet.
Any ideas? Thanks.
li Arc
Click to expand...
Click to collapse
If your getting to the boot animation it doesn't sound like any sort of brick.
It could be a few things. Try holding the volume down button while powering on. When the text appears up the top left just wait 5 seconds and you will have 3 icons on screen. press volume down to go to the wipe icon and then press volume up to select it.
If this doesn't work post back and we can try some other things.

flumpster said:
If your getting to the boot animation it doesn't sound like any sort of brick.
It could be a few things. Try holding the volume down button while powering on. When the text appears up the top left just wait 5 seconds and you will have 3 icons on screen. press volume down to go to the wipe icon and then press volume up to select it.
If this doesn't work post back and we can try some other things.
Click to expand...
Click to collapse
Yep, that did it! I didn't want to do a wipe via CWM since I thought it might destroy something else, so I was going to do the wipe upon bootup, but I guess a wipe is pretty standard whatever the ROM (I did use the wipe method you mentioned though, maybe that's not the same as the CWM wipe?). When I first tried to install via ROM Manager, I did check "Wipe data/cache", but obviously that fell through when the unit was still locked. Anyways, maybe I'll try to install something like TWRP for ease of mind later. Thanks!
li Arc

Related

Now my new G-Tablet won't boot.

So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help

[Q] GTab woes

I'll try to keep this to the point and not too noobish. I've been a lurker for awhile and had Vegan Tab Ginger Edition on my Gtab awhile now. I tried to re-flash with this rom (Flashback - Honeycomb 10.1) the other day and that's when the problems have started. I used clockwork mod from this (Install clockwork, a rom, and market) thread back when I first re-flashed my device. I followed the guide for that rom and it seemed to be successful until it rebooted. I believe it just sat at the ViewSonic screen and didn't go any farther... I looked for NVFlash and set that up and was able to flash the recovery rom from here (I think..). I tried the hotkey to boot back into the recovery and the screen said android but had the exclamation point. I tried installing a later version of clockworkmod but it seems to be stuck in an installation loop unless I boot into TapnTap and remove the update.zip and recovery folder. So my questions are, is it possible to go back completely stock or to "square one" so I can get a later version of clockworkmod, then put either that Honeycomb rom or a newer version of VeganTAB (or even CyanogenMOD) on it? Also, how do I tell what bootloader I've got? I've had this tablet for at least a year and I know it was before the newer bootloader was released that had so many issues. Last but not least, When I try the shortcut to get it to boot into NVFlash mode it doesn't recognize the key... Here's hoping I didn't wear out the volume - button. :/
Thanks
dreamersrevenge said:
I'll try to keep this to the point and not too noobish. I've been a lurker for awhile and had Vegan Tab Ginger Edition on my Gtab awhile now. I tried to re-flash with this rom (Flashback - Honeycomb 10.1) the other day and that's when the problems have started. I used clockwork mod from this (Install clockwork, a rom, and market) thread back when I first re-flashed my device. I followed the guide for that rom and it seemed to be successful until it rebooted. I believe it just sat at the ViewSonic screen and didn't go any farther... I looked for NVFlash and set that up and was able to flash the recovery rom from here (I think..). I tried the hotkey to boot back into the recovery and the screen said android but had the exclamation point. I tried installing a later version of clockworkmod but it seems to be stuck in an installation loop unless I boot into TapnTap and remove the update.zip and recovery folder. So my questions are, is it possible to go back completely stock or to "square one" so I can get a later version of clockworkmod, then put either that Honeycomb rom or a newer version of VeganTAB (or even CyanogenMOD) on it? Also, how do I tell what bootloader I've got? I've had this tablet for at least a year and I know it was before the newer bootloader was released that had so many issues. Last but not least, When I try the shortcut to get it to boot into NVFlash mode it doesn't recognize the key... Here's hoping I didn't wear out the volume - button. :/
Thanks
Click to expand...
Click to collapse
Most probably you flashed a 1.2 ROM on a 1.1 Bootloader.
If you have a year old gtab you are most probably on a 1.1 Bootloader.
Bootloader/ROM table here
http://viewsonic-gtablet-for-dummies.webs.com/rom.htm
I havent had to do this myself, but from what I hear the best place to figure out how to fix in your case would be
http://viewsonic-gtablet-for-dummies.webs.com/
code red section.
Awesome, thanks, I'll check that out.
I tried the battery disconnect trick and let it sit like that overnight. Unfortunately it still refuses to boot into APX mode. Maybe I should try and short the capacitors out too?
Even if you soft brick the gtab, APX mode usually still works. When you press the - volume button and then the power button, do you see the 3 birds shows up and then the screen black out, if so it is normal.
Do a adb devices to see if you can see the gtab.
I'll see what I can do with it tonight, hopefully I Can get it un-bricked so I can throw a better ROM on it and make it usable again.

[Q] Help with recovery on Optimus One P500?

Ok, So I've recently updated to stock gingerbread 2.3.3 with baseband .35. I rooted my phone with the SuperOneClick method. Root was successful (Finally).
I then wanted to install a custom ROM, so I installed ClockworkMod's ROM manager, flashed the clockwork recovery image and everything. I decided to make a backup image in case I didn't like the new ROM. I then selected the "Backup Current ROM" option, and left my phone to it's own devices. When I got back about 5 minutes later, I find that I have a hard reset on my hands :| To add to that, I don't even have a backup image!
I tried doing that a couple times more, once, I even held the POWER+VOL.DOWN+HOME combo and all. The same thing happened each time. The recovery backdrop and a sliding progress appeared, after about 4 seconds, the progress bar stopped moving, it shifted back to the LG boot logo. If I kept the combo pressed, it would go on and on for about 5 times, if I released it, it would just continue on to the boot and I would get another hard reset every time. I tried "Reboot into Recovery". Same thing. Once, I selected "Install ROM from SD card", with the backup option selected. Somehow or the other, due to the combo or something, I came to a screen that had four options.
1) Reboot
2) Install from SD card:update.zip
3) Wipe data
4) Wipe dalvik cache and cache
I was able to scroll up and down with the volume rocker, but the only other button that worked was the Home button, which toggled between the screen I mentioned above and a screen where all of the text was removed and there was just the recovery background. I finally popped out the battery and booted, and got yet ANOTHER hard reset.
HELP!
It seems Clockworkmod recovery was not flashed correctly. What you see is the stock android recovery. The recovery key mapping is:
volume rocker-up/down
menu (left most button)- select current option
back - go back
the behaviour you see when pressing the home button is normal.
After using Rom manager to install CWM recovery, it is not recommended to do further operations through rom manager, best uninstall it. Instead, boot into recovery using the three button combo and do operations from there.
I would suggest try again to re-flash CWM recovery.
mihir287 said:
After using Rom manager to install CWM recovery, it is not recommended to do further operations through rom manager, best uninstall it. Instead, boot into recovery using the three button combo and do operations from there.
I would suggest try again to re-flash CWM recovery.
Click to expand...
Click to collapse
Thanks, but do you have any idea WHY using ROM manager is a bad idea? Just curious.
snitch_95 said:
Thanks, but do you have any idea WHY using ROM manager is a bad idea? Just curious.
Click to expand...
Click to collapse
Well, one reason I've encountered is that while flashing cwm recovery, if the download fails for some reason, Rom mananger has flashed the incorrectly downloaded file without verification resulting in a fastboot semi-brick for many users.
Another reason is related to the way it operates the recovery. I'm not very sure about this point, but I've seen many people having problems with backups and flashing.
Thanks, you were brilliant. I flashed another recovery from ClockworkMod, this time with a WiFi connection, and everything worked great.
I was updating firmware of my LGP500 optimus one using kdz updater for 2.2 to 2.3.3...
battery level might be 40 to 50%.....
at the end i got an error and phone turn off.. now i tried to start it again but its not turning on....
any key combination is not working.. like home+down vol+ power_button or..
return+ up_vol+power_button,,,, what to do to get my phone turn on ??
even when i plugged in it to charger or USB cable .. it shows nothing on screen...
hardik.gcet said:
I was updating firmware of my LGP500 optimus one using kdz updater for 2.2 to 2.3.3...
battery level might be 40 to 50%.....
at the end i got an error and phone turn off.. now i tried to start it again but its not turning on....
any key combination is not working.. like home+down vol+ power_button or..
return+ up_vol+power_button,,,, what to do to get my phone turn on ??
even when i plugged in it to charger or USB cable .. it shows nothing on screen...
Click to expand...
Click to collapse
after the kdz method i think that u can do nothing, if u r under warranty then give your phone back and just say after trying to update through original lg software ur phone would not start at all. or try reading and asking in this thread
I am on 2.2.1 and I installed CWM recovery via ROM manager through wifi. Everything is perfect but whenever I go into recovery it just boots and resets my phone. Its my friends phone and I need help. I have tried other recoveries too but it is the same problem. Please help.
djdhruv said:
I am on 2.2.1 and I installed CWM recovery via ROM manager through wifi. Everything is perfect but whenever I go into recovery it just boots and resets my phone. Its my friends phone and I need help. I have tried other recoveries too but it is the same problem. Please help.
Click to expand...
Click to collapse
try to reflash recovery again and select reboot recovery from rom manager itself after flashing recovery
if still it doesnt work then flash recovery by below method
http://forum.xda-developers.com/showthread.php?t=1318750&highlight=recovery+through+lgdmp

[Q] VAPD7 stuck at splash screen

I have a VPAD7. It's stuck at the viewsonic Birds flashscreen. This is not a looping boot such has has been described in other threads -- it doesn't alternate between the flash screen and brief bursts of blank screen. It just sits there at the splash screen; I've left it for hours, and it just sits.
This all started when I rebooted to FTM (holding down the power button and vol down at the same time) in order to get this information:
* SWVer=3.240
* MODEL:FM6-0001
* HWVer:107
When I rebooted (power cycled) after that, it was stuck.
I have rooted the machine in the past (months and months ago), and installed CW mod. I *can* reboot the machine into recovery mode, holding both volume buttons when pressing the little pin reset button and then quickly pressing and holding the power button. I get the "ClockworkMod Recovery v2.5.1.2" screen. From there, I've tried wiping the cache, wiping the Davlik cache (although I get an error message when doing that about how it can't mount /dev/block/mmcblk0p2), flashing the update.zip on my SD Card (which is lakehousetech's Froyo 2.2 enhanced), and "wipe data/factory reset". I've also tried restoring from some of the backups I made in the past.
No matter what I do, if I try to do a straight boot, the device just hangs there at the splash screen. I can boot to FTM mode, and I can boot to recovery mode, but nothing seems to allow me to get the thing to actually boot all the way up and run.
Does anybody have any ideas of what might be wrong and how I might do something about it?
Thanks,
-Rob
You have new version of viewpad7. Maybe lakehouse rom is not compatible, please try other.
Sent from my ViewPad7 using xda premium
To OP, Froyo ROM that you've saved should be ITE (multi-touch screen) compatible with H/W ver. 107 - I don't think the custom ROM itself is the source of the problem, unless your saved CWM files are corrupted somehow ?
Do you have another mSD card, try formatting it first and copy the CWM folder/files on it, insert into Vpad7 and boot into Recovery, then do a full dalvik, cache and system/data wipe 3 times - before doing a Restore of the Froyo ROM.
Make sure your device is fully charged and let the ROM boot up & settled down, which can take as much as 10 minutes. If you have a 3G mobile Sim card, pull it out although it should NOT affect anything - just precautionary to rule out other factors.
If still NOT good, you will have to try flashing another custom ROM from scratch, I've been very happy with EU V1.7b ITE verision since last Sept/October - the original developer Amalgation hasn't been around, I think, and his link might still be broken for the download - hopefully, you have it saved before. Otherwise, post or PM me and I can provide a secured link for the untouched, original zip file as uploaded before - so that you can try to get the device back in working order.
Or, download the factory *.nb0 file and install it with the Viewsonic utility - for stock, unrooted condition as shipped. Then, you can use SuperOneClick to root, install CWM v2.x again (I personally like it better than the newer 4.x or 5.x verisons to set up A2SD) and resume playing with the limited choice of Roms out there now ...
Good luck & post your efforts/results back here to see whether other ideas might be useful. You didn't try to install/override with any overclocking kernel as none of them work with the ITE hardware, right :fingers-crossed:
Here's a link to some of my earlier notes written about the Vpad7 - in case you missed them. Many of the links are down & sadly, no longer available.
http://forum.xda-developers.com/showthread.php?t=1264647

Please help with rooting Galaxy S5 (g900t)

I've followed these instructions to the tee but have not had any luck with getting this to work. The flash always just results in my phone getting stuck on the "recovery booting.... recover is not seandroid enforcing - Set Warranty Bit : Recovery" screen. Odin reads as "PASS!" but my phone seems like it's just stuck. I've scoured over dozens of forums searching for answers but what works for others just doesn't seem to be working for me.
The instructions all seems so clear, and multiple forums' instructions gave me confidence that this would work no problem as long as I followed the instructions precisely. I guess that wasn't the case. I can't afford a new phone right now, but I'm sure my phone isn't completely bricked. There's gotta be a way! Can you please help me, xda community?
EDIT: I forgot to mention that I also tried the "uncheck the Auto Reboot option" method, and I'm a little confused about the last sentence. See below:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
I'm confused about the "This will start the install process" sentence. I flash, let it finish until Odin says "Pass!", remove the battery, boot into recovery, and then I have two options from there - I can either go into download mode again, or I can start the phone normally. Starting the phone normally just brings me right to the recovery mode which gets stuck there indefinitely. I've left it there for 15+ minutes and it still just stays stuck there.
EDIT 2: Exactly how long is it suppose to take to boot up after it's been flashed?
EDIT 3: IT WORKS. So, If you just sort of hold down all the buttons at the same time, the phone will restart a few times and eventually bring you into the TWRP menu. This is what I was unaware of before. I'm not exactly sure what the specific method or timing is for that, but just tinker with holding all the buttons, and I think you can let go when you see little blue letters on the top left that says recovery or something. Of course, being able to access the TWRP menu means you must first have flashed the TWRP thing, which I did using Odin. Just download the latest TWRP .tar file and flash it with Odin.
EDIT4: SUCCESS! I am now successfully rooted! I reflashed the twrp-3.0.2-2-klte.img.tar and then I was able to access the actual GUI. I guess what I had before was some super stripped down version of the TWRP that only gave me access to a command-line looking interphase in recovery mode, with very limited options. So there you go, if you find yourself looking at pictures on forums of a supposed TWRP with an actual GUI you can navigate, that's because it does exist! Download the one I just mentioned, flash it using Odin, and boot it up by holding VolumeUP, Home, and Power. From there you can flash Zip files, just put the zip files into an sd card. I put my zip right into the sd card, not even in it's own folder or anything.
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
goog888 said:
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
Click to expand...
Click to collapse
Interesting, thanks for the info! Funny enough, while I was at Best Buy last night, I decided "what the heck" and asked a Geek Squad guy about my phone, and told him how I attempted to root and now it wouldn't boot, etc. He took my phone, and just sort of held all the buttons together and it restarted a few times, and he just kept fidgeting with it until eventually it came up to the TWRP recovery menu! So, I did a factory reset and started up the phone. It is currently on 5.1.1. I have since been able to get myself into the TWRP recovery menu by fidgeting like he did, even though I'm not entirely sure what exactly the timing or button combos are. The Geek Squad guy said he just held down ALL buttons, even VolumeUp and VolumeDown at the same time. So whatever, TWRP menu IS accessible finally.
At this point, I'd prefer to flash CM13 to it, and apparently I can just put the CM13 file on my phone storage/sd card, and then flash it through the TWRP recovery menu. But since I factory reset my phone back to 5.1.1, should I first update my radios? A techy friend of mine introduced me to a new fear - that if you flash a ROM that is incompatible with an older radio, it could "hard brick" my device. So now that's where I'm at. I want to flash a rom to gain simple root access, but don't want to risk bricking my device.
Here is my phone's information:
SM-G900T
Android 5.1.1
Baseband version G900TUVU1FOG6
Build Number LMY47X.G900TUVU1FOG6
I don't know how to mark this solved, but it is, as described my my 4th edit in the original post.

Categories

Resources