Related
I've got cyanogen's optimized 1.5r2v3.4, and Recovery Image v1.2. I have read half a dozen threads on how to get your phone back to stock, including this one http://forum.xda-developers.com/showthread.php?t=491350, but I have a unique impediment.
The screen on my fiance's brand new phone completely stopped working after less than a week. I can only interact with the phone via adb connected to the recovery shell, so I have to be absolutely sure it goes perfectly the first time (since the odds of having a working recovery shell after a bad flash are slim). I have not changed the second splash screen, so by what I read, all I need to flash back are the SPL, then the DREAIMG.nbh, correct?
How do I do update.zip for flashing the SPL via the recovery console? I had no problems getting the phone from stock to rooted, followed the instructions step by step. But now that I have to try and figure out how to do EVERYTHING via adb ONLY, I read the most simple instructions and find myself going 'wait, what?', trying to figure out how that would work done entirely without being able to see feedback on the phone screen.
Use the DREAIMG.nbh and recovery.img for rc29 stock its in the rooting thread.......load up the phone in fastboot (camera and power button) the phone will recognize the files and tell u to hit a button....you hit that whopping one button and wait 2 minutes and you'll be back to stock rc29 where then you can reroot or just sit around waiting for Over the air updates from t-mobile to catch u up to cupcake.....honestly i don't use fastboot EVER but i always keep those two files on my sdcard so if i have a problem i just run it and blast back to rc29 and start over......hope u see this before its closed in 5 seconds for not using the SEARCH BUTTON
sorry just use just reread ur post...use the DREAIMG.nbh it has the old SPL built into it
i'm not sure how this would be done, but what iwould suggest is put the original SPL on the SD card as update.zip and the DREAIMG.nbh on the sd in the root of the sdcard, then reboot holding home, give teh phone 5 minutes to boot into recovery then press alt+S wait 10 or more minutes to let it flash and then press home and back to reboot, or in adb shell type reboot bootloader, give it a minute or so and then press power, wait 30 minutes and hit the trackball, if after hitting the trackball the phone vibrates then it went fine, if not then the .nbh didn't flash
tubaking182 said:
i'm not sure how this would be done, but what i would suggest is...
Click to expand...
Click to collapse
Yeah, that sounds like a plan. Thanks, I just really couldn't get my head around how I could possibly do this!
Can I ask why you are bothering? Are you afraid they will hit you with an out-of-warranty fee because it's rooted? They won't, I've returned a first gen G1 that had the issue of the screens ribbon cable coming unplugged (sounds like your problem) and T-Mobile sent us a new one no problem.
GenericNode said:
Are you afraid they will hit you with an out-of-warranty fee because it's rooted?
Click to expand...
Click to collapse
Yeah, actually. *shrug* it doesn't seem to have flashed back to the stock image anyway, so I guess it'll have to go back in whatever form it's in. Hopefully you're right and they don't care about custom images.
heldc said:
Hopefully you're right and they don't care about custom images.
Click to expand...
Click to collapse
They sure didn't care about mine.
And besides, whether or not your phone is rooted isn't in the check-list of questions a CSR is supposed to ask before accepting a return, so how could it be your fault?
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked(which i found odd since the demo phone in my t-mo store is rooted and running dude 1.2). as long as it doesn't have a custom splash screen it should be ok.
also you could always grap the OTA update and edit it in some way(resize a pic and put it back) and then resign with testkeys and rename update.zip then the only thing they'll see if they really look at the phone is a bootloader that's been changed and recovery, but the rest will look like their stuff.
tethering caused double post sorry
tubaking182 said:
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked
Click to expand...
Click to collapse
No way. Sweet. I haven't seen this policy yet, but I never pay attention
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
tubaking182 said:
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
Click to expand...
Click to collapse
When you talk to those people you have to sound as newbish as possible, that's probably why they kept asking if you rooted it.
trust me i sound like a freaking idiot. "they told me on the t-mobile forums to press the homekey and turn the phone on and i got a triangle with an exclamatioin point, and then i pressed alt+w and after a few seconds my phone rebooted but the screen is always sideways when i open apps." i act like an idiot and they replace it. the only problem i had was when the guy asked what my favorite thing about the phone is, right after i told him i didn't know what root was. i just said games cause that's all i could come up with
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
I have to have screwed the pooch pretty bad, I'm caught in a loop at the HTC splash screen and then it reboots. Any helps would be very much appreciated. I know I did something, I just don't know what.
you dont give enough info..i mean what steps did you follow? when did things go wrong? what step was it? what was the last thing you did?
pull the battery and then boot into recovery (hold volume down+hold power)
EVOKeith said:
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
Click to expand...
Click to collapse
Flash the RUU from the "All roms" thread
Everything was fine after the root guide I followed (the idiot-proof one). When I attempted to do the Nand access portion something went wrong because I got an error that the SD card was blank or had an unsupported file system. The only choice I had was to format the SD card.
Now, when I attempt to install a downloaded .zip from recovery it acts like it is going to install but goes right back to the menu after a few seconds. IF I tell it to reboot then I get caught back in the splash screen rebooting over and over again.
do a full wipe and cache wipe, reboot and see if that helps before you go any further. you do that when you boot into recovery. that will likely fix it. If not post what it does then.
What happens:
When I boot into recovery the first bit is that it tried to load PC36IMG.zip, I get the following:
Main version is older!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I selected No and went into Recovery. I wiped all data and cache and rebooted. Once again the white HTC EVO 4G screen comes up for a few moments and then the phone powers off and restarts with the same screen over and over. I'm at a complete loss.
bumping for help
is that pc36img.zip the rom that you initially flashed that worked or is it a different one that was part of the 'nand access portion'? I figured that would be from an 'update.zip', but I barely know what I'm doing outside of the well detailed guides.
If it isn't the rom you flashed, try loading that rom back on there. I hope you have another device you can read/write micro-sd's from.
If it is the rom you flashed try flashing another rom.
...I'm a noob here too, but I'm on my second rooted/custom recovered phone so I'll help as I can.
Did you make a nandroid backup?
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
EVOKeith said:
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
Click to expand...
Click to collapse
Lucky for you that none a single rep I've ever spoken to in any Sprint store has any idea about anything whatsoever. I returned a Samsung Moment that I never bothered to restore to stock...hey turned it on, it booted up with a "Hacksung, XDA developers" screen, proceeded to load up a (then hours old) 2.1 lock screen and said "Okay, it still works", didn't check to see if I had kept the memory card in or even re-packed the charger and gave me a refund for everything on the receipt, even things I didn't have in the bag.
...another time before that I was asking about the Android 2.1 update and when it was being rolled out to which the sales rep stood up, turned around and yelled "Bobbyyy....what's an android and when do we get one in?"
Though I'm sure there is a way to bring your phone back...perhaps check in on the thread where you got your rom and see if anyone else has had such issues, give all the details you can in the order in which they happened.
If you can still get to the hboot screen try the zip posted here using the instructions here
I've been ROM-hopping, trying Synergy, Alliance, Myn, and several others. On the last one, MikG 2.3, I had it loaded up and working fine. I started installing apps from the Android Market. That, too, was going fine, until it suddenly rebooted in the middle of an app download/install.
It went to the white screen with HTC EVO 4G on it, and then went black, then back to the white screen, over and over.
Six hours later, I'm still stuck in the loop. To make matters worse, I accidentally lost root (I see "S-ON" at the top). So now I'm stuck without root until GB is rooted successfully, which hopefully isn't tooooo far off in the future.
But that's the least of my concerns. I would be extremely happy with a stock install of any sort at this point, but I can't get anything to load. No recovery, no ROMs, but I can get into HBOOT so I'm able to try to load any PC36IMG.zip files. The last one I tried was the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed.zip" (renamed to just PC36IMG.zip, of course). It appears to load just fine and in the end says "Update Complete... Do you want to reboot device?"
I choose yes, it reboots... and we're back in the loop. I have no idea what to do or try at this point. Any help anyone can provide would be greatly appreciated! My next step is to take it to the Sprint store, but that's over an hour away and will have to wait till the weekend.
Thanks everyone!! If you need any more information, let me know. Believe me, I'll be monitoring this thread closely!
/Kevin
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Papa Smurf151 said:
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Click to expand...
Click to collapse
Yeah, I tried. I have several SD cards of varying sizes (4GB, 8GB, and my primary 16GB). Formatted the 4- and 8GB ones and tried from each, but no go. Thanks for the try though!
/Kevin
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
trim81 said:
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
Click to expand...
Click to collapse
Just did it and the process went well, said it was successful... but it's still stuck in the same loop. I'm thinking the phone is beyond repair. Thanks for trying, though. It really looked like it might work for a second.
/Kevin
what was the app?
That's what I want to know and how do you get accidentally to S-On?
Put the phone in a refrigerator ... as crazy as it sounds, it might be the infamous overheating issue.
Put in refrigerator, for about 5min
The app was "Kid Zone" (Zoodles), but I'm not blaming the app by any means. I've used it for a long time, it's highly-rated in the market, etc. I'm sure it's just a coincidence.
As far as getting back to S-ON, I think it must have been when I flashed the stock recovery. I was flashing so many things out of desperation that I can't swear to that, but I'm pretty sure that's what did it. Now that it looks like I'm heading to the Sprint store tomorrow, I guess it's a GOOD thing it's back to S-ON. Heh.
Pretty sure it's not heat-related. My phone was off all night (since it's not usable) in an air conditioned room, so it's cool to the touch. I tried the RUU process again with the same results. (I'm not sticking it in the refrigerator, because I'm afraid of activating the water-damage sensor -- I don't want any excuses from Sprint when I bring it in tomorrow!)
Appreciate the help!!
/Kevin
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
HipKat said:
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
Click to expand...
Click to collapse
I hear ya. I haven't run into any techs at my local stores that are knowledgeable about this kind of stuff. (I know others have, so you never know, but I have yet to see one.)
/Kevin
To conclude this: I went to the Sprint store today where they assured me they would reload the software but it would take 1.5 hours. I came back 1.5 hours later... and they handed me a new (refurb) EVO. They said they weren't able to load anything on the phone.
So, no surprise with the outcome there. I was fairly certain they were going to have to replace the EVO, and they did.
Thanks to everyone who tried to help, but it was just beyond help!
/Kevin
I had that same problem with my phone back in November. Continues boot loop. Finally, having boot loop for 8hrs, I took it to Sprint and they replaced my phone. They called it a power cycle issue. $35 new refurbished phone works well. Never had a problem since.
tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?
Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry
ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great
I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....
buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk
still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ
Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...
Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region
hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622
My Glacier has started booting a screen with three skateboarding Androids. Per another thread about this problem, I've downloaded multiple PC15IMG files and have tried booting into the bootloader with VolDown + Pwr, none of which have worked. I've tried multiple SD cards, none of which work. The LED also blinks orange when the phone is on.
I haven't really been able to find any consensus about this problem after googling besides using the PC15IMG.zip to restore, which I can't. Any help?
Umm, make sure you named the file PD15IMG.zip. If its not named that exactly, it won't work. Sounds like the issue.
http://forum.xda-developers.com/showthread.php?t=1476745
Use this like to get your PD15IMG.zip. I suspect that you were using roms that you had to flash in recovery instead of the stuff that you flash in bootloader. Don't ask me the difference because i don't know.
My bad, I did name it PD15IMG.zip, not PC. Also, I got the .zip from the mentioned thread, so it's not a recovery zip.
Well, what does hboot say when it scans for the file?
estallings15 said:
Well, what does hboot say when it scans for the file?
Click to expand...
Click to collapse
That's the thing, it doesn't. All you see on bootup is a plain white screen with three skateboarding Androids centered. None of the version info up top, no menu, and nothing regarding scanning.
Uuuh, it sounds like you phone is screwed.
Anybody else want to chime in on this? Where is Jack_R1 (or whatever) when you need him? Lol
Uh oh, this doesn't sound good. If anyone has advice about getting out of this weird bootloader limbo, it would be much appreciated.
Is it booting straight to hboot? my moms phone does this and the only way I can get it to boot it is to do fastboot reboot in cammand prompt.
In her case it just sits in hboot, and volume controls don't work and it doesn't scan for.the pd15. But for whatever reason it boots up when I do that
3 white scateboarding Androids in the middle aren't HBOOT. Looks like the bootloader doesn't load properly, in which case, indeed, you're screwed.
Sorry, I take a break from forums from time to time
Jack_R1 said:
3 white scateboarding Androids in the middle aren't HBOOT. Looks like the bootloader doesn't load properly, in which case, indeed, you're screwed.
Sorry, I take a break from forums from time to time
Click to expand...
Click to collapse
Here to save the day again. Thanks for dropping by.
More like - to deliver bad news Not my favorite task.