Related
I've been trying to re-root my phone since late last night, and have had nothing but problems. I've searched all over the internet, and tried anything that I thought would apply to my situation in the slightest.
I originally downgraded from 2.3.4 to 2.3.3 and rooted my phone using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1298990
I ran Revolutionary, ClockworkMod, and SuperUser. Everything worked perfect the first time around. Installed the Cyanogenmod 7.2 ROM and Tiamat v1.1.5 kernel. Then I started having issues with my battery, and Cyanogenmod seemed to be increasing the issues. At that time HTC announced they'd be releasing ICS, yada yada yada. I found a stock ROM online, and installed it, and updated as they were released OTA. Having finally gotten a new extended battery, I'd like to re-root & ROM my phone, but I've hit some road blocks.
I currently have the Android Version of 2.3.4 & Software Number of 5.10.605.9
I tried to re-do the entire process that had previously worked for me, but once I used the command hack-vivow.cmd, the phone would boot to the Revolutionary (of HBOOT ?) screen. Command line shows this, and just hangs:
c:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
Click to expand...
Click to collapse
Phone shows this:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT -6.13.1002
RADIO -1.09.01.1111
eMMC -boot
Click to expand...
Click to collapse
Phone gives me the options of "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", & "POWER DOWN". "REBOOT BOOTLOADER" changes "FASTBOOT" briefly to "FASTBOOT USB", but changes back in about 15-20 seconds. When I select "BOOTLOADER", the screen freezes for a few seconds, and it won't let me select any options, "FASTBOOT" changes to "HBOOT", and I get this in green text:
SD Checking
Loading...[PG32DIAG.zip]
No image!
Loading...[PG32DIAG.nbh]
No image or wrong image!
Loading...[PG32IMG.zip]
Click to expand...
Click to collapse
The next screen of green text says "Parsing...[SD ZIP]" followed by 9 things, and I'm only given an option to Update or No/Reboot. No/Reboot reboots my phone into an endless bootloop, until I remove the battery and power back on with Volume Down + Power Button. Update does a reset of my phone, and puts me right back to where I am now. While it is updating there is an error message at the bottom that says "Can not roll back hboot version".
I've tried multiple things to attempt to fix this... I ran the TacoRoot method from here:
http://forum.xda-developers.com/showthread.php?t=1751796
When the 8th line was completed
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
, the phone rebooted, it got stuck in a bootloop.
So that's where I am now. I'm stuck with S-Off, the PG32DIAG/PG32IMG errors, an HBOOT that seems to be far too new of a version, and I haven't found a way to get back to 2.3.3. As you can see I'm a noob. I'm really not sure where I went wrong (other than going back to a stock ROM and allowing it to update). Unfortunately a lot of things are just way over my head, without seeing a step by step process. But I'm just stuck at the moment. If anyone has any ideas on how to fix this, or any ideas of things to try I GREATLY appreciate it.
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Cleanincubus said:
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Click to expand...
Click to collapse
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
gtdtm said:
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
Click to expand...
Click to collapse
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Cleanincubus said:
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Click to expand...
Click to collapse
So with Froyo on there can you get to the stock recovery?
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I think you should be able to do 1B at this little how-to site:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I also just noticed...did you do "fastboot devices" first to make sure it actually recognized your phone? I'm really guessing, but I figured it was worth asking.
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Cleanincubus said:
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Click to expand...
Click to collapse
You shouldn't be flashing romantic zips as PG32IMG. That's what clockwork is for. If get it back to froyo, then go to the HTC recovery and follow the clockwork instructions I linked to. But maybe someone more knowledgeable than I can answer better.
Sent from my ADR6350 using xda app-developers app
After you go onto bootloader and it flashes your IMG you either rename the file on your SD card or delete it from your SD card. You will be able to proceed after that has been done
sent from my incredibly paranoid inc2
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Your s-off so the hard part is done.
sent from my incredibly paranoid inc2
You're right. The PG32IMG.zip was a problem. I removed them from the SD card's root, and it's working as it should.
Now the issue is the instructions in that link. I can't find any update.zip for the phone anywhere. I also can't find any options in the Recovery for "re-install package". I go to "BOOTLOADER" and then "RECOVERY". The Phone then boots to a small image of my phone with a red "!". I press Volume Up + Power button, and it loads the "Android system recovery <3e>". I have a Yellow error at the bottom stating"
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
sjpritch25 said:
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
Click to expand...
Click to collapse
screenshot for you
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Cleanincubus said:
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Click to expand...
Click to collapse
I don't think it's going to work until you get fastboot devices and adb devices to recognize your phone. I wish I could point you in the right direction, but I'm not very experienced with it.
I'm assuming you have the drivers for our phone installed? Some people have to reboot the pc to get those to recognize the device...
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Cleanincubus said:
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Click to expand...
Click to collapse
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
sjpritch25 said:
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Click to expand...
Click to collapse
Yup, it's there.
Did those commands, and it ended in the same result. No errors or "waiting" messages at the flashboot devices command, but it didn't show my device either.
Jasonp0 said:
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
Click to expand...
Click to collapse
Definitely installed driver. I originally tried to install the driver I previously used with my original s-off/root/rom, but it didn't work with Windows 8 (previous PC was WinXP), so I found the correct one for my OS. The "adb devices" command never found my phone, before installing the current driver.
I never installed HTC Sync. Just double checked the "Uninstall or change program" in the Win8 control panel (previously "Add/Remove Programs") to make sure it didn't get installed with out my knowledge, and it's not in there.
If you mean on the phone: "Settings" > "Applications" > "Development" > check box for "USB debugging", then yes. If it's a command of some sort, then no & I don't know how to do it.
I'm also making sure to run these commands by right-clicking the Command Prompt and selecting "Run as administrator", before doing these commands.
Hello !
Here's my prob :
I installed CWM Recovery on my OUYA, and then i wanted to flash a ROM via recovery.
Unfortunately, i've done a full wipe while in recovery, and restarted the console.
Now it's turning on, with the power button on, black screen, and identifyed as an MTP USB device.
I tried the alt + Sysreq + i trick, but it doen't seems to work here ...
Any chance to get it back to life in other way ?
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
imerrn said:
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
Click to expand...
Click to collapse
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
ElMeteK said:
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
Click to expand...
Click to collapse
Try these timings. I had the same issue and these worked for me. The keyboard trick is currently your only hope.
I keep pressing alt + sysreq + i keys at the same time takes me about 30 times to get to recovery the light will flash one time then i know im in recovery some times iget the ouya smile with a ! mark some time a black screen then i press home button to get to recovery push the home button again it goes away i have done about three ouya.
Problem solved.
My ouya doesn't loved my Microsoft Keyboard...
I used a generic on, and it works directly
Ouya saved
Another advice : if it doesn't work, try another keyboard !
Ouya Bricked Need Help Reward For The Fixer
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
labossiere said:
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
Click to expand...
Click to collapse
You have to fastboot the "boot.img" supplied with CM10. I had the same issue so pm me if you need help.:good:
Never, ever ever ever ever ever wipe the boot.img, if you want to be safe, never replace it either, you can always 'fastboot boot boot.img" it.
Sent from my SAMSUNG-SGH-I317 using xda premium
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
glitchhawk said:
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
Click to expand...
Click to collapse
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
ok, cuz im basically in the same boat as everyone else. i flashed CM10 and now its hanging at the CM boot screen. so i guess its time to sit there and tap keys for hours lol.
BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
glitchhawk said:
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
Click to expand...
Click to collapse
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
BUS DR1V3R said:
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
Click to expand...
Click to collapse
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
glitchhawk said:
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
BUS DR1V3R said:
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
Click to expand...
Click to collapse
well this is lame.. it keeps telling me Error: Closed
glitchhawk said:
well this is lame.. it keeps telling me Error: Closed
Click to expand...
Click to collapse
What keeps telling you that? What are you doing? I need more information.
BUS DR1V3R said:
What keeps telling you that? What are you doing? I need more information.
Click to expand...
Click to collapse
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
glitchhawk said:
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
Click to expand...
Click to collapse
If it says <waiting for device> then its probably a driver issue with fastboot. When you reboot into the bootloader go into device manager and check the driver again. I also had this issue.
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Edit: In the fastboot screen at the top it says ***Tampered*** ***Relocked*** ***security warning**
also when i try to press recovery it shows the htc screen for 1 second then back to the same menu
i found this http://forum.xda-developers.com/showthread.php?t=2710735 but i cannot even get into recovery
haydenrbm said:
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Click to expand...
Click to collapse
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
MattMJB0188 said:
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Click to expand...
Click to collapse
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
ashyx said:
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
Click to expand...
Click to collapse
I would...but when im trying to use ADB devices it isn't found
haydenrbm said:
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
I would...but when im trying to use ADB devices it isn't found
Click to expand...
Click to collapse
Do fastboot devices ... adb commands itself won't work in bootloader, it has to be fastboot commands.
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
mushages said:
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
Click to expand...
Click to collapse
How can I unlock the bootloader again without the device showing in adb?
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
i think you have your unlock token. start from here
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
If it's in bootloader it should show in command prompt when you type fastboot devices after connecting it to PC. If it doesn't then there is a driver problem perhaps. Check to make sure you have HTC drivers installed, or reinstall them. Might as well make sure adb is up to date as well, can do that through the Android SDK Manager. Another possibility might be that the usb cable isn't working correctly, try another cable. Fact of the matter though is, if it's in bootloader and you connect it to the PC adb/fastboot SHOULD pick it up.
So check and fix those things. Also make sure you use the correct commands, in bootloader mode, it'll be fastboot commands, not "adb devices" but "fastboot devices" ... "fastboot reboot" etc etc. Also make sure you're running the commands from within the adb/fastboot folder path(just for in case yeah...)
mushages said:
i think you have your unlock token. start from here
Click to expand...
Click to collapse
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
haydenrbm said:
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
Click to expand...
Click to collapse
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
BerndM14 said:
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
Click to expand...
Click to collapse
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
haydenrbm said:
Okay i have got into the bootloader now, thanks.
the adb devices will show it if i have it in recovery mode but not bootloader, why is that ?
Click to expand...
Click to collapse
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
BerndM14 said:
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
Click to expand...
Click to collapse
Sorry I skipped past your first response, that makes sense now.
So I need to put the rom on my internal storage then go into recovery and install the zip using TWRP..but when I plug my phone into the computer the internal storage wont show up.
I do have sync manager installed also, and it wont show up in that either
haydenrbm said:
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
Click to expand...
Click to collapse
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
BerndM14 said:
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
Click to expand...
Click to collapse
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
haydenrbm said:
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
Click to expand...
Click to collapse
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
BerndM14 said:
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
Click to expand...
Click to collapse
Hello BerndM14, thank you for this baby steps. Mine m8 is a gpe version, it's 4.4.2 google rom, rooted, cwm recovery, s-on. I was trying to flash the full google 4.4.3 zip rom under recovery, however, after that, my m8 automaticlly enter recovery everytime reboot. And I can manually enter the bootloader, my pc can find the m8 both in recovery and bootloader. I searched this post, and do it accordingly, I download the gpe stock backup KOT49H.H16 - 1.16.1700.16 - CWM Philz touch and use adb sideload gpe3.zip to the cell phone sucessfully, then the recovery automaticlly starts installing rom, then, I got below message:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully!
@symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.
Install from sideload complete.
then, I reboot it manually. problem still there, still enter the recovery automaticlly.
do you have any comments on this? please.
thanks,
Hello,
I downloaded the March OTA .zip from the thread in the general forum with the intention of installing via ADB sideload for the first time. I've installed the Android .sdk and confirmed that adb does work. Typing "adb devices" in the command prompt gives me the serial number.
I've used that to reboot to bootloader, go next to recovery, and click the "install via adb" option, at which point it instructs me to go back to the computer and push the file. I shift+right click on the folder containing platform-tools to open a command prompt tied to this folder (which also contains the downloaded OTA update, renamed "update" for convenience).
When I enter the command "adb sideload update.zip" it tells me that the device cannot be found. I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Device is stock, unrooted, bootloader locked. I wanted to try this before messing with fastboot and the binary images to get my feet wet, but it's been a headache inducing afternoon so far. I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Thanks in advance!
Try putting the OTA zip file in the same folder as the adb.exe file (in the platform-tools directory)
Moonboots said:
I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Click to expand...
Click to collapse
Are you using a Windows machine? I am far from an expert on these matters, but my sense is that failing to "see" the phone in recovery is usually a driver issue. See if this thread helps.
Moonboots said:
I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Click to expand...
Click to collapse
My experience has been that the only hard part of sideloading OTAs is the initial step of getting ADB running on a windows computer. Once you sort that out, it is very easy and also very liberating to not have to wait for updates over-the-air. Good luck!
Thanks for the help, all! The trick was letting Windows find its own driver (not the automatic setting, had to select this option) when the phone was in adb sideload mode. It's a different driver than fastboot and with the phone on.
Sideloaded the update last night and we're going strong! ?
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Edit:Fixed!!
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
roirraW edor ehT said:
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
@avivasaf There may not be anything you can do to fix it, then. To fool around with Android Betas, you really should unlock the bootloader first so that you have more recovery options. Hopefully, someone else with more experience recovering from such a situation responds with some other ideas.
avivasaf said:
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
Click to expand...
Click to collapse
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
avivasaf said:
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Click to expand...
Click to collapse
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Lughnasadh said:
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
Click to expand...
Click to collapse
Tried it, didn't help
fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
avivasaf said:
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
Click to expand...
Click to collapse
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
fil3s said:
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
Click to expand...
Click to collapse
I know that, but in my case its to late, any suggestions?
avivasaf said:
I know that, but in my case its to late, any suggestions?
Click to expand...
Click to collapse
I'm sorry mate. It might be a brick. I know its a crappy thing to hear, but it's one of those life lessons learned the hard way I guess.
All I would try to do is remove the device in device manager, install google USB driver in fastboot and try again.
You can try to use Google's flash tool (it's reportedly worked for some with even locked bootloaders) to get a booting device.
Android Flash Tool
flash.android.com
If you can't get your PC to recognize your P6P while it's in bootloader mode, and you're using Google's own USB driver (which is obviously recommended) for Windows, I had this very issue today. I solved it by abandoning the Google driver for clockworkmod's universal adb driver which after installation, allowed my PC to finally recognize my P6P in bootloader mode...
You might have to wait for Official Android 13 to drop with a locked bootlaoder
Fixed!!!
I downloaded the ota file! Not the one that didnt worked from beta program, the ota file could sideload and phone back to life!
After that used android flash tool to return to public Android 12
fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Your ota file saved me, thanks alot
avivasaf said:
Your ota file saved me, thanks alot
Click to expand...
Click to collapse
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Lughnasadh said:
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Click to expand...
Click to collapse
There are 2 files the one that call ota is the one that saved me, the other one is the the one from beta program