I would really appreciate some help on this one... I attempted to flash the updated Mahdi Rom (09/20 build) this morning. I'm using the latest Philz Recovery if that matters. I performed the normal wipe procedure and when I went to flash the rom it told me the file was invalid. I think I might have tried to use a zip that wasn't fully downloaded.
I didn't have any other recoveries on my phone (I know... not smart) so I need to figure out how to flash a new rom without using recovery. I'm not completely hopeless and I'm willing to do what it takes to get my phone back!
Any help would be great! Thanks.
Have you tried adb? Your phone will be called sideload when you command adb devices.
Sent from my LG-D800 using Tapatalk
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Rogueharvest said:
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Click to expand...
Click to collapse
You can load adb on Mac. I believe there's a zip somewhere on xda with only the three files need, or download the package from Android. Place it in whatever your username folder is too make life easier. Also add ./ (dot slash) before every command.
Here's the command order for my setup.
cd Android/platform-tools
./adb devices
./adb sideload **DRAG FILE INTO TERMINAL**
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Update: I think I figured it out. The command prompt needed to be reinitiated.
Thanks again for you help! Moments like that are always a little scary!
Rogueharvest said:
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Click to expand...
Click to collapse
Does it recognize sideload when you type ./adb devices? If not and you're in adb on Philz unplug/replug the charger.
Related
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1781250
follow that guide, will get you back to stock then start again, and dont erase sd card next time! just factory reset to go from stock to CleanROM
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
Put the ROM zip file in your Android SDK/platform-tools directory on your computer. Open a command prompt window, change directories to your Android SDK/platform-tools location (for me that's: cd sdk/platform-tools) and type in:
Code:
adb push <name of ROM zip> /sdcard
Wait about 30-60 seconds until it's done, then flash your ROM. It'll be on the root of your internal storage (/sdcard).
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Nico_60 said:
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
danman132x said:
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Click to expand...
Click to collapse
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
RMarkwald said:
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
yudanjah said:
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
Click to expand...
Click to collapse
You should ask in the kindle fire 2 forums as some advice may be hardware specific.
Ive tried installing this MOD on my device
http://forum.xda-developers.com/showthread.php?t=2055231
I have MoDaCo Custom ROM Installed... and now I'm stock on boot screen loading forever!
I forgot to make a back up I thought I have one but I don't...
Is there any way to mount my phone to my pc through Clockwork Recovery? What should I do?
You need to use adb to push a rom in recovery.
While in recovery use the command:
adb push rom.zip /sdcard/
Then you can flash it
El Daddy said:
You need to use adb to push a rom in recovery.
While in recovery use the command:
adb push rom.zip /sdcard/
Then you can flash it
Click to expand...
Click to collapse
I have no rom on my phone
can u explain more?
I'm a noob
shahabk818 said:
I have no rom on my phone
can u explain more?
I'm a noob
Click to expand...
Click to collapse
I know you don't have a rom on your phone. This is how you can push one to your phone.
You must be booted in recovery
Put the rom in the same directory on your PC where you have adb.exe
Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/
The file with push to your phone and then your can select it and flash it from recovery.
Thank you
Hi i have similar problem and more. Using galaxy nexus, i was playing with this updates and now screwed up. Using Mac makes it even harder. What is ROM file u referring to?? And also in adb it says my device cannot be found. Please help asap.
sajeenath said:
Hi i have similar problem and more. Using galaxy nexus, i was playing with this updates and now screwed up. Using Mac makes it even harder. What is ROM file u referring to?? And also in adb it says my device cannot be found. Please help asap.
Click to expand...
Click to collapse
You've gotta be clearer. First, you're in the wrong thread if you are using a galaxy nexus. You tried the nexus 4 4.2.2 update on your gnex? Or you tried the paranoid platinum for nexus 4 on your gnex? Mac should make it easier, in my opinion. Try updating your android sdk, or just adb: http://forum.xda-developers.com/showpost.php?p=37928936&postcount=24
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Trickee360 said:
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Click to expand...
Click to collapse
Can you get into bootloader with power+vol down?
boot into the bootloader, then via fastboot..
fastboot boot recovery recoveryname.img(press enter)
remember to put the recovery img file in the same folder that fastboot is located, on your computer.
bootloader's good to go and I'm in recovery but I need a way to get the rom on my tablet. Mounting sdcard doesn't appear to do anything while connected to my pc
EDIT: tried the CWM flash from sideload option and my command line says it "cannot read 'sideload'" do I need to start/restart the server another way? I feel like a total noob, lol
adb push rom.zip /sdcard/
Pirateghost said:
adb push rom.zip /sdcard/
Click to expand...
Click to collapse
started the daemon then got error: closed
Trickee360 said:
started the daemon then got error: closed
Click to expand...
Click to collapse
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Pirateghost said:
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
no Can I do that through the sdk manager or do I have to update the sdk itself?
sdk manager can handle it
Pirateghost said:
sdk manager can handle it
Click to expand...
Click to collapse
Ugh. SDK manager won't install anything. EIther it says whatever package I'm working on requires API17 (which I'm trying to get, lol) OR it just plain can't "find" the package because acces is denied? What am I doing wrong?
I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler
What's up now ?
Sorted it out or still issues there ?
I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"
I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"
I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord