Related
Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.
You're bricked
Sent from my Desire HD using telepathy...
I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?
I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER
If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Lol least its on
Sent from my Desire HD using XDA Premium App
HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it
marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.
Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App
So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.
Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...
Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...
Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?
Hey guys, I was running slim bean build 5. Went to update to build 6, followed the directions and now when I try to power on my phone, it vibrates about once every few seconds and the screen remains black. I cannot boot to my recovery, I tried to flash the stock ROM with Odin, it says its successful but the problem persists. Please help me! Did I hard brick it??
SGH-i337
f.rod123 said:
Hey guys, I was running slim bean build 5. Went to update to build 6, followed the directions and now when I try to power on my phone, it vibrates about once every few seconds and the screen remains black. I cannot boot to my recovery, I tried to flash the stock ROM with Odin, it says its successful but the problem persists. Please help me! Did I hard brick it??
SGH-i337
Click to expand...
Click to collapse
If you can boot, you can get to recovery. Hold down Power and Volume up until it reboots. release power and hold volume up until it gets past the blue "booting recovery" and then some more until recovery comes up. Then restore your nandroid that you made before this started.
alacrify said:
If you can boot, you can get to recovery. Hold down Power and Volume up until it reboots. release power and hold volume up until it gets past the blue "booting recovery" and then some more until recovery comes up. Then restore your nandroid that you made before this started.
Click to expand...
Click to collapse
When I do that there is nothing on my screen. It just keeps vibrating every few seconds. The only thing I have been able to get to show up on the screen is the "Downloading" green android bot.
f.rod123 said:
When I do that there is nothing on my screen. It just keeps vibrating every few seconds. The only thing I have been able to get to show up on the screen is the "Downloading" green android bot.
Click to expand...
Click to collapse
If you can get into download mode you are golden, get odin and stock firmware and odin back to stock. Google will point your way to the millions of how to odin back to stock threads
Sent from my SGH-M919 using xda premium
Manufactured consent said:
If you can get into download mode you are golden, get odin and stock firmware and odin back to stock. Google will point your way to the millions of how to odin back to stock threads
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
As my OP states, I have flashed the stock firmware with Odin (3x now). The progress bar finishes and it reboots but the screen just remains black and it vibrates. I did do a manual format in TWRP as the Slim Bean changelog states I should have done. I am freaking out If I bring it back to the store (its less than 30 days old) will they deny me a replacement? I can't see how they could tell I did anything to it if I just say "IDK what happened it just stopped working."
EDIT: I flashed both Slim Bean Build 6 and their Addon pack at the same time.
f.rod123 said:
As my OP states, I have flashed the stock firmware with Odin (3x now). The progress bar finishes and it reboots but the screen just remains black and it vibrates. I did do a manual format in TWRP as the Slim Bean changelog states I should have done. I am freaking out If I bring it back to the store (its less than 30 days old) will they deny me a replacement? I can't see how they could tell I did anything to it if I just say "IDK what happened it just stopped working."
EDIT: I flashed both Slim Bean Build 6 and their Addon pack at the same time.
Click to expand...
Click to collapse
You have to do a factory reset from your recovery, but getting into the recovery is all about timing. Pull the battery, put battery back in, hold power, home and volume up until it vibrates, as soon as you feel vibration, let go of power only... Then if you get into recovery, do a factory reset and reboot
Sent from my Nexus 7 using xda premium
Go figure :/
Manufactured consent said:
You have to do a factory reset from your recovery, but getting into the recovery is all about timing. Pull the battery, put battery back in, hold power, home and volume up until it vibrates, as soon as you feel vibration, let go of power only... Then if you get into recovery, do a factory reset and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
My phone is in the same boat. im about to go try and exchange it i got it like 5 days ago. tyed kies and odin.
kies dosint see my phone. odin wrights the stock back but still vibrates with blank screen. RECOVERY DOES NOT WORK!!!
not how matter you try its gone. I dont understand how odin isint fixing it. i went to instal kernal and after that phone went ape s**t
IT wont even show the SAMSUNG first logo just black screen with vibrating evey 4 secs.
if phone won't boot and it wont show anything on the screen just vibrating. do you think att is going to run me around. im within my 14day return policy. are they going to be able to tell what i did with nothing to see let alone Odinsaid it did right so that means even tho it wont boot the root is gone becasue its back to factoy but no boot.
thank you for you time and help. hopefully someone out there has an awnser.
4purple2haz0 said:
My phone is in the same boat. im about to go try and exchange it i got it like 5 days ago. tyed kies and odin.
kies dosint see my phone. odin wrights the stock back but still vibrates with blank screen. RECOVERY DOES NOT WORK!!!
not how matter you try its gone. I dont understand how odin isint fixing it. i went to instal kernal and after that phone went ape s**t
IT wont even show the SAMSUNG first logo just black screen with vibrating evey 4 secs.
if phone won't boot and it wont show anything on the screen just vibrating. do you think att is going to run me around. im within my 14day return policy. are they going to be able to tell what i did with nothing to see let alone Odinsaid it did right so that means even tho it wont boot the root is gone becasue its back to factoy but no boot.
thank you for you time and help. hopefully someone out there has an awnser.
Click to expand...
Click to collapse
Yeah, I'm going to go to AT&T later. No matter what I try, I cannot boot into recovery. Kies won't see it, Odin doesn't work. I'm within 30 days of my purchase so hopefully they'll replace it.
f.rod123 said:
Yeah, I'm going to go to AT&T later. No matter what I try, I cannot boot into recovery. Kies won't see it, Odin doesn't work. I'm within 30 days of my purchase so hopefully they'll replace it.
Click to expand...
Click to collapse
If its AT&T i think its 14 days now as to what i was told when i got it.
so there is no one that has figured this out. im seeing more about it but no one can figure it out.
PLZ let me know what happens at AT&T. im going after work at 7. untill then im looking every where for anwsers.
NOT GETTING SAMSUNG POST SCREEN
Can ATT tell with the phone just vibrating with nothing showing. you can get in to odin but thats it.
can AT&T tell with out seeing anything saying custom or SU.
DO they have a device that can detect the sytem in its state.
4purple2haz0 said:
If its AT&T i think its 14 days now as to what i was told when i got it.
so there is no one that has figured this out. im seeing more about it but no one can figure it out.
PLZ let me know what happens at AT&T. im going after work at 7. untill then im looking every where for anwsers.
NOT GETTING SAMSUNG POST SCREEN
Can ATT tell with the phone just vibrating with nothing showing. you can get in to odin but thats it.
can AT&T tell with out seeing anything saying custom or SU.
DO they have a device that can detect the sytem in its state.
Click to expand...
Click to collapse
REALLY!?! KNOW ONE ELSE have this problem and fixed it if not at least an awnser about the att thing.
do they have a for sure way of telling modification if the phone wont even boot to recovery or show the first SAMSUNG post spash.
want to find out befor going in there and looking like an idiot.
thank you
sorry for sounding demanding just frustrated :/
The employees at your local store won't have a clue or would even try to figure out the issue. Where the phone gets sent to for repair is a different story. I'm pretty sure those guys can tell the difference between a rooted phone and one that's not.
Thanks took it back and got another. The guys there were clueless trying to get into recovery and it wouldent work. Any one have this happen to them you have 14 days from purchased date. If your over the 14 day then im sorry to tell you that your phone could be stuck that way unless you send it out to get it fixed. Samsung will not help you with warrenty on this.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4purple2haz0 said:
REALLY!?! KNOW ONE ELSE have this problem and fixed it if not at least an awnser about the att thing.
do they have a for sure way of telling modification if the phone wont even boot to recovery or show the first SAMSUNG post spash.
want to find out befor going in there and looking like an idiot.
thank you
sorry for sounding demanding just frustrated :/
Click to expand...
Click to collapse
Well, I went back to best buy, tried to play it off like IDK what happend. Guy saw right through me and said "it looks like the phone was damaged while rooting" I admitted to it. Luckily he said Geek Squad Protection covers rooting errors. Because I was within 30 days of purchase, he let me sign up for it. So now I have to wait a week and make a claim for a new phone.
Cuz
4purple2haz0 said:
REALLY!?! KNOW ONE ELSE have this problem and fixed it if not at least an awnser about the att thing.
do they have a for sure way of telling modification if the phone wont even boot to recovery or show the first SAMSUNG post spash.
want to find out befor going in there and looking like an idiot.
thank you
sorry for sounding demanding just frustrated :/
Click to expand...
Click to collapse
They will prob replace it...
they only check certain things...
is not like the phone police will come running out the stockroom door when you enter the store.... but maybe they should, heh heh
Woop
Hhaha! "Golden" This guy knows :good:
Has anyone figured this out? Also, will AT&T replace it free of charge? I am stressed out now. I flashed the same Slim Bean, how the hell does it brick our devices beyond where even Odin cant restore? Does anyone have a boot loader for download maybe? I really need some help here, and would be nice for those in the future to figure out how to fix this
Tylor
You are in a month old thread. Would probably help giving some specifics aboyt you're issue
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
fredphoesh said:
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
Click to expand...
Click to collapse
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
abdel12345 said:
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
fredphoesh said:
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
Click to expand...
Click to collapse
Your welcome I'm glad you got it working. Make sure to that k wugfresh as well for his awesome tool
Sent from my Nexus 10 using xda app-developers app
I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page