Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.
In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.
Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..
The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app
I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app
Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.
are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!
Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app
Related
Hi Guys!
I know, some people will hate me now because I opened a thread for that.
But the search did not help for chinese FW, so I wanna give it a try here!
I just got a chinese Atrix with the following information in settings:
System Version:45.2.14.ME860.ChinaRetail.en.CN
Android: 2.3.5
Baseband: BP_N_01.41.00R
Webtop: Unavailable
Kernel:2.6.32.9-00007-g9570040 [email protected]#2
Build number: 4.5.3-118_OLY-14
Superuser is already instaled and when i bootup the phone, "Unlocked" is shown in the upper left corner!
What I wanna know:
Is it rooted (yes of course, I think!)
Is the bootloader unlocked (never had a phone that says "unlocked" when booting up with an unlocked BL...)
Can I just flash CM9 for example or is there anything I should be aware of?
Sorry for beeing an Atrix n00b =)
And thanks for all suggestions!
The Unlocked text on the Motorola screen is an indicator that your device's boot loader is unlocked. I would recommend referencing the NOOB threads covering rooting and flashing ROMs for the rest.
Thanks for that!
But it's already rooted (super user is installed and I tried apps that need root).
What I wanted to know is, if I can just flash new roms or do I have to be cautioness, like many threads say: Don't flash back if u use build nr. xyz...
muhski said:
Thanks for that!
But it's already rooted (super user is installed and I tried apps that need root).
What I wanted to know is, if I can just flash new roms or do I have to be cautioness, like many threads say: Don't flash back if u use build nr. xyz...
Click to expand...
Click to collapse
Check if you have cwm recovery installed. If not install the latest and flash the latest version of cm9 through cwm
Sent from my MB860 running Jokersax's CM9
unlock is needed for flash custom ROM in CWM
weiyin5210 said:
unlock is needed for flash custom ROM in CWM
Click to expand...
Click to collapse
Did you read the first post?
"Superuser is already instaled and when i bootup the phone, "Unlocked" is shown in the upper left corner!"
Click to expand...
Click to collapse
Atrix 4g from Taobao 19 Apr.
Hi muhski,
I am in the same situation.
I just buy Atrix 4g from Taobao and receive it on 18 Apr.
When Gapps is not installed, I was very disappointed and call them to complain.
They ask me to send it back but I tried to get to know the phone more.
System Version:45.2.14.ME860.ChinaRetail.en.CN
Android: 2.3.5
Baseband: BP_N_01.37.00R (Yours is BP_N_01.41.00R)
Webtop: WT-1.2.0-163_11 (Yours is Unavailable)
Kernel:2.6.32.9-00007-g9570040 [email protected]#2
Build number: 4.5.3-118_OLY-14
Superuser is already installed and rooted.
Booting up the phone, "Unlocked" is shown in the upper left corner!
If you do a thorough search, you will know that to start to flash cm9, you need:
1. bootloader unlocked, machine rooted
2. clockworkMod (cwm) flashed
3. then flashing CM will be easy. Just put some zip files in root of sd card and then run ClockworkMod.
See but dun follow the cwm installation:
wiki点cyanogenmod点com/wiki/Motorola_Atrix_4G:_Full_Update_Guide
Your Atrix and mine are probably in stage 1.
Last night I tried to follow the old instruction in the link above to flash cwm.
But the fastest manner to run cwm is by installing Rom Manager instead.
Rom manager is super easy to use and I manage to get it to flash cwm in my Atrix. With cwm running, I boot from it and get cwm to flash Gapps in my Atrix.
Now I got cwm & gapps both running very well.
All my gmail, gPlay, gCalendar, gMap..... running quite well.
The next step I can make is to save cm9 zip files in the root of sd card and run cwm to flash it.
I am currently stuck like you. I wan to flash ics thru cm9 but worrying bricking Atrix. Moto may come up with ics for atrix real soon so I dun know if I want to wait.
Good luck
Sounds like you are on the right track. Once you have cwm flashed you can reboot, hold the volume down rocker as the phone reboots. Once you see another option under the "unlocked" text you can then tap the volume down rocker until you get to the recovery option, then tap the volume up rocker. This will bring up a whole new menu that you can use to clear cache, Dalvik cache and factory wipe.
When I flashed my first ROM I was very nervous that I was going to ruin my phone, but I have flash many ROMs since then some with gapps included and some that require you to flash gapps seperate. I have enjoyed many ROMs and have not run into any problems I couldn't fix by rebooting into recovery.
Good luck and enjoy the ROMs of your choice!
Hey guys!
Thanks for all your help!
First, I forgot to say, it's not the first time doing this stuff xD
It's my third android phone, so all is very similar to the Defy, but still I like to ask one time too often instead of crying about a bricked phone =)
What I have done now: Because bootloader was already open and cwm was already insalled, I could skip the hardest part and jumped right into flashing.
Ok, not really, because I updated cwm to romracers version (not really necessary, but everyone suggested it...)
Right now I'm running Neutrinos CM7 mod because other mods gave me randome reboots
First problem was: My Radio version does not work with this rom! "About phone" says "Baseband unknown".
I went crazy bcs I thought I got a broken phone from taobao, but smart as I am (hrhr) I made a nandroid backup before, flashed it back, and tadaa, with the old backup I had network connection....
So I googled a little more and found out about the Radio-Thread here.
Now I'm testing all the radios to ind the best one...
Good thing is, network connection is working now, bad thing is, it sucks my battery dry like a h**ker that gets too much money
@qqqqaa: does your radio version work with CM9?
Maybe I should try yours...
Can any of you with the Chinese ROM confirm that call recording works on your phone and if possible, do share a dump of your ROM.
I bought it and it appears to have ICS because the Android version is 4.0.3 but that is all I really know right now. I expect that it was never updated OTA though because the guy I bought it off had it for 2 months and he was not the one who rooted it. I was going to leave it as is because I bought it for my 10 year old daughter...but the camera takes very blurry, kind of grainy looking pictures.
I am not afraid to root because I had a Samsung Fascinate and I loved the custom roms I downloaded to it. It had been over a year since i had the Fascinate so i am a little rusty when it comes to all if this. My problem is not knowing where to start with this A500 because I am unsure what has already been done to it.
The guy who sold it to me said he did a factory restore, but when I ran the check root app it does state that it's rooted and I figured it was because there is a app called superuser on the device. I don't know what kernal it has. I don't know if it has a bootloader and/or the version number. I don't know if it has CWM and/or the version. number.
What is the best way to proceed? By the way, the tablet is very clean with absolutely no scratches anywhere. Not a bad buy for $175 with a leather case...
Setting > About tablet. That should tell you quite a bit of info about it no?
download the acer recovery app , it will tell you what Bootloader you have and what recovery
Thanks for the replies! When I get home I will check. I don't want to brick the thing. I ordered a micro SD today and I will get it in 2 days so there is no hurry for me to proceed. Is it worth it to keep it rooted? Is the OTA ICS good enough? I don't think my daughter cares if the tablet is overclocked but if the roms are much better than stock than I would keep it rooted and then download a preferred rom.
Vintage144, in another post you specified that there is a Acer recovery beta...will I need that or would I just get the one from google play? Also when I find out which version of recovery and bootloader I have...I am not sure what to do with the information. Could AfterOta help me accomplish what I want if my goal is to try and fix her camera issue...either by going back to stock or updating the kernal and rom.
I don't want to seem like a noob but my only rooting experience was with my Fascinate which I did everything from stock. Now that I am not coming from stock, I am unsure where to go with what I have. It's like trying to get to a goal but not sure what step to start at. If I was starting from stock I could follow some of the threads here but it's not stock.
What info will I need to post here to let you guys know what is in my A500? I know that the Android version is 4.0.3 , what else will I need to post?
well the beta copy I believe is at thors tegra forum , but its by euclids brother (thats his name on xda) anyway if you've upgraded your BL it will tell you version you have and might give you accurate Recovery as well, if the device is only for your daughter and she's too young to really do anything I would stick with a stock rom and realistically I would upgrade the boot loader , why be left behind?
Theres no reason to root if you dont plan on doing anything major with it,that being said you wont be able to get a newer Boot Loader or custom recovery without it, and custom recovery is well worth the effort!
You guys are the pros so I will take your advise. I don't mind it being rooted and if there are some really nice roms I expect my daughter would like the different looks...it would seperate hers from others.
Android
4.0.3
Kernel version
2.6.39.4+
Image version
Acer_AV041_A500_RV16RB02_WW_GEN1
Build number
KJY2010lcylicious
Anything else I will get when I get home.
I would like to know how to get through all this in case I decide to get myself a A500 it's a really nice tablet.
Okay
Recovery Version: Revamped for Iconia 3.16
Bootloader Version: 3.01
With all the above information what would be my next step?
Sorry
Recovery Version: RA Revamed for Iconia 3.16
Damn auto correct!!!
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
ultramag69 said:
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
Click to expand...
Click to collapse
Probably want to hold off on flashing roms a second.
He's running an HC Bootloader. I'm 99% sure of this. Reason, RA Revamped 3.16 doesn't work with ICS Bootloaders. So you can install an ICS Rom, but, it has to be an ICS Rom for the HC Bootloader. And the performance under HC BL is not near as good as ICS BL.
I would do like UltraMag mentioned as far as install steps and such. It's how we install roms.
Check this thread;
http://forum.xda-developers.com/showthread.php?t=1622425 (steps 1-6)
, and install an unlocked ICS Bootloader and a CWM 7 or 7.2 recovery. Then install one of the Roms made for the ICS Bootloader.
I know AfterOTA will do some of this for you. But this thread gives a good idea of what's going on.
Thanks for your help. I will be getting my micro sd card on Friday. In the mean time I will do a bunch of reading about the things you guys told me to do...again thanks a lot. I really appreciate the help.
I am the kind of person that really wants to know what I am doing...I don't expect all the answers, I just don't want to brick this device.
Forstir9,
Moscow Desire is a great dev on this board, his information about updating the bootloader is dead on. I recommend reading the entire OP in that thread, and then re-read section listed as Automated Flashing Tools, it really helps tremendously if you are a person familiar with root, but not extremely dynamic with making these changes.
I've rooted several BN Nooks and my A500 many many times and love it. I had the Honeylicious ROM that you listed prior to what I'm currently running. KYJ had a great HC ROM with that one! Personal preference currently for me on the ICS ROM is FLEXREAPER from Civato, poster of the referenced article from MD above, you can find that ROM info here: http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1 Lots of cool features and step by step directions, which are what UltraMag69 listed in their post. There are many many different options though and I recommend reviewing several and then settling in on one when you find the one that fits your (or your daughter's) preferences best.
If you enjoy doing this and playing with the tablet your daughter may not keep it and may end up getting something different, because you may have too much fun with it...good luck, have fun, don't be scared to try things and ask questions (after you read first), and most importantly BACKUP BACKUP BACKUP...
Good luck,
-DB
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
forstir9 said:
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
Click to expand...
Click to collapse
First off. Thanks for thinking I am the "God" of the 501". Yeah, I know it pretty well.
Second, Ultramag, is is one of my right hand men. So I suggest you heed his advice well. I always trust his judgement. Am sure he has puled my arse out of the wringer a few times. Well, maybe not, but you get the picture. Some of us on XDA, support each other. That's how it is. I just noticed the bootloader version, And being one who likes flashing experimental code, well, I noticed.
So;
1. ALWAYS make a recovery backup. Then, restore it to make sure it works. (lots of people don't do this and they get fubar'd later).
2. UID. Seriously. Ok, the link on the many ways to get it. You don't want to get it, well... your;e pretty much fubar'd
http://forum.xda-developers.com/showthread.php?t=1624645
3. He has the normal, and one with a kernel you can overclock. Your choice. Really, if you don't OC, then you run the same as the original. Please don't ask me the names of Civatos roms. The extreme will be fine for you. Just don't overclock it if you don't want to. Only difference is the kernel. Not the OS.
4. Yes.
5. For recovery, I would say CWM 1.7.2. Should work for you. 1.7.0 is also ok. Publick recovery is ok too.
6. Never ran After OTA. But hear it is good when you already have ICS.
Forget AcerRecovery. You will already have bootloaders and recovery installed.
MD
Know I'll probably get a bashing out of this but there's a V1.7.3 recovery on the site that must not be named (cough, tegraowners, cough) that supports the Aroma installer - on Thor's ICS rom anyway...
Just thought I'd throw that in too...
I am ready to do a backup...it's asking me what I want to backup...it has a (X) next to the following...
Boot
System
Data
Cache
Flexrom
Is this correct the way it is?
EDIT: ignore this post I didn't see page 2 -_-
Sorry that I didn't post this in Friday...but I really want to thank everyone for their help. It went very easy and it want too much different than my fascinate.
The camera still takes grainy pictures and a few apps has sounds issues but she really likes the rom a lot.
Thanks again for the help.
Hey there. I rooted my Vibrant successfully, but realized I left some important things out. I used this guide to root my Vibrant: http://forum.xda-developers.com/showthread.php?t=723479
The problems:
1) I can't nandroid (not that I need to, I only have 4 apps)
2) I would like to install either Miui v4 or CyanogenMod 9 but cannot as my recovery screen does not show me the options to do so (I only get the 4 options you normally would get unrooted, such as "Reinstall Packages"), so I'm stuck with the lame default homescreen.
3) I'm currently on 2.1-update1; should I upgrade to 2.2? If so, must I unroot to upgrade, and then reroot? And if this were the case, how do you unroot, and can I reroot using the same method in the link above?
Also, I was looking at this guide: http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery
and noticed the line "This guide assumes the Samsung Vibrant already has Android 2.2 build UVKB5 already installed on it."
Does this mean 2.2 is required to install the CWM Recovery?
Thank you.
I'm not sure how you don't have CWM recovery if you followed the guide as it is written. Maybe its because the 2.1 is updated? I would do the following and see if that's all it takes. You definitely don't want to update to stock 2.2 via Kies or anything of that nature.
Worst case scenario, we can have you Odin back to stock JFD. You'll be smooth sailing from there.
Search the forums and find the update.zip for CWM for our Vibrant.
Put that on the lowest level of your INTERNAL storage. Not your microsd card. For example f:\update.zip
Now go to your boring 4 option stock recovery and select reinstall packages. It will reboot to the same boring screen. Select reinstall packages again, and it will reboot into Clockwork Mod Recovery.
Let me know if that does anything for you. Also what version of stock recovery do you have?
Toast6977 said:
Search the forums and find the update.zip for CWM for our Vibrant.
Click to expand...
Click to collapse
Can pull that directly from my signature, if OP wants. (Only works on Eclair [JFD] build btw)
Also OP, You will have to have a ROM that you are going to want to flash saved on your Internal SD card. Jsut download it, put in a folder and follow the ROM OP's instructions. Since you are fresh and new, I would NOT suggest flashing anything of ICS or JB until you get the hang of things first.
Read, read and then read somemore. When it comes time to flash ICS or beyond, there is a guide in my signature. Good luck and make sure to hit Toast's "Thanks" button. He is a good asset to have around here.
Wow! I was hesitant to even check today, let it alone this early! Did not think that I would have two very useful replies waiting for me. Thanks guys, much appreciated!
I'll try the Odin thing out first before I even try to flash (you need root first before flashing, I'm assuming). Just out of curiosity, what is JFD and Odin? I'm still gonna try it out using the guides found here, but just curious.
EDIT: Damn, it worked like a charm! Now I have CWM. The mistake I made was that I only installed the Superuser/ROOT and not both. Gonna play with it for a bit now
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Toast6977 said:
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Click to expand...
Click to collapse
Thank you for teaching me the etiquette around here as well
*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'm writing this as a new Nexus 7 2013 owner so that people with a moderate level of tech savvy and are still on the fence about unlocking and flashing their device can check it out from a non expert perspective. I think a lot of times people are afraid after reading tutorials and a bit intimidated by the procedures (and XDA).
I decided to get a nexus device because they are very well supported here on XDA and the general consensus is they are nearly impossible to hard brick barring a hardware issue or the user doing something really really dumb
After unboxing the device I put it on charge while making some final decisions on what direction I wanted to go with the "rebuild". As you will see some of these decisions will have cascading effects...
I settled on cleanrom 2.6 and the elementalx kernel, I also decided I wanted to use CWM (non touch) recovery instead of TWRP because I'm familiar with it and hoped that I would not spend enough time to justify having a gui.( and ... to be honest I am not a fan of TWRPs gui ).
So now that I have made my decisions for better or for worse it is time to proceed. I powered on and configured the device for the first time. Since I wasn't paying attention Google started downloading all my apps from Play. This was not a big deal but folks on a data plan might want to make sure they read the screens and decide not to restore their apps. The option for OTA upgrade was available from jellybean to kitkat, so I went ahead and proceeded with the OTA. In retrospect it was a waste of time because you can download the stock images and reflash them later if you want.
ADB and FASTBOOT were already on my Debian desktop and working properly so I went ahead and unlocked the bootloader, then rebooted and flashed CWM. I them installed supersu from CWM. (I left out the part about using adb to push the files but you get the picture...) So far so good except there was a fatal flaw in my plan. Cleanrom and ElementalX both use aroma installer, which doesn't work on CWM. So as I was doinking around In CWMs advanced options looking for a slim possibility of salvaging the situation I managed to end up in the key test application. The problem here being that since the device doesn't have a back button there was no way to get out of they key test. No worries though I simply connected the USB cable fired up adb and did "adb reboot". A few minutes later I had downloaded and installed TWRP and was ready to pick up where I left off.
Here is a note for folks doing this for the first time, read the instructions and erratta for your new kernel and ROM carefully before you proceed so that you avoid time consuming issues. By reading up a little before I started the project I knew that the ROM and kernel were compatible and work well together. I also knew that I would need to install the ROM first, then the kernel, because I I installed the Kernel first I would have to re-install it after flashing the ROM. No point in doing it twice, right?
SO I fired up TWRP and did a factory reset in preparation for flashing the ROM. So far so good. Cleanrom installed, but AROMA did not ask for my installation options. Fearing something was wrong, I clean flashed (wipe first then flash) the ROM 2 more times with the same result. After the third flash I said wth, as long as the ROM flashed and works I can always change software on my own. So a quick reboot and test drive of the device confirmed the ROM was installed and there appeared to be no glaring issues, so I went back to recovery and flashed the kernel. BTW I did check the md5sums and verified that the files were correct and not corrupted.
I know there is an option to flash more than one update with TWRP but since the install did not occur the way I expected I chose to install the ROM and kernel separately, I'm sure some more experienced members of XDA will agree with this decision and others will say that "it's nexus, go ahead and flash the ROM and kernel at the same time, you can't break it
Anyhow the kernel installation went fine and AROMA prompted me as expected before installing. Note to newbies like me, reading the thread really helps, Knowing exactly how you want to configure your kernel before you install it will save you hassles down the line. Expect the first boot to take a little extra time.
In nutshell, there really is no reason to be afraid of installing a custom kernel on your Nexus device. Sure the possibility is there for you to screw things up, but unless you do something very drastically wrong you wont brick the device, trust me -- If I can do it you can do it. Just think ahead a little and prepare yourself by downloading the files you need and maybe even writing yourself an outline of the steps. I'm sure that I could do this again and again now without referring to notes or tutorials, but having them readily available for guidance and reference was comforting.
I could continue with the saga of getting Debian to recognize the tablet in MTP mode but this post has already gone long and that is a rite of passage...