Related
Hey,
I'm new to Android, and still pretty bad with it, so when I set out to flash a custom rom last week, I never bothered to setup a backup. I didn't think it was going to be as complicated to get back to the way it was when I took it out of the box. I guess I'm still use to the iPhone. Now, I'm not completely happy with my phone and am looking to go back to stock.
I've looked in to it, and it seems easy enough, but I just have a couple of questions:
Pre-CM7 I'm pretty sure my phone was GRI54, and i9020, It's now GRI40. Does this make any difference?
And, finally, where can I download an official version of this?
Any help is greatly appreciated,
Thanks.
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=1056062
Graham19 said:
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've downloaded the i9020a one, but when I'm trying to update it it's saying "Installation aborted". I tried doing it from clockwork mod - and I don't know anything about it. Do you know where I'm going wrong here?
tylerisgood said:
I've downloaded the i9020a one, but when I'm trying to update it it's saying "Installation aborted". I tried doing it from clockwork mod - and I don't know anything about it. Do you know where I'm going wrong here?
Click to expand...
Click to collapse
Use the unofficial full rom for the i9020a. apply it from cwm. Then wipe the phone
Sent from my Nexus S
Matridom said:
Use the unofficial full rom for the i9020a. apply it from cwm. Then wipe the phone
Sent from my Nexus S
Click to expand...
Click to collapse
Do you know where I can get this download from?
I haven't been able to find anything for this. The closest I found was someone saying 'use this one instead', but that got me stuck at the Google screen.
tylerisgood said:
Do you know where I can get this download from?
I haven't been able to find anything for this. The closest I found was someone saying 'use this one instead', but that got me stuck at the Google screen.
Click to expand...
Click to collapse
It is in my sticky for the 2.3.4 ota. Very first post
Sent from my Nexus S
Matridom said:
It is in my sticky for the 2.3.4 ota. Very first post
Sent from my Nexus S
Click to expand...
Click to collapse
Sorry, maybe I'm doing something wrong, but I've tried using that zip a few times (286d814dee5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip 12mb) and it says install failed.
I boot into recovery, factory reset, wipe cache, install zip from sd card, pick the file, agree.
Have you checked the MD5 hash to ensure the download isn't corrupt?
Graham19 said:
Have you checked the MD5 hash to ensure the download isn't corrupt?
Click to expand...
Click to collapse
I'm incredibly new to this, and have no idea what this means. How do I try this?
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Matridom said:
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Click to expand...
Click to collapse
I love you. Thanks a lot
One last quick question:
Is it possible to get rid of clockwork?
tylerisgood said:
One last quick question:
Is it possible to get rid of clockwork?
Click to expand...
Click to collapse
yes, the default for all stock 2.3.4 roms will restore the recover back to stock on each reboots you have to rename/delete the install-recover.sh script to prevent it from happening
Matridom said:
yes, the default for all stock 2.3.4 roms will restore the recover back to stock on each reboots you have to rename/delete the install-recover.sh script to prevent it from happening
Click to expand...
Click to collapse
Sorry? I have to delete the files to keep clockwork from being removed?
All I did was flash it, restart, and clockwork was still there.
Also, my phone's internet speeds seem really slow now. Could this be from now having a different build? (GRI54 -> GRJ22)
Sorry for my complete lack of knowledge. It's quite obvious I jumped into something that's much over my head.
tylerisgood said:
Sorry? I have to delete the files to keep clockwork from being removed?
All I did was flash it, restart, and clockwork was still there.
Also, my phone's internet speeds seem really slow now. Could this be from now having a different build? (GRI54 -> GRJ22)
Sorry for my complete lack of knowledge. It's quite obvious I jumped into something that's much over my head.
Click to expand...
Click to collapse
A stock rom has the script. So flashing it will also restore stock recovery. If the rom you installed does not restore the recovery partition, the the rom was not completely stock.
Sent from my Nexus S
Matridom said:
A stock rom has the script. So flashing it will also restore stock recovery. If the rom you installed does not restore the recovery partition, the the rom was not completely stock.
Sent from my Nexus S
Click to expand...
Click to collapse
I used the rom you linked.
tylerisgood said:
I used the rom you linked.
Click to expand...
Click to collapse
I've never used it myself.
Looking over the zip file, the script has been renamed, so it's not 100% stock.
Normally you would need to root the phone to change the file name.
Perhaps renaming the file in the zip will correct the issue?
try renaming /etc/install-recovery.sh.bak to /etc/install-recovery.sh and re-apply the zip. ( no need to wipe )
That rom was posted by dsixda, he may be able to confirm what needs to be done.
If you had root, it would be fairly easy to rename it.
Matridom said:
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Click to expand...
Click to collapse
That was my upload, but is it confirmed that the radio in this one gets flashed to AUCKD2? I uploaded another one with the same radio but slightly different.
Matridom said:
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Click to expand...
Click to collapse
This doesn't seem to work. It does gets you back to stock rom but I still have the old modem I flashed, old APN, CWM Recovery and still there and factory reset doesn't works. Just hangs with the little Android guy and an exclamation mark.
Is there something like ODIN for Nexus S to go back to stock?
SpoonerPS3 said:
This doesn't seem to work. It does gets you back to stock rom but I still have the old modem I flashed, old APN, CWM Recovery and still there and factory reset doesn't works. Just hangs with the little Android guy and an exclamation mark.
Is there something like ODIN for Nexus S to go back to stock?
Click to expand...
Click to collapse
This should work:
http://android.grdlock.net/index.ph... S&PHPSESSID=9dc0c107b878587d1e0b21ec1e3130ef
This should bring you to stock 2.3.3 for the i9020a
Then apply the official patch:
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
This will then bring everything to stock 2.3.4 with proper baseband and recovery
I bought a used TF300T, 16GB
Unlocked
It has TWRP 2.4.4.0, JB 4.2 bootloader, and EnergyROM 3/28 10.6.1.8
Kernel 3.1.10-g59bc3cb
I was wondering if I should leave it alone, or restore it to factory. Is that even possible?
If I keep it as it is, how do I update?
I knew I should have bought a virgin Asus, lol.
Thanks for any info!
You can restore it to factory by flashing a stock Asus blob in recovery (I recommend using the 10.6.1.8 ROM since that was the last one on your tablet). It will wipe all data, including whatever's on the internal storage. Once you get that set up, flash the OTA updates incrementally to avoid issues (there are only two updates to flash). You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be.
All the blobs you need should be on Asus' website. If you need more help, there are lots of "how to flash back to stock" threads with instructions. Just read carefully, and if you decide to flash a custom recovery when you're done, DO NOT flash one with "-JB" at the end of it or you could brick your tablet. You will need a recovery that ends in "-42". Be absolutely sure, because there are 3 different bootloaders for the TF300, and flashing one from either of the other bootloaders will brick your tablet.
EndlessDissent said:
...You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be...
Click to expand...
Click to collapse
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
skank_boy said:
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
Click to expand...
Click to collapse
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
EndlessDissent said:
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
Click to expand...
Click to collapse
Okay, I will try again. Maybe three times the charm. Thanks!
skank_boy said:
Okay, I will try again. Maybe three times the charm. Thanks!
Click to expand...
Click to collapse
You've flashed the stock blob in TWRP twice already? You're not flashing TWRP afterwards, are you? I've flashed a stock blob in TWRP, and I had the stock recovery afterwards. Are you rebooting into Android after you flash it?
I tried to flash, it failed....BUT this time it worked (??!!) lol.
Obviously I wasn't doing something right, but I have now. I installed 10.6.1.8, now on to the next in the normal manner.
Thanks again!
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.
I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.
Hi, this is my first post so bear with me if I did something wrong.
I got the notification to update my Nexus 5 (OTA) to 4.4.4. I stupidly agreed to update it and whatya know? I lost root. Here's the break down of what happened:
CWM asked me if it wanted to flash the stock recovery or keep CWM (the actual message was: ROM may flash stock recovery on boot, NO or YES. Along side yes it told me that selecting yes would keep CWM). I selected yes.
Then, in the next page, CWM warned me that I *may* loose root access if I select no, but I had no idea what would happen if I selected it, so I selected yes (keep root), and my phone rebooted.
After that, my phone booted and when I checked, it was still on 4.3.
I went on the XDA thread: [INFO] Nexus 5 OTA Help-Desk. It told me in order to update (Section C), I must uninstall Xposed Framework, and then just flash the OTA.zip how you would normally.
But now it becomes tricky, as I can't uninstall Xposed because I'm not rooted.
So why don't you just do Scenario #1? Because I have CWM which won't let me apply the update from adb (or at least I don't know how to)
So why don't you use Scenario #2? Because I'm not rooted but can get into CWM.
So what am I supposed to do now? How will I get my SU back, along with root permissions? Do I have to reroot? Please help!
I understand this may be a no-brainer for people who actually know about rooting and recoveries, but my head is hurting right now trying to work this out, so a step by step would be helpful. I found that other threads would say like "oh just do this!" and what they mean is a bunch of steps to reach that point. Thanks A LOT!
ThatAngryGnome said:
Hi, this is my first post so bear with me if I did something wrong.
I got the notification to update my Nexus 5 (OTA) to 4.4.4. I stupidly agreed to update it and whatya know? I lost root. Here's the break down of what happened:
CWM asked me if it wanted to flash the stock recovery or keep CWM (the actual message was: ROM may flash stock recovery on boot, NO or YES. Along side yes it told me that selecting yes would keep CWM). I selected yes.
Then, in the next page, CWM warned me that I *may* loose root access if I select no, but I had no idea what would happen if I selected it, so I selected yes (keep root), and my phone rebooted.
After that, my phone booted and when I checked, it was still on 4.3.
I went on the XDA thread: [INFO] Nexus 5 OTA Help-Desk. It told me in order to update (Section C), I must uninstall Xposed Framework, and then just flash the OTA.zip how you would normally.
But now it becomes tricky, as I can't uninstall Xposed because I'm not rooted.
So why don't you just do Scenario #1? Because I have CWM which won't let me apply the update from adb (or at least I don't know how to)
So why don't you use Scenario #2? Because I'm not rooted but can get into CWM.
So what am I supposed to do now? How will I get my SU back, along with root permissions? Do I have to reroot? Please help!
I understand this may be a no-brainer for people who actually know about rooting and recoveries, but my head is hurting right now trying to work this out, so a step by step would be helpful. I found that other threads would say like "oh just do this!" and what they mean is a bunch of steps to reach that point. Thanks A LOT!
Click to expand...
Click to collapse
Just flash supersu in CWM and you are rooted
GtrCraft said:
Just flash supersu in CWM and you are rooted
Click to expand...
Click to collapse
I'm sorry if I sound like a total noob, but how would you do that?! Is there something you have to download and then put it on your device and then flash it? Do you have a download link?
ThatAngryGnome said:
I'm sorry if I sound like a total noob, but how would you do that?! Is there something you have to download and then put it on your device and then flash it? Do you have a download link?
Click to expand...
Click to collapse
Check the thread named "unlock bootloader and root" which is linked in my signature. You should get the download link and steps to be followed from there.
You were rooted previously, right? Forgot the steps already?
- Sent from an IceCold Hammerhead!
Replied to wrong post. Oops.
HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks
Disregard the message.
Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg
All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?
Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L
I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
thanks! Ah OK I see so that's the whole ROM there as opposed to just an update
davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse
The file I quoted is not a whole ROM, it's 31 MB.
AH OK, sorry I thught you referred to the 500mb file
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
I'm having the same issue. Anyone?
Got the same problem. Any idea?
duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?
Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658