So, im trying to install an update that i received a notification for...i believe its the one that helps with 3g connectivity and what-not. But while trying to install it, I rebooted to a black screen with a ! inside a triangle and the little android standing next to it...what does that mean?
I let it sit for a GOOD long while, yet nothing happened. Does this mean i can never update?
***This has been solved. My last post in the thread says what i did.***
If you are rooted and you tried to do the OTA then you'll brick your phone.
i was rooted with stock. the OTA came up while i was texting and normally i hit reject, but i accidently hit ok while texting and now every time i start up, it says "Powering Down..."
Any OTA flashed over a rooted device will brick it, I believe.
Edit: Well I found this. May help.
http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Superthrust said:
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Click to expand...
Click to collapse
Glad to hear you're good to go!
Don't flash OTAs when you're rooted next time!
^_^_^
Related
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
venkavis said:
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
Click to expand...
Click to collapse
Hopefully a guru can answer this question. A guru I am not..
But what I think you did should not be an issue. I typically wipe data and then wipe cache partition when flashing a new ROM. sometimes I wipe cache and data just to get the ROM running from scratch again. But this should not affect booting..
One thing I think might be the problem is that you have a new kernel from one of the newer nightlys. Recently they added perhsoots May kernel. Whenever a new kernel is included in a nightly you usually need to clear dalvik cache. this is in CWM under advanced.
I hope this helps.
Tried clearing dalvik cache. No change.
Going back to stock and see.
Copied the stock ROM file and used the CWM to do the update. Now the g Tablet is gioing into a Boot loop. It Tap n Tap then displays a animated icon and after a minute repeats the same.
Tried the recovery option and its going into an installing loop again. Not sure how to get out of this.
Does anybody have this experience before?
Is this bricked now? Call viewsonic support? I am not sure if they support, They may say its nor under warranty.
Just to remind you, the last effort to resolve this is to NVFLash it...
Have you tried CWM method twice or repartition it and do it again? It's a tablet for you to enjoy your Internet, reading, video but not flashing all day long..etc
To pass it quick, if I were you, I would NVFlash it back to 3588, put back my favorite ROM, reinstall the Apps I like and start Internet browsing, converting movie (so I can watch on the road), reading news...
good luck!
rcjpth
After this I definitely agree. But seems I am stuck again. Hope this is the last time.
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Called Viewsonic support and the tech support person pointed me to below post on XDA
http://forum.xda-developers.com/showthread.php?t=1036956
When I read the article it talks about a locked boot loader. Does is mean if I use this and fix the tablet, I will not be able to do any more rooting?
venkavis said:
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Click to expand...
Click to collapse
So you also tried the alternate file, nvflash_gtablet_46_2010112600.zip? That's what worked for me, but I also have to swap partitions 7 & 8 to get CM7 working again.
Since I'm a glutton for punishment, I wiped my cache from nightly 75 and didn't run into any problem.
Just downloaded the alternate zip and flashed again. Having the same looping issue.
Seems like I Have to send it to viewsonic only. The technician said there is a $75 charge to fix.
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
As the title states, I get the 0x13e error when updating via the OTA update.
It will download, reboot the phone, begin installing. When it gets to about 4 or 5%, it will display 0x13e.
The most likely culprit is that I have CMW installed. I am also rooted and on stock E97011c. I have done the Fast Dormancy mod in the past as well, although I have done a full wipe after that.
I've searched Google and the forums with no definitive answer.
Any workarounds or will I have to wait for a .ZIP to flash?
It's because you're using a custom recovery (in this case, CWM)
If you can, relock and try again, or wait as you suggest.
I say "if you can" because your phone might now say that you're up to date, even though you're not
shrike said:
It's because you're using a custom recovery (in this case, CWM)
If you can, relock and try again, or wait as you suggest.
I say "if you can" because your phone might now say that you're up to date, even though you're not
Click to expand...
Click to collapse
even if it says you are up to date and to check back in 24 hours you can just go to applications>all>com.lge.omadmclient and force stop/clear data. After that it will reset the timer and you can check again right away. I LGNPSTed back to 11c and had to do this a couple times before it found the update.
I would wait, don't relock or anything. A flashable zip will be available soon, I'm sure.
StriderMage said:
even if it says you are up to date and to check back in 24 hours you can just go to applications>all>com.lge.omadmclient and force stop/clear data. After that it will reset the timer and you can check again right away. I LGNPSTed back to 11c and had to do this a couple times before it found the update.
Click to expand...
Click to collapse
Not necessarily. 11c has been out for months any my phone only just decided to let me know that it was available this sunday just gone (I've been on 10o since December, and have checked for updates a couple of times a week since). After the 11c update failed (same issue - I have a custom recovery), it's gone back to saying I'm up to date, no matter how many times I clear the data for com.lge.omadmclient and recheck.
And pro-tip: No need to force stop it, just clear the data.
It still shows that I can re-download the update if need be. I think I'm just going to wait for a flashable .Zip to become available. Shouldn't be too long anyway. If a week or so passes and no one has made one, I'll either A)Figure out how to do it myself or B)Revert to stock recovery, if I can, and install.
Thanks all!
Hi everyone,
I would like to preface with I made some very stupid mistakes late last night/early this morning. I decided at around 11pm I was going to root and install a custom recovery on my SGP311. I followed this guide exactly to obtain root and recovery and it worked PERFECTLY.
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Then the mistakes started happening. First mistake I made.
1) Instead of backing up everything in recovery I just Wiped everything. I deleted cache, davlik cache, system, and data. I thought at the time no big deal ill just flash a rom.
2)I decided to flash a CM nightly and I got the "your device is a pollux and this rom is for pollux_windy" error and assumed I was wrong. I downloaded the pollux version, and flashed it. That was the dumbest thing I did. I booted and immediately started looping at the cyanogenmod screen.
3) I attempted to troubleshoot by flashing firmware and kernels through Flashboot. It made it worse and now I cant get into recovery at all.
Here is the positives
I can connect to the device through Flashmode and Fastboot.
What should I do next to remedy this situation?
TheShackSpecialist said:
Hi everyone,
I would like to preface with I made some very stupid mistakes late last night/early this morning. I decided at around 11pm I was going to root and install a custom recovery on my SGP311. I followed this guide exactly to obtain root and recovery and it worked PERFECTLY.
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Then the mistakes started happening. First mistake I made.
1) Instead of backing up everything in recovery I just Wiped everything. I deleted cache, davlik cache, system, and data. I thought at the time no big deal ill just flash a rom.
2)I decided to flash a CM nightly and I got the "your device is a pollux and this rom is for pollux_windy" error and assumed I was wrong. I downloaded the pollux version, and flashed it. That was the dumbest thing I did. I booted and immediately started looping at the cyanogenmod screen.
3) I attempted to troubleshoot by flashing firmware and kernels through Flashboot. It made it worse and now I cant get into recovery at all.
Here is the positives
I can connect to the device through Flashmode and Fastboot.
What should I do next to remedy this situation?
Click to expand...
Click to collapse
I just quickly read your post from work but since you wiped it and can no longer boot your tablet...just flash back a stock FTF with FlashTool and your tablet will back to full stock...you'll have to re-root obviously. Hope this helped... :good:
Crash338 said:
I just quickly read your post from work but since you wiped it and can no longer boot your tablet...just flash back a stock FTF with FlashTool and your tablet will back to full stock...you'll have to re-root obviously. Hope this helped... :good:
Click to expand...
Click to collapse
I'm downloading the FTF right now, Ill let you know how I make out so that people can see the resolution!
*EDIT* IT WORKED!!!! I missed the simple solution because I am so tired right now. But my tablet is working which is the important part THANK YOU!!!!