Related
Any body having problems updating maunauly after flashing cyanogens multitouch. Nexus cnat verify package. Can anyone help?
If the package can't be verified it's probably bad...or a corrupted download. Try downloading it again.
I tried downloading file three time and still get the same thing. Does it have to do anything with flashing cyanogens multitouch? should I wait for OTA update?
I too am having this issue. I am more than willing to donate to his hacking cause if I can just find a way to get this update. I am no opposed to flashing EVERYTHING back to factory. Please would someone look into this.
It's working now
artvandelay300 said:
I too am having this issue. I am more than willing to donate to his hacking cause if I can just find a way to get this update. I am no opposed to flashing EVERYTHING back to factory. Please would someone look into this.
Click to expand...
Click to collapse
I was able to process the update using a guide i found androidcentral . com
I am too new of a member to post links I guess. If you need this link feel free to let me know. Loving the new update
I'm having the same exact problem. Rooted my n1 to install cyanogen's multitouch and now when i try to manually install the OTA update it fails. I'm desperate for help >__< anyone have any tips?
Ok, so here's what I've learned over the last 18 hours.
If your phone is rooted, custom rom OR stock, you can't install the official update package, either over the air, or manually.
You CAN, however, install the patched version of it that modaco released here:
http://forum.xda-developers.com/showthread.php?t=627411
You'll need, at minimum, his 'main update,' and his 'radio update.
You'll also need his NEW VERSION of superboot, if you want to re-root your phone. Installing the updates breaks root, so you'll need this.
DO NOT use the old superboot that you previously used. It broke my Wi-Fi. Get the new one.
Additionally, you'll have to switch from the stock recovery program to Amon-Ra's recovery, available here:
http://forum.xda-developers.com/showthread.php?t=611829
The stock recovery program can only install official updates, and on a rooted phone, that doesn't seem to work. So use Amon-Ra.
So, to review here's the steps in the order you'll need to do them:
1. Install Amon-Ra Recovery 1.5.3
2. Install modaco's main update
3. Install modaco's radio update
4. Use fastboot to flash modaco's new superboot.img to re-root your phone.
Done!
Ok so assuming i follow that tutorial and break my root access, i'd be able install future OTA updates without having to go through all this again correct?
The only reason we can't install it manually now is because we're rooted so it would make sense to say that removing root access would let us perform future updates legit without having to find patches right?
I'm new to android and i honestly don't even need root privileges, i only wanted multitouch.
Well, to my understanding, no, you won't be able to install stock OTA updates, because your rom (your OS), is no longer stock, so stock updates will fail verification, like they did with this one.
I think you can probably restore OTA ability by reflashing your phone with the stock rom, thereby restoring it to the stock state. There's a very detailed tutorial here, with links to a stock image:
http://forum.xda-developers.com/showthread.php?t=614850
Also, here's a link that's stickied in the developer's forum for stock recovery options from modaco. Slightly less detailed, but it looks simpler to me:
http://forum.xda-developers.com/showthread.php?t=619801
I'm pretty sure that being rooted at all breaks OTA support, and having anything in the OS non-stock also breaks OTA support (ie the early MT browser). I could be wrong on that, but I think that's the case.
Crap. I wan't to try installing the stock rom but i'm looking at the directions and i can't follow them. I'm guessing all the things in bold are commands i have to run somewhere but i don't know where.
Yeah, it's a bit confusing, and a lot to get your head around.
You mean the fastboot commands?
You used fastboot when you rooted, right? To flash the superboot.img.
You have to plug your phone into your computer and reboot while holding down the trackball to get the fastboot screen (the white screen).
Then you put the stock images in the same directory as fastboot (which you should still have from when you rooted your phone with superboot) and flash them, using the commands from the tutorial page. (You run them from the command prompt or terminal, depending on what OS your computer has)
tonyx3 said:
So, to review here's the steps in the order you'll need to do them:
1. Install Amon-Ra Recovery 1.5.3
2. Install modaco's main update
3. Install modaco's radio update
4. Use fastboot to flash modaco's new superboot.img to re-root your phone.
Done!
Click to expand...
Click to collapse
Thanks Tony I was also a nub and trying to find the proper way to de-root my phone this worked 100%!
Deetz said:
Thanks Tony I was also a nub and trying to find the proper way to de-root my phone this worked 100%!
Click to expand...
Click to collapse
De-root? So you didn't re-root with the new superboot?
Also, you do know that your phone isn't stock now, right? And that future OTA updates will probably not work without similar steps?
If you followed those instructions, you now have the update, but it's a modded version of it, designed for non-stock roms.
Glad it worked, though!
tonyx3 said:
Yeah, it's a bit confusing, and a lot to get your head around.
You mean the fastboot commands?
You used fastboot when you rooted, right? To flash the superboot.img.
You have to plug your phone into your computer and reboot while holding down the trackball to get the fastboot screen (the white screen).
Then you put the stock images in the same directory as fastboot (which you should still have from when you rooted your phone with superboot) and flash them, using the commands from the tutorial page. (You run them from the command prompt or terminal, depending on what OS your computer has)
Click to expand...
Click to collapse
The tutorial i used to root my phone required me to download superboot and put the folder in my C: drive. The folder is called superboot but when i was running commands on the command prompt some of them said fastboot, so is superboot the same thing as fastboot? This is what that folder looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's what i THINK i have to do.
Download the stock image, extract all the files and put it into the superboot folder i have on my C: drive. Then open up a command prompt and type in:
Code:
cd\
cd\superboot
adb reboot bootloader
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
All while my n1 is plugged in while booted normally but with debugging enabled.
Is this correct or am i missing something?
Fastboot and superboot aren't the same thing.
Fastboot is the bootmode on your phone when you hold the trackball down while powering on. The one with the white screen and androids on skateboards. Fastboot allows you to connect via usb and the command prompt to run some commands on the phone, via your computer, such as flashing the img's on.
Superboot is the name of the img file you flashed (using fastboot), which alters the boot up settings on the phone, giving you root priveleges.
As for your list of commands, I think it looks right. Just do all the steps from the tutorial for restoring stock.
Yes, you start with the phone booted normally, but with debugging enabled. But when you use the adb reboot bootloader command, it will reboot into fastboot mode. You could skip that step and just turn your phone on while holding the trackball down.
Good luck!
And let us know how it goes, eh?
Oh ok cool, i think i get it now.
One last thing before i give it a try though, i was looking at step 11 but a file they want me to flash isn't in my superboot folder, even when i dump the stock firmware files in there. Do i have to get the file "system.img" from somewhere first and put it in the superboot folder or is it auto-generated some how?
Code:
Step 11. fastboot flash system system.img
-edit-
also, this is what my superboot folder looks like WITH the stock firmware files dumped into it:
The boxed files are from the unzipped firmware. Did i place them correctly?
Oh, I see.
The tutorial page has two links to stock roms.
But they seem to be in slightly different formats. The first one is hosted on rapidshare, and the second on modaco, right? So you downloaded
"22607-ERD79-update-nexusone-stock-signed.zip"???
That one has it in a different format from the instructions. Either download the one on rapidshare, or go here and get the "Image Format Download" :
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/300414/18-jan-22607-erd79-stock-rom-for-nexus-one-images-update-zip-online-kitchen-optional-root-insecure/
(note: i've downloaded the one on rapidshare, but not the one on the modaco page I just linked, so I can't verify that they're identical, although they appear to be. I'm downloading the modaco one now, to check the md5sum)
Edit: I downloaded the modaco image in the link, and it is indeed exactly the same as the one hosted on rapidshare in the tutorial (the md5sums match)
Oh ok, ill try grabbing it now then.
I did a checksum for MoDoCos and got a mismatch. Zipped i get:
Code:
5e17b0351024c8fb1a2020f1fd55210e
and non-zipped is:
Code:
e4cf141242e1a362f136a8afd841e0f3
Either way, the rapidfire one is downloading so ill see if that has what i need
-edit-
Cool, the rapidfire md5sum matches up and has my missing file
PhantomRampage said:
Oh ok, ill try grabbing it now then.
I did a checksum for MoDoCos and got a mismatch. Zipped i get:
Code:
5e17b0351024c8fb1a2020f1fd55210e
and non-zipped is:
Code:
e4cf141242e1a362f136a8afd841e0f3
Either way, the rapidfire one is downloading so ill see if that has what i need
Click to expand...
Click to collapse
Right, the checksums won't match, cause the data is different zipped and unzipped. The math that it does on the data wont yield the same result. But the zipped one you posted matches mine. And the other download should match the md5sum posted in the tutorial.
Ok so everything went fine, i now have a non-rooted nexus one with an unlocked bootloader.
Unfortunately, i still cant manually install the OTA update I get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying current system...
assert failed: apply_patch_check(MTD:boot:20930
56:1d155a5be2f8cc6d7cef733f87f3bce97be2c3bd:2101
248:e7f20e513e5bd5c30e20670e992092296ee731a0")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
So what are my options now? Oh and thanks tony, i really appreciate your help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked/locked Device)
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Perform the official upgrade to the US10.4.2.9 firmware manually
Download US10.4.2.9 from Asus: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Remove any external storage media attached to the device before proceeding.
The downloaded file is to be placed in the root directory of the internal storage (/sdcard). Reboot to install if the prompt to install doesn't come up right away.
(instructions by Bolandk. not tested by me.)
FROM THIS POINT FORWARD, THE INSTRUCTIONS BELOW ARE OBSOLETE AND ARE KEPT HERE FOR FUTURE REFERENCE ONLY
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Region conversion instructions
Since ASUS has posted the Jellybean updates for a while now, I thought I'd update this post with instructions to change to another region.
To region convert, you need to download the firmware for the target region. Ideally you want the version you are currently on. I think you may end up losing root in the process, but I don't know a way around that at the moment.
You do not have to be bootloader unlocked to do this.
Extract the xxxUpdateLauncher.zip into the root directory of a microSD card formatted to FAT/FAT32. Then rename the file as EP201_768_SDUPDATE.zip. Reboot into the bootloader (vol - and power), and select the first option (left most square) when the menu comes up. The firmware update will start automatically in this mode.
I converted back from a US to a WW build without wiping using this method.
xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
Good luck!
Click to expand...
Click to collapse
Do you know of a way to force downgrade from Jelly Bean to ICS 9.4.3.17? I don't have any root access and need to restore it.
This works good it took me a little over an hour
but you lose root and the ability to flash a custom recovery (CWM,TWRP)
Please correct me if I am wrong
I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
jvanassche said:
Alright, after some work, I finally got this to install on my unlocked device following these steps:
1) If not already on stock, wipe everything and reflash to stock .30 update and reinstall TWRP 2.2.1.3. Be sure to backup before wiping.
2) Download the zip from the OP, and extracted it to a folder on your hard drive.
3) Open META-INF\com\google\android\updater-script in Notepad.
4) Deleted line 3 and 4 of the file. The Line to be deleted should read assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
5) Create a new zip file containing all of the files you extracted in step 2, including the modified updater-script file, and copy to your device.
6) Reboot into TWRP
7) In TWRP, under mount section, ensure all four mount options are checked, and internal memory is checked at the bottom
8) Flash the zip file you copied in step 5.
9) Reboot, and enjoy your Jelly Beans.
Click to expand...
Click to collapse
Turbojugend said:
I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
Click to expand...
Click to collapse
Just attempted this but got "install fail"
Its my 1st time creating a zip file so maybe I goofed at it. Used 7zipper.
Sent from my Nexus S 4G using Tapatalk 2
I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.
Zadeis said:
I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.
Click to expand...
Click to collapse
You still have root or lost after flash the rom?
wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
You will lose root without a modified dlpkgfile update-script.
wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...
Zadeis said:
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...
Click to expand...
Click to collapse
I'm in the same boat. I backed up root with the OTA Rootkeeper, but after the upgrade, it it doesn't restore root.
I did read in another thread, that some people were successful in restoring root in JB with OTA Rootkeeper, but they had SuperSU installed. Of course, I came across that little tidbit right in the middle of the upgrade
Actually, i'll what I said back. I actually managed to restore my root. I'm not sure what I did differently, but I have thankfully have root again!
i was able to restore root too.
FYI, this worked for me with an unlocked bootloader.
Extremely happy right now. Thanks for this.
Works great with unlocked bootloader, thanks again.
Sorry but what is the point if you already unlocked bootloader/root/install custom recovery , and now you tried to flash back to stock to get OTA update ?
- You tried to root/ flash custom rom at first place, and now you back to stock to get OTA update and you can't root once you update to 4.1.1. More important, 3-4 peoples already get their tab bricked when they tried to flash CWM after Jelly bean update as they attempt to root their device again. And now they screw up cause they can get warranty from ASUS. Why don't you guys wait couple days when developers make a new custom roms based on official 4.1.1 updated so yous just easily flash through recovery. Just my 2 cents :highfive:
sorta works
It worked sort of.
My tf300 was already "unlocked"
But the instructions didnt work exactly.
Here is what I had to do:
1. Use TWRP recovery to install the ICS official rom from ASUS
2. Use the idcrysis method for rooting after initial setup (failed the first time but worked the second try after rebooting)
3. put the dlpk file on the root of the tablet from: http://forum.xda-developers.com/showthread.php?t=1840397
4. Root the firmware using the DebugFS method: http://forum.xda-developers.com/show....php?t=1706588
5. copy "dlpkgfile" into /cache/ directory
6. create the file called "command" under /cache/recovery/
7. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Dunno why it didnt work for me the right way but this is how I got it to work. Not root doesnt work but I can live with that till I read about rooting Jelly Bean tomorrow when I wake up.
If anyone else has issues forcing the jelly bean update these steps I did worked. I am definetely NOT a programmer, just had to follow steps from multiple posts. I kind of wished I could relock the bootloader again. This was such a pain in the rear!
OTA and Fully Removied Moded Binary
xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked Device)
0) Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Good luck!
Edit:
If you are unlocked, you might as well wait for a repacked ROM.
Click to expand...
Click to collapse
I was wondering if you do a full reset, is the device OTA Eligible for future updates and are you able to remove the moded binary by doing a full reset.
does this have any side effects, eg no more ota or is the us version crippled because of patents?
OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.
turdbogls said:
OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.
Click to expand...
Click to collapse
dlpkgfile
All credits to thecubed, autoprime, shelnutt2, everyone else.
Leak from here:
http://www.androidiani.com/forum/modding-lg-g3/417371-twrp-recovery-d855-only-tethered-avvio-da-fastboot.html
Click to expand...
Click to collapse
Hello everyone, I searched the internet today & stumpled upon this TWRP recovery accessible through adb fastboot. This is a Tethered TWRP bootloader, which means you need to be at a computer to open the recovery, (just like iPhone jailbreaking).
THIS DO ONLY WORK ON THE International D855 LG G3 Phone, DO NOT TRY IT ON OTHER VARIANTS/BRANDS!
YOU HAVE BEEN WARNED.
Confirmed working on D855p variant (Mexico version) by badtzo
However, this is not my work. This TWRP recovery comes from androidiani.com.
The following have been translated by Google:
Exclusive for androidiani.com
With pleasure that I want to share the first exclusive international REAL custom recovery , TWRP for the' appuntto and therefore the best, fully functional in all its features, and most importantly optimized for LG G3 with the latest release.
Thank Dees_Troy (TWRP Creator) for collaboration with myself (wolfgart).
Update: Now DPI Full Size. A full screen and with the 'option for backing up the EFS partition active
The below is a bootable recovery in fastboot mode then necessarily need the pc, at least until we have "liberated" the bootloader also the G3 so as to make it bootable from the phone itself.
Why it is still useful to use the TWRP recovery even being able to launch (for the moment) only from PC (fastboot)?
You can finally get your Nandroid Backup and keep it aside.
You can now restore the Nandroid Backup fact, returning to the state in which you want in seconds.
It finally has the chance to try many roms and more, tools, and Spippola the G3 and as much as you like, make sure that you can finally return to the state of your backup created as and when you like.
It finally has a file manager directly from recovery.
Click to expand...
Click to collapse
Steps before it all start:
All though, I HIGHLY RECOMMEND THAT YOU READ THE FAQ FIRST!
Download the package that contains adb , fastboot, and the work on the TWRP:
https://docs.google.com/uc?authuser=0&id=0B9YFzKYNIAlRS1Ntck1GZ0JCOHc&export=download
- Extract the package and place it on your desktop for convenience.
- Enable USB debugging on G3 and connect it to pc with cable. (Also screen-timer is good to have at 1/5min before it goes off)
- Start (inside the extracted directory) the file - 'cmd' .
First time usage (recommended to do!):
1. We now proceed to backup the original recovery in a way that we know it always will be possible to access, (on our PC). Run the following commands pressing Enter each line:
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img (recovery.img you'll find it in the root of sd card)
2. We now proceed to 'elimination of the recovery system and then get out of the mode adb:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
3. Now reboot into recovery (but in reality it will be now, our fastboot mode on phone):
Code:
adb reboot recovery
4. And now we make the much desired TWRP bootable on a G3, fully functional and operational:
Code:
fastboot boot d855.img
Subsequent usage: (when you already have a backup.)
Code:
adb reboot recovery
fastboot boot d855.img
Voila, you have the original TWRP on board.
This is tested on my own device (D855 with Version F & is rooted)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Best regards & all of luck too you all.
I will not be hold responsible for what happens to your device.
Do this at your own risk.
FAQ:
Q: Why does your first post contain so many QUOTES??
A: If some people should post a reply of the original post, it won't contain everything including pics & steps, which is annoying for other users to see all over again.
Q: Is this Tethered Recovery working on other variants/brands of the LG G3
A: NOOOOOOO! DON'T EVEN TRY!
Q: Will this have impact on future OTA updates ?
A: YES! 2 persons, have been stuck in fastboot mode!! Please reload the original recovery, before doing OTA FLASH!
Q: HEEEELP, stuck in FASTBOOT mode! Credits to @clandes #88
A: Put the back'd up recovery into the folder (or download it from the link below) and write
Also do read #93 credits to @Tectas - if you're still having trouble.
Code:
fastboot boot recovery.img
Q: How do I restore to the original recovery? Thanks to pRo_lama #7
A: You need to have backup and must be in root of sdcard aka internal memory. Then do the following:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Q: Can I boot into the TWRP recovery without a computer, maybe through buttons??
A: No you can't, that's what Tethered means.
Q: adb shell - don't work??
A: Ensure that your screen is on & you have trusted the computer, your trying to access your phone with! Also ensure that you are running the cmd from the folder!
Q: su - don't work??
A: You must have rooted your phone, before flashing this recovery else you can't give SuperSU to adb shell on your phone!
Q: Is it possible to theme TWRP?
A: No, not unless you know how to open up the .img & replace the pictures.
Q: Is it possible to root my after doing a CSE flash of a original rom?
A: adb should also be working in the Tethered TWRP recovery, so that should be possible (waiting for ppl, to confirm).
Q: Can I flash this - xxxxxxxxxx ??
A: This is new to all of us, so we can't answar that. You have to test it for yourself & give feedback afterwards.
Q: Will this have any effect on my battery usage?
A: Nop.
Q: Will I lose root after doing this?
A: Depends on what you are doing in the recovery?
Q: What's not working?
A: You tell me & I will write it here. :good:
Q: Do you have a link to the recovery? I accidently deleted it.
A:
LG G3 - 16GB Version:
Official V10F-GLOBAL-SI (16GB Italy): https://mega.co.nz/#!Yd91ALDA!C-cfGKhVCCi3SOJ6q3o-Lzy1Qe7q89afj98hrtoLY2M
Official V10G (16GB Italy): http://forum.xda-developers.com/showpost.php?p=54496418&postcount=80
LG G3 - 32GB Version
Official V10F (32GB Indian): http://www.4shared.com/file/MOn-Ji8-ba/recovery.html
Click to expand...
Click to collapse
Thanks for posting it here bud:thumbup:
I'll try to install it later on... Hopefully my win 8 allow me too lol
Sent from my LG-D855 using XDA Free mobile app
d855 only
hello00 said:
d855 only
Click to expand...
Click to collapse
I have now edited it with an First & Second attempt to clarify that you don't need to take a backup everytime.
danny_and_2 said:
I have now edited it with an First & Second attempt to clarify that you don't need to take a backup everytime.
Click to expand...
Click to collapse
This isn't official is it? I tried to find our phone on their website and it is not listed
Tested and it's working on my D855.
If you want to restore your original recovery use this commands (you need to have backup and must be in root of sdcard aka internal memory):
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
F4M0U569 said:
This isn't official is it? I tried to find our phone on their website and it is not listed
Click to expand...
Click to collapse
It isn't listed, because our bootloader isn't fully cracked yet. This tethering fix, should however let us do pretty much the same. :good:
pRo_lama said:
Tested and it's working on my D855.
If you want to restore your original recovery use this commands (you need to have backup and must be in root of sdcard aka internal memory):
Click to expand...
Click to collapse
Added to FAQ, thanks pRo_lama for clearing that up! :fingers-crossed: :good:
just to confirm ....we cannot enter this recovery through buttons ? we need to be at a pc with adb working i think
confirmed working on D855
I believe development on the G3 should begin soon
rraaka said:
just to confirm ....we cannot enter this recovery through buttons ? we need to be at a pc with adb working i think
Click to expand...
Click to collapse
As mentioned in the FAQ, yes you are 100% right. We can not access this through buttons YET.
sooti said:
confirmed working on D855
I believe development on the G3 should begin soon
Click to expand...
Click to collapse
Great to hear that you got it working!
Lets hope the devs, will have some more options open now!
danny_and_2 said:
As mentioned in the FAQ, yes you are 100% right. We can not access this through buttons YET.
Great to hear that you got it working!
Lets hope the devs, will have some more options open now!
Click to expand...
Click to collapse
As long as you can flash kernel + system, it should be possible to develop CM roms and so on,
Once the CM team adds the G3 device tree, I promise to bring roms such as 'beanstalk', 'AOSB and others to the G3 (I brought lots of them to the galaxy s2).
Its only a matter of time,
Keep in mind though that it will not be a permanent solution, since the bootloader is still locked, so once LG patches this, you will not be able to flash custom roms again
danny_and_2 said:
This is a Tethered TWRP bootloader, which means you need to be at a computer to open the recovery, (just like iPhone jailbreaking).
Click to expand...
Click to collapse
Works like a charm, thanks.
Since the phone is already hooked to the computer, is there a way to write the backup to the computer without first writing to sdcard ? (I have no space left on sdcard)
sooti said:
As long as you can flash kernel + system, it should be possible to develop CM roms and so on,
Once the CM team adds the G3 device tree, I promise to bring roms such as 'beanstalk', 'AOSB and others to the G3 (I brought lots of them to the galaxy s2).
Its only a matter of time,
Keep in mind though that it will not be a permanent solution, since the bootloader is still locked, so once LG patches this, you will not be able to flash custom roms again
Click to expand...
Click to collapse
Sounds good, I do only have knowledge about how it works for the S4, but it seems it's a bit more hardcore here at LG.
I know it's not a permanent solution, hopefully there's soon a backdoor there will open the locked bootloader. :good:
Yea, lets see what LG's move is next. Good thing we aren't forced to update, so we can just cancel the upcomming updates/OTA, until we are sure the tethered recovery works at the next version :victory:
MrTip said:
Works like a charm, thanks.
Since the phone is already hooked to the computer, is there a way to write the backup to the computer without first writing to sdcard ? (I have no space left on sdcard)
Click to expand...
Click to collapse
Unfortunately, I am not that sharp to linux dd commands, maybe @pRo_lama can help?
danny_and_2 said:
Unfortunately, I am not that sharp to linux dd commands, maybe @pRo_lama can help?
Click to expand...
Click to collapse
My wording lacks precision, english is not my first language.
I meant a nandroid backup. Performing twrp backup using usb cable to write files on the computer.
MrTip said:
I meant a nandroid backup. Performing twrp backup using usb cable to write files on the computer.
Click to expand...
Click to collapse
I'm not sure if this is possible in TWRP.
MrTip said:
My wording lacks precision, english is not my first language.
I meant a nandroid backup. Performing twrp backup using usb cable to write files on the computer.
Click to expand...
Click to collapse
pRo_lama said:
I'm not sure if is this possible in TWRP.
Click to expand...
Click to collapse
Seems like it is, however I would still perfer to do it directly to the sdcard & then transfer. Heres the link:
http://forum.xda-developers.com/showthread.php?t=2611099
danny_and_2 said:
Seems like it is, however I would still perfer to do it directly to the sdcard & then transfer. Heres the link:
http://forum.xda-developers.com/showthread.php?t=2611099
Click to expand...
Click to collapse
I meant directly in TWRP. I know that can be done with commands in ADB.
pRo_lama said:
I meant directly in TWRP. I know that can be done with commands in ADB.
Click to expand...
Click to collapse
Good question. It don't seem like it when I search on the internet.
A upcomming queston you might can help me answar:
Is it possible in this TWRP recovery to run the adb commands? If ppl forget to restore the original recovery & perform a CSE flash to a new version.
Can they run the adb commands in TWRP to ex. PurpleDrake Lite to acquire root?
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
If your stupid like me :silly: and you blindly follow the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide you may be trying to figure out how to fix your phone.
The beginner guide linked above is amazing to say the least but the OP has not updated it yet to reflect the 6.0 update. If your phone has Marshmallow 6.0 and you follow the instructions you will render your Nexus 6 unusable. Not bricked, just not functional. You will get an error that states Your device is corrupt. It can't be trusted and may not work properly. (seen below) Followed by a blank screen. But don't worry, its very easy to fix with just a few extra steps. :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are here, it is assumed that you have already done the following steps:
Step 0.1 Download and install the Android SDK tools (adb and fastboot), as well as the Google USB drivers. This is step 2 in the beginner guide and there is a great write up here on these tools. [noob-read] adb and fastboot. What is it? How can it help you?
Step 0.2 Unlocked the Bootloader.
Step 0.3 Ran the CF-Root tool. The file name is CF-Auto-Root-shamu-shamu-nexus6.zip
If you watched the CMD window closely this is where the problem happened. There will be a couple errors thrown. You will wait to see the big red Android on your phone but instead you will see the above warning message flash briefly followed by a black screen. If this is the case, proceed to step 1
Please Note: Parts of these steps are copied and pasted from other instructions. Consider this a grouping of other instructions for the purpose of simplification.
Step 1 - Install a Custom Recovery (taken from the original guide)
Go HERE to download the latest TWRP recovery for the Nexus 6. At the time of this write-up, I used 2.8.5.0
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img
Move the recovery.img file to C:\Program Files (x86)\Android\android-sdk\platform-tools
Open command prompt and run the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it.
After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Power off the phone
Step 2 - Install the Modified boot.img (Original steps HERE)
Download the modified boot.img from http://downloadmirror.co/android/sx/shamu-mra58k-boot.zip
Unzip the file and move it to C:\Program Files (x86)\Android\android-sdk\platform-tools
Boot the phone back into bootload mode using Power + volume down.
Open a command prompt and enter the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash boot boot.img
Power off the phone
Step 3 - Flash the SuperSU zip via TWRP Recovery v2.56 beta (original steps HERE)
Downlaod SuperSU x2.56 from http://downloadmirror.co/android/u1/SuperSU-v2.56-20151030013730.zip
Boot your phone into the bootloader mode with Power + volume down
Enter recovery mode. This will open TWRP Recovery
After TWRP Recovery is open, connect your phone to your computer.
Open My Computer where youc an see the C: drive, and other connected drives. You should see your Nexus 6 listed. Open it.
Move the SuperSU zip onto your phone. I placed mine in the TWRP folder.
On your phone, select Install, then navigate to the folder that contains the SuperSU zip. Click on the zip file.
Swipe to Confirm Flash and begin the flash.
Once SuperSU is flashed, select the Reboot System option.
And that's it, your phone should now boot back up to your fresh rooted copy of Android Marshmallow 6.0. You can download a root verification app to confirm the root. :victory:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
simms22 said:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
Click to expand...
Click to collapse
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
For those of us who have been down this road a time or two, this guide will not help them at all. Its really just directed to newbie's who are now stuck because of the beginner guide above.
K!ngpen said:
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
Click to expand...
Click to collapse
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
simms22 said:
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
Click to expand...
Click to collapse
I'm right there with you. My first rooted device was a motorola xt720 sometime in 2010 I think. It was a company phone and like most very young IT folk I was curious lol. New versions of Android started rolling out but the phone wasn't going to get the update. So i was suck on Eclair. I stayed after work and tried the root, and it didn't work to say the least... I stayed at work until 2am trying to get that darn thing to work. 3 days later I got it to flash cyanogen. It was buggy as hell but i didn't care because I didnt have to explain to my boss that I broke my phone by trying to "hack" it lol. That was a win in my book. I later worked up the courage to get it back on a rooted version of Froyo. Pretty bumpy start to my rooting career to say the least. Now I'm a die hard Nexus follower just looking for an excuse to root the next device.
K!ngpen said:
You followed the correct instructions haha...
Click to expand...
Click to collapse
Everyone who is trying to help other users earns respect.
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Noopguy said:
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Click to expand...
Click to collapse
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
K!ngpen said:
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
Click to expand...
Click to collapse
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Noopguy said:
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Click to expand...
Click to collapse
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
K!ngpen said:
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
Click to expand...
Click to collapse
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Noopguy said:
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Click to expand...
Click to collapse
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Noopguy said:
I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp.
Click to expand...
Click to collapse
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
sjgore said:
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
Click to expand...
Click to collapse
That's strange, I sideloaded that for MRA58K, MRA58N and MRA58R and I don't think I was ever prompted to update the binaries. I'm not sure you are being asked to.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
Thanks guys, this really helped. Flashing 2.52 did the trick and i didnt need to update the binaries after i flashed it. I am also on MRA58R
I was going to say as well, SuperSU v2.52 is what needs to be installed via TWRP, not v2.56. I believe v2.56 is for the new systemless root option but it sounds less stable and buggy.
Does this wipe any data? I have been looking to root and actually followed that guide myself, got the same issue and fixed by reflashing a factory image.
EDIT: I'm assuming I don't have to break my phone again to do this correct? Can I just pick up from step 1 to flash the recovery and go from there?
Something weird happened to me after flashing TWRP and I thought I'd share. So my N6 wasn't corrupted at all, but I decided to root my phone and I started by flashing TWRP. I went into boot loader and then recovery to make sure it worked and it did. When I went to reboot the system, I got the the "your device is corrupt screen." I pressed the power button and the screen turned black for a few seconds and then it rebooted normally. I went back into recovery to try and reproduce this and it happened again, Not sure why this happened but everything is functional.
New to rooting and I want to root my Nexus 6
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
atvisic said:
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
Click to expand...
Click to collapse
Lol why break it first. I didn't read through the op here but all you need to do is unlock the bootloader. Flash twrp with fastboot. Reboot to recovery without booting the phone, if you boot the phone before going into twrp it will get overwritten and you will need to reflash it. Flash a custome kernel in twrp, flash SuperSU 2.52 or higher in twrp.
The instructions in the op are more complete naturally. But when it has you flash the boot.img, you can use a custom kernel instead.
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.