Related
Hi,
My device started boot looping while trying to restore to stock ROM to update to a new ROM.
I wen't through the nvflash process successfully (meaning nvflash wrote the images to the device) but it continue with the loop.
Eventually, it powered down and now it will not power up at all. Battery is fully charged.
Any ideas?
Thanks.
OK, so I figured out that the device was stuck in APX mode.
nvflash doesn't seem to be fixing the problem, so I'm trying adb. It doesn't seem to see the device at all. I'm sure I'm missing step on how to work with adb.
Can anyone point me in the right direction for getting adb connected properly?
Thanks.
I'm trying to get adb working following this guide:
http://forum.xda-developers.com/showthread.php?t=902860
but it cannot see the device. The drive is installed fine but the device does not show up.
I know that if I can get into the device I can put it in debug mode, but I'm not sure how to do this now. I'm thinking this could be my problem, that the device is not in the correct "mode"
Any ideas?
Thanks.
did you get this resolved? i'm having the same problem.
williec30 said:
did you get this resolved? i'm having the same problem.
Click to expand...
Click to collapse
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
pgonza02 said:
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
Click to expand...
Click to collapse
i was able to get the device back into apx mode and run the nvflash utility again.
williec30 said:
i was able to get the device back into apx mode and run the nvflash utility again.
Click to expand...
Click to collapse
I've been able to do that a couple of times, but after nvflash completes, just get into a TapNTap logo loop and eventually just powers down. When I am able to turn it back on, it goes straight into APX mode.
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
kostyamat said:
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
Click to expand...
Click to collapse
Do you mean to install CW from external micro SD?
Thanks.
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
Finally Worked
I have no idea what made it work.
I decided to just take a break and left the tablet connected to the computer through USB but powered down. Came back a couple of hours later and when I turned it back on, I got the Viewsonic screen.
After that, I was able to reboot and go into CW and do a factory reset, which put it in a really old version. It was all easy from there.
pgonza02:
As I understand, you can now power off and reboot you GTab.
Can you recall what were your steps to get to this point?
I'm stuck in APX mode for almost a month! I don't know what else to try...
Thanks in advance.
I tried many things, including:
Install CW by replacing the image for partition 9 with the update.zip for CW (basically rename update.zip to whatever the img file is called)
Add CW to external SD card and attempt to reboot.
Eventually I just left the tablet alone and when I came back I turned it on I saw the Viewsonic birds (this seemed to be the key, when it was not working I never saw it)
I read a thread somewhere that mentioned that nvflash has the ability to redirect output through the HDMI out so you would not see it in the main screen. My guess is that what's happening is that the output of something, that is taking time to complete, is going out that way and I just could not see it. By leaving it alone, whatever it was, completed. This is just a guess, maybe someone with more knowledge can confirm.
Sorry I couldn't give you more details.
Boot loop and black screen
I'm having the same problem. In fact, I'm unable to boot into APX mode.
I have the cover off and read about a hardware reset button. I tried pushing the
reset button (k2) but nothing happened. I also read that I can disconnect
the batter. But, I don't see where the battery wire can be just disconnected
without soldering.
Any ideas?
I followed this guide http://forum.xda-developers.com/showthread.php?t=861950 (Roebeet's post) which brought me back to stock.
However, when I apply the 1.1-3588 the tablet shuts off and is unable to be turned back on. The only way to turn it back on is to run the nvflash_gtablet batch file. At which point a receive a notice saying 'The update to version 1.1-3588' was not successful. Please try again or contact customer support.'
Why is the tablet unresponsive after the failed update? Why must I NVFlash to reactivate the screen?
I searched through the forums for the past hour and although I found similar problems I have yet to run into my exact one. I am hoping to find some help.
Edit*
I have the same problem as another user which can be found here http://forum.xda-developers.com/showthread.php?t=903684
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Click to expand...
Click to collapse
The fix posted by acidburn89 was unsuccessful for me
Citi,
I'm not sure exactly what you are doing, but if you are getting the message
you described, that sounds more like you are booting in recovery or a regular
boot and not APX (Power/Volume - to be the white, the black APX NVFlash screen).
My suggestion is to do the stock recovery NVFlash Procedure again. Check
everything step by step to make sure the right files are there and the right
things done.
See if you can complete that and get back to a working bekit 1105 (Stock
Version 2638).
If you can do that, go into Settings/Display and set it so the display does not
turn off).
THEN, if it offers you the OTA Update, let it run.
If it is unsuccessful again, post back here and I will see if I can find the file
and instructions to load 3588 manually.
Hope this helps,
Rev
Ok so I reread Roebeets NVFlash post and double checked my files. All of them are there and in the correct location. I set up my USB drivers, booted into APX mode and ran the nvflash_gtablet.bat
Then the tablet loads properly into the stock TNT 2638. After setting up my WiFi I get a notification that the 3588 update is available. I download the update and after it ask me if I would like to apply now or later. I have tried both options however both seem to fail.
At this point if I hit apply now it shuts down the tablet however it does not turn on. The only way to turn it on is using nvflash_gtablet.bat file. Which it then boots up properly (and it is not wiped, it's as if it is jut turning on normally)and I either get one of two errors.
'The update to version 1.1-3588' was not successful. Please try again or contact customer support.'
or
'The update process cannot proceed due to an unrecoverable error. More information about the error is below, 'Verify checksum: file was not found. Downloaded file does not exist.null'
Hope this helps, I am not new to rooting/flashing roms but this is a completely new error to me.
Citi,
Did you do what I said about setting the display not to go off?
I tell people to do that because I have heard that it can
interrupt the download.
Whatever is happening, it seems like the download is not happening
or not finishing.
You can go to the Developer Forum (or there may be one in General)
and find the thread that tells where to download the .zip version of
the OTA 3588 download.
Then go down to end of the top 4349 thread in General and I wrote a post there for a
guy on how to install an update from the .zip file.
Rev
Yup I set the display to never turn off. However, it seems as if I have this problem http://forum.xda-developers.com/showthread.php?t=999832
I am currently working on this method
Edit* Well I figured out the exact problem however the link I posted was unable to solve it
Another thread on my problem, and the fix found to work for others has not worked for me,
http://forum.xda-developers.com/showthread.php?t=903684
Just bumping this as it is still relevant and it seems to be a unique issue, as all past solutions have yet to fix this problem. I spent the whole day on IRC and have seemed to stump a few people. Looks like I may have the first fully bricked tablet
Have you tried re-partitioning?
Can't get into CWM to do so, stuck in an infinite APX mode and I can only turn the power on via an NVFlash
Citi said:
Can't get into CWM to do so, stuck in an infinite APX mode and I can only turn the power on via an NVFlash
Click to expand...
Click to collapse
get the recovery.img from from cwm .8 zip file and then use nvFlash to load that.
nvflash --bl bootloader.bin --download 9 recovery.img
(make sure you put the recovery.img in you nvFlash folder and then issue the command above. That will install cwm .8)
from what you wrote above it seems like you are getting stuck in apx mode when you reboot. So my question is what files did you download to setup your nvFlash????
I will attempt to load CWM using NVFlash, and I followed this guide EXACTLY http://forum.xda-developers.com/showthread.php?t=861950 for NVFlash for windows
Citi said:
I will attempt to load CWM using NVFlash, and I followed this guide EXACTLY http://forum.xda-developers.com/showthread.php?t=861950 for NVFlash for windows
Click to expand...
Click to collapse
which files did you download from his dropbox????? I am more interested in knowing if you used nvflash_gtablet_2010110500.zip or nvflash_gtablet_46_2010112600.zip????
I initially used that nvflash_gtablet_2010110500.zip and had the same problem as you few weeks ago. So I tried using nvflash_gtablet_46_2010112600.zip and that worked a lot better for me .
hope that helps...let me know if you stuck anywhere.
enjoy
Unfortunately I tried out both with the same result
So the problem has changed from not being able to load an update to being in an APX loop? If I understand your original post correctly you were indeed able to nvflash back to original stock and boot normally. Then it failed when you tried to do the update to 3588. If you can still do that...
1) nvflash to bekit's 1105 stock
2) do not install the update
3) clear cache and data with Method I from: http://forum.xda-developers.com/showthread.php?t=1030915 - If this fails due to not being able to enter recovery then your nvflash was no good. You'll need to verify that you have the correct drivers installed, you're using the correct version of nvflash and that your image is sound. Easiest way to do that is to download them again.
4) install ClockworkMod .8 using MicroSD card method.
5) Re-partition 2048 and 0
Were there any error messages in the output of your latest nvflash attempts?
I posted on how you can get cwm .8 installed on your tablet if you are stuck in apx mode. There are also other threads that are pinned under the development section that explain how you can get cwm .8 using nvFlash. You will need that to get out of the apx loop that you are stuck in.
The problem is found here http://forum.xda-developers.com/showthread.php?t=903684
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Click to expand...
Click to collapse
And I attempted to install CWM using the NVFlash method with no success. It seemed to install however when I booted the system back up (using the batch file) I saw the "Android" screen and then the tablet went black, no green CWM menu appeared or anything
rbansal2 said:
I posted on how you can get cwm .8 installed on your tablet if you are stuck in apx mode. There are also other threads that are pinned under the development section that explain how you can get cwm .8 using nvFlash. You will need that to get out of the apx loop that you are stuck in.
Click to expand...
Click to collapse
Citi said:
The problem is found here http://forum.xda-developers.com/showthread.php?t=903684
And I attempted to install CWM using the NVFlash method with no success. It seemed to install however when I booted the system back up (using the batch file) I saw the "Android" screen and then the tablet went black, no green CWM menu appeared or anything
Click to expand...
Click to collapse
If the screen is blank then connect it to your computer and see if your tablet is in APX mode. You will probably hear the usb connect sound and you can go in device manager to see if it is connected. Let me know and then we can go from there
Yes it has been in a permanent APX mode since my original NVFlash, with the only way to turn the tablet on is to use the nvflash_gtablet.bat file. This will bring the tablet to TnT however my data has not wiped since my original NVFlash and the Wifi and other information is still present. It prompts me to download the new update however there is no need since once the tablet shuts down it will go to APX mode, with a rinse repeat of the cycle and I use .bat file to turn the tablet on.
ok try this...not sure if it will work but its worth a try
1. replace part9.img with the recovery.img ( i m sure u have done this already. this is so cwm .8 gets installed when you do a full nvFlash)
2. when you boot on for the first time.. press the power & + so you go in cwm .8.
let me know if you access cwm .8 if you do this ....we'll move forward from there
Failed first time I did it, but I just tried again and what do you know...success, unsure why.
Currently sitting in CWM looking at that beautiful green screen. I am in the IRC room if we could continue there that would probably work better and faster.
ya i m still at work and cant get on irc here :/...but if you are in cwm .8 then first thing i would do is wipe data then clear cache and then clear dalvik...then go under mounts menu and mount all the partiontions and then format all the partitions...once you are done with that i would mount your tablet so you can see is as a mass storage device on your computer and upload stock frimware 3588 on there...
use this link http://forum.xda-developers.com/showthread.php?t=861950 and go down to post nvflash and get the 3588.zip
from the 3588.zip get the update.zip and copy that to your tablet...once u have that go to the main menu of cwm .8 and choose the option to install update.zip form sdcard...i thikn thats the second one down
try that and see if it works...if not then i'll on irc in the evening today and i'll help you out ...dont stress we'll get your tablet up and running again
i have a gtab and it is giving me a headache already trying to figure out how to fix it. I have search high andd low for a solution but havent quite found one, yet.
This is my brother-in-laws gtab. For some reason he tried to flash to a different rom and update the tablet. Right now, the tablet won't boot. It gets stuck on the 3 bird screen. If i try to go into recovery, i still get the 3 birds with the "detected a recovery key pressed."
What i have done...well since i can get into apx mode, the first thing i did was flash nvflash 1.1, that should clear things up, then i pushed recovery. But that didn't work, i am still at the same place i started. So i flashed nvflash 1.2, still didn't work. I re-downloaded the files again from different sources and tried it again, and again, and again. I have tried it atleast 6 times but all with the same outcome. I am still stuck at the 3 birds. I tried holding the + while in nvflash to boot into recovery but that didn't work either. I am fresh out of ideas. Everything i read tells me to wipe cache/data, but i can't even get into CW. And nvflash isn't working for me either.
I am still on the same screen, this darn gtab is giving me the bird three times over. so right now i am going to allow the battery to drain then try again. unless anyone can suggest anything that will give me some hope....or even to tell me that i have bricked the "unbrickable."
oh and everytime i do the nvflash the device does not reboot itself...it stays stuck on the "entering nvflash recovery mode / nv3p server"
I had a similar issue with my gtab except I keptrebooting into apx mode. I then downloaded some nvflash from roebert that said deprecated not use (in a dropbox) and flashed that, my gtab came back to life there... funny thing is that I'm pretty sure I ended up on 1.0, luckily I was able to flash came from that and it's all been good from there.
I would say give that a try, then again I'm relatively proud to say I'm a n00b at Modding these things so tread carefully.
PS : as unbrickable as the gtab might or might not be it can (and to me it is) quite frustrating ; so I feel your pain
rantsh said:
I had a similar issue with my gtab except I keptrebooting into apx mode. I then downloaded some nvflash from roebert that said deprecated not use (in a dropbox) and flashed that, my gtab came back to life there... funny thing is that I'm pretty sure I ended up on 1.0, luckily I was able to flash came from that and it's all been good from there.
I would say give that a try, then again I'm relatively proud to say I'm a n00b at Modding these things so tread carefully.
PS : as unbrickable as the gtab might or might not be it can (and to me it is) quite frustrating ; so I feel your pain
Click to expand...
Click to collapse
yeah i tried it...i wish it was that easy..but it didn't work..it still didn't do a reboot after nvflash, and when i powered it off i didn't get anything...
butwhydoitalk2u said:
i have a gtab and it is giving me a headache already trying to figure out how to fix it. I have search high andd low for a solution but havent quite found one, yet.
This is my brother-in-laws gtab. For some reason he tried to flash to a different rom and update the tablet. Right now, the tablet won't boot. It gets stuck on the 3 bird screen. If i try to go into recovery, i still get the 3 birds with the "detected a recovery key pressed."
What i have done...well since i can get into apx mode, the first thing i did was flash nvflash 1.1, that should clear things up, then i pushed recovery. But that didn't work, i am still at the same place i started. So i flashed nvflash 1.2, still didn't work. I re-downloaded the files again from different sources and tried it again, and again, and again. I have tried it atleast 6 times but all with the same outcome. I am still stuck at the 3 birds. I tried holding the + while in nvflash to boot into recovery but that didn't work either. I am fresh out of ideas. Everything i read tells me to wipe cache/data, but i can't even get into CW. And nvflash isn't working for me either.
I am still on the same screen, this darn gtab is giving me the bird three times over. so right now i am going to allow the battery to drain then try again. unless anyone can suggest anything that will give me some hope....or even to tell me that i have bricked the "unbrickable."
oh and everytime i do the nvflash the device does not reboot itself...it stays stuck on the "entering nvflash recovery mode / nv3p server"
Click to expand...
Click to collapse
www.viewsonic-gtablet-for-dummies.webs.com/
You're a code red. You've been missing a very important step. Please follow instructions precisely.
goodintentions said:
www.viewsonic-gtablet-for-dummies.webs.com/
You're a code red. You've been missing a very important step. Please follow instructions precisely.
Click to expand...
Click to collapse
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. either way, after i flash nvflash the tablet does not reboot it stays at the nv3p server screen. If i turn it off and back on again the birds come out again. i have even held to the volume + during nvflash and it shows the nv3p server, detect a recovery key pressed, and booting recovery kernel, but no go...it's just stuck...i can turn it on and off, i can get it in and out of apx but it will not reboot after nvflash or boot up a rom or clockwork recovery.
btw, i do have my own tablet as well and i ran nvflash on it just for giggles, and it works as it is suppose to. After it flashes it boots up to tap n
butwhydoitalk2u said:
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. either way, after i flash nvflash the tablet does not reboot it stays at the nv3p server screen. If i turn it off and back on again the birds come out again. i have even held to the volume + during nvflash and it shows the nv3p server, detect a recovery key pressed, and booting recovery kernel, but no go...it's just stuck...i can turn it on and off, i can get it in and out of apx but it will not reboot after nvflash or boot up a rom or clockwork recovery.
btw, i do have my own tablet as well and i ran nvflash on it just for giggles, and it works as it is suppose to. After it flashes it boots up to tap n
Click to expand...
Click to collapse
Try code detox, you need a pc/laptop and load the proper driver, run the bat file from the directory. This mode completely reload all the petitions and usually fixes the issue. I think your boot petition is toasted.
Good luck.
tsukaza said:
Try code detox, you need a pc/laptop and load the proper driver, run the bat file from the directory. This mode completely reload all the petitions and usually fixes the issue. I think your boot petition is toasted.
Good luck.
Click to expand...
Click to collapse
This is not normal...
I did the detox and i DID get the "magic value mismatch" in the apx mode. But then i loaded the nvflash it is still in the same state as it was before...not loading recovery, booting, i can only get into apx mode...this is really weird..
I did the detox with both nvflash, 1.1 & 1.2, with and without Clockwork, but none worked. I can do the nvflash "format" and i still get the mismatch message but redoing the nvflash to get the tap n tap stock image or heck even not seeing the darn birds it won't do...
I have even taken it apart, let the battery run out, pulled the battery, pressed the reset button...but nothing!
I can't push anything in adb since i can't boot or get into clockwork...i think the tablet is offically bricked...i have ran out of ideas and have read many...i
butwhydoitalk2u said:
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. . .
Click to expand...
Click to collapse
Give this one a try and let us know if it helps.
Dave,
mydave1 said:
Give this one a try and let us know if it helps.
Dave,
Click to expand...
Click to collapse
I just tried ... and no cigar... i can go all the way to step 2.1 but it won't boot to recovery...it stays at the apx "entering nvflash...recovery key detected...booting recovery..."
to me it seems like it is not retaining any of the info that i am pushing onto it...like a "bios" is being reset and not remembering what to do...
A new error message.
Sent from my PC36100 using Tapatalk
Edit: i reflashed nvflash 1.2 and got rid of the error message...but i am back at square one...but taking a look at the error and from what i am seeing the tab is not finding the kernel image to start recovery. but why?
Cannot get NVFlash to "take"
butwhydoitalk2u said:
A new error message.
Sent from my PC36100 using Tapatalk
Edit: i reflashed nvflash 1.2 and got rid of the error message...but i am back at square one...but taking a look at the error and from what i am seeing the tab is not finding the kernel image to start recovery. but why?
Click to expand...
Click to collapse
Did you (or anyone else) discover the "secret" here? What did you do?
Unfortunately, I am now experiencing EXACTLY the same issues. My processes have fixed tons of GTabs that people thought were bricked. I *THOUGHT* that there was no way to HARD-brick the device but I may have been wrong!
I really need some help here. Anyone have an answer?
You could install a copy of Ubuntu and try nvflash with that. That would eliminate any possible driver issues since Ubuntu does not require drivers for apx mode. From the error you posted earlier "entering nvflash recovery mode / nv3p server" it would appear nvflash is not actually flashing anything.
Sent from my Nexus S using XDA App
NVFlash does not "take"
the3dman said:
You could install a copy of Ubuntu and try nvflash with that. That would eliminate any possible driver issues since Ubuntu does not require drivers for apx mode. From the error you posted earlier "entering nvflash recovery mode / nv3p server" it would appear nvflash is not actually flashing anything.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks for the comment. I agree about Ubuntu. I use it exclusively - have for a couple years. I did all my testing and attempts with it. I finally decided to build a WinXP machine and I am now trying to use it.
You are correct about NVFlash not saving anything to the device. There is no bootloader and although all of the NVFlash commands are "successful" it just does not save.
When I try to use the external SDCard to run recovery, the GTab does not seem to recognize it. It acts just as if there was not a recovery file on the card.
One thing that seems to give me some hope. I am seeing the USB connection (while not in APX mode) with the Windows Machine. So, I will install ADB and see if I can grab control that way. But ADB is such a bugger with Windows.
Alright guys, I need some help.
I tried installing twrp using adp / fastboot. I thought everything was going well. Everything came up as finish, the blue bar was full for a good 10 min, so I issued the restart command, and crossed my fingers it restarted.
I stared as I hoped I didn't screw something up.... android seemed to load fine and go to the lock screen. I was relieved. :
So, I tried rebooting (PWR + Vol Down) and choose RCK to load twrp. Now it just sits there, at " Booting recovery kernal image" and dosen't go anywhere.
Any ideas?
My goal is to flash AndroWook HairyBean.
Edit
Let me add that I am a novice at this at best. As far as I know, twrp may not have even took? But once I get twrp working, I can flash Hairybean, right?
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted