Related
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
kujhawk1977 said:
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
Click to expand...
Click to collapse
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
playya said:
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
Click to expand...
Click to collapse
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
kujhawk1977 said:
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
Click to expand...
Click to collapse
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
CWM will not be able to flash OTA successfully. You need to sideload it through stock recovery or TWRP.
playya said:
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
Click to expand...
Click to collapse
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
kujhawk1977 said:
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
Click to expand...
Click to collapse
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
playya said:
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
Click to expand...
Click to collapse
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
kujhawk1977 said:
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
Click to expand...
Click to collapse
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
I what to do whatever I have to do to fix my problem and I am not sure what that is.
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
Click to expand...
Click to collapse
OK I have adb platform tools. And I have the krt16s.zip Where can I find instructions on how to push the rom over to my phone and flash?
kujhawk1977 said:
I what to do whatever I have to do to fix my problem and I am not sure what that is.
Click to expand...
Click to collapse
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
playya said:
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
Click to expand...
Click to collapse
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
kujhawk1977 said:
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
Click to expand...
Click to collapse
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
playya said:
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
!!!!!!!!!!
So I still have the problem and cannot find a fix. Anyone here up for the challenge?
I was stuck in a bootloop and a failed OTA 4.4 update.
My nexus 4 is rooted and has CWM so yes I know i should have updated manually in the first place, but I didn't. After the update failed, it was stuck in a bootloop.
The next step I did was to side load the update. It ran through the install and at the end when 100% is says Installation Aborted. When my device is rebooted it is now stuck on the screen Google in white font.
Some other notes that MIGHT be related: USB Debugging is NOT enabled, as I can not boot into my device.
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
---------- Post added at 07:37 PM ---------- Previous post was at 07:31 PM ----------
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
No one has answered your question yet. I will.
Edited to say I did find a way to bridge (adb) files over without having USB Debugging selected on the phone.
Updated drivers and used ADB / SDK to move new Recovery and ROM over to my phone using CWM. Never trusting TWRP again
Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
Go to “Advanced”
Choose “Wipe dalvik-cache”
Now go to “Mounts & Storage”
Choose “Wipe /cache”
Reboot your phone
The bootloop should be gone now. If it still persists, do this.
Boot the phone again into CWM Recovery
Now go to “Mounts & Storage”
Choose “Wipe /data”
Choose “Wipe /cache”
Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
i did something stupid... lol. was running PA 4.4 rom with no troubles, had a backup as well. in preporation to sell this thing, i restored my stock backup , and noticed there was an update from att. so i decided to try installing it. well it downloaded fine, but when i tried to install it, it rebooted into twrp recovery. now i cant get it to boot into the OS. i tried restoring backup again but it still boots into recovery. any help?
At this point sideload pa 4.4 or return to bone stock they are described in the forums clearly.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
At this point sideload pa 4.4 or return to bone stock they are described in the forums clearly.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
i am trying to return to bone stock, but i cant get it to boot in to download mode? it still boots into recovery? can you elaborate or point me in the right direction of how to sideload ?
ssreynolds said:
i am trying to return to bone stock, but i cant get it to boot in to download mode? it still boots into recovery? can you elaborate or point me in the right direction of how to sideload ?
Click to expand...
Click to collapse
To get into dl mode....turn off the device....then hold ONLY the volume up button while putting in the usb cable...it will go into dl mode.
MalignantQuechnitlan said:
To get into dl mode....turn off the device....then hold ONLY the volume up button while putting in the usb cable...it will go into dl mode.
Click to expand...
Click to collapse
thanks for the reply... i know how to do it, but its not working because i screwed my device up by trying to insall an ota update with a rooted device and a custom recovery. so my only option now is to sideload, which i am working on... hope it works...
cant get adb to recognize my device, maybe because i dont have usb debugging enabled? which i cant enable because icant boot into os... what do i do to get this thing working again? i have android sdk tools installed
Omg I can't believe tons of people are having same problem, ok here u go stock lg drivers don't seem to help pc recognize phone in recovery mode what I did was downloaded pdanet on pc and connected phone to pc in recovery mode and then opened pdanet in pc and installed lg drivers through it and then my pc recognized my phone as adb sideload when adb was run hope it helps you too.
Sent from my LG-D800 using xda app-developers app
I had the same thing happen today, couldn't get into download mode. I followed the fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2477595 and it worked great.
He has links in that window to the specific file to flash.
lingarajug said:
Omg I can't believe tons of people are having same problem, ok here u go stock lg drivers don't seem to help pc recognize phone in recovery mode what I did was downloaded pdanet on pc and connected phone to pc in recovery mode and then opened pdanet in pc and installed lg drivers through it and then my pc recognized my phone as adb sideload when adb was run hope it helps you too.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I tried this, along with everything else, and my phone is still stuck in a boot loop. I cannot enter download mode. I was rooted with custom recovery, but i could never get the recovery to work. I tried to update to the OTA (i know, i know) and it killed the phone. Now when I connect it nothing happens other than a bunch of drive popups asking if i want to format. No download or recovery mode. only the LG logo screen and then a quick flash of the "Secure booting error Error: Boot Certification Verify!" screen, and nothing else since.
The main issue is that i cannot get my phone to be recognized by the computer for any type of reflash. If I could get into download mode, I could handle it from there. I hope I don't have to buy a new phone. Im not sure how verizon would feel about it if I took it back to them and it shows as rooted.
Can u at least get into twrp recovery using key combination
Sent from my LG-D800 using xda app-developers app
lingarajug said:
Can u at least get into twrp recovery using key combination
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
No, I cant get to recovery mode either. I think this is a hard brick. I've only had it for one day. Something told me not to mess with it.
Roninceo said:
No, I cant get to recovery mode either. I think this is a hard brick. I've only had it for one day. Something told me not to mess with it.
Click to expand...
Click to collapse
hei.connect to pc you can see a lot of drive to format？sorry my poor english
来自我的 Galaxy Nexus 上的 Tapatalk
pageniao said:
hei.connect to pc you can see a lot of drive to format？sorry my poor english
来自我的 Galaxy Nexus 上的 Tapatalk
Click to expand...
Click to collapse
Yes,
When I connect it to my computer I see a large list of drives to format. the messages keep popping up from G: to V:
Roninceo said:
Yes,
When I connect it to my computer I see a large list of drives to format. the messages keep popping up from G: to V:
Click to expand...
Click to collapse
maybe i can help you.
can you see a new device called "QHSUSB_DLOAD" on PC "device manager" when you connect your phone to pc？
来自我的 Galaxy Nexus 上的 Tapatalk
pageniao said:
maybe i can help you.
can you see a new device called "QHSUSB_DLOAD" on PC "device manager" when you connect your phone to pc？
来自我的 Galaxy Nexus 上的 Tapatalk
Click to expand...
Click to collapse
Mine says "QHSUSB_BULK"
see this
http://forum.xda-developers.com/showthread.php?t=2477595
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
see this
http://forum.xda-developers.com/showthread.php?t=2477595
and from chinese
http://bbs.gfan.com/android-6728131-1-1.html
pageniao said:
see this
http://forum.xda-developers.com/showthread.php?t=2477595
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
see this
http://forum.xda-developers.com/showthread.php?t=2477595
and from chinese
http://bbs.gfan.com/android-6728131-1-1.html
Click to expand...
Click to collapse
Ive seen the pages. Thanks for the help. I cannot get into recovery mode and unfortunately I can't read Chinese.
i dont know if you have tried this but i hear it works. it didnt for me, i keep getting a no memory error but if you get it to work can you please let me know how http://forum.xda-developers.com/showthread.php?t=2451696
on chinese .this problem so easy.
来自我的 Galaxy Nexus 上的 Tapatalk
this worked for me, and will work for those of you who are stuck in recovery boot loop... this is caused from installing an att update on a rooted device with a custom recovery and or rom. so heads up, if your rooted and you have a custom recovery and or a custom rom, NEVER install a OTA update!!!
so folow the instructions in the link, basically while in twrp, you use the amazing terminal emulator feature to type in the foillowing command, and viola! your phone will boot into the OS!!! make sure to type it in exactly as shown , with spaces and all... good luck!
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
http://forum.xda-developers.com/showthread.php?t=2451696
First off, I'm an idiot.
Nexus 4, 4.3 with Cyanogenmod. Working great until I decided to download Franco Kernel. I installed the latest then the colors inverted. I googled it and found out that the latest update didn't work well with Cyanogenmod and that #188 was the last that did work. I.. like an idiot decided to download and install #188 on top of #192 or whatever it was. Phone goes into **** mode, couldn't do anything on my phone without a popup telling me that android had stopped working so I decide to try factory reset, I don't know what I did wrong this time but now my phone won't even get passed the Google sign on boot up.
Bootloader and recovery still works. I cant push factory zip file to my phone without being in adb mode. What can and should I do?
Cheers
Sivi.N4 said:
First off, I'm an idiot.
Nexus 4, 4.3 with Cyanogenmod. Working great until I decided to download Franco Kernel. I installed the latest then the colors inverted. I googled it and found out that the latest update didn't work well with Cyanogenmod and that #188 was the last that did work. I.. like an idiot decided to download and install #188 on top of #192 or whatever it was. Phone goes into **** mode, couldn't do anything on my phone without a popup telling me that android had stopped working so I decide to try factory reset, I don't know what I did wrong this time but now my phone won't even get passed the Google sign on boot up.
Bootloader and recovery still works. I cant push factory zip file to my phone without being in adb mode. What can and should I do?
Cheers
Click to expand...
Click to collapse
If you can get into recovery, my suggestion would be a FULL wipe. System/Data/Cache/Dalvik. Then start over from scratch!
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
If you can get into recovery, my suggestion would be a FULL wipe. System/Data/Cache/Dalvik. Then start over from scratch!
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Have done this and am still stuck on Google sign, what should I do afterwards? I still can't push files to my Sd card.
Sivi.N4 said:
Have done this and am still stuck on Google sign, what should I do afterwards?
Click to expand...
Click to collapse
If you can boot into recovery and/or the bootloader, half of your problem is solved. I'm not understanding exactly what is the problem. What I'm saying is, I fully understand what happens when you let the phone do its thing and it stayed on the Google logo, but what I'm NOT understanding is, you not being able to connect to the phone when it is in the bootloader.
Can you boot into the bootloader and connect to your computer?
Sent from my Nexus 7 (2013)
You need to be in fastboot mode to push install a new rom. Press the vol+, vol-, and power.
Berrydroidcafe said:
If you can boot into recovery and/or the bootloader, half of your problem is solved. I'm not understanding exactly what is the problem. What I'm saying is, I fully understand what happens when you let the phone do its thing and it stayed on the Google logo, but what I'm NOT understanding is, you not being able to connect to the phone when it is in the bootloader.
Can you boot into the bootloader and connect to your computer?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yes I can do that.
I am using a toolkit right now, and when I try to push the factory 4.3 I get told that I need developer tools on.
Sivi.N4 said:
Yes I can do that.
I am using a toolkit right now, and when I try to push the factory 4.3 I get told that I need developer tools on.
Click to expand...
Click to collapse
Which toolkit are you using?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Which toolkit are you using?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Using Unified Android Toolkit v3.1.0 by SkipSoft
Sivi.N4 said:
Using Unified Android Toolkit v3.1.0 by SkipSoft
Click to expand...
Click to collapse
Not familiar with that one.
Sent from my Nexus 7 (2013)
---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------
Sivi.N4 said:
Using Unified Android Toolkit v3.1.0 by SkipSoft
Click to expand...
Click to collapse
Are you able to see the phone on your computer?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Not familiar with that one.
Sent from my Nexus 7 (2013)
---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------
Are you able to see the phone on your computer?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
That's a shame.
No I am unable to see my phone on my computer, I can see it in the Device Manager but not under My Computer.
Sivi.N4 said:
That's a shame.
No I am unable to see my phone on my computer, I can see it in the Device Manager but not under My Computer.
Click to expand...
Click to collapse
Sounds like a driver issue. Try first uninstall present drivers, plug the phone back in and see if your computer will reinstall the drivers. Oh, before you do that, switch to mtp see what happens.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Sounds like a driver issue. Try first uninstall present drivers, plug the phone back in and see if your computer will reinstall the drivers. Oh, before you do that, switch to mtp see what happens.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I can't switch to MTP because I can't actually get onto my phone, it doesn't boot.
I'll try to reinstall drivers now, thanks.
Sivi.N4 said:
I can't switch to MTP because I can't actually get onto my phone, it doesn't boot.
I'll try to reinstall drivers now, thanks.
Click to expand...
Click to collapse
I assumed that since the phone showed up in the Device Manager.....
Can you boot into the recovery?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
I assumed that since the phone showed up in the Device Manager.....
Can you boot into the recovery?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yes I can boot into my bootloader and recovery, but not actual Android or whatever you would call it.. sorry.
Computer installed drivers automatically but I still can't see my phone under My Computer.
In CWRM what should be mounted/unmouted under "Mounts and Storage Menu"?
When you did a factory reset, did you do it from the settings on the phone or through recovery?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
When you did a factory reset, did you do it from the settings on the phone or through recovery?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Through Recovery
Sivi.N4 said:
Yes I can boot into my bootloader and recovery, but not actual Android or whatever you would call it.. sorry.
Computer installed drivers automatically but I still can't see my phone under My Computer.
In CWRM what should be mounted/unmouted under "Mounts and Storage Menu"?
Click to expand...
Click to collapse
I wouldn't worry about the mounts and storage, but I do believe this is where you can mount USB. Try that and see if that works.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
I wouldn't worry about the mounts and storage, but I do believe this is where you can mount USB. Try that and see if that works.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
When I press mount USB storage nothing happens but the menu resetting, it doesn't change to unmount USB storage like the other options do either. I feel like this phone is a goner
I've tried to sideload factory 4.4 but it didn't work, I googled the error and people were saying that it doesn't work for rooted devices. I'd unroot though I'm just afraid that I would break something else.
Sivi.N4 said:
When I press mount USB storage nothing happens but the menu resetting, it doesn't change to unmount USB storage like the other options do either. I feel like this phone is a goner
I've tried to sideload factory 4.4 but it didn't work, I googled the error and people were saying that it doesn't work for rooted devices. I'd unroot though I'm just afraid that I would break something else.
Click to expand...
Click to collapse
It wouldn't change to unmount unless it was successfully mounted.
Phone might not be recoverable, but why not download and install NRT by WugFresh? At this point, it couldn't hurt. I would uninstall the first one you were using.
Sent from my Nexus 7 (2013)
would recommend making sure ur drivers are ok....also make sure u got adb on ur comp with fastboot. these 2 are the main things.
honestly skip other things n flash stock on ur own...just so u can be happy...u havent hard bricked the phone...its still working...
try to find universal naked drivers...smthng on that lines....n N4 is superb...its a Nexus...wont die soon
Hi all,
I recently updated my ClockworkMod rooted phone to KitKat 4.? (whatever the latest auto-update release is). It seemed to go well until it asked me if I want to restore root (cannot be undone!!!) and I said YES. Now my phone gets stuck on the boot screen (animated colored circles).
I can still connect with adb and my sdcard looks good (whew) but I cannot use my phone. Can anyone recommend a fix?
Thanks in advance,
Barry
BarryF said:
Hi all,
I recently updated my ClockworkMod rooted phone to KitKat 4.? (whatever the latest auto-update release is). It seemed to go well until it asked me if I want to restore root (cannot be undone!!!) and I said YES. Now my phone gets stuck on the boot screen (animated colored circles).
I can still connect with adb and my sdcard looks good (whew) but I cannot use my phone. Can anyone recommend a fix?
Thanks in advance,
Barry
Click to expand...
Click to collapse
Full wipe and flash TWRP.
Or if you like, flash twrp and see if that alone will help, but most times the two is usually needed. However with the way things are, ymmv!
Sent from my Nexus 7 (2013)
I will full wipe as a last resort only.
BarryF said:
I will full wipe as a last resort only.
Click to expand...
Click to collapse
Understood.
Sent from my Nexus 7 (2013)
---------- Post added at 09:32 AM ---------- Previous post was at 08:43 AM ----------
BarryF said:
Hi all,
I recently updated my ClockworkMod rooted phone to KitKat 4.? (whatever the latest auto-update release is). It seemed to go well until it asked me if I want to restore root (cannot be undone!!!) and I said YES. Now my phone gets stuck on the boot screen (animated colored circles).
I can still connect with adb and my sdcard looks good (whew) but I cannot use my phone. Can anyone recommend a fix?
Thanks in advance,
Barry
Click to expand...
Click to collapse
Darn, forgot to ask you if you are able to get into recovery? If so you might be able to backup everything before you flash the new recovery. My bad! :banghead:
Sent from my Nexus 7 (2013)
BarryF said:
Hi all,
I recently updated my ClockworkMod rooted phone to KitKat 4.? (whatever the latest auto-update release is). It seemed to go well until it asked me if I want to restore root (cannot be undone!!!) and I said YES. Now my phone gets stuck on the boot screen (animated colored circles).
I can still connect with adb and my sdcard looks good (whew) but I cannot use my phone. Can anyone recommend a fix?
Thanks in advance,
Barry
Click to expand...
Click to collapse
No issues. Use adb reboot bootloader to reboot into fastboot mode. Flash the factory image, except userdata.img, you won't lose any apps or SD card contents, no wipe necessary. If you don't know how, I'll post a link to a guide.
Or just use some toolkit like Wug's and do everything from pc through simple menus.
Unleashed by my Nexus 4
just do a full flash via fastboot...
and flash data ...n roms too
Send my signature phone to XDA with bad grammar
ykumar00 said:
No issues. Use adb reboot bootloader to reboot into fastboot mode. Flash the factory image, except userdata.img, you won't lose any apps or SD card contents, no wipe necessary. If you don't know how, I'll post a link to a guide.
Click to expand...
Click to collapse
I would certainly appreciate it if you posted that link. Thank you!!!
Berrydroidcafe said:
Understood.
Sent from my Nexus 7 (2013)
---------- Post added at 09:32 AM ---------- Previous post was at 08:43 AM ----------
Darn, forgot to ask you if you are able to get into recovery? If so you might be able to backup everything before you flash the new recovery. My bad! :banghead:
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Um, how do I get into recovery, please?
Thanks in advance...
http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 7 2013 using Tapatalk
---------- Post added at 08:00 AM ---------- Previous post was at 07:58 AM ----------
http://forum.xda-developers.com/showthread.php?t=2018179
Sent from my Nexus 7 2013 using Tapatalk
Hello,
SOOOOooooo I posted a thread a few days ago. Bear with me, this introductory post is long BUT it is worth including all details I can right from the start to cut down unnecessary communication.
Here goes the continuation in some kind of a bullet form timeline format:
-Bought fully functional d801
-rooted (using ioroot) and unlocked succesfully
-attempted to install twrp using freegee (it didnt work giving me comparable results to this: http://forum.xda-developers.com/showpost.php?p=50501346&postcount=867)
-went on to install it manually from terminal emulator (I installed the rogers version as suggested by another user here as this is exactly my situation: http://forum.xda-developers.com/showpost.php?p=50502408&postcount=869
***
PROBLEMS STARTED HERE
***
-Tried many things
-Lost sleep
-Flashed succesfully using flash tool to the original firmware (D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone) I even flashed it twice. (still had the exact same issues
-Hard resetted countless times
-lost faith in humanity
Thats basically it so far.
Here are the symptoms:
-Imei = null
-Phone resets/reboots randomly and consistently every 5 to 15 seconds
-I can get all the way through to the android os all seems normal Except:
-No keyboard. ever.
-no wifi
-camera even works
-cant get into security and settings (crashes automatically into reboot)
Very good recent news thanks to advice from a memeber on here:
I tried in vain connecting to adb (always giving "offline") until someone suggested trying a different architecture (x64vsx86) or just different pc altogether.
It worked. Now the device is recognized and it says : "some serial number" device
and not "offline" as before
inputting "adb shell" yields: "[email protected]:/ $"
I am open to answer any question.
I am open to try anything.
This phone is a total loss right now so I am obviously open to anything. :laugh:
Phone is still rooted according to "download mode" interface.
Stock recovery installed right now.
I have what I believe to be EFS backups outputted by the initial Ioroot rooting automation (modemstat1.img and modemstat2.img)
You folks are the best.
Much peace and love.:good:
Your t-mobile, right. D801? (Not 100% on that) if you are, you need lg flash tool. I don't have a link because I'm on my phone but it's around. You need to download the T-Mobile files in the 1st post of the thread. Just follow the directions. Wish I had links
Sent from my LG-D800 using xda app-developers app
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Using that will bring you back to stock. From there you can root, twrp, and flash custom rom. Good luck
Sent from my LG-D800 using xda app-developers app
I am not with t-mobile.
Phone is from Videotron (Canadian phone)
I have reinstalled the stock .kdz using flash tool and am also already rooted.
Still have the same issues.
I cannot install anything from wifi since it isnt working...
Any guides on how to install twrp using adb interface?
Or any other suggestions?
Will a custom rom really solve these kinds of issues?
Thanks a lot for the advice I really appreciate any input at this point.:good::good::good:
zprovo said:
I am not with t-mobile.
Phone is from Videotron (Canadian phone)
I have reinstalled the stock .kdz using flash tool and am also already rooted.
Still have the same issues.
I cannot install anything from wifi since it isnt working...
Any guides on how to install twrp using adb interface?
Or any other suggestions?
Will a custom rom really solve these kinds of issues?
Thanks a lot for the advice I really appreciate any input at this point.:good::good::good:
Click to expand...
Click to collapse
Have you tried this http://teamw.in/project/twrp2/197 method.
Initially I tried almost everything but only this worked after couple of tries. http://forum.xda-developers.com/showthread.php?t=2449670
andro ninja said:
Have you tried this http://teamw.in/project/twrp2/197 method.
Initially I tried almost everything but only this worked after couple of tries. http://forum.xda-developers.com/showthread.php?t=2449670
Click to expand...
Click to collapse
Ok really good news :laugh::good:
Making slow but certain progress here.
So just to update also: I now CAN acces the phone from my computer when I put it in PTP (camera) mode.
First I realized that root was installed but that I did not have the supersu installed. I realized this because I could not access "su" in adb shell.
So I reinstalled the ioroot. Complete success. Super su is in the apps and su commands work.
Next I went on to download the rogers TWRP file (even though my phone is a videotron phone) and install it using this:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Which worked!!!
I went to hard reset data and booted into the twrp interface.
I wiped everything from within twrp and went to reboot. it then informed that supersu was NOT installed on my phone and to slide the bar over if I wanted to install so I said yes...
But kind of bad news now:
Stuck at lg logo...:silly: Stays at lg logo and led is lit up changing from blue to green.
So what now?
Any suggestions?
Thanks a lot for the help everyone.:good:
See if you can get into recovery using adb or the holding the vol+pwr keys
Sent from my LG-D800 using XDA Premium 4 mobile app
andro ninja said:
See if you can get into recovery using adb or the holding the vol+pwr keys
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like into the TWRP interface?
Easily yes, I absolutely can.
Next?
(it also seems I can no longer access the internal storage from windows explorer, although the phone is being recognized in devices and printers as "modem LG G2"... It attains this status when it is stuck at the lg boot loading screen)
zprovo said:
Like into the TWRP interface?
Easily yes, I absolutely can.
Next?
Click to expand...
Click to collapse
Did you take any backup using TWRP earlier? If yes then restore it.
If no then you can push another ROM for your device on to sdcard using ADB and install it and see.
andro ninja said:
Did you take any backup using TWRP earlier? If yes then restore it.
If no then you can push another ROM for your device on to sdcard using ADB and install it and see.
Click to expand...
Click to collapse
Ok I will try this now.
If you could provide with adb code example for copying a file to /sdcard i would really appreciate it.
Where do I go within the twrp recovery afterwards?
Thank you so much.:highfive:
adb push <local> <remote>
Sent from my LG-D800 using XDA Premium 4 mobile app
andro ninja said:
adb push <local> <remote>
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ooouuuufff.
New problem
Houston we have a problem:
adb devices = nothing.
How can I get adb devices to work if I cant boot into os and it is not recognizing it when in recovery?
Ahhhhhhhhhhhhhhhhhhhhhhhhh:silly:
zprovo said:
ooouuuufff.
New problem
Houston we have a problem:
adb devices = nothing.
How can I get adb devices to work if I cant boot into os and it is not recognizing it when in recovery?
Ahhhhhhhhhhhhhhhhhhhhhhhhh:silly:
Click to expand...
Click to collapse
Windows ****!! Follow this thread http://forum.xda-developers.com/showthread.php?t=2263822 and install that driver and try.
If not then find yourself a linux box and try. I am sure It'll work.
andro ninja said:
Windows ****!! Follow this thread http://forum.xda-developers.com/showthread.php?t=2263822 and install that driver and try.
If not then find yourself a linux box and try. I am sure It'll work.
Click to expand...
Click to collapse
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
zprovo said:
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
Click to expand...
Click to collapse
You don't really have to burn a CD/DVD, you can use a USB drive.
I don't know much though. I've been doing these things for quite some time now so have experience and I am totally free now so helping you here.
zprovo said:
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
Click to expand...
Click to collapse
It WORKED!
Awesome fix.
adb devices now gives:
(device number) recovery
Ok going to copy a rom and kernel and try to install.
Tried two different roms. Same result
Failed.
set_metadat_recursive: some changes failed
E:Error updating updater binary in .zip '/sdcard/...zip'
Wow just wow.
Any ideas?
This was with omni and cm11. Going to try with a stock rooted rom as soon as it finished downloading.
zprovo said:
Tried two different roms. Same result
Failed.
set_metadat_recursive: some changes failed
E:Error updating updater binary in .zip '/sdcard/...zip'
Wow just wow.
Any ideas?
This was with omni and cm11. Going to try with a stock rooted rom as soon as it finished downloading.
Click to expand...
Click to collapse
look here http://forum.cyanogenmod.com/topic/86979-cm-11-20140124-set-metadata-recursive-some-changes-failed/
---------- Post added at 11:57 PM ---------- Previous post was at 11:23 PM ----------
Just get a latest version of the recovery for your device and install it.
andro ninja said:
look here http://forum.cyanogenmod.com/topic/86979-cm-11-20140124-set-metadata-recursive-some-changes-failed/
---------- Post added at 11:57 PM ---------- Previous post was at 11:23 PM ----------
Just get a latest version of the recovery for your device and install it.
Click to expand...
Click to collapse
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
zprovo said:
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
Click to expand...
Click to collapse
I remember I had same problem. I use to restore only the boot partition from a backup of a stock rom.
So try installing a stock rom like this one http://forum.xda-developers.com/showthread.php?t=2595586. If it works then boot into recovery and take a backup then install whatever you want to and the just restore the boot partition if your are stuck at boot logo.
zprovo said:
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
Click to expand...
Click to collapse
Ok just finished installing the stock bell rom from the site I linked in a previous post.
Stock D803 rom with stock D803 kernel, both installed succesfully.
Phone is back to exactly how it was when I started this thread. EXCEPT that I now also have TWRP running alongside it.
So that includes:
-*#06# = IMEI Null
-phone reboots randomly every 5 to 15 seconds
-keyboard never comes up
-widgets always have a "loading" circle spinning on them
-trying to enter security and settings = auto reboot
-all other options are accesible and useable as long as no keyboard is involved since it never comes up
-no wifi
Wow, this is one hard to fix phone.
Or it simply has hardware damage. but I doubt it since it has no issues running recovery.
Any ideas?:laugh: