Related
Hello, im SO desperate...
I rooted my Droid X a while ago, and just decided to flash a custom ROM yesterday.
I tried ApeX; worked great. Buy it reminded me of my rooted CM'd G1, so i wanted something else. I decided to try a bunch of ROMs so i could make an educated desition.
Needless to say Bootstrapper worked great.
I tried Fission, then, DarkSlide; GummyJar, Liberty 1.5 & finally, Tranquility.
I must say, the latter one is a bit too buggy for me.. For one thing, lock screen.. doesnt shoe the lock button, so you kinda just have to trust it'll unlock when you swipe your finger, and in most cases, it does... But it aint what i was looking for.
Ive decided i liked Liberty, for its easy to use GUI for customization.
Heres where the problem starts...
My device will boot into Tranquility just fine, but if i try to run recovery thru bootstrapper... uh-uh. Nothing happens, I guet stuck in the Tranquility boot screen (tranquility replaced the default M screen, as well as the animation boot, just like liberty)....
I tried using clockworkmod rom manager and i got the EXACT same results.
I tried formatting my sd card; nuttin... i read somewhere, someone said that "charging the battery to a full 100% worked for him"... it doesnt make any sense, but ive tried it.
I dont know what to do... i mean, my phone works fine, but i dont wanna get stuck with TRANQUILITY!
ive also tried unrooting and rerooting... uninstalling and reinstalling both bootstrapper and clockwork...
If i shut down and boot with the home+power pressed buttons, the phone WILL enter its recovery mode, ive already tried a "factory reset", and all i get is... THE SAME THING! Itll reset my Tranquility as if it were the first time i flashed it.
How can i flash another rom?
I read something about an SPL, but ive no idea what that is nor what to do with it.
Id appreciate your help...
Paul Suquet
First of all it is an SBF, and will get to that in a second, first try booting while holding just the volume down button with the power button. If that does not work, you may want to SBF. This is a process that erases all the data and system files and takes you back to how the phone was when it came out of the box, or 100% stock. After doing this you could root again and then install liberty. If you want a guide on how to SBF, then just Google it. There are many guides available
There is a thread here called getting into clockwork mod the hard way. You could try it before doing an sbf.
Sent from my DROIDX using XDA App
try turning ur phone off, plug it into ur charger let it do the charging animation and then turn it on, it should boot into recovery
Ok people, [SOLVED]
Good news people, i successfully recovered via Verizon's SPL.
Allow me to recap; i own a Mexican Droid X, known as Motoroi X. I rooted via one click root, and installed Fission ROM. Then i wanted to try ApeX, after that, i tried GummyJar, then Liberty, then DarkSlide, and finally Tranquility. I don't know if i did something wrong, of if this is a problem Tranquility has, but after Tranquility, bootstrapper woudn't boot to recovery... so, i wasnt able to switch roms. Tranquility booted just fine, but if i tried to boot to recovery (be it via Bootstrapper, or via ClockworkROM), i got stuck in the "tranquiliy boot screen" (not even making it into boot animation), so , i had to take the battery off, and boot regularly... Trouble is, I didnt lile Tranquilty (all my respect for all dva's but, Liberty 1.5 was my choice, and it is at the moment). I liked the easy customization it has. One of my friends decided on ApeX (he liked the idea of having a bit of Blur).
SO, what troubled me was:
(1) My phone aint from verizon. I live in Mexico City, and my carrier is called IUSACELL... my phone actually had a totally different version on it when i first got it. Ill give out the version it had from factory, to trigger search results towards this page; hence help the multiple people in mexico city who bought their Droid X device via this carrier... my Sistem Version was:
Version.3.0.15.MB810.Iusacell.en.MX
Ive attached a screenshot of what my "About Phone" looked like from stock.
Cant attach anything, due to being quite new to the forum, sorry about that.
So anyway, I, and one of my best friends (with the same phone and carrier... allow me to say, that in mexico, this phone is not commercially known as a DROID X, its called Motoroi X, buy as you can see by the version MB810, it is the exact same hardware you verizon users know).
Let me say that, my phone was able to keep all my carrier config (that is, PRL, VPNs and such). So, to all other Iusacell Motoroi X users; ROOT YOUR PHONE; AND RUN ANY ROM YOU LIKE!
(2) I heard so much about SPL, but no one could tell me what the heck that was... SO here it is, plain english; its just like doing a firmware update; or, like updating your bios... Let me call it "hardware formatting"... Just a way to get your phone TOTALLY back to stock... Now, this SPL i found, was for Verizons stock, (which had a lot more crap than Iusacell did...), but hell, it saved my @$$. Youll need an Ubuntu Live CD (i use Ubuntu as my daily OS, so... no need to do that), the SPL per se, your phone, and a micro usb cable (no, not a mini USB, we all know motorola did a trick on us and used this micro USB instead of the common mini usb... i suppose they saved some space).
Here are the complete instructions: (remember this will flash your phone, so, be sure to backup at least all the contents of your SD, and; even if there is a slight chance, remember that any of this thing COULD potentially brick your phone, i'm willing to help all i can; anyone out there, but dont hold me responsible, this worked GREAT for me, and it MIGHT not work for you).
Please note that most of these instructions are not authored by myself, i just made a few adjustments to thm and i wanted to make them publicly available to those out there who are in the same ordeal i was:
1: Download the Ubuntu image. It's an .iso file - this means it can be burned onto a cd/dvd. Do so.
2: Once the burn is complete, reboot your computer, set your bios to boot from cd/dvd if you have to.
3: Ubuntu's Menu will appear, select "Try" to boot into the OS without altering your current setup.
4: Download the .sbf_flash utility and the proper .sbf file (note that a file that starts with a period, means to linux, that it is a hidden file. The sbf_flash I got, dont remember where i got it from but it weighs exactly 24KBs. And the .sbf file i found is called "VRZ_MB810=_2.3.34_1FF_01.sbf" weighting 445,393KBs. Dont you dare change the name of these; as Linux doesn't recognise spaces as a character, so, if you changed all the underscores to spaces, Linux' console would not be able to "see" it. If you can't find it, post a reply in this forum, ill see the way of getting it to you.
5: Flash the image onto your phone:
Turn on hard recovery mode; turn phone off; press (and keep pressing): CAMERA + VOLUME DOWN + POWER. Until it comes on. You may have to release all three, and press again power (usually the screen is "blocked").
Now youre in hard recovery mode, and the phone will recognize the computer via USB; so... CONNECT YOUR PHONE VIA USB, duh!
Place the .sbf file to a directory (e.g. Documents)
Place the sbf_flash file into the same directory
Open up a terminal window
Change to the directory that the files are in. [cd] is the command you use; so if in Documents, type [cd Documents].
Ubuntu is caps sensitive, so you need to type the capital "D". If you type "ls" (the equivalent of typing "dir" on Windows Command, or DOS) it lists all the files in the current directory you're in, so type [ls], if you see the files, you're golden.
Type [chmod +x sbf_flash] (ignore brackets) – this command makes sbf_flash an executable. If you've been rooting your phone with ADB Tools you've seen this command before.
Type [sudo ./sbf_flash [name of sbf file, starts with 'VRZ_']] (once again ignore the brackets) – this command runs the sbf_flash file. 'sudo' is the linux-y way of 'running as administrator' in Windows.
It will prompt you for your password - enter it (if your in a Live CD; password is most likely "admin", with no quotes)
Your Ubuntu machine will hard format your phone. Youre probably used to seeing your phone itself perform the installation of a ROM, this is similar. But it aint your phone directly doing it; its Ubuntu... Glorious, faithful ubuntu.
Your phone will reboot, and youll be in a Verizon Stock Rom. You WONT be in the version i described before (but that version was lost since your first Rom...) Iusacell Mexico will work flawlessly... youll still have your telephone line working, and your data plan (if applies). All you have to do now, is run bootstrapper again (this time itll work), your phone is most likely still rooted. If its not, run one click root again; and run your favorite Rom.
Ive tried all roms and decided to keep Liberty 1.5, only downside ive found is; a) camera works, but stock software seems a bit buggy, and b) NO HDMI port. My friend kept ApeX, there IS an HDMI port on ApeX, but as far as I know, youll need to install Stock (Blurry) gallery.
It is a shame HDMI can only be used for picture and video taken from the phone, viewing... I trust sooner or later, there'll be a rom (or a paid app...) able to exploit the HDMI capabilities of the Droid X.
Forum admin: is it ok to publicly plug my twitter account for spanish speaking X users to follow me if they wish to? (Sorry for asking, violated one forums code before, dont want to do it again)
suquet.paul said:
Good news people, i successfully recovered via Verizon's SPL.
Click to expand...
Click to collapse
There, i got the screenshot attached.
Great to hear its working
[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?
I just got a brand new K1. Fresh out of the box with 3-3 pre-installed, I downloaded and used TimmyDean's permanent root tool, flashing a rooted 2-2 firmware. I then enabled the backdoor and ran all the OTA updates up to 14-14. This took several hours in all. I then ran the BusyBox and SU Tools install script. Everything was looking okay. I selected the choice to exit the script with reboot. The K1 turned off and came back on with the Lenovo logo, but, at the top of the screen was red writing:
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002).
It stops there and goes no further. No bootup.
Attempting to research the error, it seems this is not an error too many people encounter or know about, so my guess is that my only way of fixing this problem is to flash the whole thing over again from the beginning. (Unless someone here knows something about this problem. That would be tremendously helpful.)
Having already experienced what it took to go from 2-2 to 14-14 the first time with the permanent root package, I'd certainly like to shortcut it however possible. In this thread, http://forum.xda-developers.com/showthread.php?t=1404351 , TimmyDean posted a rooted 13-13 that we can start from. However, the link to the download file for it is Multiupload.com, and Multiupload.com does not seem to be up for me. Does anyone know where else I can go to try and download a copy?
I'd have posted directly in that Development thread, but, since I am an XDA noob, the forum system only allows me to post in this General section.
After experimenting with the "permanent root" package several times now, each time ending up with the "Unsupported menu option selected: 1" error after any OTA update, I have to believe there is an incompatibility between the K1 I have and the bootloader files in the "permanent root" package. I do not know if my K1 is recently manufactured and they are now doing something different with them that causes this incompatibility or what, but I felt I should warn you all that flashing the "permanent root" package could cause your K1 to not take official updates or to otherwise brick it with the "unsupported menu option" error. Perhaps the 13-13 package, which I don't have and can't test, didn't have this problem.
My serial number is CB1245XXXX. Manufacture date is "11/11/27."
I have now given up on getting root on my K1 and would just be happy to get it back to a working condition that can take Lenovo's OTA updates without bricking. I am currently trying these instructions and will update as to whether or not that resolves the problem: rootzwiki.com/topic/13877-guide-ideapad-k1-restore-to-mostly-stock-with-ota-updates/ (The forum software will not allow me to post hot links, so copy and paste that to browser.)
The rootzwiki procedure did not work to correct the problem. After any update, the tablet is bricked with the error. There are a few threads on the Lenovo support forum on this issue now, and there is no solution.
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Unrecoverable-Boot-Loader-Error/td-p/683633
I believe these old bootloader files will not work and will brick newer K1's, so my warning is:
DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
This might only apply to more recently manufactured K1's, but, since we do not know when this problem begins, it is not possible to know beforehand whether or not you will brick yours.
To be on the safe side, DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
Unfortunately, there was no backup option in the rooting packages, so I could not get a copy of the stock bootloader or any other files, if they are indeed of a different and newer variety. If someone has a recently manufactured K1, perhaps you can get those files and share them, because a lot of people are starting to see this problem now.
I have one with sn#1250xxxx, mfg dt 11/11/29. I wasn't even trying to root the thing. I happened during an OTA update. I tried probably all the recovery/rooting option out there. None of them worked. I have the tablet booting at lenovo screen. But I think you are right about the bootloader. If we can get the correct bootloader, we might be able to the the tablet back to life.
fix?
Has anyone come out with the fix for your issue.. I have the same issue . Used TImmy Dean's method.. and anything updating past the 02_02 (loaded from the tool I get the error... Anyone here have access to contact JimmyDean to ask him for help?
I see that he updated the tool to K1_A301_13_13_111209_US and maybe K1_A301_14_14_111209_US but all the links are dead.. anyone have a good place to download the files?
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
those are just OTs.. not image files.. If you don't have a compatable boot loader, you can't load those files.. We don't have a compatable bootloader.. so this is why we need ver 13 of timmy dean..
rezapatel said:
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
Click to expand...
Click to collapse
Can someone who's getting this bootloader error send me a pm. I put together a stock 120109 update that may work around the issue and I need someone to test.
Was this issue ever resolved, I didnt attempt to root mine, only attempted to wipe it clean and got this..
No, no real resolution. What I ended up doing was NVFlashing one of khanning's ROMs, like this one: http://forum.xda-developers.com/showthread.php?t=1560441
I don't know what's going to happen when I have to update again, such as the upcoming Ice Cream Sandwich update promised by Lenovo.
*** SOLVED ***
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Psychlone said:
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Click to expand...
Click to collapse
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
gears177 said:
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
Click to expand...
Click to collapse
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
if your on the honeycomb bootloader simply flash a honeycomb rom and kernel no need to use afterOTA or anything else if i remember correctly
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
dibb_nz said:
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
Click to expand...
Click to collapse
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
gears177 said:
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
Click to expand...
Click to collapse
Yeh 2nd line of my post hc bootloader ics rom, and u correct use 3.01 buggy update,zip or stock update.zip I shoulda been clearer - thanks gears
Thanks guys, I really do appreciate the help, but I'm still having serious issues reverting back to HC.
I feel like an idiot, but I have to say that even though it seems so, I'm actually the owner of a computer repair business, have 28 years experience in PC/Mac repair, and have rooted and modded every android device I've owned (including some for friends as well) - all the way back to the very beginning with the D1. This, however, has thrown me for a loop. NOTHING with this A500 has been this complicated! Everything up to this point has literally been stupid-proof and I've actually been quite impressed at just how easy modding is on the A500...
Anyway...
Here's what's going on and what I've tried today:
I've tried unsuccessfully several times to get ANYTHING working on my laptop, but to no avail. Same story as last night, no progress whatsoever - however, I did note that with CWM 134, I was able to restore an earlier version of ICS 4.03 (Flexreaper R10 I believe) - but it wasn't easy... I ended up restoring the main image and then using parts and pieces (using Advanced Restore) from other saves to finally even get it to boot.
This clearly wasn't getting me anywhere, so I moved the entire operation to another computer - my main rig (also a Win7 x64 - in fact, I don't own a computer that's not Win7 x64)
Now I've got USB driver issues! I can't even install the standard USB drivers from Acer's website because the installer errors out saying that there's no version of Acer Iconia 3G Driver Install is installed. wtF? That's what I'm TRYING to do!
I did get a different USB driver installed - the USB Driver_Acer_1.06.1500_A30H_A500, but nothing wants to use it and Blackthund3r's APX Flash Util won't see it, AfterOTA won't use it, and it's basically useless anyway. AND I can't install the Acer_1.00.0524_A30H_A31H_A32H_A500_A501 drivers no matter if I've got any others installed or not.
In my device mangler, there is no device with an exclamation, and in fact, sees my Acer Iconia A500 under USB Serial Bus Controllers as "Acer Picasso USB Boot-Recovery Driver", only when it's plugged in. NO other instance shows up at all.
I'm actually at the point of trying to follow through with the EUU (dibb_nz's "last resort"), but vache's website is down and I can't download anything for it. In fact, there's nothing from that guide that has a valid link...
(http://forum.xda-developers.com/showthread.php?t=1632392)
So now where do I go? I understand IT really well, so you don't need to talk to me like a complete noob, but dang if I can't figure this one out!
If I can get valid links to all the downloads from the link above, I'd be more than happy to give it a go and see if that works, but I can't piece together all those things from random places. If either of you (or anyone else for that matter) has valid links for everything needed to follow the EUU guide, I'd be very grateful!
Any other advice would certainly be appreciated as well! I don't have to use either of these computers, but as mentioned, ALL of my computers have Windows 7 x64 on them. I suppose I could try one of my customer's computers for all this, but that's not morally right and probably something that I would prefer not to explore.
I feel as if I could get the USB drivers installed properly on EITHER machine, that I'd likely be in good shape. I think that's what my problem actually is on the laptop as well, even though they're all installed and shows as installed until I boot into any recovery - then I get the MTP Device Driver Fail. There's likely other Acer driver issues there though, since Blackthund3r's utils don't follow through for anything... everything just hangs. AfterOTA just hangs.
Advice please?
And thanks again for your knowledge!
Psychlone
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
dibb_nz said:
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
Click to expand...
Click to collapse
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
EDIT::
OK, so I'm really in bad shape here - now the EUU (PBJ20upgrade) comes back with the error:
Please download the newer image for the upgrade.
Current image version: Acer_AV041_A500_1,054.Acer_AV041_A500
New image version: Acer_A500_1.016.05_Com_GEN1
What now????
Psychlone said:
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
Click to expand...
Click to collapse
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
dibb_nz said:
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
Click to expand...
Click to collapse
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Psychlone said:
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Click to expand...
Click to collapse
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
THANK YOU!
dibb_nz said:
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
Click to expand...
Click to collapse
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Thanks again,
Psychlone
With what I went thru use Civs nvflash and rom and I'd stick with third cement until your safely patched and on ics.do all the wipes and follow instructions to the letter ...I'll check back in shortly
EDIT wtf "third cement" dang auto correct ... should read thors recovery
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
excellent news glad it worked for ya
Psychlone said:
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
Click to expand...
Click to collapse
if its referring to newer image then the data cable is connected!
and it will spit this error at you....
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
Click to expand...
Click to collapse
yup now you're cookin
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Click to expand...
Click to collapse
oh yeahhhhh!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Click to expand...
Click to collapse
nps glad to be of assistance -
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Click to expand...
Click to collapse
becoz then you'd have thousands of posts to look thru and no-one would bother reading it all....i try to keep my cpuid thread updated with things 'unbricking' but its too hard to put 'everything' in one post unfortunately
---------- Post added at 07:01 PM ---------- Previous post was at 06:48 PM ----------
Psychlone said:
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
Click to expand...
Click to collapse
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
dibb_nz said:
excellent news glad it worked for ya
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
Click to expand...
Click to collapse
CM10 is SLICK. Think CM9 on graphics steroids and you're close!
I appreciate your position more than most. I get a lot of enjoyment out of helping others as well - I've written overclocking guides for AMD systems that was written years ago, revised a couple/three years ago and is still used to this day, even though I've long since moved over to Intel's "dark side". I also participate pretty deeply in helping others at a couple PC hardware forums pretty much daily, even though that's my actual job - I own 2 computer repair businesses in my hometown, and with well over 20,000 computers to fix, I'm ALWAYS busy but still always find time to help others in need.
As for adding ***SOLVED*** to the title, I'd love to...but it won't let me. Perhaps it's because I don't have a high enough post count, or because it's reserved for Mods, but I can't do it.
Thanks for everything once again - it's quite refreshing to be on the receiving end!
Psychlone
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
You tried house of moto to fastboot flash 98.30.1? Sux they found a way to relock them...
Sent from my XT907 using Tapatalk
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
RikRong said:
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
Click to expand...
Click to collapse
@AndroidGreg
There's a line in the fastboot xml file with gpt_main0.bin (somithing really similar to that, been a while since I flashed it...) and all that's necessary is removing that line and flashing the fastboot with rsd, or just manually flash the fastboot skipping that partition, either or will work and fix the problem. Even though the bootloader is unlocked, that particular partition IS still controlled by securtiy and is blocked from downgrading -- luckily for us the partition table never changed between rom versions so it's perfectly safe to flash or not to flash it.
I've never flashed with RSD, but IIRC, there's also two more lines in the fastboot's xml that need to be removed for it to properly flash. I've only flashed my phone with moto-fastboot from linux and used MythTools from windows -- MythTools is an interactive script for the Atrix HD to flash stock fastboots, root, unlock the bootloader, flash a custom recovery, boot logos, and soon different radios -- Similar to Mattlgroff's tool.
The Atrix HD has the exact same issue with that partition.
download the sbf file from http://sbf.droid-developers.org/phone.php?device=5
install these drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
connect the phone in fastboot mode.
now extract the "fastboot_rsd.zip " to a folder.
extract the contents of the downloaded sbf/xml file into the fastboot_rsd.zip folder
execute "flash_fastboot_erase_userdata"
worth a shot.
always works for me..
good luck.
RSD does not detect the phone at all, only the quick utilities did and they failed. Verizon overnighted my new phone and its here already, not unlockable im just gona root and keep it for a while till I switch to strait talk with the nexus 5, I cant afford $100 a month anymore anyway.
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
Click to expand...
Click to collapse
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
RikRong said:
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
Click to expand...
Click to collapse
Exactly. The Atrix HD gives us this error if we flashed the stock Mexican firmware (our latest) and try to flash anything below it, or the Bell firmware (2nd newest) and anything below that, and so on and so forth. All that's necessary is to remove the gpt flashing line and go again....just like we have to remove the oem lines from the fastboot xml.
First time I had that error, I went WTF (the first flash after unlocking my bootloader if ya'll's curious), knew that GPT is a partition table from grub experience, figured that the partition table has never changed since stock ICS roms, removed the GPT line, flashed ICS, and I was happy.
I'd love to be able to combine all the data, system, cache, and any other partition that don't need a fixed place (like modem, etc) and be able to use ZFS or BTRFS volumes to maximize the amount of storage we can have -- I've always wondered why they don't do something like that already...
Ok 3 computers 1 xp and 2 windows 7, nothing, mac nothing, even made a factory cable because the battery just got to low, nothing, no computer will detect it, using any of the 3 motorola branded usb cables plugged directly into the laptops. Now the utilities from matgroff and the other guy (cant think of his name but he made the 2.0 utility) will not even try to flash the phone they say please plug a phone in that is in fastboot mode, I
Serious question, but have you tried Linux? My old Bravo wasn't detected by Windows (XP or 7, been 2 years now) after a bad RSD flash, but I was able to manually flash it from Linux (either Manjaro or Debian Testing). After that, to this day it'll flash with RSD, but it isn't detected properly. I still flash it, and almost everything else, from Linux because I don't trust flashing from Windows anymore. I made an exception recently to help with a tool and because my Linux partition was down for a month.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
Click to expand...
Click to collapse
I tried doing the exact same thing as the OP - factory reset to "stock" and then flash back up in preparation for KK, after using TiBu to save everything and using SafeStrap to make a Nandroid (very thankful I did). I ended up with the identical screen that the OP had, even stating that my previously unlocked BL had been apparently "relocked." For me, RSD Lite did recognize my phone (I updated RSD to the latest version beforehand), however it would not flash anything for me (the flashing process would start and then immediately say "failed").
See my post for the details and the solution I used: http://forum.xda-developers.com/showthread.php?t=2674431.
I was completely freaked out for a couple of hours until I stumbled upon bweN diorD's GPT partition fix. And then everything was fine for me.
Hope this helps anyone who falls into the same trap.
AndroidGreg said:
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
Click to expand...
Click to collapse
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
scoobaspeaz said:
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
Click to expand...
Click to collapse
@AndroidGreg, do you still have the phone?
Sent from my DROID RAZR HD using Xparent BlueTapatalk 2