Related
Brand new user here! So much info on this site; truly amazing
I have read so much, but still can't seem to figure out the best, error free method to root the TF700.
- New tablet that I bought 5 days ago.
I understand how to unlock as that's simple.
I understand I need to install TWRP.
After reading a website on androidcentral, I got the impression I need to start the Fastboot tool in Windows, and boot tablet into Fastboot mode, connect to PC...ect.
XDA forums suggests downgrading the firmware and using MOTOCHOPPER
Also, someone said to just install Scott's recovery install tool and rooting will be an option.
Any help would be great as I don't want to mess up my new toy!!!!!
Bryan480 said:
Any help would be great as I don't want to mess up my new toy!!!!!
Click to expand...
Click to collapse
Very understandable!
Downgrading to .8 and using Motochopper is useless by now. That was the easiest method to get TWRP on your tab. You would root and use GooManager to install TWRP. But Goo doesn't support flashing recoveries anymore - so root doesn't get you any closer to getting a custom recovery and a custom rom.
You have to use the fastboot method now (and need to be unlocked for that).
If you are new to this, you may want to read this:
http://forum.xda-developers.com/showthread.php?t=2277112
Scott's tool is a possibility but hasn't been updated or supported in quite a while. I would recommend the Minimal ADB Fastboot Tool:
http://forum.xda-developers.com/showthread.php?t=2317790
Or you go for the whole enchilada and install the SDK Developer tool on your PC.
http://developer.android.com/sdk/installing/index.html
Which is kinda overkill if you don't want to develop stuff for Android. What you really need out of that package is the Platform Tools.
Either way - get the correct drivers installed on your PC and fastboot TWRP 2.6.1 or 2.6.3.1 (I prefer the earlier version) onto your tab.
Then flash away :cyclops:
berndblb said:
Downgrading to .8 and using Motochopper is useless by now. That was the easiest method to get TWRP on your tab. You would root and use GooManager to install TWRP. But Goo doesn't support flashing recoveries anymore - so root doesn't get you any closer to getting a custom recovery and a custom rom.
Click to expand...
Click to collapse
While it is true that GooManager downloads no longer work, it is still possible to install a recovery from a rooted Android using dd to mmcblk0p4. But it is a good idea to do it via fastboot, just to learn how that works in case one really needs it.
Hello
Thank you so much for the reply!!
So I basically need to install the ADB fastbood on my PC and connect my TF700 to my PC via USB?
Do I need to install it on my TF700 also?
Bryan480 said:
Hello
Thank you so much for the reply!!
So I basically need to install the ADB fastbood on my PC and connect my TF700 to my PC via USB?
Do I need to install it on my TF700 also?
Click to expand...
Click to collapse
No you put your TF700 into fast boot mode by booting into the bootloader by holding down power and Volume Down when powering on.
First make sure you have downloaded the correct TWRP recovery blob file for your device from the TeamWin webpage. Use their search to find and choose the blob image for JB4.2 for the TF700T.
Rename it to twrp.blob and put it into the same folder as the fast boot.exe file
Then with it connected to your PC via USB, open a command window in the fastboot.exe folder (shift, right click, open command window here) and type or paste the following one line at a time. Wait for each line to finish:
Code:
TWRP:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot bootloader
When it reboots back into the bootloader pressing the volume down on ECK will now load TWRP
Hello
Think I understand most of this...
Do I need to do anything with USB debug?
When I open command window, due I include TWRP: in each line, or is that not needed?
And what is volume down on ECK?
Sorry If I sound like an idiot; this is all new to me.
Thank you so much!
Bryan480 said:
Hello
Think I understand most of this...
Do I need to do anything with USB debug?
When I open command window, due I include TWRP: in each line, or is that not needed?
And what is volume down on ECK?
Sorry If I sound like an idiot; this is all new to me.
Thank you so much!
Click to expand...
Click to collapse
Omit the TWRP ahead of the fastboot command. I think sbdags meant to write that outside of the code marks.
He's a busy man....
ECK is a typo. Supposed to be RCK, the icon for your recovery in the bootloader menu. And you have to push Volume UP on the flashing icon to enter it. Volume Down let's you cycle through the icons.
He's a busy man
Sent from my DROID4 using Tapatalk
berndblb said:
Omit the TWRP ahead of the fastboot command. I think sbdags meant to write that outside of the code marks.
He's a busy man....
ECK is a typo. Supposed to be RCK, the icon for your recovery in the bootloader menu. And you have to push Volume UP on the flashing icon to enter it. Volume Down let's you cycle through the icons.
He's a busy man
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Oops yep ignore the TWRP: bit and also ECK should be RCK
Ok great
I'm going to try this and will report back!
Thanks again
Hello,
I just want to make sure I have the correct bootloader before I do this, as I don't want to break my new toy!!
My tablet is new...just bought about a week ago.
Thank you so much!!
You guys are great!
Well, if you have a 10.6.1.14.x bootloader, you're good to go.
Sent from my DROID4 using Tapatalk
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Bryan480 said:
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Click to expand...
Click to collapse
What happens when you try to unlock? Need more info.
Bryan480 said:
ok so this has been such a pain!
I can't unlock the tab!
All I want to do it install TWRP via fastboot( i have the TWPR file, and installed fastboot onto my WIN 7 PC) and install a custom rom!
Please help I will donate
I'm and work and plan on trying again tonight.
Click to expand...
Click to collapse
My recent experience with unlocking:
http://www.transformerforums.com/fo...ent/40226-my-recent-unlocking-experience.html
Dave
ok I finally got it to work after at least 15 attempts. Maybe because I bought on ebay?
Flash time.
I flashed TWRP
I put the reboot code...how long does it take?
Bryan480 said:
I flashed TWRP
I put the reboot code...how long does it take?
Click to expand...
Click to collapse
Less than a minute - are you unlocked now?
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Bryan480 said:
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Click to expand...
Click to collapse
Well done and welcome aboard. If you want to change the launcher settings you should flash Apex or Nova launcher from the installer and then you can mess with all sorts of things The stock launcher can't be changed.
Bryan480 said:
Success!!
FINALLLY got everything to work; so easy once I figured it out.
I installed _that's v4, didn't disable fsync....to scared!!
Any other ideas for a first time user?
I'm looking to conserve battery, but also would like good performance.
Oh yeah and how can I get rid of the 5 home screens?!?!
Thanks for everything
Click to expand...
Click to collapse
When you have your system up and running the way you want, go back to your TWRP and do a nandroid backup. After the backup, you can disable your Fsync. The worse case is to restore your back or reinstall your rom but you will enjoy your tablet more with Fsync off...
My phone suddenly started showing zero reception, so i tried wiping it to just get a clean start. Im using TWRP (which i havent really used in the past) and did the "Wipe Data" option rather than the normal wipe because i'm a ****ing idiot. now it says there is no OS installed, so yeah.
I can still boot into recovery but not much else obvously. I'm hoping there's a way for me to mount the phone to my mac and load on a rom and fix it. I understand how stupid i sound but i really need someone to walk me though this. I used to mess around with my GS3 and all my old phones all the time and never had a problem but i haven't with my nexus really since i first got it. I swear i'm not actually retarded.
What are my options here?
FixedTheFernBack said:
My phone suddenly started showing zero reception, so i tried wiping it to just get a clean start. Im using TWRP (which i havent really used in the past) and did the "Wipe Data" option rather than the normal wipe because i'm a ****ing idiot. now it says there is no OS installed, so yeah.
I can still boot into recovery but not much else obvously. I'm hoping there's a way for me to mount the phone to my mac and load on a rom and fix it. I understand how stupid i sound but i really need someone to walk me though this. I used to mess around with my GS3 and all my old phones all the time and never had a problem but i haven't with my nexus really since i first got it. I swear i'm not actually retarded.
What are my options here?
Click to expand...
Click to collapse
You could probably just flash the stock Nexus 5 image from here developers.google.com android section. You'll see a bit saying nexus factory images.
If you can't actually manage to transfer the file on to your phone and flash it from recovery, then just use the tutorial on that page using adb and fastboot.
Yep. The options are fastboot flash stock system and boot.img or adb push a flashable zip to your sdcard and flash via recovery
Click link in signature for sticky then read my adb and fastboot thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yep. The options are fastboot flash stock system and boot.img or adb push a flashable zip to your sdcard and flash via recovery
Click link in signature for sticky then read my adb and fastboot thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot. Solved it with adb sideload cm11. i hadn't really ever used adb before so i was in a bit of a panic.
FixedTheFernBack said:
Thanks a lot. Solved it with adb sideload cm11. i hadn't really ever used adb before so i was in a bit of a panic.
Click to expand...
Click to collapse
Excellent
Sent from my Nexus 5 using Tapatalk
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.
Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images
You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk
Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script
Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.
I'm not the one asking for help. Anyways, carry on.
Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.
Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please
I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs
Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app
my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!