Hey everyone,
I'm sorry if this question has been asked before. I have looked but can't find a definitive answer.
I needed to unroot my Nook because I could no longer download books which I purchased online. First, I did the factory reset. I was successful but could not complete the registration process. I got to the part where it asks for my email and password, and I always get 'Sorry we're having trouble setting up your NOOKcolor. Please shutdown the device and try again.'
I called Customer Service- what a joke. They determined, after almost an hour on the phone, that it was a deregistration issue on their end (I did it on my end as the 2nd step of the factory reset).
I thought that maybe it wasn't competely unrooted, so I did another reset by flashing the latest version of CWM and a stock zip file (followed Huskermania's video). I ended up having to use 1.0.0 stock because CWM determined that 1.0.1 and even 1.3 stock files were 'bad'. I got a boot loop at first and then it automatically downloaded updates. The Device Info screen says it's 1.1.0.
Still can't reregister after chatting with a 3rd rep online and 5+ attempts to deregister on their end. Has anyone successfully gotten BN to replace their device while having this problem? I did not tell them I was unrooting, just that my device froze during use. I hope I don't end up with a paperweight!!
Related
G-Tab with TabnTab
Right out of the box... it would not boot. The Viewsonic splash came up... then the "G" Tab splash... then screen went dark. Pressed the Power button to turn it off - and after 3 attempts to start, I got the TabnTab splash and the thing started. After running battery down, turned it off and when tried to boot... same thing -- only worse. After dozens of tries, nada. Finally did the Power + and On/Off and reset to factory. Did this a couple of times during the day as the problem reoccurred.
It's finally running somewhat... keeps going into some deep sleep mode that requires a reboot -- and then more of the same... the latest attempt how has the TabnTab splash up... but it is "running" a LONG time.
I left a message at the dump tech support number -- after some lady answered w/o even saying a company name. I'm not holding my breath for a return call.
I'm a complete newbie... but has a slight background with other OS'... so if there is something relatively "safe" to fix this... send your suggestions.
I do have a 8GB SD card in the machine.
Thanks in advance for any help...
Follow this link to all the info you need to install a new os or just install cwm to clear cash and factory reset.
http://viewsonic-gtablet-for-dummies.webs.com/
Simple easy to follow instructions.
Good luck
Boot Problem
Mine does the same with build 4349, and has done it since 4349 was released.
I talked to "Ken" at G-TABLET Support, and he said my tablet just needed to be re flashed in a way that only the "factory" can do it. He issued me and RMA and I am sending him the unit tomorrow.
I you want more info Email me at [email protected]
You might also want to try an SD repartition (but you'll need the 1.2 version of clockworkmod for that) - the gtab for dummies site has the link.
You could RMA it and get something just as bad, so I wouldn't do that quite just yet. Usually we try things in this order, before we give up completely:
- Wipe data (which you already did)
- Re-flash the ROM. For 4349, there are ways to do that, as well as older stock ROMs.
- SD repartition, via clockworkmod. This actually solves a LOT of issues, so I would definitely attempt it.
- Re-flash with nvflash (the last ditch effort).
Onefrink said:
Mine does the same with build 4349, and has done it since 4349 was released.
I talked to "Ken" at G-TABLET Support, and he said my tablet just needed to be re flashed in a way that only the "factory" can do it. He issued me and RMA and I am sending him the unit tomorrow.
I you want more info Email me at [email protected]
Click to expand...
Click to collapse
Probably either an SD repartition or nvflash is my guess.
Good luck!
Going RMA route
Well, I did everything but the ROM and Kernel mods... and it worked for a few hours.... but after turning it "off," it went back to not booting completely.
I finally got a response from the 3rd-party support company ("Ken" -- who signed his email "Joe" -- go figure....) and he promptly issued a RMA when I told him... "It wouldn't even boot right out of the box...)
Kind of funny... U.S. Merchants is in freaking Beverly Hills, CA! "Biz must be good!"
I have a 80 G9 (16GB) . It came with 3.2.79, I updated to 3.2.80 when it came out.
I successfully rooted 3.2.80 using information from this site.
This weekend I tried to update to the new 4.0.4. The update seemed to "hang", and I ended up forcing a power-off.
I subsequently used the recovery menu to do a full system format, and then tried to reinstall the 4.0.4 firmware - I've tried this a few times and each time it *seems* to be successful. After copying the AOS file to the device over USB, and selecting "ok", it says to leave the USB connected, a progress bar winds its way across the bottom of the screen, and then it reboots.
However, each time when it tries to boot, it just sits at the animated boot logo and never proceeds further. I've even tried letting it sit overnight - when I checked it in the morning after allowing it 6+ hours, it was STILL just sitting there rolling that bright bar across the "ARCHOS" logo..
I've tried to go back to 3.2.80, it gives an "update failed" on that every time I try.
I did the "remove developer edition" in the recovery menu, thinking perhaps the official firmware was balking on a 'rooted' device. Reformat, recopy AOS file, reboot, still no cigar..
I tried downloading the AOS file again, no luck..
Am I now the not-so-proud owner of a flat shiny brick? Is there some other procedure I can try? Has anyone else experienced this?
ANY advice or suggestions will be greatly appreciated.
If anyone needs more details or other info just let me know.
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
gen_scheisskopf said:
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
Click to expand...
Click to collapse
I've already done 2,3,4 several times. I managed to get a hold of someone at Archos that said that the file gets validated when it goes to update, and I'd get an error if it was corrupt. It doesnt give me an error there, it accepts the file.
As I'm currently on a slow hotel Internet connection, does anyone have an md5sum or sha1sum of their ICS .aos file I can use to validate mine against? (Annoying that Archos doesnt include a hash on their site)
Update .aos file is digitally signed (this also includes checksums of contents). If signature check fails recovery will not flash it.
My guess is that you'll have to give tablet to service unfortunately
tapatalked from Desire
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Megadave123 said:
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Click to expand...
Click to collapse
I cant believe you got through to support. I have been trying for the best part of 3 months and got no reply. I am new to XDA since I recently got a HTC Sensation. Saw that we have this section here for Archos G9s. Got my ''broken'' one out of storage and rooted and flashed it with a custom ROM. And it works again. Surprised since I had the exact same issue you got but I was not rooted when updating.
Hey guys, I rooted my galaxy 10.1,(Model Number:Gt-N8013, Kernel Version:3.0.31-813049) but after the rooting process, ( I used KingoRoot) I immediately went and unrooted my tablet, and everything went well, it said i successfully unrooted it, but after I restarted my device, I tried to access my google playstore, but it told me to log into my google account, confused, I put in my log in information, but it said, "Couldn't sign in, can't established a reliable connection to the server", after repeatedly trying to sign in, I changed my internet, After reading some forums, it said NOT to do a factory reset, but i'm a noob. I don't know anything about "flashing the kernel", or like "flashing the rom", so being the ignorant fool like myself, I reset factory reset it, but after i did the deed, of course prepared, I lost everything (which really didnt bother me), I still couldn't sign into my google account, I emailed the KingoRoot software team and they said they thing was unrooted correctly. HELP!!!! Thanks, I will try everything.
TL;DR An unrooted device wont let me log into my google account.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Title is self-explanatory. I got locked out of my phone, so I went into recovery mode and did a hard/factory reset then rebooted the device. Everything was fine and well until the Device Protection from 5.1 kicked in and asked me to log back into my google account due to "unauthorized reset". I cannot access that google account anymore; I only created it for this phone and I never wrote down the password. I tried every password recovery option. I am COMPLETELY locked out of my phone, AND I deleted all my data for no reason. Grrr.
I read somewhere that since DP wasn't intoduced until 5.1, flashing the phone back to 5.0 would circumvent the entire problem, making it a nonissue. What I need to know, is how to do this in download mode. Please tell me it's possible. I'll try anything at this point; the phone is already a paperweight so any idea is a good idea.