Related
Hi,
I have STF, but can't find what I'm after.
Earlier today, my phone kept locking up/freezing, so much so that it'd stop the clock from running. The only way to get it back was to pull the battery out (which I realize now was probably a big mistake). Eventually I got stuck onto the HBOOT screen. Again, in hindsight, the phone was possibly performing the Sense 3.0 update that was due (even though it hadn't notified me on this)
Now I'm stuck with;
SAGA XA SHIP S-ON RL
HBOOT-0.98.0000
RADIO-038.03.02.11_M
eMMC-boot
MAR 10 2011, 14:58:38
With various options below, I have the standard android recovery, and have performed various reset and wipes to no avail, I still end up back at HBOOT
I had installed clockworkmod, but had never got around to S-OFF/Rooting the phone, I've tried to use the revolution method, but it just its there "waiting for phone..." even though I uninstalled HTC Sync, rebooted, installed the fastboot drivers and rebooted again.
I'm at a bit of a loss, I could take it back to the store and get them to fix it as it is a geniune problem. however, as I was intending a custom rom anyway, if I can recover this myself it'd be a good thing.
My questions;
Can I S-OFF/Root from the HBOOT menu?
is it possible to use a RUU stock ROM from the recovery mode?
Do I just take it back to the shop
Thanks
Dave
i had problem very similar to this .. you can install ruu form fastboot, but it will only work if the ruu version is older then the phone rom version or at least the same
Thanks for that, I didn't realise that the RUU would be an EXE (it took a while to download) It's found my phone and Updating now
Thanks for the quick response
Dave
Ok, Maybe I was too hasty ...
the update completed, the phone rebooted but stuck at the HTC Screen.
I've now tried to re run the RUU; RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
File and now it won't update, and the phone sits there on the fastboot screen.
Any other advice would be appreciated
Thanks
Dave
dpensox said:
Ok, Maybe I was too hasty ...
the update completed, the phone rebooted but stuck at the HTC Screen.
I've now tried to re run the RUU; RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
File and now it won't update, and the phone sits there on the fastboot screen.
Any other advice would be appreciated
Thanks
Dave
Click to expand...
Click to collapse
To be sure that is the correct RUU check the guide in my signature first (to setup adb and fastboot). Then connect the device to PC, make sure that on the screen of the phone is written FASTBOOT USB and type:
Code:
fastboot getvar version-main
fastboot getvar cidnum
Hi,
How do these look? (it is originally un unbranded UK phone)
C:\android-tools>fastboot getvar version-main
version-main: 1.28.401.1
finished. total time: 0.012s
C:\android-tools>fastboot getvar cidnum
cidnum: HTC__001
finished. total time: 0.008s
Thanks
Dave
dpensox said:
Hi,
How do these look? (it is originally un unbranded UK phone)
C:\android-tools>fastboot getvar version-main
version-main: 1.28.401.1
finished. total time: 0.012s
C:\android-tools>fastboot getvar cidnum
cidnum: HTC__001
finished. total time: 0.008s
Thanks
Dave
Click to expand...
Click to collapse
All correct. Should work. One last try with 1.28.401.1. Connect the phone in FASTBOOT USB mode and type in command prompt:
Code:
fastboot oem rebootRUU
then start the RUU on the PC
If not working download and try version 1.47.401.4
One question: you have written in OP that you have installed ClockWorkMod - probably you have tried to install it or you actually have it?
Hi Thanks for that,
I could get either of those to work, so admitted defeat and to it back to the shop, they're going to send it to HTC and hopefully they'll reflash it.
I had installed ClockworkMod from the Android market, but never gone any further with it.
As soo as I get the phone back, I will S-off, Root and do a full backup as I think many more recovery options would have been available if I'd have done this in the first place. I do quite like sense, so will have to find a ROM with it in.
Thanks
Dave
This is probably the best decision since your phone is Stock.
About the Sense ROMs - do not worry - there are plenty of them in each version: Sense 2.1, Sense 3.0 and Sense 3.5. You can find them in the Index thread in the Development section. Maybe Sense 4.0 will join soon, who knows
Hey guys, I'd really appreciate a hand with this one:
My OneX wasn't able to install the update from rogers. The phone was rooted, but was running stock and did NOT have CWM. I tried the update many times, but always got a red triangle icon while installing. The phone would then reboot into the old version.
I did a factory reset, which removed root, but the update still fails.
Now I'm trying to install the rogers RUU and see if that will make the update work.
The phone is now unrooted. Recovery says: Locked, Tampered
I got my hands on the following RUU and extracted it.
PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip
I ran:
Code:
fastboot flash boot boot_signed.img
And got this error:
Code:
sending 'boot' (6236 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
Does this mean that it needs to be unlocked to install the RUU? I thought it does not need to be unlocked because the RUU files are signed.. Is that true?
Any ideas how I can get the RUU working, or other ways to make the update work?
Thanks in advance
SOLVED:
1. I updated to the latest version of HTC Sync Manage. I used the link that opens when windows detects the phone being connected, NOT the one that is available on the HTC website. I disabled antivirus while installing it.
2. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=1658929
When doing step 2, I moved my RUU zip (with the really long name mentioned above) into the ARUWizard folder and renamed it to "rom.zip".
i think your supposed to do this method http://forum.xda-developers.com/showthread.php?t=1658929
DvineLord said:
i think your supposed to do this method http://forum.xda-developers.com/showthread.php?t=1658929
Click to expand...
Click to collapse
I can confirm this works as I did this a few months ago.
Thanks for the replies guys!
I gave it a shot, but my phone hangs at a silver HTC logo when it is supposed to be rebooting into the bootloader... ARUWizard says "waiting for bootloader..." and eventually times out. The phone stays stuck at the silver logo till I restart it.
I found this: http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Which suggests the following commands instead of using ARUWizard:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
But I get the same thing: freeze before going to the bootloader with a silver HTC logo.
Any ideas?
start the phone in bootloader then try it?
I updated to the latest version of HTC Sync Manager and now it seems to be working!
Says: "Sending..."
EDIT: Yep, it worked. Thanks guys.
My HTC One XL went on low battery and i plugged it on charge. Power outages meant the phone couldn't charge and when power came back on, I plugged it again on charge for about two hours. I tried booting the phone and the phone couldn't start, but the red light kept blinking even though it was unplugged from the charger. I pressed and held the power button for a while and turned it on again. It came on, but could not boot pass the "HTC quietly brilliant" screen, it kept restarting from that screen after it stays on for some seconds.
Next thing i did was to boot into bootloader. The bootloader was initially "Unlocked" but when the bootloader came up, it showed "LOCKED", which means the bootloader has gone back to locked all by itself. I tried unlocking the bootloader again, but when the unlocking warning screen shows up and i select "YES", it restarts and the "HTC quietly brilliant" screen keeps restarting. I tried factory reset from bootloader but the htc screen comes up and restarts from there.
The next thing i did was to look for an RUU. I couldn't find any, as most of the links were down. So i downloaded "RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radi o_0.19as.32.09.11_2_10.105.32.25L_release_271865_s igned" and I tried flashing from there, but the RUU loader could not load on the phone, could not even restart into the bootloader, as the HTC screen keeps restarting. RUU could not also be loaded from fastboot commands. I tried flashing a new kernel, but the phone doesn't allow the command to push the "boot" image file.
The phone was running on the official T-Mobile 4.2.2 Sense 5 which I updated OTA before unlocking the bootloader, and everything was working just fine, until the phones battery run low and the bootloader went back to locked by itself. Please help, as it seems all options have been exhausted. I have attached a copy of an image of my bootloader. But the details are as follows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 14 2013, 16:02:22:-1
Please help :'(
Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).
redpoint73 said:
Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).
Click to expand...
Click to collapse
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.
Economistaterry said:
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.
Click to expand...
Click to collapse
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.
redpoint73 said:
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.
Click to expand...
Click to collapse
so can the bootloader be repaired? if yes, how?
Economistaterry said:
so can the bootloader be repaired? if yes, how?
Click to expand...
Click to collapse
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
redpoint73 said:
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.
Click to expand...
Click to collapse
The red light which shows that the battery is charging never turns green. I have left it on charge over night so many times, but green never shows. Then the red light also stays solid for like 6seconds, goes off for like 2 or 3 seconds and comes back on. It never turns solid like it does when it's fully working, even when I leave it on charge for a long time.
twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
When ever I give the rebootRUU command, the phone restarts, the black HTC screen never shows.
Have you tried
fastboot erase cache
and then try rebootRUU?
twistedddx said:
Have you tried
fastboot erase cache
and then try rebootRUU?
Click to expand...
Click to collapse
Yes please, I just did that a couple of times. It only reboots the HTC white screen, same problem.
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
I gave the "fastboot flash recovery recovery.img" command and all i get is "sending 'recovery' (9060 kb) . . ." and nothing happens. The green bar which will show on the bootloader shows, but doesn't load. I have done this a couple of times, same results
twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.
So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"
twistedddx said:
So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"
Click to expand...
Click to collapse
-yes, 5.08 OTA
-yes, can not boot into a ROM
-yes, can not boot into recovery
-yes, INFOcid: T-MOB101
-yes, can clear cache with fastboot
-yes, flash recovery fails
-fastboot oem lock comes "INFODevice is already locked!"
-yes, unlocktoken fails. Got millions of new tokens from htcdev, all can't unlock, but will try again
-yes, RUU fails, will try the version u mentioned
-yes, rebootRUU fails, and i know its case sensitive
Thanks a lot for your support. Am in Ghana, no htc servive center here, no jtag repair center too.
Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?
Economistaterry said:
Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?
Click to expand...
Click to collapse
It could be a hardware issue.. But I doubt a hardware issue would mess up your hboot to the point you cant do anything.
You won't be able to flash anything with a locked bootloader. Keep trying to unlock the bootloader. Use the same unlock token, you do not need to re-request new ones everytime. if/when it fails to unlock, press and hold power until the phone shuts off, let go of power, press and hold volume down to go back into bootloader then try again with the same unlockcode bin file. Repeat until it unlocks. It may take many many tries. Press and hold power to hard power off the phone between tries every time.
When you finally do get it to unlock post here and we will fix your hboot issues.
redpoint73 said:
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.
Click to expand...
Click to collapse
twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?
Economistaterry said:
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?
Click to expand...
Click to collapse
absolutely nothing will flash with a locked bootloader. Nothing nothing nothing.
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:
Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .
I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247
Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon
Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.
Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...
So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.
I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?
Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?
You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery
It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.