Related
Hi guys,
Here's what happened. My phone ran out of battery and died while I was out earlier. I came home, charged it up, and turned it on. I get a notification saying that a system update to 4.04 is available. I went ahead and downloaded it, then rebooted my phone. When it started back up, all I got was the android and an exclamation mark inside a triangle. I couldn't turn it off, so I pulled the battery and turned it on again. This time it booted up fine, but when I check for system updates, it says my system is up to date, but I'm still on 2.3.6. How do I update my phone to 4.04??
Here's some background info about the phone.
Nexus S I9020A
Baseband version I9020AUCKF1
Kernel version 2.6.35.7-gf5f63ef [email protected] #1
Build number GRK39F
The phone is rooted with the Superuser app installed, but the bootloader is still locked to my carrier, Rogers. I used something called DooMLoRD root to root my phone. All I had to do was run a batch file that did everything for me. I'm assuming that the failure to install ICS properly was due to the root.
Please help me figure this out! Tell me what I need to do and I'll do it.
ICS failure would have been due to the root. First, you'll need to unroot. To do that, assuming you have used the bog-standard DooMLoRD script, there is a link in the original thread that gives you a way to unroot. Pretty straight forward, this may or may not work to re-root 4.0.4 though.
After this, try opening up the dialer and typing *#*#checkin#*#* - hopefully an update will show. If not, you can probably manually update from here, assuming you are on stock 2.3.6 (and now unrooted).
Alright, I've unrooted using the method advised. Using the dialer, I typed *#*#checkin#*#*, and I get a notification that says "checkin succeeded", but no new updates are available.
I took a look at the thread you suggested, and on page two there seems to be a .zip file that I'm assuming contains the update. How do I install the update from the .zip file?
full installation instructions: http://andwise.net/?p=275
I followed your instructions, and I get a Status 7 error, and the installation is aborted. I did a little reading and found that the status 7 error has something to do with Google making it so that you can't manually update using the stock bootloader.
Apparently the only way for me to get 4.04 involves a full wipe, unlocking the bootloader, then flashing CWM, then flashing 4.04 using CWM. Is there any way to avoid all of this so I can keep my data?
error 7 is not because you didn't do a full wipe. you can update without a full wipe, however if you have problems later full wipe could fix it.
could you type this in the command prompt:
adb shell getprop ro.build.fingerprint
and let me know the output of it
C:\Users\sm1ke>adb shell getprop ro.build.fingerprint
adb server is out of date. killing...
* daemon started successfully *
google/sojua/crespo:2.3.6/GRK39F/189904:user/release-keys
OK so you have to use the file for i9020A. Be sure to backup before.
Sent from my Galaxy Nexus using xda premium
andwise said:
OK so you have to use the file for i9020A. Be sure to backup before.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I used the file for the i9020A, as referenced in your instructions.
http://android.clients.google.com/packages/ota/google_crespoa/IEzMw3FU.zip
Copied the update to the SD card, renamed the file to "update.zip", then turned off the phone. Booted into fastboot mode, went to Recovery, and I got a warning sign. Pressed power, then vol up to enter main recovery, then selected apply update from /sdcard, and chose update.zip from list. At this point I get the status 7 error.
Btw, thank you so much for trying to help me out guys! I really appreciate it.
You can't apply the ota update zip in stock recovery manually anymore.
Boot the phone normally and see if the ota notification comes.
Or look into how to do it manually with cmw etc
I can't say for sure since i don't use stock recoveries or the 850MHz variant, but i'm pretty sure it is 4.0.3 recoveries and greater don't allow manual updating, 2.3.6 should allow you to do it perfectly fine. However some other people have said they had issues with updating the i9020A, pretty sure with a status 7 error.
Guaranteed way is unlocking bootloader method, will remove all personal data though. Best way, for now at least, is give it a few days and follow the steps in the update thread (OP), maybe they'll work for you. Or maybe it'll just pop out for itself soon.
Sorry i can't really help more than that, hope you can get yourself on stock ICS soon
just force into CWM.
flash ICS 4.0.3
flash incremental update 4.0.3 -> 4.0.4.
ur problem solved
As harbb says for 4.0.3 you need cwm for 2.3.6 usually no but you have to have your bootloader unlocked. In fact I would suggest to flash to cwm anyway and make nandroid backups.
Sent from my Galaxy Nexus using xda premium
Alright, thanks guys.
I'll look into flashing CWM and all that, never done it before.
Its easy http://andwise.net/?p=268
Sent from my Galaxy Nexus using xda premium
albundy2010 said:
You can't apply the ota update zip in stock recovery manually anymore.
Boot the phone normally and see if the ota notification comes.
Or look into how to do it manually with cmw etc
Click to expand...
Click to collapse
I successfully applied the 4.0.4 update from stock recovery from 2.3.6 on a i9020a.
Sent from my Nexus S (Telus ) using xda premium
rhagemeyer said:
I successfully applied the 4.0.4 update from stock recovery from 2.3.6 on a i9020a.
Sent from my Nexus S (Telus ) using xda premium
Click to expand...
Click to collapse
Which update file did you use?
try going from 2.3.6 to 4.0.3 then do the incremental update to 4.0.4
Alright, so I've decided to try using CWM, since nothing else seemed to work. I unlocked the bootloader, and flashed the CWM recovery image. Then I went into Recovery, this time it looked a little different (blue text, gear and hat image in the background). I went to the option to install update from sdcard, chose the update file for 2.3.6 to 4.04 for the i9020a, and I'm still getting a status 7 error.
I'll try updating from 2.3.6 to 4.03, then from there going to 4.04, but I read about the radio not working on 4.03 or something. Will I have to worry about that, or will the update to 4.04 fix the issues from 4.03?
Also, if anyone has a link to the 4.03 OTA for i9020a I'd appreciate it.
sm1ke said:
Which update file did you use?
Click to expand...
Click to collapse
I believe I used IEzMw3FU.zip
Richard
Hello,
I have a Motorola Atrix 2 that my friend somehow had put it on the stock rooted deodexed 2.3.6 rom. Then following that he un-rooted it while still on the stock rom and now I can not root it at all. If anyone knows a was to root this device I would love to know or a way to flash it to were it is completely stock so I can root it. I have just had alot of trouble with the apps and I want to go back to another rom or the stock rom.
Thanks xda-developers, Aedyn.
what have you done to try to root it ?
in the development forum there's a clear step-by-step to root stock ROM ..
*Reply*
I have used the click to unroot application...
He had a few other roms on it before so he went and flashed the deodexed 2.3.6 rooted firmware to it then unrooted it.
Now alot of apps will have force closes and I cant log into myyearbook.
Id like a way to get it to a complete stock firmware...
Thankyou for the help!
Try super one click. That's what I had to use as the other method did not work for me. I posted a drop box link to it in this thread a while back. Just do a search for it.
Sent from my MB865 using XDA
1 Hard reset your phone once
2 Follow steps as shown at Deodexed rooted ROM page.
3 You will be rooted else Follow the instructions to root 2.3.6
Good Luck...
If none of the above works, you may have to
1.) flash the 2.3.5 fkz,
2.) root 2.3.5
3.) install bootstrap
4.) flash 2.3.6 deodexed (which will retain root)
farshad525hou said:
1.) flash the 2.3.5 fkz,
2.) root 2.3.5
3.) install bootstrap
4.) flash 2.3.6 deodexed (which will retain root)
Click to expand...
Click to collapse
This would be my suggestion
This is the most recommended.
farshad525hou said:
If none of the above works, you may have to
1.) flash the 2.3.5 fkz,
2.) root 2.3.5
3.) install bootstrap
4.) flash 2.3.6 deodexed (which will retain root)
Click to expand...
Click to collapse
Or you can try to do this:
1.) flash 2.3.5 fkz
2.) update OTA to 2.3.6
3.) root 2.3.6
4.) install bootstrap
5.) Up to you (you can stay on stock rooted or restore another rom)
Well i was trying to flash SC v7 and was following the steps as directed, Installed Bootmenu Manager and downloaded the bootmenu files and gave me error about logwrapper.sh and i ignored it and selected custom recovery mode. Since then am stuck in bootanimation and it wont go beyond boot animation so is there a possible Soln?
And when i try to reflash the stock ICS i get an errorassert failed apply patch check("system/app/AABSync.apk". and so on so installation aborted
Is there a fix for Getting back to stock ICS..
THX in advance..
kc92iyngr said:
Well i was trying to flash SC v7 and was following the steps as directed, Installed Bootmenu Manager and downloaded the bootmenu files and gave me error about logwrapper.sh and i ignored it and selected custom recovery mode. Since then am stuck in bootanimation and it wont go beyond boot animation so is there a possible Soln?
And when i try to reflash the stock ICS i get an errorassert failed apply patch check("system/app/AABSync.apk". and so on so installation aborted
Is there a fix for Getting back to stock ICS..
THX in advance..
Click to expand...
Click to collapse
You have to use the patched fxz. You will have to use the proper fxz and patch it with the pieces from the Chinese forum that posted here a week or so ago... that is what I used to make the US AT&T version script that I posted. You can't use the ICS OTA as a backup.. it is a patch for 2.3.6 ONLY.
This one:
http://forum.xda-developers.com/showthread.php?t=1799702
This is just a patch that you apply over YOUR proper 2.3.5 fxz.
Well am now on 2.3.6..
THX again.
kc92iyngr said:
Well am now on 2.3.6..
THX again.
Click to expand...
Click to collapse
How can you be at 2.3.6 and flash scv7? that is ONLY for people on ICS?
Just go to the noob thread and follow the fxz instructions for 2.3.6.
NO i was on 4.0.4 and by the time i replied i had fxz back to 2.3.5 and ota to 2.3.6..
Hey guys so i got a used Atrix 2 AT&T (MB865) running 2.3.6. Every time i reboot the phone all the data seems to get wiped and the android setup screen appears. I tried to FXZ to 2.3.5 using RSDLite and the correct replacement packages and the phone goes through the process but when it says its done the phone goes into stock recovery. I try rebooting out of stock recovery and the phone boots back into 2.3.6 with the setup screen but the problem is still there. Also, when i try to OTA to ICS the update installs, but the phone goes to stock recovery after reboot. Please help
Atrix 2
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Apex_Strider said:
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Popwii said:
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Click to expand...
Click to collapse
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
41rw4lk said:
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
Click to expand...
Click to collapse
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Popwii said:
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Click to expand...
Click to collapse
First, make sure your drivers and RSDlite are up to date. This isn't totally necessary, but you might as well have a clean slate to go from. So make sure your phone is unplugged from your pc, uninstall MotoDeviceManager, reboot, then install it again from here.
RSDlite 6 is here
After everything is fresh, connect your phone and give it a few minutes to detect and install your drivers. Once that's done, boot into fastboot and verify that it sees your device, if you're already in fastboot then just verify.
Code:
fastboot devices
On your phone screen it should tell you what bootloader version you have, it should say 0A.72, if not, then stop and post back what it says. Otherwise, open RSDlite, and try to flash the Official ICS FXZ you downloaded previously. By the way, the FXZ should be named InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip and the MD5sum should be 2BF9CCD528C05D26523ACC5B38AC76C6 if neither of those match, you need to make sure you have the right FXZ and make sure that the MD5sum matches what I posted.
So, if all is well and everything checks out, point RSDlite to the FXZ and start the flash, be patient. If it still fails, then you might try this. It's a way to flash the Official AT&T ICS FXZ without RSDlite, just download it, extract it, and follow the simple instructions in the readme.txt. Make sure RSDlite is closed before you run the .bat file. If you have to resort to this method, and it works for you, make sure you find Alteredlikeness around here and thank him, he put the script together.
If none of that works, then post back and we'll go from there.
Ok so i booted into fastboot and it says the bootloader is 0A.65
Popwii said:
Ok so i booted into fastboot and it says the bootloader is 0A.65
Click to expand...
Click to collapse
Alright, your bootloader is still for 2.3.6, obviously the OTA attempt never flashed the new one, or it never went properly. You might download the 2.3.6 FXZ here the MD5 sum for it is FCC0FBFDEDEAE084F90E34BF2523EB27
Flash it with RSDlite, that will hopefully get you on a clean and stable GB 2.3.6 After that, if you want to get on ICS and need some help, post back, or if getting back to 2.3.6 doesn't work, post back.
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Popwii said:
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Click to expand...
Click to collapse
How did you get into the state you're in originally? Did you try to flash something? A rom? A FXZ? You said you got a used Atrix2, was it messed up from the get go? Anyway, download this unzip it and follow the directions in the readme.txt. You'll need to unzip the Official ICS 4.0.4 FXZ that you downloaded previously as well. Basically unzip the ICS FXZ on your desktop (not the 2.3.6), then unzip the restore script and put everything in your unzipped 4.0.4 FXZ, put your phone into fastboot mode and run the restore-to-ics.bat file. Post back with results.
*Note - keep an eye on your bootloader version, if it changes from 0A.65 do NOT try and flash anything Gingerbread, you'll have to stick strictly to ICS if that changes.
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Popwii said:
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Click to expand...
Click to collapse
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
41rw4lk said:
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
Click to expand...
Click to collapse
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Popwii said:
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Click to expand...
Click to collapse
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
41rw4lk said:
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
Click to expand...
Click to collapse
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Popwii said:
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Click to expand...
Click to collapse
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
41rw4lk said:
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
Click to expand...
Click to collapse
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Popwii said:
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Click to expand...
Click to collapse
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
41rw4lk said:
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
Click to expand...
Click to collapse
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Popwii said:
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Click to expand...
Click to collapse
You should try to downgrade to 2.3.5 and start from the beginning. Since your system is borked and you can't update, hopefully downgrading will at least get you to something stable that you can work with. The noob guide will tell you how to downgrade from 2.3.6 to 2.3.5, just pay attention because you'll most likely have to replace some FXZ files since the 2.3.6 you're on is most likely from an OTA.
About 1/3rd of the way down the page you'll see "How to flash the FXZ once applying the OTA update and get back to 2.3.5", follow those instructions.
Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app