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
Related
GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK release 13 click the file name android-sdk_r13-windows.zip (34 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Note: from SDK release 14 onward, Google removed the fastboot command, you'll have to maker the fastboot command yourself if you want to use the latest version of the SDK
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"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"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
droidmage said:
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools
that way you'll have all the necessary files in the same location to prevent errors
MIRROR:
since CW website seems to be down, here's a mirror for the Image file.
download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)
Good guide but i have a question,
didn't you miss the step about renaming the install-recovery.sh script
that reflash recovery if crc is wrong?
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Cubfan185 said:
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Click to expand...
Click to collapse
thank you, that was the idea.
many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.
it's fairly simple, the instructions are as simple as this
http://forum.xda-developers.com/showthread.php?t=884097
and you can choose any stock ROM to flash back
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.
Edit: Any reason why root required apps are saying they don't have root access?
Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?
silly question... which fastboot binary did you use? the one from the htc developer site?
onicrom said:
silly question... which fastboot binary did you use? the one from the htc developer site?
Click to expand...
Click to collapse
it is included in the Android SDK 2.3 ... read the step by step guide again
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
AllGamer said:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
Click to expand...
Click to collapse
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
sinatosk said:
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
Click to expand...
Click to collapse
yes, i actually like it this way, it keeps your original safe
Titanium Backup and few other apps are why i ROOT the phone as well.
after you fastboot over the CW recovery image and rooted, were you able to install Super User?
there is another trick, you can Install Super User first from Market
then repeat the steps to fastboot the clock work recovery image and get root access
jvblack82 said:
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
Click to expand...
Click to collapse
Followed the guide to a T as well and did not get root access. But unlocking the bootloader, installing the SDK and learning about fastboot and such was very helpful. Using that, I used the automated batch file posted in this topic http://forum.xda-developers.com/showthread.php?t=882333 and it worked.
What to do if my Device Manager showed Android 1.0?
ykphuah said:
What to do if my Device Manager showed Android 1.0?
Click to expand...
Click to collapse
you select the correct driver to install the ABD support or Bootloader support, depending in which screen you have the phone on
just review the step by step guide, it is mentioned there
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
knytphal said:
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
Click to expand...
Click to collapse
... yeah I know. Made a post earlier today about it in this thread...
{
"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
**** if you are looking for rooting your one m9 with android 6.0 , follow this simple guide of mine (http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354 ) ****
HELLO EVERYONE WITH A ONE M9
heres what you've got to do to unlock the monster in your device
1)unlock the bootloader
2)use a custom, more powerful recovery
3)root your phone
4)use a custom rom
you must have working adb and fastboot and htc drivers, if you dont know how to get these files, pls leave a reply.
Now We Will Learn 1,2,3,4
STEP 1:
NOTE:- YOU WILL LOSE YOUR DATA(Unless you have a dev edition htc onem9 , if u have one , skip step 1)
follow these steps:-
A]create a htc dev account here-https://www.htcdev.com/register/
B]go here , make sure ur logged in on htc dev website! -http://www.htcdev.com/bootloader/unlock-instructions/page-2
C] dont download anything ! from htc dev website.
D]connect ur phone to pc and enter download mode :- adb reboot download
E] type the following in cmd< fastboot oem get_identifier_token > look at the pictures on the web page, link in step B, as to how to mark and copy your token identifier code , then paste it in the space provided bellow.
you will get an email from htc dev with a file called Unlock_Code.bin
download it and in cmd type < fastboot flash unlocktoken Unlock_Code.bin>
now, use ur volume buttons to select unlock bootloader and press power button.
FACTORY RESET !
NOTE:- if you have problems following these steps , check out this bootloader unlocking video. im sure it will help you.
https://www.youtube.com/watch?v=Stl4A-ue5IE&app=desktop
DONE! bootloader unlocked
STEP 2:
Note: HTC one m9 is different from previous generation htc ones as it has a block based ota update system. in brief, any modification done to the system will result in an ota update faliure. keeping that in mind, follow my steps as it is
A] download the recovery.img here we are using a beta version of twrp.
http://forum.xda-developers.com/devdb/project/dl/?id=11987
after downloading, rename this file to twrp.img
Also download su bineries+ supersu (required for rooting later)
http://download.chainfire.eu/735/SuperSU/BETA-SuperSU-v2.48.zip?retrieve_file=1
put this file on ur sd card now!
B]go to download mode
type this adb command: adb reboot download
C]go to the directory where you have downloaded the recovery image
type in this fastboot command as soon as the phone is in download mode: fastboot flash recovery twrp.img
DONE!
STEP 3:
A]enter bootloader
B]enter recovery
C] TAKE A BACKUP. A COMPLETE BACKUP . MOST IMPORTANTLY <<<<SYSTEM>>>> DO NOT SKIP THIS STEP. THIS IS VVVVVVV IMP. IF U WANT TO TAKE AN OTA UPDATE EVER WITHOUT RUNNING ANY SORT OF RUU.
D]once thats done, go to advance->terminal and type this as it is:-
mount -t ext4 /dev/block/bootdevice/by-name/system /system
once this is done, go to mount and make sure system is selected.
now install the zip file i had asked you to download in the previous step.
DONE! You are rooted!
if You have forgotten to take a system backup, dont worry, you can find it here, you can flash it at the time of an ota,
https://www.androidfilehost.com/?fid=95916177934550813
STEP 4:
A]For a custom rom , download the customrom.zip file
browse the zip file and extract the file called boot.img
now , put the zip file on ur phone storage or sd-card.
boot to recovery and install the zip file. make sure to wipe cache,dalvik cache, system, and-secure before installing for a clean install, leave data as it is .
IF YOU ARE S-OFF, SKIP THIS STEP:-
B] reboot to download mode and type this fastboot command from the directory you unzipped your rom or extraced the boot.img:-
< fastboot flash boot boot.img>
reboot and enjoy your custom rom !
EXTRA SECTION (VVVVVV IMP)(TO TAKE AN OTA update)
if ever you get an ota update heres what you have to do . do not download it now. first follow these steps.
A)download stock recovery from here:-
https://www.androidfilehost.com/?fid=95916177934554373
rename it as recovery.img
B) download system.img from here ( only if you have not taken the system backup from twrp when in r/o state)
https://www.androidfilehost.com/?fid=95916177934550813
take only the system.emmc.win file from the twrp backup of the original system i had asked you to make before rooting your phone. if you dont have it? you will have to hunt for an ruu, well dont ask me how to do that .
put the system file and recovery.img and put the same folder. run cmd from that folder (right shift+right mouse click ->run command window here)
and type in
adb reboot download
fastboot flash system system.emmc.win / fastboot flash system system.img (depends if you are using a twrp backup or the system image you have downloaded from above)
fastboot flash recovery recovery.img
fastboot reboot
thats it. now download the ota update and once the installation is done, you will need to re-root. follow from step 2 again.
if you get a boot-loop, return to download mode, flash the twrp beta recovery and wipe cache and dalvik-cache. and then reboot , then go back to download mode and re-flash stock recovery.
hope ive helped you
sishirbaid said:
HELLO EVERYONE WITH A ONE M9
heres what you've got to do to unlock the monster in your device
Click to expand...
Click to collapse
Nice job ..thanks
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Duncan1982 said:
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Click to expand...
Click to collapse
If you need help I can start a IRC chat with you. Maybe I can try to help. Let me know.
aooga said:
If you need help I can start a IRC chat with you. Maybe I can try to help. Let me know.
Click to expand...
Click to collapse
That is very much appreciated, I have gone through everything, all SDK stuff installed as per HTC dev but the command is like if the adb and fadtboot is not there on my com, but I have installed.
I will wait as my M8 was so so so easy to unlock, M9 is just a headache.
My computer is off for tonight, I honestly have a sore head with trying to figure it out.
Again your reply and offer of help is appreciated.
Thanks Again, but for tonight "I give up" lol
Haha headache cleared so attempted again from scratch now HTC dev is not allowing me in, reset password and nope saying my login details are incorrect which is Bs as its the one they sent.
I really do now believe my M9 cannot be unlocked lol
That's KARMA.. nothing can be done - everything depends thru which hole you penetrated into this world in the first place..
P.S. Try different web browser though..
jauhien said:
That's KARMA.. nothing can be done - everything depends thru which hole you penetrated into this world in the first place..
P.S. Try different web browser though..
Click to expand...
Click to collapse
Haha Karma indeed, no I'm just going to say F it and be happy with S-On & locked, I managed the all my 12 devices without issue, rooting and unlocking for some, bar the Z2 which was the same headache as this M9 of mine lol
Karma has spoken and I am listening lol
Hello. Great guide. My question is about step 3, system backup for future OTA. I rooted my phone a few days ago, when no all things were clear. So, i made before flashing custom ROM only system backup not a full backup. I have system.emmc.win file saved. can i use it or a full backup is mandatory? thank you.
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Security555 said:
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Click to expand...
Click to collapse
Use TWRP 2.8.6.4
jauhien said:
Use TWRP 2.8.6.4
Click to expand...
Click to collapse
I do. TWRP 2.8.6.4, stock .15 rom
Use SuperSU v2.48 zip
jauhien said:
Use SuperSU v2.48 zip
Click to expand...
Click to collapse
Thanks! Installed 2.48 instead of 2.46 and everything is fine, I have root! Once again, thanks a lot! )
Duncan1982 said:
That is very much appreciated, I have gone through everything, all SDK stuff installed as per HTC dev but the command is like if the adb and fadtboot is not there on my com, but I have installed.
I will wait as my M8 was so so so easy to unlock, M9 is just a headache.
My computer is off for tonight, I honestly have a sore head with trying to figure it out.
Again your reply and offer of help is appreciated.
Thanks Again, but for tonight "I give up" lol
Click to expand...
Click to collapse
don't use google sdk for adb and fastboot! i would suggest this installation. Remember, install it system-wide.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Duncan1982 said:
Haha Karma indeed, no I'm just going to say F it and be happy with S-On & locked, I managed the all my 12 devices without issue, rooting and unlocking for some, bar the Z2 which was the same headache as this M9 of mine lol
Karma has spoken and I am listening lol
Click to expand...
Click to collapse
use chrome , access htcdev , select device not listed and follow the steps , if u want me to make the steps easier i shall post a reply, let me know
Duncan1982 said:
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Click to expand...
Click to collapse
Remember, install it system-wide.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
also , install htc sync manager,for htc drivers. may be the drivers are outdated , m9 being a new device.mine worked fine with the newest htc sync manager.
Security555 said:
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Click to expand...
Click to collapse
ill post the link to the newer supersu.
cclhuzhou said:
The other just reboots into boot loader with it still locked.
{
"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
i dint get ur problem ?
Haha headache cleared so attempted again from scratch now HTC dev is not allowing me in, reset password and nope saying my login details are incorrect which is Bs as its the one they sent.
I really do now believe my M9 cannot be unlocked lol
Click to expand...
Click to collapse
create a new account ! simple
note- htc account and htcdev account are different
ioni2ioni said:
Hello. Great guide. My question is about step 3, system backup for future OTA. I rooted my phone a few days ago, when no all things were clear. So, i made before flashing custom ROM only system backup not a full backup. I have system.emmc.win file saved. can i use it or a full backup is mandatory? thank you.
Click to expand...
Click to collapse
Did u take a system backup using twrp beta? if so , ur safe else if u used twrp (not beta) then you have taken a backup of system with the changed checksum. you are in urgent need of a stock system backup. let me know, ill host it if u need
and ya, only system.emmc.win is good enough if backuped via twrp beta .let me know as to what exactly you did.
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------
Duncan1982 said:
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
Click to expand...
Click to collapse
I want to add the creator of this thread is very helpful though and he offered to guide me through, I was stubborn and knew I could sus it out.
Duncan1982 said:
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------
I want to add the creator of this thread is very helpful though and he offered to guide me through, I was stubborn and knew I could sus it out.
Click to expand...
Click to collapse
Thankyou for that ,I appreciated. It just another thing, could you post the link to the YouTube video you followed ? Thanks
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.
Hi Guys,
So, I spend a few hours reading many posts regarding recovery of the Fire Stick 4K.
I'm in the infinite boot stage and trying to reset to the factory settings after Google Services fu*** up everything.
What I tried:
- adb connection from MacBook
- keyboard recovery
ADB Method Issues
When I connect via adb I get Device Unauthorized and don't really know what to do next. I tried to run fastboot but it stuck on Waiting for any device...
Screenshots:
{
"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"
}
Keyboard Method Issues
I tried the combination of Alt+I+PrintScr many times. None of the sources specifies if I should hold the buttons or keep pressing them on/off during the boot (eg 15x) or at which point I should start or finish pressing. So success here either.
I also tried to use remote but every source shows different buttons to press. Power + Volume Up, Middle Button + Arrow RIght etc.
What should I try next, I'm on OSX?
spyderdsn said:
What should I try next
Click to expand...
Click to collapse
Here is the unbrick thread.
Ok, so I need Windows PC to start with...any other options?
spyderdsn said:
Ok, so I need Windows PC to start with...any other options?
Click to expand...
Click to collapse
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
brick00444 said:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
Click to expand...
Click to collapse
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
spyderdsn said:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
Click to expand...
Click to collapse
I'm almost sure there is a factory rom posted here somewhere. Just use that instead of the rbox rom.
A good reminder to everyone, don't try anything with your device with debugging disabled.
spyderdsn said:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
Click to expand...
Click to collapse
It isn't a cfw, but the stock recovery gets replaced during the unlock. Therefore the stock update app in fireOS won't work as expected, you need to use TWRP recovery and do all updates manually.
brick00444 said:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
Click to expand...
Click to collapse
So the steps in other post are not exactly clear as I'm using the iso
HTML:
https://github.com/amonet-kamakiri/fireiso/releases
.
I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?
Thanks
spyderdsn said:
So the steps in other post are not exactly clear as I'm using the iso
HTML:
https://github.com/amonet-kamakiri/fireiso/releases
.
I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?
Thanks
Click to expand...
Click to collapse
I don't own a macbook but I would think you can because you have to boot to the usb stick and I just use the default option. Wait until you see the desktop. Then go to the internet and look up the unlock thread. You may need to have an ethernet cord plugged into your mac to access the internet (my wifi doesn't work in the iso).
1. Download kamakiri-mantis-v1.2.zip from the link in the original thread.
2. Extract the kamakiri-mantis-v1.2.zip somewhere you will remember. I extract to desktop.
3. Open the kamakiri-mantis-v1.2 folder and then open the kamakiri folder and right click inside that folder and choose open terminal.
4. enter this command in terminal " ./bootrom-step.sh " minus the quotes and click enter. It will say something to the effect of "waiting for device".
5. Short the correct point to the tin casing. It looks like you are shorting it correctly by your pic.
6. Connect the stick to your computer (while keeping it shorted).
7. The script should tell you to release the short and hit enter,. Just pull the tinfoil off the stick . Then click enter (after removing short).
It will take awhile to finish so if it looks like it stalled out give it time.
8. When it is finished enter the command : " ./fastboot-step.sh " and click enter.
9. It will now reboot into TWRP.
10. You can now install the rom. If you don't know how you can follow this guide "https://forum.xda-developers.com/fire-tv/orig-development/newbie-guide-how-to-unlock-bootloader-t4015273" .
Hopefully this helps you. Anyone can add to it or correct it if I missed or forgot something.
Thanks guys for the help. I managed to unbrick my Firestick 4K. and after brick00444 steps I followed this steps:
HTML:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Worth mentioning. Since I used Mac I downloaded https://unetbootin.github.io/ to do the fat32 bootable stick. The stick runs to the menu but is not able to load Linux. I had to find Windows 10 machine and use https://rufus.ie/ to install the iso and everything worked. All other steps I followed brick00444
My Firestick did not had enough space to push the room zip above so I used Adblink http://www.jocala.com/ to remove some apps.
One more question.
I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.
Thanks for your help.
spyderdsn said:
One more question.
I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.
Thanks for your help.
Click to expand...
Click to collapse
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Sus_i said:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Click to expand...
Click to collapse
The sick has been updated now. The update took whole night and it has downloaded 1GB of stuff as my storage was very low at the time. Now I have the latest update and everything seems to work fine.
Sus_i said:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Click to expand...
Click to collapse
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?
spyderdsn said:
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?
Click to expand...
Click to collapse
It's like I said, I guess there is a (partial or full) fireOS update pending
The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.
This is why your stick boots into recovery.
The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).
Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery
Another option, disable updates and keep the OS version on the stick (for now).
Code:
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
But for this option you need magisk installed...
Sus_i said:
It's like I said, I guess there is a (partial or full) fireOS update pending
The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.
This is why your stick boots into recovery.
The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).
Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery
Another option, disable updates and keep the OS version on the stick (for now).
Code:
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
But for this option you need magisk installed...
Click to expand...
Click to collapse
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above
theflashfromthecw said:
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above
Click to expand...
Click to collapse
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.
spyderdsn said:
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.
Click to expand...
Click to collapse
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip. The otacerts is certifying the update that's being rolled out properly and since you renamed it to .bak, you can no longer have it applying the update. It still will update but not apply it if you do end up keeping devicesoftwareota. Only disable the override and leave the rest alone for factory reset reasons because it needs the devicesoftwareota enabled to go through the wizard
theflashfromthecw said:
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip.
Click to expand...
Click to collapse
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues.
but renaming just one zip on system won't trigger dm-verity I guess!?
Sus_i said:
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues.
but renaming just one zip on system won't trigger dm-verity I guess!?
Click to expand...
Click to collapse
It won't. Fire TV devices don't have dm verify at all and it's safe to rename the zip however you want. Because of this, Amazon doesn't have oem unlock and a setting to enable it, there's no official way for the device to check for dm verify and because the bootloader unlock isn't modified to have its own recovery. I have an LG unlocked device that supports oem and after I unlock it, it tells me to relock the bootloader since the manufacturer allowed my device to be oem unlocked.