Hi, I am currently using the Nexus S i9020a on 4.0.4 and it's unrooted on stock rom.
I wanted to know if it was possible to root it (for apps like AdAway) and maintain the stock rom? The reason why I want to keep the stock is because I tried Cyanogen a few months back and it crashed at least twice a week for me. This is troublesome because at night I use the phone as an alarm and it crashing would kill the purpose.
Thank you!
does it show the unlock icon when you boot?
if so, it should be pretty easy.
just flash a su.zip
if you're locked
you need to unlock your bootloader (which may factory reset your phone)
so backup, unlock bootloader, flash clockwordmodrecovery and su.zip
and there you are, stock, with root
The bootloader is unlocked.
How do I flash su.zip? I had someone do it for me last time so I can't remember how.
I can DL the SuperUser app off the app store but I've learned that it does nothing.
Lastly, is it possible to flash su.zip (wherever that is found) without using a USB cable (mine broke, need a new one I guess)?
Nook000 said:
The bootloader is unlocked.
How do I flash su.zip? I had someone do it for me last time so I can't remember how.
I can DL the SuperUser app off the app store but I've learned that it does nothing.
Lastly, is it possible to flash su.zip (wherever that is found) without using a USB cable (mine broke, need a new one I guess)?
Click to expand...
Click to collapse
you can use SolidExplorer's share files feature (via FTP client) , or AirDroid (via internet browser) to push over su.zip
su is here
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
move that to your sdcard and boot into clockwork recovery with (VolUp + Power, then select Recovery)
I tried downloading that file and then going to Recovery.
I did "apply update from /sdcard" and hit the .zip file but I get the following errors:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?
Nook000 said:
I tried downloading that file and then going to Recovery.
I did "apply update from /sdcard" and hit the .zip file but I get the following errors:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
are you sure you have clockworkmod recovery installed?
Not completely sure, when I go to Recovery, the top says:
"Android System Recovery <3e>"
Edit: I just went to http://www.clockworkmod.com/rommanager to download CWM Recovery but it's an .img file which it won't let me flash after reboot into Recovery.
Flash it either via fastboot or download through Rom Manager and install. I usually do the former.
Open up adb.
Turn off device and power back on into fastboot(power+vol up)
Make sure the recovery image is in the same directory as adb.
Name the recovery image to recovery if it hasn't been changed
Type fastboot flash recovery recovery.img
I've done it that way for a while now no issues. You also need a script or a .zip file that will keep the custom recovery so the stock one doesn't replace it.
You can flash it:
http://forum.xda-developers.com/showpost.php?p=23125913&postcount=2
Or you can edit the file that does this by following these steps in this post
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
HTH
Thank you a whole very much!! Using both of your advice, I was able to root the device. It took a while because despite installing the drivers, when I went into the Bootloader, it wasn't detected. The remedy was manually setting it to the Bootloader driver irregardless of Windows suggesting I shouldn't.
Now it's all good to go! Thanked you both.
chronophase1 said:
Flash it either via fastboot or download through Rom Manager and install. I usually do the former.
Open up adb.
Turn off device and power back on into fastboot(power+vol up)
Make sure the recovery image is in the same directory as adb.
Name the recovery image to recovery if it hasn't been changed
Type fastboot flash recovery recovery.img
I've done it that way for a while now no issues. You also need a script or a .zip file that will keep the custom recovery so the stock one doesn't replace it.
You can flash it:
http://forum.xda-developers.com/showpost.php?p=23125913&postcount=2
Or you can edit the file that does this by following these steps in this post
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
HTH
Click to expand...
Click to collapse
He's right...and thanks for the refrence
If you are going to keep stock then when you reboot Clockworkmod Recovery won't stick. Do as I said in the referenced post or flash a new Rom (my choice , or just live with it. If you want CWM you will have to USB, cmd fastboot flash recovery recovery.img every time.
Edit: posted a minute before me. Awesome and enjoy!
Glad to hear it worked! And no problem, bud! I try to keep the good posts saved for situations like this
guide
Personally when i rooted my nexus S for the first time,i followed this guide
Its precise,step-by-step and includes a video incase you need one
i am prevented from posting the link but if you search google for nexusshacks.com,you should easily find it.
Related
Alot of the guides floating around showing how to flash back to stock rom is incomplete ( missing a few steps ) and will result in boot loop most of the time. the correct procedure is :
Part 1 : Setting up Fastboot.
1. Make sure you have java installed, if not get it from here : http://java.com/ and install it.
2. Download the Android SDK manager from here : http://developer.android.com/sdk/index.html ( get the exe download )
3. Install SDK manager, then run the android SDK manager.
4. Once launched it will show you available updates, choose ONLY these two "Android SDK Platform Tools and Android SDK Tools" and update them.
5. After update is complete close the sdk manager and go to the SDK manager platform-tools folder, normal path is : ( C:\Program Files\Android\android-sdk\platform-tools )
6. Copy the following 3 files from this folder : "adb.exe" , "AdbWinApi.dll" and "fastboot.exe"
7. go to your c drive ( c:\ ) and make a new directory called "fastboottools"
8. copy the 3 files above into your fastboottools folder.
9. so now your should have a folder like this : "c:\Fastboottools" with the following 3 files in it "adb.exe" , "AdbWinApi.dll" and "fastboot.exe".
Click to expand...
Click to collapse
That is it, Fastboot tools is setup. Proceed to next guide.
Part 2 : Flashing guide.
1. download the ROM from here:
ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35. 3033h_7.51.35.19_release_228383_signed.zip
or here ( mirror link ) : ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed.zip
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.
Click to expand...
Click to collapse
after trying EVERYTHING else, this is the method that worked for me, i tried to cover every step possible ( alot of the other guides skipped few steps and that is where i got problems ).
hope this helps.
( PLEASE BE AWARE : This will remove recovery and root. if you flash back to stock rom using this method you will have to root your phone again. It will still be unlocked, just recovery and root will be removed. to re add recovery and root check part 3 below. )
Part 3 : Add recovery and root access back after installing stock rom.
1. Download the following 2 files, you will need them :
PH06IMG.zip
su-2.3.6.1-ef-signed.zip
2. Extract PH06img.zip to your "c:\fastboottools" directory. it will add the "recovery.img" file to fastboot.
3. Copy the file su-2.3.6.1-ef-signed.zip to your phones SD card, dont change the name, keep it standard, just put it in the root directory of your SD card.
4. go to the settings on your phone "Settings -> Power -> and Uncheck Fast boot" ( This is important, make sure fastboot is unchecked.
5. Take out your battery, put battery back in and boot into bootloader ( hold down volumedown + power )
6. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
7. Go to the Fastboottools directory "c:\fastboottools", Hold CTRL+Shift and right click in that Folder and open Command Prompt.
8. type inside command prompt : "fastboot flash recovery recovery.img" and let it finnish, takes less than a minute.
9. reboot your phone, but reboot it back into bootloader ( hold down volumedown + power )
10. Now using volume keys choose "recovery" and press "enter" ( not power button, rather use enter button in recovery else you sometimes get a "hat like" picture on the screen )you should now see the recovery options.
11. find the "install zipd from sd card" option and press enter, then choose su-2.3.6.1-ef-signed.zip and confirm to flash it.
12. once flashed reboot the phone and you will now have recovery and root access back again.
Click to expand...
Click to collapse
it is recommended you update superuser to newer version and also install busybox.
Now that you have recovery installed you can also flash custom roms again.
I STRONLGY recommend once you reach this step that you make a backup of your rom via the bootloader recovery menu, that way you dont have to go through all this pain again next time.
The End !!!
feel free to post any problems you encounter below.
stuck on bootloop at step 10
I've attempted the recovery and get as far as step 10, but unfortunately
"still suffer the bootloop.
what am I supposed to do in the recovery step to get it working fine!
do i load the update.zip?
please reply if availale... am stuck on bootloop
ty
bootloop ussualy happens when you dont clear your cache properly before flashing.
Make sure to clear ALL cache, and also make sure to follow the steps exactly as they are posted, even if it looks like you can skip a step DON'T. do each step as posted, and clear all cache when you are told to. then you wont get boot loops.
Hi,
I bought HTC chacha locally at a online retailer. Its not tied to any sim/operator. However I am stuck at android version 2.3.3. (firmware version 1.20.720.1). If I try to run the (ota)software update, the phone says no updates available.
I really need to unlock the boot loader. However if I try the htcdev.com, the RUU utility says that the please update to 1.57.XX and then try unlocking the bootloader. I am really stuck here.
My question is can I try the steps mentioned above in this post to get the firmware update, with a locked bootloader?
Any other suggestions to update my firmware to the latest 1.57.XX?
--Thanks in Advance..
htc status restore factory 2.3.3
No, I didn't make a real backup! I thought titanium backup would cover that, it didn't, so I have no backup of the stock stuff.
I have a HTC Status (aka chacha) US ver with att. I unlocked the boot loader by htc's site, worked fine. Then I rooted it with cmw, worked great.
Recently the ota 2.3.5 update (48mb) became available. I downloaded it and tried to install it, it failed with checksum. I know it is the cmw mod. How can I get the stock load 2.3.3 back onto my htc status? The above directions mention the "asia" load. Are the files mentioned generic for all phones with the exception of the cid?
p.s. It would be great if someone out there had the stock 2.3.3 recovery file for the status! That would be easier to load than the sdk stuff.
update : both ruu files listed above show to be corrupt when unzipping.
Update: I installed a newer zip utility than the stock win xp one and it unzipped without any trouble. Moving on to the next step.
Update: all went well, except the "english" option, I chose english singapore. Installed cwm and rooted again. updated to 2.3.5. Thanks for the info above.
thank you!
raymerjacque said:
Alot of the guides floating around showing how to flash back to stock rom is incomplete ( missing a few steps ) and will result in boot loop most of the time. the correct procedure is :
Part 1 : Setting up Fastboot.
That is it, Fastboot tools is setup. Proceed to next guide.
Part 2 : Flashing guide.
after trying EVERYTHING else, this is the method that worked for me, i tried to cover every step possible ( alot of the other guides skipped few steps and that is where i got problems ).
hope this helps.
( PLEASE BE AWARE : This will remove recovery and root. if you flash back to stock rom using this method you will have to root your phone again. It will still be unlocked, just recovery and root will be removed. to re add recovery and root check part 3 below. )
Part 3 : Add recovery and root access back after installing stock rom.
it is recommended you update superuser to newer version and also install busybox.
Now that you have recovery installed you can also flash custom roms again.
I STRONLGY recommend once you reach this step that you make a backup of your rom via the bootloader recovery menu, that way you dont have to go through all this pain again next time.
The End !!!
feel free to post any problems you encounter below.
Click to expand...
Click to collapse
thank ! but dont update rom to 1.57.707.3,why?
Does the phone need an unlocked bootloader?
Can the be a way to debrand the firmware? Is the firmware attached the latest generic one?
Thanks
can't flash new htc status att rom 2.14.502.2 ruu security fail
Goatman5467 said:
No, I didn't make a real backup! I thought titanium backup would cover that, it didn't, so I have no backup of the stock stuff.
I have a HTC Status (aka chacha) US ver with att. I unlocked the boot loader by htc's site, worked fine. Then I rooted it with cmw, worked great.
Recently the ota 2.3.5 update (48mb) became available. I downloaded it and tried to install it, it failed with checksum. I know it is the cmw mod. How can I get the stock load 2.3.3 back onto my htc status? The above directions mention the "asia" load. Are the files mentioned generic for all phones with the exception of the cid?
p.s. It would be great if someone out there had the stock 2.3.3 recovery file for the status! That would be easier to load than the sdk stuff.
update : both ruu files listed above show to be corrupt when unzipping.
Update: I installed a newer zip utility than the stock win xp one and it unzipped without any trouble. Moving on to the next step.
Update: all went well, except the "english" option, I chose english singapore. Installed cwm and rooted again. updated to 2.3.5. Thanks for the info above.
Click to expand...
Click to collapse
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Thanks man
Tried and made it
Work very fine except I cannot update sofware to newer version... Stuck on 1.54.401.2
Goatman5467 said:
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Click to expand...
Click to collapse
I'm having the same issue.
You need the stock rom for the update to work. But frankly, I did not see any improvement. Battery life sucks.
I'm back to CM9
Goatman5467 said:
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1752473
good lesson
Hi everyone.
I want to take my htc cha cha for warranty service by HTC. It means that I need to un-root the phone and take it back to official rom by HTC.
My phone is in Asia area, anyone has this stock/ official rom? Plzz share to me.
Thanks so much.
...
Hi ..
i have a problem with coming back to the stock arabic rom
the wizard stops and gives 2 errors !!
Signature check fails
Is there a way to switch off or bypass signature checking?
>fastboot flash system system.img
sending 'system' (254104 KB)...
OKAY [ 57.650s]
writing 'system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 293.043s
>fastboot flash boot boot.img
sending 'boot' (2584 KB)...
OKAY [ 2.340s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 4.633s
thanks!, it worked for me
Link doesn't work
Dear, thank you for the super thread. But I have 2 problems (as I'm a newbie to HTC Chacha).
1. The download links for the files PH06IMG.zip & su-2.3.6.1-ef-signed.zip does not work. and 2. I cannot get the code from HTCDev website.
Please Help.
Thanks in advance.
Hello Everyone
Currently my ChaCha is running on GB 2.3.5 with version 1.57.720.1 (ASIA)
i want to the stock rom of this verison may be upgraded also
The links mentioned for the stock rom in this thread is not working
can i get the working links
P.S if i flash my ChaCha with CyanogenMod9 can i switch back to my stock verison without any issues (sorry if my question is annoying)
Thank you
I have S-OFF but it seems like every Clockwork Recovery that I download doesn't work. If I do it through the PC on Fastboot, it says "Can't load IMG." and if I try to load it through through the Bootloader on the Phone, it says "Wrong image". Plus there are so many recovery images floating around, I have no idea which is the right one.
Try following instructions. Works every time for me.
Kevc44485 said:
Try following instructions. Works every time for me.
Click to expand...
Click to collapse
Thanks but I would have liked some real help. Anyone else please?
trufan1 said:
I have S-OFF but it seems like every Clockwork Recovery that I download doesn't work. If I do it through the PC on Fastboot, it says "Can't load IMG." and if I try to load it through through the Bootloader on the Phone, it says "Wrong image". Plus there are so many recovery images floating around, I have no idea which is the right one.
Click to expand...
Click to collapse
You could try EXT instead. Part I to install the recovery. Part I & Part II to install EXT & 3.32 firmware.
PART I: Flashing 4EXT recovery touch
To dowload and install the newest version of 4ext recovery TOUCH (v1.0.0.5 RC3). Use one of the following methods provided:
Third method: Download this file, check the MD5 of the zip and install it following the steps 4 and 5 from post#1 in this thread.
NOTE: File used in third method WILL NOT install the needed 3.32 firmware in any way, only contains the recovery.img to flash 4ext recovery touch.
PART II: Updating the firmware
This step is MANDATORY otherwise your ROM will not boot.
After updating the firmware you will have the 3.32 firmware with unlocked bootloader. Which basically means that you can use advanced fastboot commands, such as: flash new radios and splashscreens
Download compatible firmware from here.
Copy the PG58IMG.zip file you've downloaded to the root of the sdcard. Root of the sd card mean that you can't put the file inside any folder. Also, you can't rename the file. Please keep the PG58IMG otherwise the bootloader won't recognize it.
Power off your phone or remove the batt and put it back again.
Hold volume-down + power button to boot into the bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once it completed successfully and prompted you to reboot, pull the battery out.
Connect your SD card to the PC and remove the PG58IMG.zip file.
Quoted from here
.
Click to expand...
Click to collapse
I have a TF300, recent OTA Jellybean, unlocked, TWRP installed... but for the life of me I can't figure out how to root or if it is possible.
Most google searches date back to pre-Jellybean. I have tried flashing the hydroponic and stock ROMs but I end up with "signature verification fails" after trying to install via TWRP.
I assume this means I need root access... but I can't install root access without root access?!?
Please help, I know I am probably missing something obvious.
Thanks.
hormiga0 said:
I have a TF300, recent OTA Jellybean, unlocked, TWRP installed... but for the life of me I can't figure out how to root or if it is possible.
Most google searches date back to pre-Jellybean. I have tried flashing the hydroponic and stock ROMs but I end up with "signature verification fails" after trying to install via TWRP.
I assume this means I need root access... but I can't install root access without root access?!?
Please help, I know I am probably missing something obvious.
Thanks.
Click to expand...
Click to collapse
First there are two hydro roms, one JB and one ICS. When you get signature verification error you are most likely flashing an ICS rom, recovery, etc on a JB bootloader.
Try this link http://forum.xda-developers.com/showthread.php?t=1697227. It includes most of what you need on XDA for TF300.
There are recovery flashable roots available also.
Good Luck!
hormiga0 said:
I have a TF300, recent OTA Jellybean, unlocked, TWRP installed... but for the life of me I can't figure out how to root or if it is possible.
Most google searches date back to pre-Jellybean. I have tried flashing the hydroponic and stock ROMs but I end up with "signature verification fails" after trying to install via TWRP.
I assume this means I need root access... but I can't install root access without root access?!?
Please help, I know I am probably missing something obvious..
Click to expand...
Click to collapse
You must use this part:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse
This part works well
Hi,
Following on from this thread I'm trying to get back to stock rom.
Each time I attempt to flash from (stock) recovery I get
check.partition.size=[__PROP_UNDEFINED__]
Installation aborted
I've tried CUS1 and GEN1 roms from Acer site both with and without the 1st line of the script commented out.
Any ideas?
Clumzie said:
Hi,
Following on from this thread I'm trying to get back to stock rom.
Each time I attempt to flash from (stock) recovery I get
check.partition.size=[__PROP_UNDEFINED__]
Installation aborted
I've tried CUS1 and GEN1 roms from Acer site both with and without the 1st line of the script commented out.
Any ideas?
Click to expand...
Click to collapse
OK, is there another way I can approach this as I need to get back before sending the tablet off to be fixed.
1) Can I push the ROM somehow using adb? If so, how?
2) What about installing CWM to flash the ROM and restore custom recovery? This would be my last resort as if it didn't work I'm stuck with root files & CWM!
Any help gratefully received as I need to send it back this week.
First off, I have some questions:
1. Are you unlocked?
2. Are you root? (Doesnt really matter)
3. Android 4.0 or 4.1?
4. At which point is that error showing up?
5. What about the stock beta ROMs?
6. Did you rename the ROM to update.zip and to what place did you copy it ?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
TomONeill said:
First off, I have some questions:
1. Are you unlocked? No
2. Are you root? (Doesnt really matter) Root files (su and busybox) but not superuser.apk due to JB OTA
3. Android 4.0 or 4.1? 4.1.2
4. At which point is that error showing up? After Finding/opening/verifying package
5. What about the stock beta ROMs? No, just the 2 official ones on the Acer site
6. Did you rename the ROM to update.zip and to what place did you copy it ? The downloaded files from ACER are a zip file with a pdf and update.zip inside. I copied update.zip to my SD card. Am I supposed to extract a particular file from it and create an archive out of that that or use the entire thing as I did?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
/system/bin/sh: push: not found
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
Click to expand...
Click to collapse
I'm a bit hesitant about installing CWM as I'm not convinced I won't encounter the same problems as I did with stock recovery.
Thanks again Tom
TomONeill said:
First off, I have some questions:
1. Are you unlocked?
2. Are you root? (Doesnt really matter)
3. Android 4.0 or 4.1?
4. At which point is that error showing up?
5. What about the stock beta ROMs?
6. Did you rename the ROM to update.zip and to what place did you copy it ?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
Click to expand...
Click to collapse
Hi I have question. If my phone USB can't working with PC anymore because the terminal cut out and my Gionee e3 phone stuck on boot logo or bootloop, how can I get it back to normal? Is there a flashable zip files can solve it? If there was please help me. Thanks.
Hey cryingbee,
Can't you get to the recoverymode by pressing volume down and the power button? If not, try booting into fastboot, which I think is volume up + the power button. If those combinations won't work, google for your phone name + fastboot mode. If you can reach fastboot, you can boot into a recovery by using fastboot commands or install new roms etc.
i rooted my deviced. Used systemless root. in the hope OTA would work when a update arrived.
Now there is a update but.... it says the update fails. (in dutch).
I used supersu unroot, but it still says update failed.
I tried using the MDM tools as here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91996
... but that is giving a bogus cannot connect to internet message (I think it just means that there is no server for the g4 phone, internet is fine and fast on phone and pc)
I want the update but Now i am stuck:
-I do not want to re-lock the phone
-I do want the update. (euret -> may to juli security update)
Questions:
-Are there any meaning full error messages.. anywhere?
-are there other ways to flash the OTA?
-I see flashing stock should work. But is my unrooted rom different from stock?
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
Edit: and maybe logo.bin when you had removed the unlocked warning
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
downloading XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip now.
is only option anyway because after trying to flash supersu it won't boot anyway. (but still boots into fastboot mode.. no brick yet)
thx
have you used xposed? or custom kernel?
Bender1987 said:
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
Thank you for this information Bender. I was wondering the exact same thing. I am rooted on a Moto G4 and i was wondering if a OTA update, or reflashing stock would wipe my data + all installed apps.
If i do it your way it shouldn't be any concerns?
srgudhka said:
have you used xposed? or custom kernel?
Click to expand...
Click to collapse
no only supersu and modified hosts file with adaway (main reason for root is titanium backup)
flashed boot, recovery and system with
Code:
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
system boots now with all user data intact in may 2016 update.
However system update nows says it is up to date. .... maybe they retracted the update temporary? ... patience.... (reteu).
@leuk_he
I have a RETEU version here in germany and download the XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip file, which had the same build no as my g4+.
If you try to flash files from the wrong rom, you get an error while flashing or lost temporary your WiFi and IMEI till you find and flash the right one.
So compare the build no on your phone and the stock rom file.
@Zajbot
As long as you don't wipe cache or data or use fastboot erase userdata, all your data should be there.
I have done the same yesterday and all data is still on my phone
---------- Post added at 13:16 ---------- Previous post was at 13:11 ----------
You don't need the OEM fb_mode_set.
Try it again in few hours or reboot, the update should pop-up again, don't worry.
Wifi and imei info are correct(NL) I checked the XT1642_ATHENE from the bootloader screen (did not know this number)
but... patience is a hard one.... :crying::crying: ... and if people say "don't worry... i worry..." bad habit.
Build number accorindg to phoneinfo is MPJ24.139-48 ... but i think that is what i just flashed. Not sure if that is what was in the phone before.
i added the oemset becuase it cried about wrong signature on boot.img it still did afterwards.
@leuk_he
Then you have maybe the wrong ROM. I flashed boot recovery and system and had no errors. But my build no. matches before the update.
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
How does the sideload works?
Thanks
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Bender1987 said:
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Click to expand...
Click to collapse
Didn't work for me. I get the bootloadermenu and when I switched to RECOVERY I got the ANDROID-Picture with "No Command".
Flashing a new recovery.img don't change anything.
Is a sideload flah with adb possible?
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Bender1987 said:
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Click to expand...
Click to collapse
I think there is a problem with my recovery. I flashed the recovery from rom-zip
Edit: get the recovery
Edit 2.: Give up, get with my and yours OTA.zip a sideload mistake (number 7). Now I wait for the next OTA, next days will be hard without ROOT
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Bender1987 said:
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Click to expand...
Click to collapse
thanks for your hint, I start it tomorrow, have a good night
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
SoNic67 said:
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
Click to expand...
Click to collapse
I haven't flash the TWRP, I always boot by mfastboot to TWRP
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
Tried sideloading with twrp , but it gave error 7 on build number. "this device has . "
thx anyway for sharing.
I will now try load older system images with older build number.
/edit:
Flashed MJP-..23 like bender and it now says a update is availble.
interesting side note. when using the build-48 it already showed battery indicator on motowake screen but still at may-2016 security update.