It has been a long while since I felt the need to flash a rom but today i decided to update to current. Made a huge mistake and formatted the sd card and wiped the os and Rom install files. Right now i can access fastboot, Hboot, and recovery. But for some reason USB doesnt work in recovery. with no OS to boot my device just sits at the Htc factory white screen. I have not been able to find one way to adb into my device to"push " the needed OS zip. Also have tried to flash a factory RUU but no adb access. Can someone help me out of this problem?
adrianh85 said:
It has been a long while since I felt the need to flash a rom but today i decided to update to current. Made a huge mistake and formatted the sd card and wiped the os and Rom install files. Right now i can access fastboot, Hboot, and recovery. But for some reason USB doesnt work in recovery. with no OS to boot my device just sits at the Htc factory white screen. I have not been able to find one way to adb into my device to"push " the needed OS zip. Also have tried to flash a factory RUU but no adb access. Can someone help me out of this problem?
Click to expand...
Click to collapse
Are you able to issue fastboot commands? If so try fastboot reboot recovery and see if adb is then recognized.
sabres032 said:
Are you able to issue fastboot commands? If so try fastboot reboot recovery and see if adb is then recognized.
Click to expand...
Click to collapse
Nope that didnt work. Is there a Update or img zip file that can be flashed via bootloader that includes a rom?
I recommend you to check if HTC has some recovery utilities. Exactly the same thing happened to me months ago with an Xperia SP, but recovery didn't work either, not to mention adb nor usb ; my computer didn't recognise the device at all. At the end I found a Sony program that made me manually choose my phone and region, made the phone recognizable for the program, and flashed full stock. HTC should have something similar.
adrianh85 said:
Nope that didnt work. Is there a Update or img zip file that can be flashed via bootloader that includes a rom?
Click to expand...
Click to collapse
What happens when you boot to recovery and type adb devices?? If nothing shows up try.
adb kill-server
adb start-server
adb devices
and see what happens.
What recovery are you using?
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
I had this problem not too long ago. I could not get anything to work until installer a generic adb setup for all androids. Then my phone was recognized and I was able to sideload a rom through TWRP.
https://www.dropbox.com/s/mrodur1ig8uup4u/adb-setup-1.3.zip
swantexan
Related
Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
choubeyaakash77 said:
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/oneplus-x/general/oos-2-2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
If you can enter in fastboot mode, flash the recovery from fastboot command. Flash blu_sparks recovery, it's better
seems you can still go to TWRP recovery? just flash the OOS 2.2.0 full ROM.
choubeyaakash77 said:
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
Obviously...
You told the phone to boot to TWRP by flashing it to 'Boot' and that's exactly what is happening.
Just reflash your ROM and you're good to go.
choubeyaakash77 said:
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
Click to expand...
Click to collapse
If you didn't know what you were doing, why ask before doing it?
You always have to flash the recovery .img from fastboot mode via adb. Not flashed by twrp.
Reference thread :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Maybe, just flash from adb the OLD recovery.
From this recovery, reinstall your Save.
Then install new recovery via ADB.
Or flash full ROM, then reflash, VIA ADB, the OLD recovery.
Then same as above. Restora + new recovery.
Boot your phone into fastboot mode, connect it to the PC, in adb directory, open cmd promote, type
fastboot flash recovery twrp. img
Click to expand...
Click to collapse
(replace twrp. img to the recovery img you downloaded, and put it under the adb directory). Or you can type
fastboot boot twrp.img
Click to expand...
Click to collapse
, the phone will then boot into the recovery you downloaded, where you can flash a new rom. DON'T flash recovery from recovery!
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
And if you want restore the backup on th sdcard, you might need change the storage location to sdcard in TWRP recovery,
Thanks all you guys. I'm back on with OOS 2.2.0. Had to download the complete ROM and flash it through TWRP.
I didn't wanted to download a whole almost 1 GB zip, so I tried to search for the original OxygenOS boot.img to flash it to boot. It might have worked if I hadn't completely wiped out my OS by wiping /system. Plus its almost impossibe to find that file online...
Anyway, had a nice experience screwing things up and getting back up better than before. Had fun. Learned stuff...so probably I'm not a newbie to rooting anymore.
Thanks guys for your support.
Here's the ROM I downloaded (for future reference) : https://www.androidfilehost.com/?fid=24389512218017971
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
FixFaier said:
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
Click to expand...
Click to collapse
fking hell.
this helped me a lot.
thx man :good:
Thank you so much. For now just gonna be content witht the stock rom.
I unlocked my bootloader installes twrp and linage. What do i need to go full stock? Stock recovery stock os lock bootloader.
follow this thread
https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
Abdullah S.A. said:
follow this thread
https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
Click to expand...
Click to collapse
i am a real noob i found this one but got lost on what to do i dont want my phone rooted.
noiz13 said:
i am a real noob i found this one but got lost on what to do i dont want my phone rooted.
Click to expand...
Click to collapse
I will help you.
You know how to work with adb right? since you have unlocked your phone and flashed TWRP i think you have a little bit experience with adb.
first: download this zipfile:
https://wileyfox.wetransfer.com/downloads/aba80df646f39937021ef49438a629a320171121140241/aaa9dd
unzip it in the adb folder in your PC
make sure USB debugging is on in your phone and connect your phone to your PC
Optinal: open adb and type this command to make sure your device is properly connected:
adb devices
open adb and type this command:
adb reboot bootloader
now type these commands one after one (DO NOT REMOVE YOUR PHONE DURING THIS PROCESS):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and wait ..
once this process is done boot to the recovery (through typing this command: adb reboot recovery
or from the bootloader) and do a factory reset
Optional: Update your phone through the adb and relock the bootloader of your phone after this is done through the following command:
fastboot oem lock
Optional2: if you don't know how to update your phone through the adb, then just relock the bootloader and update it via the phone updater in the settings.
I hope this will help you
---------- Post added at 10:32 AM ---------- Previous post was at 10:27 AM ----------
Forgot to say:
this will delete all your files on your phone and will unroot your device if it was rooted (so don't worry about the root)
Abdullah S.A. said:
I will help you.
You know how to work with adb right? since you have unlocked your phone and flashed TWRP i think you have a little bit experience with adb.
first: download this zipfile:
https://wileyfox.wetransfer.com/downloads/aba80df646f39937021ef49438a629a320171121140241/aaa9dd
unzip it in the adb folder in your PC
make sure USB debugging is on in your phone and connect your phone to your PC
Optinal: open adb and type this command to make sure your device is properly connected:
adb devices
open adb and type this command:
adb reboot bootloader
now type these commands one after one (DO NOT REMOVE YOUR PHONE DURING THIS PROCESS):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and wait ..
once this process is done boot to the recovery (through typing this command: adb reboot recovery
or from the bootloader) and do a factory reset
Optional: Update your phone through the adb and relock the bootloader of your phone after this is done through the following command:
fastboot oem lock
Optional2: if you don't know how to update your phone through the adb, then just relock the bootloader and update it via the phone updater in the settings.
I hope this will help you
---------- Post added at 10:32 AM ---------- Previous post was at 10:27 AM ----------
Forgot to say:
this will delete all your files on your phone and will unroot your device if it was rooted (so don't worry about the root)
Click to expand...
Click to collapse
didnt work the device wont boot
drewster1978 said:
didnt work the device wont boot
Click to expand...
Click to collapse
r u sure you've done everything as described? Check it again.
drewster1978 said:
didnt work the device wont boot
Click to expand...
Click to collapse
If you can get to stock recovery (Power and arrow down I think) then do a factory reset in recovery. That worked for me.
Flashed files and no errors but just wont boot stuck on wileyfox..Ive tried factory reset and also flashed other recovery files but nothing is working.
drewster1978 said:
Flashed files and no errors but just wont boot stuck on wileyfox..Ive tried factory reset and also flashed other recovery files but nothing is working.
Click to expand...
Click to collapse
This is what worked for me a couple of times.
https://forum.xda-developers.com/showpost.php?p=75771334&postcount=2
divvykev said:
This is what worked for me a couple of times.
https://forum.xda-developers.com/showpost.php?p=75771334&postcount=2
Click to expand...
Click to collapse
Ive tried that way as well,i went to the website and on chat they are happy to fix it,just have to send it to netherlands.
drewster1978 said:
Ive tried that way as well,i went to the website and on chat they are happy to fix it,just have to send it to netherlands.
Click to expand...
Click to collapse
Was that with STK?
Wow thats good news
Abdullah S.A. said:
I will help you.
You know how to work with adb right? since you have unlocked your phone and flashed TWRP i think you have a little bit experience with adb.
first: download this zipfile:
https://wileyfox.wetransfer.com/downloads/aba80df646f39937021ef49438a629a320171121140241/aaa9dd
unzip it in the adb folder in your PC
make sure USB debugging is on in your phone and connect your phone to your PC
Optinal: open adb and type this command to make sure your device is properly connected:
adb devices
open adb and type this command:
adb reboot bootloader
now type these commands one after one (DO NOT REMOVE YOUR PHONE DURING THIS PROCESS):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and wait ..
once this process is done boot to the recovery (through typing this command: adb reboot recovery
or from the bootloader) and do a factory reset
Optional: Update your phone through the adb and relock the bootloader of your phone after this is done through the following command:
fastboot oem lock
Optional2: if you don't know how to update your phone through the adb, then just relock the bootloader and update it via the phone updater in the settings.
I hope this will help you
---------- Post added at 10:32 AM ---------- Previous post was at 10:27 AM ----------
Forgot to say:
this will delete all your files on your phone and will unroot your device if it was rooted (so don't worry about the root)
Click to expand...
Click to collapse
I need this file for relock my bootloader but that web file expired ,where i can download this firmware ,tx b4
warj04 said:
I need this file for relock my bootloader but that web file expired ,where i can download this firmware ,tx b4
Click to expand...
Click to collapse
It's been a while man. I don't have the file anymore and I am not sure if it's still online.
Abdullah S.A. said:
It's been a while man. I don't have the file anymore and I am not sure if it's still online.
Click to expand...
Click to collapse
? I got the file, but can I install Deodex and Wileyfox Swift 2 Plus can use ROM Nougat
---------- Post added at 09:18 AM ---------- Previous post was at 09:15 AM ----------
Abdullah S.A. said:
It's been a while man. I don't have the file anymore and I am not sure if it's still online.
Click to expand...
Click to collapse
I got this file from here https://androidfilehost.com/?w=files&flid=184243
after a serious of stupid operations, here is the current state of my nexus 9 lte..
1. no android os is correctly installed, after reboot, it stay on a black screen with google logo.
2. it can be connected to pc and use adb and fastboot.
3. it is oem locked! fastboot oem unlock return error.
since it is locked, I can't use fastboot to flash the factory image, I try adb sideload the full ota img, and it finished without error, but after reboot it still stay on the google logo.
any suggestions? is there anything else I can do?
yitahutu said:
after a serious of stupid operations, here is the current state of my nexus 9 lte..
1. no android os is correctly installed, after reboot, it stay on a black screen with google logo.
2. it can be connected to pc and use adb and fastboot.
3. it is oem locked! fastboot oem unlock return error.
since it is locked, I can't use fastboot to flash the factory image, I try adb sideload the full ota img, and it finished without error, but after reboot it still stay on the google logo.
any suggestions? is there anything else I can do?
Click to expand...
Click to collapse
Do you have twrp installed by any chance? If yes, see if this will help. Good luck.
If stock recovery, sorry dude. I'm not sure.
madbat99 said:
Do you have twrp installed by any chance? If yes, see if this will help. Good luck.
If stock recovery, sorry dude.
Click to expand...
Click to collapse
no twrp, it's stock recovery, looks like game is over!
yitahutu said:
after a serious of stupid operations, here is the current state of my nexus 9 lte..
1. no android os is correctly installed, after reboot, it stay on a black screen with google logo.
2. it can be connected to pc and use adb and fastboot.
3. it is oem locked! fastboot oem unlock return error.
since it is locked, I can't use fastboot to flash the factory image, I try adb sideload the full ota img, and it finished without error, but after reboot it still stay on the google logo.
any suggestions? is there anything else I can do?
Click to expand...
Click to collapse
Can you access stock recovery? If so grab an OTA image (NOT FASTBOOT IMAGE!!! AN OTA IMAGE!!!) and sideload it via adb sideload. Make sure you have adb 1.0.32 installed or above. I needed to do this for my Nexus 9.
---------- Post added at 06:45 AM ---------- Previous post was at 06:43 AM ----------
yitahutu said:
no twrp, it's stock recovery, looks like game is over!
Click to expand...
Click to collapse
Not at all game over, there is never a game over on XDA.
https://developers.google.com/android/ota
Just find the Nexus 9 tab and run "adb sideload [path to ota.zip]" like normal. remember, when you get to stock recovery from HBOOT, hold down power, hit volume up, and release both keys to get to the menu where you can choose to do a "USB update"
Forgot about the ota images. Never used one. I knew there was a way, when people started having this issue I thought I remembered Google making a fix.
Galaxyninja66 said:
Can you access stock recovery? If so grab an OTA image (NOT FASTBOOT IMAGE!!! AN OTA IMAGE!!!) and sideload it via adb sideload. Make sure you have adb 1.0.32 installed or above. I needed to do this for my Nexus 9.
---------- Post added at 06:45 AM ---------- Previous post was at 06:43 AM ----------
Not at all game over, there is never a game over on XDA.
Just find the Nexus 9 tab and run "adb sideload [path to ota.zip]" like normal. remember, when you get to stock recovery from HBOOT, hold down power, hit volume up, and release both keys to get to the menu where you can choose to do a "USB update"
Click to expand...
Click to collapse
as I mentioned in my 1st post, I've already tried the adb sideload method.
yitahutu said:
as I mentioned in my 1st post, I've already tried the adb sideload method.
Click to expand...
Click to collapse
Oh sorry my bad... hmmm that is a thinker. Just keep trying different OTA images, downgrade, upgrade, everything. Do you remember what may have caused this? it may help us figure out what's wrong.
EDIT: Factory reset between each OTA image of course. /data might be wonked.
yitahutu said:
as I mentioned in my 1st post, I've already tried the adb sideload method.
Click to expand...
Click to collapse
Factory reset.
Ninja'd lol. Labs didn't update for me
today, I retry the adb sideload method with a new ota image.
in my previous test, I used the v6.0.1 mmb29x, and today I download and sideloaded the v7.0 nrd91n, this time it worked! now I can reboot and pass the stupid google logo.
yitahutu said:
today, I retry the adb sideload method with a new ota image.
in my previous test, I used the v6.0.1 mmb29x, and today I download and sideloaded the v7.0 nrd91n, this time it worked! now I can reboot and pass the stupid google logo.
Click to expand...
Click to collapse
Nice. Glad to hear