Phone wont boot after trying to get back to stock - One (M9) Q&A, Help & Troubleshooting

Hi there,
obviously I did something wrong, cause now my phone wont boot up. It is stuck on the HTC logo, and stays there for hours after hours. I can get into download mode etc, tried factory reset, but to no avail.
My phone is S-Off, but it is not recognized by adb anymore, so I cant get it to install TWRP.
My OS is 1.40.161.8 and my CID is VODAPE17
Any help would be appreciated.
Thanks,
Chris

Of course you can't get adb to work since it only works if you're booted to system. Did you try using fastboot?
(The answer of that question actually doesn't matter that much.)
To get your phone back to a working state you simply need to flash a RUU. Be aware that these methods will erase all data on your phone and it will downgrade its firmware version!
Do you have an external SD card for your phone that is not bigger than 32 gb? Format it to fat32, download this RUU and put it into the main directory of the SD card. Rename the file to "0PJAIMG.zip". (That's a zero, not an O.) Then put the SD card into your phone and boot to download mode. Follow the instructions on screen. Your phone will prompt you to power it down at the end by pushing the power button. Wait some seconds and you can restart it as you would normaly do. You can then upgrade your firmware to the latest version by using the OTA function in settings>about.
If your pc is able to detect your phone by using fastboot commands you can also use this RUU. Boot your phone to download mode, disconnect you pc from the internet (just for safety reasons because of the next step) and disable your firewall and your antivirus software (both can interfere negatively with this ruu). Then run the RUU.exe as administrator. Depending on the age of your pc it may take up to ten minutes until a new window pops up. It's recommended closing every window and programm you don't need. You don't have to do anything with your phone during this process although the ruu might say that your phone should be booted to system. At the end you need to upgrade your firmware, too, by using the OTA function.

Thanks for your help. It worked as a charm. So relieved to have it back up and running.

Related

Big time unrooting problems

Hi, Last night i rooted the phone, partitioned the sd card, installed radio .08 and so on.
Rom were working fine but i just wanted unroot cuz of the warranty issue. Heres to the problem. When i connect the phone it all looks fine. The computer finds it and i can mount the sd card and so on. But when i try to boot with the official ruu it just loses the connection to the computer and stops with the "black" "htc" logo on the screen.
Here's what i've tried: Reformated my SD card with fat32, nandroid back to stock rom (the one you get directly after rooting) and i've tried degrading my radio image to the one .04. have also reinstalled htc sync twice and get same problem...is the phone bricked in any way? im pretty noobish at this so it was foolish of me to try it on my own i know.
I can still flash roms i looks like, just not go back to unrooted
I've done the unrooting process before and it worked like a charm. why not now?
the ROm was Leedroid 1.4 if it helps
Pop onto the #modaco irc channel on chat.freenote.net
This sounds sortable.
Sounds like its just a matter of flashing the stock rom directly from the SD card....Feel free to pm me whilst in the channel
Have you try to boot your phone into Hboot/Fastboot before you execute the RUU?
After you have run the RUU file and it asks you to connect the phone, go to your windows temp folder (start->run->%temp%)
Sort folders by date and open the most recent, inside there you will see a file called rom.zip (about 120 megs) copy that to your SD card and rename it to PB99IMG.zip.
Turn the phone off and reboot holding the vol down key, enter recovery and it should scan the SD card and offer to flash the PB99IMG.zip.
Job done!!
This will also downgrade the radio images, so beware it takes a couple of boots.
I unrooted today and had the same problem, its a simple solution. When you run it the first time it gets stuck on the black screen, dont do anything with the phone, leave it connected, exit the ruu, then run it again and it'll work
I had something like this too. Just close flashing software in windows when it says connection error, unplug usb, plug it back and start firmware flash in windows again.
edit:i was too late.. lol
edit edit: i did unplug, but looks like its not needed
My solution is more elegant though
pmcguire said:
My solution is more elegant though
Click to expand...
Click to collapse
It sure is nerd way to go!

Root/Rom Help Needed ASAP!!!

Here is my issue..I have been rooted since I got the phone and actually rooted both of my EVO's. Last week I decided to go back to Fresh Rom 1.0 and inadvertently flashed a new theme at the same time. Did not flash the ROM and then go back in and flash the theme. As a result, the phone went into a continual cycle of rebooting the loading screen ( for Fresh users you know it has the little guys and says FRESSSHHH). Well that happens over and over again.
The only option I have is to take battery out and go into the bootloader mode. MY problem is this:
* Once in bootloader mode, I can't reflash because when I go into the recovery mode, the recovery says " ADB server is out date" and scrolls thru a few lines an disappears. I've tried every thing suggested to me and still have not been able to fix that.
* Cannot access root of SD card because system doesn't recognize the phone is attached.
* Tried to load PC36IMG file on the card manually and that loaded but I can't get to the restart option. It finds the file but does not give me the restart commands.
I'm at wits end right now. I tried the OTA Recovery but since I cannot connect to the computer, it won't run either.
Please help......
Restore a nandroid.
RUU start over.
I tried to do that but the computer - htc sync won't recognize the phone so I can't RUU again. When I get to the end of the process it tells me either the phone isn't connected to the USB or the USB isn't connected to the computer.
You phone says the ADB server is out of date when you boot into recovery?
It sounds like you are not completely rooted.
You should be able to volume down and power on. Then choose recovery. From there you can restore a backup. That should also give you ADB access to the phone (if you are fully rooted)
If you are not fully rooted, and you have to run some bat file on your computer to get the phone into full recovery, you may be skrewed.
No, the computer says that when I go into recovery mode and have the black screen and red triangle on it. I then go to the computer and try and run the recovery file that I've been running as I've flashed 10-12 ROMS already. The CMD screen on the computer comes up as ADB Server is out of date...and another line or two scrolls by and then it disappears, never connecting to the phone and going into the next screen where I can wipe or flash from SD..etc..
Sounds like you did not complete step 2 of the root process. You should be able to enter recovery without the use of a computer.
Reboot your computer and try again, if you still get errors then I am out of tips.

HTC Desire Stuck on HTC logo - Recovery not Working - NOT SOLVED!!

Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse
USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.
Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.
Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button
awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.
Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!
@nhrsak - you save me, thanks very much!!
Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.
Have you tried flashing recovery.img via AndroidFlasher(from XDA)?

[Q] Did I brick my desire?

Hi.
I was recently experiencing some problems with my desire and I believe that I might have rushed into bricking it.
I woke up the day of the bricking. I had just installed the newest version of GingerVillain (version 2.4). My phone had run out of power the day before so I started recharging it. After it had charged for a couple of hours I went to the market to update some apps. During the update my phone suddently rebooted. I thought that it was nothing and went back to the market and continued updating. A few minutes later it rebooted agian. It kept on rebooting with less and less time in between after each attempt until it chose to reboot at the splash screen continuesly.
This is when I thought of starting the phone in recovery and do a NAND restore. As I tried to enter the recovery mode the phone froze at a black screen. I pulled out the battery and retried a couple of times without success.
I read a little on the internet about ADB and tried doing some stuff but I kept on getting errors when running commands in the tools directory. At this point I was getting desperate because I needed the phone to work as I was expecting an important call. I tried flashing a new RUU (through the installer on my PC) while the phone was in fastboot (but without using any ADB and CMD stuff). After this installation almost had finished I got an error saying that the version of the rom wasn't the right one for my phone and the phone shut off.
Since then I haven't been able to boot it into bootloader or even boot it at all. Whenever I hold down power + volume down nothing happends and if I try only pressing the power button the phone vibrates and other than that nothing else happends. Not even the screen turns on.
I since then set up ADB and got it working. I then tried to see if the phone was still able to fastboot through the following commands:
Code:
adb devices
and
Code:
fastboot devices
but found that this was not the case.
Whenever the battery is in the phone though, the bottom of the phone starts to get warm, a little like it's actually using the battery to perform some actions or something. I was also able to recharge it through my computer.
I really need a phone and as it seems I have got my hands on a spare one, but only for a limited time. I'm really thinking of handing it in to the HTC Concept Store so they can send it to the repair department and hopefully get it back as fast as possible.
Its seems.. S-LCD Brick
try This
http://forum.xda-developers.com/showthread.php?t=748498
or
http://forum.xda-developers.com/showthread.php?t=831734
Ohh dude! I BELIEVE YOU MIGHT JUST HAVE SAVED MY LIFE! TY! TY! TY! TY!
My stationary just killed itself because of the hot weather and a little bit too much work. If I was going to hand in my phone and they couldn't repair it since I had "destroyed" it, I would be forced to buy a new one, and with that I wouldn't be able to afford new components for my stationary.
I will get right on with trying this method as soon as I get home and then I will give feedback asap. It will probably be the most fun "digging in the dark" I will ever do if it turns out to work.
I was almost sure I had killed my beautiful phone, and with it only being a couple of months old that would have been a pain in the ass.
Once again TY so much!!
I have been at this for almost 4 hours now and still no result. I believe the guides could have been more noob friendly. I've been to hell and back reading all the kinds of guides out there to get it all to work and now I'm tired and believe I won't be able to fix this, or atleast doesn't have the capacity to keep on trying.
I pretty much believe that I had this SLCD-brick, but trying out different RUU's is killing me inside and stealing my time. I'd rather just hand in the phone and recieve it as it was from the beginning again to start all over.
Trying to repair a smartphone with a blackscreen is is not something I have the capacity to do. Besides I have my recently deseased stationary computer to take care of as well.
I do have a goldcard, pushed the PB99IMG.zip file to my /sdcard/ through adb and tried starting up fastboot and do as described here.
But somehow I did not find any changes to the problem and the guide itself was wierdly written although the only guide I could find on this problem.
But now I'm giving up. I seriously just hope they will repair my device at no cost.
Regards,
Me
Man.. what happen when you connect your mobile to PC.. is it showing android device and under that bootloader interface.. dont lose hope... lets try some steps...
connect your mobile to PC and see in your device manager.. can you see android.. if yes than your driver are installed...
than remove the phone from pc.. take out the battery.. and put back battery.. and start by volume down and power.. and than after 10 sec just press power button again.. and connect to pc again... and cehck device manager.. and you should see the same if not.. than install your adb driver.
Point is.. install ADB driver.. when you are on hboot screen.. as well fastboot screen..
Than your RUU will detect your phone.
Well I tried all the steps for this. I can see the phone when booting it with the following combos:
Code:
1: Volume down + Power
2: Power
1: Volume down + Power
2: Volume down
3: Power
When using the first method I should as far as I can understand myself enter fastboot and the other one is recovery. Even when running the fastboot devices / adb devices commands in ADB it tells me what state my devices in, that is either fastboot or recovery. So that's for certain.
I tried running the following RUU when I had connected my device with fastboot:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
The RUU found my device and I ended up with a 140 Error. I read in some guide that this error could be to blame of different windows drivers so I tried grabbing the rom.zip from the RUU (from Temp folder) and renamed it to PB99IMG.zip and put it on the phone. As I couldn't get access to my SD card since I can't see what's on my screen in fastboot and recovery mode I used:
Code:
adb push PB99IMG.zip /sdcard/
with the PB99IMG.zip placed in my tools folder for the transfer. It completed and now the PB99IMG.zip should be placed on the root of my sdcard.
As a notice I live in Denmark and the above RUU should as far as I can understand be the one I need and should as well be SLCD compatible.
When I try to trace the steps in the "not able to see your screen guide" placed here I get none of the desired outcomes:
http://forum.xda-developers.com/showthread.php?t=880268
I find the guide a little but confusing though. When to use the right commands to trace through a black screen fastboot/recovery and stuff isn't really "noob"-friendly.
When I tried using the following command I didn't get the desired result either:
Code:
fastboot oem gencheckpt
Which should return a HTC_<number> that could tell me whether my phone is branded or not, but instead resulted in an error. As far as I can remember I did make my sdcard a goldcard when I rooted my phone, without knowing whether I would need it, so this number should be irrelevant. So I kept on going at this point.
I have basicly tried everything that I can find guides for and have traced all the steps in detail as far as I understand the guides anyhow. I feel like at a dead end. I am having doubtsg whether the PB99IMG.zip is run when I boot my phone.
Having a clean slate (but still the PB99IMG.zip on the sdcard I have now tried the following:
Code:
Volume down + Power
Windows reported a connected Android 1.0 device and the Android Bootloader Interface.
Power once more (should now be in fastboot)
fastboot devices
confirmed the above, but using ADB devices only return a result if the phone is in recovery mode
So far so good..
I'll give this one more day which will be when I return home at 17:00 today. Then I'll head to tech support at my HTC Store.
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
jhonybravo4u said:
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
Click to expand...
Click to collapse
Okay. I'll try this and should I run it while in recovery like I did with the other one?
Does it matter if my SD card is out of the phone?
EDIT 1:
I tried with the sdcard out of the phone and with the RUU installed through windows. I now see a HTC Logo on the screen.. and an installing bar below the logo.. Seems like you were my divine interception mate.. ty a lot. I will write once the installation is done.. whether or not it succeeds.
EDIT 2:
My phone is now working. Booted with HTC Sense and a pin code request. Currently setting it up.
I guess I should now be able to re-root it again and get back to the state I was in before I SLCD-bricked it.. or what?
And in what way do I easiest remove that PM99IMG.zip file from the sdcard..? I booted my phone without the sdcard in it to avoid it running the PM99IMG.zip file..
One little question more.. I don't have any phone signal.. could this be to blame for the radio? I can connect to wifi though.. or can I simply run that other RUU I used earlier with the bootloader error to get back my signal?
So happy right now..
EDIT 3:
Nvm. I tried shutting down the phone, put in the sdcard, boot it up again. I found that the ADB push command on that PM99IMG.zip file didn't work. The file wasn't there.. and I suddently got back my signal. Only question is, can I now re-root it again and get back to my previous state without any problems?
Yes Ofcourse you can re root it.. with Unrevoked rooting wont be a big problem... and as soon as you root... just take a nandroid backup from it and be safe..
Enjoy the victory you earned... .. ;-)

Stuck on TWRP Recovery mode (LG G3 d855)

So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Malkishua said:
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Click to expand...
Click to collapse
I just got over something like this this morning. First, you need to ensure you have the LG Universal drivers installed for your phone. Get them here.
Next, reboot your machine.
After this, I made sure the PC recognized all 3 modes of my phone, TWRP mode (boot to TWRP, connect), Download Mode (boot to download mode with cable) and, at least in my case, the flashing lights mode (shows up as QHUD Bulk or something).
After that, I ran the KDZ restore program successfully.
Good luck and let me know how it goes.

Categories

Resources