Related
is there a way to unroot and lock the bootloader again ?
quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.
but as of now no way to flash the stock recovery
slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !
distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?
quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).
distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse
quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod
got it all working now thanks to you and distortedloop .
thanks a lot guys.
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.
I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk
superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.
willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.
For A701 users only running Jelly Bean Only.
Boot image used: AV051_A701_1.021.00_WW_GEN1. Should work fine on other JB builds.
New Version 3 uploaded 23/10/2012
Should fix ADB commands for /System Remount Thanks Vorbeth
2 Parts. Part 2 is full /system RW.... also know as ROOT for the A701 on JB who took the OTA
Part 1 is For people using the previous "andlommy" image flash..... For JB OTA see part 2...
Part 1
This is meant to replace your boot.img after performing the Root image flash from this thread by andlommy;
http://forum.xda-developers.com/showthread.php?t=1911437
Ok people, as some may realize, the current "root" procedure of fastbooting images doesn't allow full /system remount. This can be seen if you try to update your superuser binary. Superuser can't remount /system. Yes, you can probably delete some files via file manager, however, if you use a root app that calls for a /system remount, well, it's not going to happen. Not like it should be.
Also, the 701 doesn't have a reliable CWM, so we do things the old fashioned (and safer) way.
This method has been around in the 500 forums for some time now. Recently, I gave info to the 210 users to get the /system remount working on their tabs. I currently use the same. Why nobody tried it here, well.....
Basically it involves modifying the zimage to change security, and allow remounts. It does not involve the kernel itself, as it remains stock.
Replaces Stock A701 Boot.img
1. Allows for full /System RW
2. Increased IO over stock.
And yes, I do use the modified boot image, 2nd revision.
As always, you have to thank people who helped you in the past and present:And I owe a lot to these guys. (which is why I hit the Donate button for them)
Vorbeth
Civato
EZTerry
Skrilax_CZ
LinuxSociety
NOTE" You must have unlocked bootloader"
Also, you do this at your own risk.Most of you know this already.
Installation:
For previous somewhat Rooted JB installations.
Download the following package and unzip to your system.
FIX-JB-ROOT
1. Connect your tablet
2. USB Debugging is on
3. Open a command window where you unzipped the Fix-JB-Root
4. Type: adb reboot bootloader
after tab reboots to bootloader download, Type;
5. fastboot flash boot JB_701V3_boot.img
6. After success, reboot tablet.
7. Start Superuser and update binaries.
Part 2
AS A ROOT PROCESS. 701 only After OTA to JB.
Note that this is an alternative to the image flash method. You need only to OTA to JB, then follow the instructions.....
Needs Testing on a Stock JB 701 Make sure you've unlocked your bootloader
1. Follow the above procedures in part 1
2. After restart, with tab connected, open a CMD Window where you unzipped the package.
3. Type the following commands;
a. adb devices (and hit Enter. You should see your device listed)
b. adb remount /system (and hit Enter. You should see remount successful)
c. adb push su /system/xbin
d. adb shell chmod 6755 /system/xbin/su
e. Get Superuser and Busybox from the Playstore. Start Superuser, check for updating binaries. Install Busybox.
Hopefully this roots and grants /system RW. I don't have a stock 701JB, so would appreciate feedback if this works or not.
MD
Works perfect Thank you. Now we only nee CM10 for our 701
Thanks MD! Going to give the 4.1.1 another go this weekend, using this boot. Will let you know how it goes )
MD are you able to delete apk from "/system/vendor/app"?
IronFly said:
MD are you able to delete apk from "/system/vendor/app"?
Click to expand...
Click to collapse
Absolutely. Just moved Solitaire.apk into /Data/app
Use your root explorer and check for RW.
Remember, this just fixes a shortcoming in the original "pre-rooted image flashing" from 4.0.4 to 4.1.1 where you can't get system remounts from some root apps.
As stated near the end of the post, I haven't tried it on a "stock non-rooted" JB build.
MD
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse
fishwood said:
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
Click to expand...
Click to collapse
I answered in your original thread.
MD
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
misteral1970 said:
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
Click to expand...
Click to collapse
Yeah, I meant to tell you yesterday it won't help your situation. Your issue, is you're stuck on the ICS bootloader and it won't update to the JB one. Not to mention now, you have that "Hybrid Mix". Maybe one day can come up with a solution for it. Trying to get my hands on a 701 Service Rom.
Acer won't fess up the SBK (Secure Bootloader Key), so it sort of makes NVFlash non-usable unless we have it.
The service rom uses NVFlash, which in theory will change bootloaders (it's what we used in the 500 forums).
But until then, we're sort of stuck. I still have one trick up my sleeve, but's it's a long shot, and not even sure it'll work. Might perma-brick your tab. Will look at my old files.
MD
MD got your method working thanks for sharing this MOD!
RiceDie said:
MD got your method working thanks for sharing this MOD!
Click to expand...
Click to collapse
Which method? Experimental Root? Or just the full System RW?
Also, which build Rom are you running Mate?
MD
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
bschrib said:
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
Click to expand...
Click to collapse
The root method should work the same as with ICS and JB.
Basically need an 700 ICS and JB boot.img. to do the mod. Takes about 10 minutes. Fastboot the boot image, download SU and BB. Should be good to go.
MD
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Vorbeth said:
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Click to expand...
Click to collapse
Should have a modded boot image in a day or so. Seems the boot images are the same for all builds for 700 JB.
It's the weekend, so some family time is on order.
Thanks for the GB full update rom.
MD
Hi,
I was one of the first people who updated their A701 with the unrooted JB ROM which was posted on XDA forums. The update was flawless and smooth using the external SD card and normal recovery method. Last night I tried to unlock my device and root it using step by step instructions given on OP. Device has unlocked but it is still not rooted. I checked using Root Checker app. Have I missed any steps in performing the root operation? Please help.
Additionally after doing all the steps in the OP I reinstalled the original JB update ROM using external SD card and recovery method. Bootloader is still unlocked and device is still not rooted. Device is working fine as far as I can tell.
Awaiting expert advice and help!
Best regards,
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
farazjk said:
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
Click to expand...
Click to collapse
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Moscow Desire said:
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Click to expand...
Click to collapse
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
farazjk said:
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
Click to expand...
Click to collapse
The unlocked bootloader will have no effect on normal day to day operations.
I'll try and get a 700 or 701 stock user to run a couple of things to get the SU issue sorted out. Shouldn't take that long. Probably a matter of using adb to push it through.
The 700 already has a JB Full rom update package, so hopefully the 701 will get one soon as soon as somebody locates it
Think it's time to bother Acer, and see about a SBK......
MD
First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?
I just got the OTA Update to Lollipop
and after i download the files, i press the install and reboot,then my nexus goes to recovery mode (CWM 6)
and then there appears :
. . . (theres still some description)
E:signature verification failed
then i just reboot and get my nexus still on 4.4
im actually forget which ROM im using right now
but in settings , it is KTU84P
FYI : I just unrooted this devices and this happened too when i was trying to upgrade with Nexus Update Checker.
Please help me guys
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
jasonftfw said:
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
Click to expand...
Click to collapse
how to make it sure/check it , that im using stock ROM or not
and how to uninstall CWM ?
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
jasonftfw said:
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
Click to expand...
Click to collapse
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
---------- Post added at 03:01 AM ---------- Previous post was at 02:56 AM ----------
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
just got the OTA notification again, so I'll give it another shot (yeah, i just quoted myself)
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
jasonftfw said:
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
Click to expand...
Click to collapse
thanks but I got the OTA notification again and is now installing without problems
DarknessWarrior said:
thanks but I got the OTA notification again and is now installing without problems
Click to expand...
Click to collapse
Never hurts to know how to sideload for future.
jasonftfw said:
Never hurts to know how to sideload for future.
Click to expand...
Click to collapse
agreed.
I just installed Android Sdk and downloaded the ota from google and im having problems it doesnt side load
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Falconite said:
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Click to expand...
Click to collapse
check out the toolkit from wugfresh, that might be the easiest way for you if you don't know what you're doing... maybe take some notes so that you do remember what you're doing for future.