LG volt apparently has no bootloader. Recovery and factory reset both broken. - General Questions and Answers

I didn't find a thread for the Volt, model LS740 on Virgin Mobile. Rooted by the original owner. So I'm posting it here. I'm using adb on Ubuntu.
So I'm trying to repair a broken system by reflashing the stock ROM. I suspect the previous owner(who rooted) may have removed multiple important system apps. Upon doing a factory reset it has no home launcher or keyboard. As soon as the screen turns off it loops a com.android.systemui has stopped. Every boot you need to do a factory reset to get it to work: booting once, then again will loop the systemui crash, requiring a factory reset to work.
The android recovery works, I can get to it, but it offers install update from cache, adb, or sd card. The phone will not recognize sd card while it is in recovery, and adb doesn't work in recovery, only while booted. Copying recovery image to cache fails at 71%, I suspect the phone does not have enough RAM to move 1.17 GB from A to B. The phone may also not have spare storage space. I'm working on finding an sd card so I can try copying from there.
"adb reboot bootloader" reboots the phone normally. If there's a bootloader it skips it entirely. I found threads that say uncheck fast boot in power/battery options, but I have no such check box.
Right now, I have adb, images/zips for twrp recovery and stock rom, and I can push apks for a launcher and keyboard. But I apparently can't access bootloader or install rom via recovery. I don't have an sd card to try and copy the rom to cache, which I will try as soon as I get a card.
Adb cannot run as root, I get "adbd cannot run as root on production builds. So I can't directly push the rom to /cache/backup using adb.
Any help? I tried to get it all out there so that you guys could help better. Thanks for reading all that.

Fixed it by finding an LG recovery reflash utility and reflashing a factory version.

Related

Nexus S won't boot to OS

I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!

[Q] Is it bricked

I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
jflynn0 said:
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
Click to expand...
Click to collapse
What instructions did you follow? Is the bootloader unlocked and can you boot into it? Does adb work? Need more info if we're going to help you.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
bootloader unlocked
I was looking around in cwm menu before I tried to install the stock asus rom. Just going thru the menu's looking trying to familiarize myself with cwm. I went to backup and restore menu and there was Zip there. I hit to power button instead of the volume and it starting restoring the device. After that i have not been able to get it to do anything after the asus screen. But I can get into the menu of cwm. When i tried following the adb, i go into cmd on my computer and change directory it tells me the device is not ready. I tried putting a zip on a sd card but I cant get it to show on the device to install.
Try a factory reset in CWM, see if that helps.
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
jflynn0 said:
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
Click to expand...
Click to collapse
Can you flash a different ROM, maybe the stock one?
Had the same problem. Tried to flash stock from Twrp recovery.
Wipe do a factory reset, wipe system and than flash the aokp rom again.
Then reboot and when you are back in System you can put the rom you like on your internal SD.
Back to Recovery and flash the new rom.
I got adb working and it come up in devices list. How do i flash the aokp rom on the device. I'm learning this as i go along, after this i might get the hang of this . I cant seem to push files using adb either my directory is wrong. I unzip it into a folder (C:\romfolder\aokp_tf201_build-38.zip/sdcard) and all that comes up scrolling page of commands and help for adb when i push
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
jflynn0 said:
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
Click to expand...
Click to collapse
Do not flash a 201 rom or image. Thats for the prime. Never flash roms designed for another device no matter how similar they are.
ok I downloaded this on
http://goo.im/devs/termleech/tf300t/aokp_tf300t_unofficial_20120617_2100_build-39.zip
have to go to bed but when i get up this afternoon will try to get it o go to device.
How am I suppose to get it to the device if the sd card does not show up on file list in cwm?
Can you still use ADB? You can always push the files with that.
how do i use adb to push the file on to the device itself. because i can add it to the sdcard by just putting in on there and then placing sdcard in device but the menu as far as install zip from sdcard never shows any zips that are on the card itself. Only thing that shows up are list of directories that look like a standard list from cwm. Also if you choose any of directories from that list it returns no file found. If I choose apply update on sdcard no matter how many time i have called the file update.zip says "no such file or directory install aborted". Or how do i push and image to the restore section of the device and where do i find an image at?
well still no luck. I think I will give it a few more days and if I still cant get it guess will go to best buy and buy another on. Any thoughts on Toshiba excite?
Try this i posted a tutorial on how to fix this http://forum.xda-developers.com/showthread.php?t=1738825 hope it helps

[Q] [URGENT] Need Help For MY DEAD DEVICE

I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english
Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .

Factory reset & flashing doesn't work

Hey,
i've got a few problems with my HTC One S, running Cyanogenmod 11 (4.4.4) with TWRP as recovery.
Since a few days nearly every app crashes, ca. 3 minutes after I start the phone. In these minutes everything is working. After that there are only messages that "android.process.acore", "com.google.process.gapps" and nearly every other app has been closed. When I press OK, the message appears again.
So I tried to flash another ROM, which isn't possible because I first can't copy anything to the phone, the copying process stops after the half. I also couldn't download a ROM directly to the phone. Then I tried to flash again my actual ROM which is still on the phone, I selected the .zip in TWRP, but then the phone is restarting and nothing happened.
There are also other problems:
1. I tried a soft reset in the settings, isn't possible because nothing happens when i press the "Confirm" button
2. Clear storage and Factory reset in the boot loader isn't possible, when I select one of that the phone only starts into the recovery, without anything has been resetted
3. Pushing a zip with ADB doesn't work, it says I don't have permissions to copy anything on the storage
4. The ADB sideload mode doesn't start in TWRP
5. I tried to flash CWM as recovery, it says "successful", but when I start into recovery there is still TWRP..
6. Relocking the bootloader doesn't work, it also says "successful" but in the bootloader appears "*** unlocked ***" After that I tried to turn back to stock ROM with the RUU exe by HTC, but when the process starts, the phone just turns off.
Does anyone have a idea? Do I maybe have a virus? Sometimes it appears to me that there are problems with the storage or anything like that..
I really tried to do everything, and also searched in this forum and in other but I didn't find anyone with the same problem..
Thank you!
Give the Mount option a try in TRWP and see if you can copy a ROM over to the phone.
Okay I had to install the right driver for adb..
Then adb push worked, I could select the .zip in the Install option in TWRP, but the phone again just restarts without installing the rom..
ADB Sideload also worked with the driver, but after I tried to ADB sideload the ROM it said "* failed to write data 'protocol fault (no status)' *"..

Samsung Nexus S is stuck in "Google" bootloop

Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Just do a manual restore using the google factory images (google them, first result usually and a VERY user friendly page, thanks google!).
Don't use the script, just reformat everything via fastboot, then manually flash the images to their respective partitions.
"cd [path to unzipped images]"
"fastboot format /[partition] ext4"
"fastboot flash /[partition] [path to image]"
and so on and so on. Then after, "fastboot reboot". I assume you've found a fix by now but maybe someone else will stumble on this. Keep in mind, I'm writing this from memory and with no drivers or way to test this on my mac, my Nexus S is coming in the mail soon so take what I say with a grain of salt and try to double check the commands. For the most part however, they should be correct. format, reflash, reboot. All you should have to do.
padhpataka said:
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Click to expand...
Click to collapse
I have the same problem.I know this was 4 years ago but as a noob I find that guides tend to assume greater levels of knowledge than I have. Trying to bypass FRP as I think this is what is causing the "system error" message when I try to access play store or Google plus. I haven't even been able to unlock bootloader or root phone . In fact I find "fastboot" and ADB downloads a mystery? How to get them to work?

Categories

Resources