I installed a rom which had a bad install so i was stuck in a boot loop, And no matter what I try i always get the boot loop, Im able to boot into twrp but going to mount im unable to see it on my windows 7 laptop? I have no idea how to push files to the device with adb as im what you'd call a slow learner lol.
Any ideas would be much apreciated.
I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!
Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?
crazyboy81 said:
I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!
Click to expand...
Click to collapse
Thats an easy one compared to me lol. go to advanced, terminal command and type in the following minus the brackets (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota)
metapy said:
Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?
Click to expand...
Click to collapse
My problem isnt anything like the bootloop, Ive done a full wipe and now have nothing on my phone to install, adb sideload isnt working for me for some reason as its coming up as adb is not a recognised command? I feel screwed?
EDIT: I may have solved my problem, currently pushing a rom onto the phone with adb sideload
Related
I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!
How did you wipe system within CWM?
But since you say you wiped internal partitions too, it seems to me that you wiped your internal emulated sdcard... so I think your only option now is to flash stock images again... Read this: http://forum.xda-developers.com/showthread.php?t=2010312
If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/
Thanks guys. Found a solution.
Flashed TWRP and sideloaded the ROM file. And flashed it.
Earlier the same process with CWM was not successful. Now the phone is loaded with PA ROM!
Thanks guys! and can u point me to the google stock images??
njarun said:
Thanks guys! and can u point me to the google stock images??
Click to expand...
Click to collapse
Glad you solved it
Here are the stock OTA and images from google and mirrored http://forum.xda-developers.com/showthread.php?t=1971169
My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?
mrjoeltan said:
My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?
Click to expand...
Click to collapse
wiped /system? have you tried simple re-flashing your ROM from the .zip ?
no worry... download the nexus 4 twrp latest img from their site, and flash it to your N4
what you needed:
twrp img file
some n4 rom
adb and fastboot
instructions:
boot to fastboot, vol key down + powerbutton when n4 is off.
on your comp, , dos/terminal - fastboot flash recovery twrp.img
reboot in recovery
select the adb side load from advanced tab in the twrp.
on your comp - adb sideload rom.zip
everything done....reboot phone.
Sent from my Nexus 4 using xda premium
I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.
blackcatvn said:
I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.
Click to expand...
Click to collapse
did you wipe using fastboot erase command? if so, you need to re-format to the android supported file system to access the partitions!
try installing the twrp recovery and perform 'FORMAT DATA' from wipe. then install ROM.
N4 no OS.
njarun said:
I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!
Click to expand...
Click to collapse
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel
Axelben said:
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel
Click to expand...
Click to collapse
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..
Same problem but...
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
El Daddy said:
If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/
Click to expand...
Click to collapse
Got it working
Hi, I got it to work. No worries guys
xXDustinoXx said:
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
Click to expand...
Click to collapse
njarun said:
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..
Click to expand...
Click to collapse
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file
nickboy360 said:
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file
Click to expand...
Click to collapse
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!
njarun said:
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!
Click to expand...
Click to collapse
Thanks for asking mate i got it done... :good:
Alright, so i rooted my phone yesterday, And i made a mistake in downloading the OTA update and it turned off my phone. Now when i turn it on it boots into TWRP and when i reboot System it takes me back to TWRP. Pretty much everything takes me back to TWRP, and when i try to flash a ROM that also takes me back to TWRP. Im able to get my device recognized in adb devices and i tried using adb push to get roms on that way but it still takes me to TWRP. When i tried using flash tools to get it to flash a stock rom from my PC, it is unrecognized because it wont boot into download mode. Any ideas?
Killiun1 said:
Alright, so i rooted my phone yesterday, And i made a mistake in downloading the OTA update and it turned off my phone. Now when i turn it on it boots into TWRP and when i reboot System it takes me back to TWRP. Pretty much everything takes me back to TWRP, and when i try to flash a ROM that also takes me back to TWRP. Im able to get my device recognized in adb devices and i tried using adb push to get roms on that way but it still takes me to TWRP. When i tried using flash tools to get it to flash a stock rom from my PC, it is unrecognized because it wont boot into download mode. Any ideas?
Click to expand...
Click to collapse
So I had this happen with an S4 I got for my son for Christmas. It was the first thing he did when he started it up. I immediately freaked out.
I plugged into a PC and got my drivers all set up. Got through on adb and did a fastboot reboot.
It let me boot back up (it can't flash the ota because of twrp).
Hope that works on the g2.
Mikkey81 said:
So I had this happen with an S4 I got for my son for Christmas. It was the first thing he did when he started it up. I immediately freaked out.
I plugged into a PC and got my drivers all set up. Got through on adb and did a fastboot reboot.
It let me boot back up (it can't flash the ota because of twrp).
Hope that works on the g2.
Click to expand...
Click to collapse
It gets stuck on waiting for device :/
That happened to me. It was a bad flash via CM updater and it was stuck in TWRP. I downloaded the ROM onto my computer then pushed it to an SD card (via a card reader). Then I inserted the card and flashed from the SD card and all was well. I have a Galaxy S3 so YMMV, but hope this helps.
Sent from my SCH-I535 using xda app-developers app
momonjava said:
That happened to me. It was a bad flash via CM updater and it was stuck in TWRP. I downloaded the ROM onto my computer then pushed it to an SD card (via a card reader). Then I inserted the card and flashed from the SD card and all was well. I have a Galaxy S3 so YMMV, but hope this helps.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ya, instead of a card reader, i just used adb push and i tried flashing a stock rooted rom for my device.. but it failed, so i was considering trying CWM instead of TWRP, which might help, but i dont know the command for flashing a recovery via terminal.
edit: i got CWM and tried installing CM-11 and it says successful like a normal flash and when i reboot system, it just boots straight back into recovery...
Killiun1 said:
It gets stuck on waiting for device :/
Click to expand...
Click to collapse
Did you try to reboot while it was still plugged in?
All I'm trying to do is get your device to stop trying to flash the ota and that adds an additional command. That's why it continues to hop into recovery... Its looking for the stock recovery.
I'm on the hunt right now to see what I can find.
Has to be a command. Let me boot up my laptop, drop into download and see what command i can get through. No adb right?
Mikkey81 said:
Did you try to reboot while it was still plugged in?
All I'm trying to do is get your device to stop trying to flash the ota and that adds an additional command. That's why it continues to hop into recovery... Its looking for the stock recovery.
I'm on the hunt right now to see what I can find.
Has to be a command. Let me boot up my laptop, drop into download and see what command i can get through. No adb right?
Click to expand...
Click to collapse
YESSS! i got it to work!! i used this:
http://forum.xda-developers.com/showthread.php?t=2451696
thank you so much for trying to help!
mods can close this thread or do whatever you guys do
I am getting a secure booting error. I can boot in TWRP but when I connect to my computer and type ADB devices, none are listed. Everything was working earlier because I just rooted the phone today. I have no backup and am trying to sideload a stock ROM. For reference, I am following this guide for sideloading. When I get to step 7, I get "system cannot find path specified". Thanks for the help.
dc5_alex said:
I am getting a secure booting error. I can boot in TWRP but when I connect to my computer and type ADB devices, none are listed. Everything was working earlier because I just rooted the phone today. I have no backup and am trying to sideload a stock ROM. For reference, I am following this guide for sideloading. When I get to step 7, I get "system cannot find path specified". Thanks for the help.
Click to expand...
Click to collapse
Hey so you have adb setup and set in enviromentals right?
RubbleTea said:
Hey so you have adb setup and set in enviromentals right?
Click to expand...
Click to collapse
hey thanks for the quick reply and yes I do. Here is a timeline of my events: rooted phone, installed TWRP 2.6.3.2. Made backup. Installed mod. Didn't like mod so restored backup. I didn't wipe so this may have been the problem? Now getting the secure booting problem
dc5_alex said:
hey thanks for the quick reply and yes I do. Here is a timeline of my events: rooted phone, installed TWRP 2.6.3.2. Made backup. Installed mod. Didn't like mod so restored backup. I didn't wipe so this may have been the problem? Now getting the secure booting problem
Click to expand...
Click to collapse
Do you till have the backup on there? If so yah prob not wiping did it. If you can just wipe and restore....if not let me know I'll help you sideload a ROM....you should upgrade to 2.6.3.3 after all this too will help if you use any 4.4 Roms and fix slow wipes on a side note
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
brickwall99 said:
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
Click to expand...
Click to collapse
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
freebee269 said:
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
Click to expand...
Click to collapse
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
brickwall99 said:
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
Click to expand...
Click to collapse
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
freebee269 said:
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
Click to expand...
Click to collapse
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
brickwall99 said:
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
Click to expand...
Click to collapse
that's because you have no adb connection. no connection = no pushing files. that's why i said you need to get adb working first.
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
brickwall99 said:
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
Click to expand...
Click to collapse
good news. hope you get up and running now. still update your twrp.
freebee269 said:
good news. hope you get up and running now. still update your twrp.
Click to expand...
Click to collapse
Okay I got the ROM transferred and I have installed it successfully.
Using this one: http://forum.xda-developers.com/showthread.php?t=2598361
But when I reboot it goes straight to recovery.
A factory reset fails. I'm only able to advanced wipe of system/data, also it fails when I wipe cache or dalvik.
So I've tried wiping system/data, then installing the ROM again, and it just reboots straight back to recovery.
I sideloaded TWRP 2.6.3.5 for tmobile. Verified it shows 2.6.3.5 TWRP now. I'll try to sideload/install the ROM again.
Edit: When trying to factory reset it says failed to mount cache.
Okay so I have successfully installed the ROM with TWRP 2.6.3.5 and when I reboot it still goes straight into recovery.
What next?
Thanks
Edit: Is there perhaps something wrong with the bootloader, or what? I'm thinking part of the issue is because I can't mount or wipe cache/dalvik?
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
rawb123456 said:
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
Click to expand...
Click to collapse
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Any luck? I tried flashing CM11 on TWRP 2.6.3.2 (per XDA instructions) and it failed. Now I am stuck in recovery and can't ADB new recovery
brickwall99 said:
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Click to expand...
Click to collapse
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
HellaBester said:
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
Click to expand...
Click to collapse
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
osugsxr said:
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
Click to expand...
Click to collapse
Yeah I considered that but no everything is up to date. It seems more like the RSA auth fingerprint is not being recognized. Plus it does recognize the phone, it just tells me it is unauthorized.
Get back into Recovery mode and use ADB from there
votinh said:
Get back into Recovery mode and use ADB from there
Click to expand...
Click to collapse
How do I get into recovery without being able to "adb reboot recovery"?
unomicu how
Bump. Anything guys? Really struggling here....
Can you get in recovery using button combination?
votinh said:
Can you get in recovery using button combination?
Click to expand...
Click to collapse
Nope, doesn't seem like it. Though I can get into download mode no problem.
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
HellaBester said:
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
Click to expand...
Click to collapse
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
super114 said:
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
Click to expand...
Click to collapse
Heyoo, just in the last hour or so I've got it all fixed!
I did a full system, data and cache format om CWM after that there was no OS or amnything of the sort, then I was able to mount the SD and adb push cm11 + gapps-kk to the sdcard, I flashed those two zips restarted, failed, then i did a system reset (resets everything but the OS) and I popped out in CM11 with a perfectly fresh install. got all that setup and am golden now ::
Congratz
Check the .android folder
My problem started when I tried to connect another phone which happened to be the same type of phone as the previous one. Not sure if that's actually related, but my working hypothesis is that ADB gets confused in this scenario. I tried everything listed here and in many other places, and nothing seemed to work. Finally, I did this:
1. Rename .android folder in your user directory (~/username/.android on Mac OSX) to .android_bak (for safe keeping).
2. Restart the adb daemon: "adb kill-server" followed by "adb start-server"
After that, I got the authentication confirmation on the phone (don't forget that part, of course) and all was well.
These steps merely recreate the .android folder and get rid of any authentication credentials you already have. Note of course that this will impact all other phones you may be connecting.