Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
juckeyy said:
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
Click to expand...
Click to collapse
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
gee2012 said:
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
Click to expand...
Click to collapse
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
gee2012 said:
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
Click to expand...
Click to collapse
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
gee2012 said:
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
Click to expand...
Click to collapse
Hmm, couldnt find my adapter. Is there no way to flash in the stock rom with odin?
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Hmm wow seems like a long process but i'll try it.
Thanks!
samersh72 said:
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
Click to expand...
Click to collapse
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
gee2012 said:
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
Click to expand...
Click to collapse
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
thank you my friend
Click to expand...
Click to collapse
Wait one minute bro.
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
Click to expand...
Click to collapse
Hey when I type in adb devies it says mine is unauthorized :/
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
-Edit- also with usb debugging disabled the serialnumber is shown.in recovery.
juckeyy said:
Hey when I type in adb devies it says mine is unauthorized :/
Click to expand...
Click to collapse
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
gee2012 said:
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
Click to expand...
Click to collapse
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
samersh72 said:
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
Click to expand...
Click to collapse
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
juckeyy said:
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
Click to expand...
Click to collapse
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
samersh72 said:
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
Click to expand...
Click to collapse
I did still didnt work. Now I managed to get a ROM into my SD-card so now i'll boot custom recovery and try to install.
lets hope for the best!
Hey again!
Just wanna thank everybody for the help. I solved everything with flashing in stock ROM with odin.
I'll try again tomorrow with other ROM:s
Thanks, Joakim.
had same problem
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
fezz64 said:
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
Click to expand...
Click to collapse
Is it the same with other roms?
Make sure the download is not corrupted.
Wipe data, cache and dalvic after flashing the rom, reboot
sent from my Galaxy
Related
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
sprafael said:
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
More info.what Phone mark modelo etc ?
Sent from my XT910 using Tapatalk 4 Beta
mc704 said:
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
Click to expand...
Click to collapse
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
sprafael said:
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
Click to expand...
Click to collapse
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
mc704 said:
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
Click to expand...
Click to collapse
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
sprafael said:
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
Click to expand...
Click to collapse
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
mc704 said:
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
Click to expand...
Click to collapse
the fastboot do you explain this link??
http://forum.xda-developers.com/showthread.php?t=2376681
I'm downloading the android SDK at this time
let's see if I understand
put the phone in adb sideload
will open the CMD in the fastboot folder,
type in adb sideload image-occam-jwr66v.zip
Flashable zip not factory image, try cm10
Sent from my Nexus 4 using xda app-developers app
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
sander-w said:
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
Click to expand...
Click to collapse
I'm going to be cautious replying here because I'm a noob, but did you try using ADB to issue commands through adb sideload in cwm? If you go to "load zip" (or something along those lines) then "load using adb" (or something similar) in CWM, you can use adb to issue these commands with your computer and it should fix it (at least, it fixed a boot loop for me when I was stuck with TWRP). Here's the link:
http://forum.xda-developers.com/showthread.php?t=2451696
First of all. DON'T PANIC!
And even before that - make a nandroid backup! Go in CWM and make a full backup.
You have recovery working so you should be able to load System on it ok.
I am not an expert but let me try to guide you step by step.
1. Make a backup!
2. Download a rom on your computer. MAKE SURE ITS FOR YOUR MODEL # of LG G2
List of roms here:
3. Make sure you have over 70% battery
4. Go into recovery CWM
5. Use Wipe > Swipe to Factory Wipe
(go back on bottom right corner)
6. Go Advanced from HOME screen of CWM
7. Click ADB sideload
7b. (I assume you have the drivers loaded. If not make sure ADB is loaded in windows and device manager shows it. Download basic ADB package so you have "adb.exe" file in it)
8. put your rom in the same folder where you have "Adb.exe"
9. Open command prompt on windows. Goto the folder where ADB.exe is. Then Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
10. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
11. Wait for a while or reboot your cwm so that the filename will appear
12. just reflash the file in CWM (Install > choose file). Wipe after again.
13. Voila!
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
sander-w said:
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
Click to expand...
Click to collapse
Basically what you need is a root shell whether it's via adb or built into recovery (cwm or twrp)
Searching the forum for "cwm bootloop ota" might give you detailed instructions for your case
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
sander-w said:
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
Click to expand...
Click to collapse
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Drachenminister said:
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Click to expand...
Click to collapse
It seems that my device was in sideload mode. when I disabled sideload mode I followed the instructions on this pag
http://forum.xda-developers.com/showthread.php?t=2451696
And it worked!!!
Thanks for your help all!!!!
I had stock android installed. And I had rooted. I tried to use flashify to install TWRP, but every time it rebooted it would go into fastboot mode. well, I didn't think it would be an issue if I decided to just let the stock update run it's course instead of flashing a rom. So I had the OTA for kitkat run. The phone rebooted, and will only boot into fastboot, and download mode. I need help to get back to stock of any form, root or no root. Please? I am quite far from any repair center at a hotel for the next few days, so Wi-Fi is quite slow.
i
eddytheyeti2 said:
I had stock android installed. And I had rooted. I tried to use flashify to install TWRP, but every time it rebooted it would go into fastboot mode. well, I didn't think it would be an issue if I decided to just let the stock update run it's course instead of flashing a rom. So I had the OTA for kitkat run. The phone rebooted, and will only boot into fastboot, and download mode. I need help to get back to stock of any form, root or no root. Please? I am quite far from any repair center at a hotel for the next few days, so Wi-Fi is quite slow.
Click to expand...
Click to collapse
at least u need to download another stock firmware to flash it through recovery
:good:
x102x96x said:
at least u need to download another stock firmware to flash it through recovery
:good:
Click to expand...
Click to collapse
I don't have a recovery. I'm at fastboot or download. No recovery...
i
eddytheyeti2 said:
I don't have a recovery. I'm at fastboot or download. No recovery...
Click to expand...
Click to collapse
so flash recovery by adb and then use recovery to install rom
:good:
Hit Thanks
flash twrp to it, while in fast boot using ADB
http://download1983.mediafire.com/k2ahkbsh07sg/wk6p32jj5hg2px9/twrp_2.6.3.3_loki-ls980.img
Cronic2009 said:
flash twrp to it, while in fast boot using ADB
http://download1983.mediafire.com/k2ahkbsh07sg/wk6p32jj5hg2px9/twrp_2.6.3.3_loki-ls980.img
Click to expand...
Click to collapse
Instructions please?
When I flash twrp, should I flash a nonstock rom, or stock? Can you direct me to stock downloads.
open command prompt in ADB and execute
fastboot flash twrpls980.img
*make sure you put the downloaded image in the adb folder or you will have to include the path to where the file is located.
I was on a stock ROM when I flashed it, here you can find some stock files. http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Cronic2009 said:
open command prompt in ADB and execute
fastboot flash twrpls980.img
*make sure you put the downloaded image in the adb folder or you will have to include the path to where the file is located.
I was on a stock ROM when I flashed it, here you can find some stock files. http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Click to expand...
Click to collapse
Can I get a link to download ADB for Windows 8? Is that all I need to type? What if I'm using a different recovery image?
What is the sprint stick rom from that download link?
sorry misread your previous post, those .zips are flashable through TWRP, here is a LS980 ZVA ROM, both odexed/deodexed, http://forum.xda-developers.com/showthread.php?t=2630748
you can flash a custom ROM if you would like, look at the thread in my signature it has tons of custom ROMs and kernels
Cronic2009 said:
sorry misread your previous post, those .zips are flashable through TWRP, here is a LS980 ZVA ROM, both odexed/deodexed, http://forum.xda-developers.com/showthread.php?t=2630748
you can flash a custom ROM if you would like, look at the thread in my signature it has tons of custom ROMs and kernels
Click to expand...
Click to collapse
ADB download?
Download this > http://download1983.mediafire.com/k2...loki-ls980.img
put it in your ADB folder and rename it to recovery.img ( just easier to find it )
plug the phone in
open Command Prompt in ADB folder ( hold shift + windows button in ADB folder )
fastboot flash recovery.img ( if you are using a different recovery image, sub it here, fastboot flash blank.img)
this should give you TWRP recovery, you can the use the .zips to update ROMs
CroI ic2009;518ADB12 said:
Download this > http://download1983.mediafire.com/k2...loki-ls980.img
put it in your ADB folder and rename it to recovery.img ( just easier to find it )
plug the phone in
open Command Prompt in ADB folder ( hold shift + windows button in ADB folder )
fastboot flash recovery.img ( if you are using a different recovery image, sub it here, fastboot flash blank.img)
this should give you TWRP recovery, you can the use the .zips to update ROMs
Click to expand...
Click to collapse
Where do i download adb?
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Cronic2009 said:
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
One last question. How do I put ROMs onto the phone in recovery mode?I don't have any rom files for the phone at all yet. Can I flash with ADB?
eddytheyeti2 said:
One last question. How do I put ROMs onto the phone in recovery mode?I don't have any rom files for the phone at all yet. Can I flash with ADB?
Click to expand...
Click to collapse
All these things can be done through ADB yes. Didn't you have to download ADB to root in the first place? You shouldnt have to download again. However if you want to check start up a command prompt and type adb devices. That should pop up something if you have adb installed. I'm not sure if you need to be in a parent folder first though.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Demonlinx said:
All these things can be done through ADB yes. Didn't you have to download ADB to root in the first place? You shouldnt have to download again. However if you want to check start up a command prompt and type adb devices. That should pop up something if you have adb installed. I'm not sure if you need to be in a parent folder first though.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used ioroot, so no ADB. I'm also not by my laptop at all. Would the rom install command be flash fastboot **********. Zip?
eddytheyeti2 said:
I used ioroot, so no ADB. I'm also not by my laptop at all. Would the rom install comand be flash fastboot **********. Zip?
Click to expand...
Click to collapse
Not if you don't have ADB installed.
Demonlinx said:
Not if you don't have ADB installed.
Click to expand...
Click to collapse
I'm going to download ADB today.
Cronic2009 said:
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
So, I have ADB installed. I am on windows 8 though, and the shift+windows button are not opening the prompt. Furthermore when I plug my phone in the computer says "windows cannot find 'C:\ Program Files (X86)\Mobogenie\Mobogenie.exe'. Make sure you typed the name correctly, and then try again" I have no clue what Mobogenie is!
Advice? if there is any for me?
Edit: I can get the ADB window open, but when I type the command "fastboot flash twrp_2.6.3.3_loki-ls980"
I get the following:
unknown partition 'twrp_2.6.3.3_loki-ls980'
error: cannot determine image filename for 'twrp_2.6.3.3_loki-ls980'
I am not sure what to do... Is the Mobogenie the issue? I have all of the proper drivers installed. though I don't see my device in computer on the laptop. Help please? I don't think I can take the device into sprint or lg, because it was rooted.
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...
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!