Related
Hey all, I had the rooted RC30, and just updated to the RC33. The update itself went fine, but when I am trying to go back into the recovery mode to apply the radio rom update, I cant get the phone to go into recovery mode anymore. I hold the home and power and all it does it cycle the G1 screen. Then boots normally. Anyone have a idea whats up?
Anyone? =/
Ok Im running out of ideas, I tried booting into recovery mode without the memory card inserted, still goes in a reboot cycle and will only boot into the normal mode, wont go into recovery, so I am really confused now. Any advice or so how to get things back to normal would be great please.
try going into the terminal and typing reboot recovery
This just happened to me to i really need help i dont know whats goin on just started... could the phone be possibly bricked? O yea and that process didnt work Tubak is there any other ways to get into recovery mode
Can you boot into the SPL (hold camera button while powering on)? If so, you can fastboot flash the latest recovery.img (from the JFRC33 1.42 build), and that should get you going.
tubaking182 said:
try going into the terminal and typing reboot recovery
Click to expand...
Click to collapse
Says "Operation not permitted"
as for holding down the camera button and powering up, I can get into that screen. So your saying just to reflash the pack I just updated with again? It wont wipe my phone will it?
But yea, would be nice to get things going again. Also oddly when I boot the phone up, normally process media is asking me to either wait or force close. Sometimes another app will be listed as well. Anyone else have that on bootup like if the phone has too much starting up with? Btw thanks for the replies so far. =)
did you run the reboot command as root? if not run it as root, sorry i assumed you knew to but i didn't specify so it can be confusing. also as daveid said you can always try to fastboot flash the recovery image
tubaking182 said:
did you run the reboot command as root? if not run it as root, sorry i assumed you knew to but i didn't specify so it can be confusing. also as daveid said you can always try to fastboot flash the recovery image
Click to expand...
Click to collapse
The response was "Can't open reboot" when I did su reboot recovery
(Edit: Scratch that I feel stupid I wasnt in # mode yet, the reboot command worked however it did the same thing, cycle the G1 screen, rebooted again and booted normal)
Also again on the flashboot, so I use the same file I used to upgrade to rc33? Also it wont wipe my phone would it by that method?
Edit: So if its not too much trouble by doing the fastboot what is the real method of using this? Also which file am I using and will it wipe? And is there any other possible reasons why this could happen that it didnt go into recovery mode?
Mysticales said:
The response was "Can't open reboot" when I did su reboot recovery
(Edit: Scratch that I feel stupid I wasnt in # mode yet, the reboot command worked however it did the same thing, cycle the G1 screen, rebooted again and booted normal)
Also again on the flashboot, so I use the same file I used to upgrade to rc33? Also it wont wipe my phone would it by that method?
Edit: So if its not too much trouble by doing the fastboot what is the real method of using this? Also which file am I using and will it wipe? And is there any other possible reasons why this could happen that it didnt go into recovery mode?
Click to expand...
Click to collapse
You will want to extract the recovery.img from the JF update.zip to wherever you have fastboot installed. Then you will enter a command prompt, change to that directory and issue "fastboot flash recovery recovery.img"
If you need further help see the sticky here.
Ok been a lil while since I went back to this issue.. (Had my phone suspended so wasnt using it) Just got it back running after a month.
I looked at the sticky, but Im guessing Fastboot wasnt installed? So to install it, do I just need to put the fastboot onto the memory card or so? Guess just need lil help cause hate this.. since I cant get into the real recovery, but I can go into the other one.
before u updated to jfrc33 you shouldve done this
if u followed directions on the thread it would worked
so this is the only way i see possible to get the recovery program back
u have to go back to rc29 and then re-root and install the recovery image
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
edit:
check my sig for the jf tutorial
"unlock your dream"
Question tho, I already had jfcr installed w/root before I updated to the newer version, which I was told was fine. I still have my root access atm as well since I use root only apps.
I can still access the other mode by holding down the camera button. So your method your suggesting, is that what I really need to do or is it something else based off this info?
Alternatively, you could push recovery.img to /system using adb.
The init script will reflash it automatically.
billc.cn said:
Alternatively, you could push recovery.img to /system using adb.
The init script will reflash it automatically.
Click to expand...
Click to collapse
adb? Explain some more please? ^^
edit: Using the terminal, ok I saw some similar commands. Ill give this a shot once I get home with my PC. Anything special I need to prep before I do it or just put the img file in the sd root dir and do the adb command for push?
Ok good news. I was more nervous about toying with things I dont know 100% however I sat down a lil more and figured out everything that was being said. The fastboot flash recovery recovery.img worked.
This posted helped ALOT.
http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
I was under the impression at 1st however that it was done all via the phone itself and not the PC. So thats where my orig confusion started. However I am now back into my recovery mode and can go back to updating my phone. =)
One quick question tho, after I got the PC to be just the ADB interface, how can I get to mount it to my PC again as a mass storage device? Just redo the drivers again? Or is there a way to swap easily between the 2 modes? (I can use a memory reader so its not a big deal but thought id check)
I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.
you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.
I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.
This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock
I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.
chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
robscar said:
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
Click to expand...
Click to collapse
You need a custom recovery! download twrp here: http://techerrata.com/browse/twrp2/tf300t
DOWNLOAD THE ONE THAT SAYS "openrecovery-twrp-2.5.0.0-4.2" and flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob" make sure you rename the blob to "twrp.blob"
*update your info your bootloader is "10.6.1.15.3" instead of "10.6.1.12.3"
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can also follow this guide. It explains what you need to do pretty well. But you do need a custom recovery, which i prefer TWRP http://forum.xda-developers.com/showthread.php?t=2187982
I was confused at first too. I think they need to change the wording in the tutorials. They say "If you're on JB bootloader, this twrp, if you're on 4.2 BL, that TWRP" and i was just thinking... WTF, both of them, 4.1 and 4.2 are jellybean.... it should be changed to 4.1 BL and 4.2 BL, none referred to as JB.
Sent from my TF300T using Tapatalk 2
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
robscar said:
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
Click to expand...
Click to collapse
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
I've a TF300TG but I think my question is associated to the title of this thread. Do I have to note the sku of my Pad or isn't that important when I flash a custom Rom?
In the threads of many custom Roms I've read nothing about the sku. So I'm not sure if I have to take care for this.
Sent from my HTC One X using xda app-developers app
noahvt said:
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
Click to expand...
Click to collapse
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
robscar said:
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
Click to expand...
Click to collapse
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
diesburg said:
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
Click to expand...
Click to collapse
I got these files from the SDK download for MAC.
robscar said:
I got these files from the SDK download for MAC.
Click to expand...
Click to collapse
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
robscar said:
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
Click to expand...
Click to collapse
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
diesburg said:
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
So, no matter what I do, the bootloader has to be unlocked, correct?
robscar said:
So, no matter what I do, the bootloader has to be unlocked, correct?
Click to expand...
Click to collapse
for a custom rom, as far as i know, yes
but for just root on stock rom i believe theres ways to root stock without unlocking the bootloader
Sent from my TF300T using Tapatalk 2
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
robscar said:
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
Click to expand...
Click to collapse
It's most likely drivers.
http://forum.xda-developers.com/showthread.php?t=1917237
Maybe that'll help?
Sent from my TF300T using Tapatalk 2
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
robscar said:
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
Click to expand...
Click to collapse
not sure exactly how a mac works but i believe its some sort of linux. can you by chance start the terminal with "administrator" priveleges or type "su" in the terminal to get root priveleges? Just my thoughts with a "permission denied" error, you dont have administrator/root access.
In that link i shared above about mac and fastboot, it says to use " ./ " in front of every command. So try the fastboot commands i said above to flash the recovery but do it with ./ infront like this: ./fastboot flash commands
Sent from my TF300T using Tapatalk 2
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
robscar said:
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
Click to expand...
Click to collapse
In the steps I told you above. The part where you do the fastboot commands in the terminal. "fastboot flash 0x(somenumber) recovery twrp.blob"
put a ./ in front of the fastboot command... so its "./fastboot flash 0x(thatnumber) recovery twrp.blob"
Sent from my TF300T using Tapatalk 2
I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.
so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..
simms22 said:
so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..
Click to expand...
Click to collapse
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.
shampiaj said:
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.
Click to expand...
Click to collapse
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery
simms22 said:
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery
Click to expand...
Click to collapse
Thanks.
Doesn't ADB side-loading still work with custom recovery?
You need to unroot
shampiaj said:
I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.
Click to expand...
Click to collapse
Yes, you need to unroot to recive the OTA, in my case, i have a custom rom, so i will go stock if the update improves perfomance,because i have installed the camera fix v 1.3 and I'm happy with it
jt3 said:
Doesn't ADB side-loading still work with custom recovery?
Click to expand...
Click to collapse
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!
AceKingNYC said:
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!
Click to expand...
Click to collapse
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
EDIT: In my original response post, I'd noted that the OP was obviously familiar with ADB, since he'd rooted his Nexus, I left that out of this post, so if you're wondering what the heck ADB is, that's why this post seems incomplete. ADB is part of the Android SDK. There are many other threads that cover its installation and use, but it's a good tool to have, even if you don't root (for side-loading updates, via the above steps, for example... no root required!).
jt3 said:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
Click to expand...
Click to collapse
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?
shampiaj said:
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?
Click to expand...
Click to collapse
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
jt3 said:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
Click to expand...
Click to collapse
Yeah, I'm stock/rooted but have flashed some mods. Luckily I keep all the .zip files so it sounds like the worst case scenario is that I'd have to re-flash the mods and re-root, which isn't a big deal. And I always make a nandroid before I do something. I'm more worried about data loss since it's taken me weeks to get to where I am now
Thanks for all this information, dude.
There's going to be boat loads of these exact same threads all over General, Q/A and Development when the update is released. Not sure why there isn't a sticky pertaining to OTA updates with regard to root, recovery, etc to curb all these posts.
To the OP, just use ADB and manually flash the images you want. Then simply flash SuperSU in recovery. Done.
If you don't know how to use ADB, then you need to do yourself a favor and learn about it. It'll save you time in the long run and you'll realize that GUI and CLI toolkits aren't necessary.
jt3 said:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
Click to expand...
Click to collapse
This is super clutch ! I thanks alot for this
Im rooted/unlockled BL and have TWRP. I havent done ANYTHING else, not even Titanium backup for fear it would affect my ability to OTA. So it seems that I should be good right?
I will almost certainly sideload the update, as I've never had a device get an OTA less than a week after it has gone live.
Assuming a bone-stock, unrooted Nexus 5, should I consider returning the phone to the factory-set Dalvik JIT instead of the ART compiler (been using this since day one) prior to side loading the downloaded OTA update (when that becomes available)?
Sent from my Nexus 5 using Tapatalk
Guys, maybe I missed something, but I did a totally different thing on my Nexus 7. When The first release of 4.4 released, I flashed manually with flash-all.sh. Then I flashed TWRP, and rooted my N7. Couple of days later I received OTA update, I didn't do anything just clicked to the flash update. It is reboot my device, and the OTA successfully installed automatically from the TWRP, and rebooted my N7. After this I reboot my device to TWRP and flashed the superuser.zip. I rebooted the N7 and everything works well.
This way is not possible to receive and install the next OTA for N5?
Sent from my Nexus 7 using Tapatalk
Okay, got the 4.4.1 update. Here's the scoop.
My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.
Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).
I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.
Here's the link, for anyone who wants it: KRT16M to KOT49E Update.
I have it on root and CWM also. I get to the step of install from sideload. I use CWM to say "install from sideload" and it starts ADBd but i can't connect to it via the pc. If i am in just android i can ADB. So something is up there.
jt3 said:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
Click to expand...
Click to collapse
jt3 said:
Okay, got the 4.4.1 update. Here's the scoop.
My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.
Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).
I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.
Click to expand...
Click to collapse
So steps 13 and 14 in your list were done in CWM recovery instead of the stock recovery, correct? So if you're attempting the sideload using a custom recovery (I have TWRP), step 14 will be just choosing "apply update from ADB" or similar depending on which recovery you use. Everything else should be the same. Just wanted to make sure I understood your steps before attempting it myself.
Thanks!
---------- Post added at 01:12 PM ---------- Previous post was at 01:02 PM ----------
Alternatively, could we just grab the stock recovery image for 4.4 and reflash that using fastboot and apply the OTA when it lands on the phone? I'm thinking about doing that for my wife's Nexus 4.
Has anyone else lost 'reboot' from the power menu? I did have the Advanced 4 way reboot menu mod installed, but restored stock menu before TWRPing the update. It this a side effect of that or just 4.4.1?