I tried to use the search and google but didn't really find anything helpful. Almost 2 years ago, I unlocked the bootloader back on honeycomb and did custom recovery, root, and custom rom. Then a little while after ICS came out, I did the OTA update.
Today, I reset the xoom back to stock ICS and tried to unlock the bootloader again...thinking nothing of it. The process was taking a few minutes so I decided to get a snack and when I came back it was rebooting.
I assumed that it worked and continued to try and fastboot a recovery image. The recovery image installed and I did another reboot but was greeted with the android welcome screen. Anyways I went through the menus and then tried to enter recovery and it gave me an android laying on its back with and exclamation point above his open chest.
I hard rebooted and can still get into my device, but adb cannot seem to find my xoom anymore. I have tried it on a 64bit desktop and laptop with no luck.
Have I messed up? Or is there a simple fix that I am missing? Thanks in advance for any help!
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
dfib1 said:
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
Click to expand...
Click to collapse
Yes, I can get into fastboot by holding the volume down key and the power button. That's fastboot, right?
Yes, I had to go through the menus the second time I unlocked.
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
dfib1 said:
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
Click to expand...
Click to collapse
I want to flash this ROM
http://forum.xda-developers.com/showthread.php?t=1997434
With whichever recovery is best. I tried flashing this recovery:
http://forum.xda-developers.com/showthread.php?t=1074979
I am on a 4G xoom on 4.0.4 but I don't use my data plan. I would like to be on a nice stable build of 4.2.
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
I think it is fine just the 3g/4g won't work.
I can get you going again but you are going to be starting with a locked honeycomb device. You will then have to either let it update to ICS or JB or unlock, root, install custom recovery and flash a rom. What xoom do you have 3g or 4g?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Okay I restored it again but this time i did a factory reset and wipe dalvick before flashing the rom and gapps. It works! Thank you for your help!
However, could I ask how to root this thing?
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
dfib1 said:
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
Click to expand...
Click to collapse
Thanks! Got it!
g;lad to hear it.
Related
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
suhas_sm said:
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
Click to expand...
Click to collapse
When it boots to that, try pressing the home button
Sent from my Onyx CM7 Google Nexus S!
You mean on the exclamation screen? I vl try that but I don't I will help cost I had remove battery to make that screen go away
Sent from my Nexus S using XDA App
Just give it a go. Battery pulls don't hurt the phone.
Sent from my Onyx CM7 Google Nexus S!
suhas_sm said:
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
Click to expand...
Click to collapse
What rom are you on?
everything stock ... clockwork mod installed from rom manager .. latest and current are same...but rooted.
kenvan19 said:
Just give it a go. Battery pulls don't hurt the phone.
Sent from my Onyx CM7 Google Nexus S!
Click to expand...
Click to collapse
Tried it. Nothing happens. Have to take battery out. But I can still access recovery by rebooting in recovery from rom manager
Try installing it from the bootloader.
Name the image file recovery.img
Put it in the android sdk tools folder(or wherever your fastboot.exe is) and run the command -
"Fastboot flash recovery recovery.img"
Then reboot, it should work.
The android with a "!" is the stock recovery. You don't have to pull the battery at that screen, just press hold power button, then press volume up, you should end up in stock recovery.
In ROM Mgr, FLASH clockwork recovery (twice for good luck, seriously) before trying to boot/backup from ROM Mgr. That should get you going.
The fastboot flash method mentioned above also works.
Part of your issue is that there's a file called /etc/install-recovery.sh that overwrites clockwork recovery with the stock one every time you boot up normally. Rename/delete that file and clockwork will stick after that.
suhas_sm said:
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
Click to expand...
Click to collapse
I have found if you to flash Clockworkmod recovery from Rom Manager and you already have the same version, it will remove it all together.
just reboot your phone and run the recovery installer once. Right now, it should be version 3.0.0.5. After you run it. Reboot your phone -> hold power + up (or down don't remember) -> select recovery.
If it is there, you should be able to get to it from the Rom Manager link also.
Serious_Beans said:
Try installing it from the bootloader.
Name the image file recovery.img
Put it in the android sdk tools folder(or wherever your fastboot.exe is) and run the command -
"Fastboot flash recovery recovery.img"
Then reboot, it should work.
Click to expand...
Click to collapse
yeah will keep that as option if Rom Manager doesn't work for me.
distortedloop said:
The android with a "!" is the stock recovery. You don't have to pull the battery at that screen, just press hold power button, then press volume up, you should end up in stock recovery.
In ROM Mgr, FLASH clockwork recovery (twice for good luck, seriously) before trying to boot/backup from ROM Mgr. That should get you going.
The fastboot flash method mentioned above also works.
Part of your issue is that there's a file called /etc/install-recovery.sh that overwrites clockwork recovery with the stock one every time you boot up normally. Rename/delete that file and clockwork will stick after that.
Click to expand...
Click to collapse
Thanks for the information That should explain why Clockwork doesnt show up everytime. And yeah didnt have to pull the battery, simply went into default recovery from that screen Thanks. will try renaming install-recovery.sh
GchildT said:
I have found if you to flash Clockworkmod recovery from Rom Manager and you already have the same version, it will remove it all together.
just reboot your phone and run the recovery installer once. Right now, it should be version 3.0.0.5. After you run it. Reboot your phone -> hold power + up (or down don't remember) -> select recovery.
If it is there, you should be able to get to it from the Rom Manager link also.
Click to expand...
Click to collapse
I installed once again. It said no recovery or image found. Installed again, could go into clockwork recovery but after rebooting again the same
renaming install-recovery.sh in etc folder worked Now can I go into clockwork recover on every boot
I I have been searching for the net how to root my gedified xoom wifi 4.1.2,
My main objectives are
a) Root my xoom (because it is needed for OCing, but if i can bypass this that would be better)
b) Overclock it to 1.5
I have found 1 way root my xoom but i am stuck. The instruction says open the xoom and press down to display "android recovery" after i press up to enter android recovery it show : Entering Android Recovery Mode Reading ODM fuse:1. BUT after that i get the lying android with a ! on his belly. then my xoom restarts.
Please help me overclock my xoom because when i play Chaos Rings it lags, and its really frustrating.
Up, can someone help me with this?
up
So the fact that you're GEDified, implies you have an unlocked bootloader.
So, Install a custom recovery, I'd recommend this one: http://forum.xda-developers.com/showthread.php?t=1235170
Then in recovery flash the zip file I have attached to root. credits to solarnz for making the zip file.
Yup i think i have a unlocked bootloader, can you give me a step by step instruction on how to install the custom recovery and flash with the zip file? (FYI: I'm a newbie in this kind of stuff)
One more thing this is my MAIN PROBLEM
I have found 1 way root my xoom but i am stuck. The instruction says open the xoom and press down to display "android recovery" after i press up to enter android recovery it show : Entering Android Recovery Mode Reading ODM fuse:1. BUT after that i get the lying android with a ! on his belly. then my xoom restarts.
thank you for the time.
matt4321 said:
So the fact that you're GEDified, implies you have an unlocked bootloader.
So, Install a custom recovery, I'd recommend this one: http://forum.xda-developers.com/showthread.php?t=1235170
Then in recovery flash the zip file I have attached to root. credits to solarnz for making the zip file.
Click to expand...
Click to collapse
scampupy said:
Yup i think i have a unlocked bootloader, can you give me a step by step instruction on how to install the custom recovery and flash with the zip file? (FYI: I'm a newbie in this kind of stuff)
One more thing this is my MAIN PROBLEM
I have found 1 way root my xoom but i am stuck. The instruction says open the xoom and press down to display "android recovery" after i press up to enter android recovery it show : Entering Android Recovery Mode Reading ODM fuse:1. BUT after that i get the lying android with a ! on his belly. then my xoom restarts.
thank you for the time.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/showthread.php?t=1468298
It's a really good, easy and simple GUI that can help install a custom recovery and more, the root function on it won't work though as I don't think it's been updated for jelly bean, but I may be wrong
yeah i think the root function wont work because i read the thread and the developer said he haven't tried it on jelly bean.Probably i'll just wait for his new update the 7heaven projekt. thanks for the help!:good:
matt4321 said:
Use this: http://forum.xda-developers.com/showthread.php?t=1468298
It's a really good, easy and simple GUI that can help install a custom recovery and more, the root function on it won't work though as I don't think it's been updated for jelly bean, but I may be wrong
Click to expand...
Click to collapse
Gedified xoom
I've been trying to access recovery on my gedified xoom and ran into the same problem. Only when i got the sleeping android with the i on the belly, the xoom did not reboot. It was just stuck like that so I pressed power button + volume up button to exit and what do you know it went into the recovery mode. The xoom now says
Android system recovery <3e>
Use volume keys to highlight ; power button to select
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Stumbled upon this by accident so dont know if it will work for you but hope it helps.
Gedified xoom
alternatively try this
http://forum.xda-developers.com/showthread.php?t=1936534
so did anyone have a sure but EASY way to root the xoom in the stock 4.2.1 state?
I'm dealing with the same problem OP stated in the first post.
shilohdrummer said:
so did anyone have a sure but EASY way to root the xoom in the stock 4.2.1 state?
I'm dealing with the same problem OP stated in the first post.
Click to expand...
Click to collapse
Ok so I am in the process of doing this myself. I'm kind of doing this off my own back as I cannot get the AIO tools etc to work, but there is a nice way of gaining root on 4.1.2.
So, assuming you have an unlocked bootloader and a PC on Windows do the following:
1) Download the root zip attached above in this thread.
2) Download the latest version with install scripts from here : http://forum.xda-developers.com/showthread.php?t=1782235
3) Put the root zip onto the external SD Card
4) Run the RUNME file
5) Use option 2 to boot into fastboot
6) Once fastboot is loaded use option 1
7) This will then install the recovery.
8) Power + volume up to reboot
9) Do not let the device boot into android, it will get rid of the new recovery menu, hold power (on the Motorola dual core splash) and get the device to turn off before android starts loading.
10) Once the Xoom is off, start it again, pressing the volume down key rapidly until you see some options at the top, select recovery, press volume up.
11) Welcome to your new recovery! So, we need to install the root update. So select install zip.
12) Choose the root zip, go through the options and install it.
13) Reboot your device
14) Check for SuperSU
Congratulations, you should now have root on your 4.1.2 GED'ed Xoom MZ604
Going put this in a fresh thread I think for any other self proclaimed noobs in my position
ratykat
shilohdrummer said:
so did anyone have a sure but EASY way to root the xoom in the stock 4.2.1 state?
I'm dealing with the same problem OP stated in the first post.
Click to expand...
Click to collapse
Same here... this is driving me mad... everything people describe in other posts just aint happening on my GED wifi Xoom!!
Please explain.......
1) Download the root zip attached above in this thread. -------- where?
2) Download the latest version with install scripts from here : http://forum.xda-developers.com/show....php?t=1782235 Which file??????
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install TWRP 2.4 touch screen recovery (a much better recovery than what you used to root.)
Download TWRP2.4 zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the TWRP 2.4 Zip and install
5. reboot your xoom
6. you now have TWRP 2.4 recovery installed.
Hey guys, I'm fairly new to this but I have my One S, H-Boot 1.18, Radio 1.08, unlocked, rooted, TWRP2.4.4.0 and S-Off...
I have successfully installed CM10, and have since restored it to the Stock RUU.
I have tried loading the Viper 2.1.0 5 times now and keep getting stuck on the "white "T-Mobile screen" with the red text on it. I have a few questions about the instructions that are posted.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
10. After you configured it, reboot to your bootloader in fastboot mode
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
Any advice, appreciated, I'm not stopping until this thing is a brick or I figure it out...
thanks ahead of time, and I have tried to read through there are almost 600 posts so if I missed something I apologize ahead of time.
I know exactly how you feel..I went through the same issues as you did. Below are my feedback on what I did, however as I found through other posts, instructions may work for some, but not all phones. So please be careful if you were to follow what I did. I put my feedback in blue and my own direction list on what I did that finally made viper one s work for me.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
Alright, seems like it's good then, I used CWM to make mine work but I'm pretty sure that you'll be fine with that one.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
This is what I figured out, as I had the same question when I was going through the installer.
-Yes: Means that you come from a kernel that is not the normal kernel, such as ElementalX.
-No: Means you are using the stock kernel.
Selecting yes will skip the new flashing of the boot.img kernel, while selecting no will flash the boot.img
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
Actually this part was the game changer for me, instead of following this, I wiped the system using my recovery, then selected install without wiping. (As I already wiped it via recovery)
10. After you configured it, reboot to your bootloader in fastboot mode
Even though I have seen numerous posts saying that once the One S is S-off you don't need to boot-flash-script..I clicked restart on the aroma installer and pressed the volume down button and the power, went into boot loader, went into fast boot USB and installed the boot-flash-script anyways..doesn't hurt
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
For me, I ignored that, because of that I have no knowledge for this question. :/
I am going off knowledge of what I did, as I had the same trouble you did. I tried to flash the rom countless times, almost bricked my phone, but after a stressful trial and error, I found the bugs that gave me my problems.
My Directions
1. Make nandroid (Just in case rom doesn't work)
2. Backup all apps as wiping phone will wipe all data and apps
2. Put viper 2.1.0 on device folder (I made a folder called roms)
3. Go to recovery
4. Wipe cache, system, and dalvik
5. Start the installer
4. Run through the desired checklists
-Select continue without wipe
-If on normal kernel select no when prompted on the kernel checklist
5. Once complete, click restart
6. Press and hold volume down and power to go to boot loader
7. Install boot-flash-script
9. Start Phone
10. It will be wiped, so go through the HTC start-up instructions
11. Once all that is done and the phone is fullyloaded, boot phone to recovery
12. Wipe Cache (to lessen lag)
13. Reboot again and done!
Don't use twrp 2.4.4.0, there are known problems flashing with it. Go for 2.3.3.0
First Thanks to both of you for the help.
So I down graded to TWRP 2.3.3.0...
Backed up my phone
Restarted phone, mounted and deleted the old back up
Began following the modified instructions
It appeared to work a little better this time ie... The installation screen colors seemed to be right and not all in a blue hue, and when it loaded it went all the way to 100% instead of hanging at 7% and then saying done.
I want to make sure this is correct also when I run the fastboot script, that this is what it should look like...
C:\htc_one\One_S_All-In-One_Kit_v3.4\Data>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (6124 KB)...
OKAY [ 0.850s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.328s
Alas this is still a "no joy" situation.
only good news is that I'm not stuck at the T-Mobile screen any more, the screen goes away after 5 seconds and now I'm sitting on a black screen.
What this has led me to think is that either the rom did not install correctly (duh) or you just downloaded the update for viper one s instead of the whole rom.
So just for clarification, now instead of on the t mobile screen it now goes to a black screen?
-Have you gone back into recovery and wiped cache again?
-Do you have a custom kernel or the stock kernel?
On another note.. Yes, the fastboot script was correct.
Sent from my HTC One S using xda app-developers app
So, I got it working, it seems that because I have my phone in S-Off, I didn't need to run the script. I just let it reboot after reinstalling it and it came up just fine.
I really appreciated the help guys, great support here... Maybe this post itself will help someone. :good:
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?
Hi, first, thanks for reading. Second, i've already searched de whole google world, and inside all this threads, but....
I CAN'T FLASH ANY RECOVERY! I don't know why!
In fastboot, i put the commands for flashing CWM, TWRP, Philz, and it works with no error. But, when i select the recovery option in my xt1032, it always boot the CUSTOM recovery. What can i do?
And sorry about my english, i´m from argentina.
Thank You!!
Hi. I don't get it. TWRP or CWM or Philz is custom recovery, so if you flash them to your device, of course the stock recovery will be replaced by custom recovery, so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery. Yesterday I flashed all kinds of recovery in order to flash ROM (flashable zip file) into my phone but it failed all the time, so I decided to install stock firmware by using mfastboot (and removed custom recovery also).
outerspacebuddy said:
Hi. I don't get it. TWRP or CWM or Philz is custom recovery, so if you flash them to your device, of course the stock recovery will be replaced by custom recovery, so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery. Yesterday I flashed all kinds of recovery in order to flash ROM (flashable zip file) into my phone but it failed all the time, so I decided to install stock firmware by using mfastboot (and removed custom recovery also).
Click to expand...
Click to collapse
So, i'm getting it wrong.... Please tell me: if i flash a custom recovery, like twrp, how can y acces to it? I though it was from fastboot>recovery
Actualy, I can't flash ANYTHING! It's so frustrating. I've tryied to flash the bootlogo, but it doesn't work either!
outerspacebuddy said:
Hi. I don't get it. TWRP or CWM or Philz is custom recovery, so if you flash them to your device, of course the stock recovery will be replaced by custom recovery, so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery. Yesterday I flashed all kinds of recovery in order to flash ROM (flashable zip file) into my phone but it failed all the time, so I decided to install stock firmware by using mfastboot (and removed custom recovery also).
Click to expand...
Click to collapse
Sorry, i misunderstand you. "so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery", you said. But no, it only boot de stock recovery! No matter how many times i've flahsed twrp cwm philz...
solauciel said:
Sorry, i misunderstand you. "so when you select Recovery option in Bootloader screen, of course it will bring you to a custom recovery", you said. But no, it only boot de stock recovery! No matter how many times i've flahsed twrp cwm philz...
Click to expand...
Click to collapse
If you want to flash a custom recovery, you need to have:
- Minimal ABD & Fastboot. Extract it into a folder.
- The recovery's .img file from its website. Its name may be very long, so you should rename it into something shorter, for example "newrecovery.img". Put this file into the same folder that you've just extracted Minimal ADB & Fastboot.
- Boot your phone into Bootloader screen (by first keep holding your Volume Down then press Power button for a short while). Connect the phone to your computer. In your computer, open the folder that contains Minimal ADB & Fastboot and the .img file of the custom recovery aforementioned. Now hold Shift key on your computer's keyboard and right click your mouse on the blank space of the folder. Choose "Open command prompt here''. When you see a black window, type:
fastboot flash recovery newrecovery.img
then Enter. The custom recovery will be installed right away. After that, choose Recovery on your Bootloader screen and the custom recovery will open. Yesterday I read on a website that some ROMs overwrote your custom recovery when your phone rebooted so that might be the reason why you cannot use the custom recovery you've just installed. I don't know how to solve this as I'm just a noob.
However, why do you need to install custom recovery? Does your phone still work properly? What kind of ROM are you using? If your phone doesn't work since the ROM has been messed up, I suggest you do a fresh install as this thread tutors: http://forum.xda-developers.com/showthread.php?t=2542219. After restoring your phone to a good state, you may try installing custom recovery again.
outerspacebuddy said:
If you want to flash a custom recovery, you need to have:
- Minimal ABD & Fastboot. Extract it into a folder.
- The recovery's .img file from its website. Its name may be very long, so you should rename it into something shorter, for example "newrecovery.img". Put this file into the same folder that you've just extracted Minimal ADB & Fastboot.
- Boot your phone into Bootloader screen (by first keep holding your Volume Down then press Power button for a short while). Connect the phone to your computer. In your computer, open the folder that contains Minimal ADB & Fastboot and the .img file of the custom recovery aforementioned. Now hold Shift key on your computer's keyboard and right click your mouse on the blank space of the folder. Choose "Open command prompt here''. When you see a black window, type:
fastboot flash newrecovery.img
then Enter. The custom recovery will be installed right away. After that, choose Recovery on your Bootloader screen and the custom recovery will open. Yesterday I read on a website that some ROMs overwrote your custom recovery when your phone rebooted so that might be the reason why you cannot use the custom recovery you've just installed. I don't know how to solve this as I'm just a noob.
However, why do you need to install custom recovery? Does your phone still work properly? What kind of ROM are you using? If your phone doesn't work since the ROM has been messed up, I suggest you do a fresh install as this thread tutors: http://forum.xda-developers.com/showthread.php?t=2542219. After restoring your phone to a good state, you may try installing custom recovery again.
Click to expand...
Click to collapse
I think you're rigth... I need to instal custom recovery because flashing from fastbooy doesn't worked at all... Realy, i've flashed a lot of firmwares and none of them seems to "get flashed" in mi device