Related
I have a rooted nexus 4 and I installed today the newest cm and it booted normally but then I went to the recovery mode (twrp) and did a factore reset and when I try to reboot to system it says no os installed and it stucks at the google screen but it doesn't connect to the pc to copy the rom so what should I do ?
PLEASE HELP ME
EDIT: the pc detects the nexus but I can't copy files to it because it isn't shown in my computer
Sysou said:
I have a rooted nexus 4 and I installed today the newest cm and it booted normally but then I went to the recovery mode (twrp) and did a factore reset and when I try to reboot to system it says no os installed and it stucks at the google screen but it doesn't connect to the pc to copy the rom so what should I do ?
PLEASE HELP ME
Click to expand...
Click to collapse
You can try flashing a rom with TWRP in adb sideload https://www.google.nl/url?sa=t&rct=...v4l4QSOgEwWvPXvTXm_X0Kw&bvm=bv.51495398,d.d2k or https://www.google.nl/url?sa=t&rct=...ZGmpgOaC9H-lOqowATpMSIw&bvm=bv.51495398,d.d2k or flash a factory image in fastboot mode.
gee2012 said:
You can try flashing a rom with TWRP in adb sideload https://www.google.nl/url?sa=t&rct=...v4l4QSOgEwWvPXvTXm_X0Kw&bvm=bv.51495398,d.d2k or https://www.google.nl/url?sa=t&rct=...ZGmpgOaC9H-lOqowATpMSIw&bvm=bv.51495398,d.d2k or flash a factory image in fastboot mode.
Click to expand...
Click to collapse
I don't have the cmd so what should I do please help me
Sysou said:
I don't have the cmd so what should I do please help me
Click to expand...
Click to collapse
Are you running windows? Else flash the factory image from here https://developers.google.com/android/nexus/images with the Nexus 4 Toolkit from here http://forum.xda-developers.com/showthread.php?t=1995688.
You can definitive flash a Factory Image via Fastboot without an Custom Recovery
Did you install nexus 4's usb driver? if you didn't install it and flash custom recovery by using abd siderode
Sent from my Nexus 4 using Tapatalk 4
I need big help, my LG LS980 device is now bricked currently works only in recovery mode with ADB commands, any firmware I tried to upload I did not succeed
adb devices
List of devices attached
03xxxxxxxxxxxx07 sideload
adb sideload aokp_ls980_kitkat_unofficial_2014-01-16. zip
sending 100%
on my screen devices
finding update package
Opening update package
Verifying update package
Installing update
assert failed: run_program ("/system/bin/loki.sh") == 0
Installation aborted.
I've tried other firmware that is supposed to my device with similar result
You may need to restore to stock firmware but I can't figure out the process.
Is there anyone who can help me to restore the device
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
bachera said:
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
Click to expand...
Click to collapse
Thanks for your reply, my problem is that I don't understand how do reroot the device.
The device does not have many options, pressing the buttons (power and Vol +) the device enters in a State Factory Hard Reset.
Pressing (power and Vol-) goes into recovery mode and loads the black screen with anticipation for the adb commands
reboot system now
update from external apply sdcard
apply update from cache
apply update from ADB
wipe data/factory reset
wipe cache partition
With closed then press the device (Vol +) and connect the USB cable enters into Download Mode, here you also don't know what to do.
When I hit the power button just opens the device showing the logo of LG and the led flashing in green/blue and after a while makes itself restarted
I searched the forum for reroot and saw that need to do some settings on the device to do root, did I forget something and so I do not understand?
Sorry, I don't understand and become tedious but it's my first time playing with the object
so, you dont have recovery now?
"adb reboot recovery" not working ?
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
I'm happy because I just unbrick my device by selecting Download Mode Firmware Update and with the LGFlashTools loaded LS980ZV8_ software 13.51097. tot.
Now I lie in my original problem, I want to unlock to accept SIM card from another provider and another country.
Some help to be able to start from somewhere the unlock process?
id3210 said:
so, you dont have recovery now?
"adb reboot recovery" not working ?
Click to expand...
Click to collapse
Who not any command except devices-sideload-kill server-start server-reboot
any other command, I was giving "error close"
votinh said:
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
Click to expand...
Click to collapse
to command push, I was giving "error close"
But all ok, unbrick my devices with LGFlashTools
Great!
Good to hear that.
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
antbox12 said:
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
Click to expand...
Click to collapse
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
natefuhr said:
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No but I fixed it. I had to put it in download mode and flash the stock rom back to it.
I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?
Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.
jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
You have to immediately boot into TWRP after flashing or the system will overwrite it with the stock recovery.
Sent from my XT1575 using XDA Labs
Thanks for that. Exactly the hint I needed.
Question
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
user7743 said:
Hi all,
Sorry if this is covered elsewhere but I cannot find it.
I successfully installed the May 2016 updates and now I am trying to get root back. I followed the usual steps for installing TWRP
Code:
adb reboot-bootloader
fastboot flash recovery .\recovery\twrp-3.0.2-0-clark.img
fastboot reboot
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
Marnina said:
Would you mind telling me what steps you took to get the May update? It's so small that I'm reluctant to do anything major to get it and I'm debating on whether to just flash the stock recovery to give that a try, or whether I'm going to have to flash the unrooted image I've saved using TWRP, then flash stock recovery, then get the OTA. Seems like a lot of work for a tiny update.
No errors seen...
Now if I try to reboot into recovery I get the "No command" page. If I then follow the power button and volume up keypress sequence, I am taken to the original recovery and not TWRP.
Any clues what I am doing wrong? I tried this several times today and no joy (yet all the other updates, I have had no problem getting TWRP and root installed).
Thanks.
Click to expand...
Click to collapse
If you have modified the system in any form, such as using Xposed, then OTA will fail. If the system image is stock that has never been rooted, in theory you should have no issues with stock recovery installed. The OTA is the May security update. Whether you feel it is necessary or not is up to you.
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't run the last command:
fastboot reboot
Select to reboot into recovery from the menu. If you're getting No command, you may need to flash the stock recovery then reboot the recovery. You should have the menu back. Flash TWRP and reboot into recovery to start TWRP.
HTH
Ooms
Sherrillface said:
I can't get any further than unlocked bootloader I get no command after trying to get straight into twrp after flash and always goes to factory recovery if that will even boot is there a secret way to boot into recovery directly after twrp flash cause I've been trying for days and days what is going on is there a way to root without twrp first please help it's the main reason I bought this damn thing
Click to expand...
Click to collapse
1. Periods, dude. Where are they?
2. Flash TWRP again.
3. In TWRP, mount /system (Advanced > Mount > system), and delete:
/system/etc/install-recovery.cfg
/system/etc/recovery-resource.dat
/system/recovery-from-boot.p
Click to expand...
Click to collapse
or add the .bak extension to the filenames.
/system/etc/install-recovery.cfg.bak
/system/etc/recovery-resource.dat.bak
/system/recovery-from-boot.p.bak
Click to expand...
Click to collapse
4. Reboot straight back into TWRP (Reboot > Recovery) to make sure TWRP sticks.
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Sherrillface said:
Can't get into twrp at all tried fastboot reboot and tried recovery mode directly after flash that's the whole issue just says no command upon trying to enter twrp directly after twrp.img flash.
Sent from my XT1575 using XDA-Developers mobile app
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Says flash successful but I don't think it truly is
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
acejavelin said:
Sounds like it's not flashing... what is your bootloader state? Try to start it with fastboot boot recovery.img command.
Click to expand...
Click to collapse
Got it a while ago wrong windroid version.
Sherrillface said:
Got it a while ago wrong windroid version.
Click to expand...
Click to collapse
Umm... OK... No offense to @Rapscallion16 but why are you using a generic toolkit on the Moto X??? It has been mentioned many times that using one click tools and other toolkits is not safe with this and most newer Moto devices, doing it manually is pretty simple.
Anyway, glad you got it working. Enjoy...
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
pentruexperiment said:
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
Click to expand...
Click to collapse
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
sk.c0de said:
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
Click to expand...
Click to collapse
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
pentruexperiment said:
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
Click to expand...
Click to collapse
Try unbrick method I think it's the quickest way to get back your device.