I took a bunch of backups before hand, but I put them on my laptop, so they're not on my phone. I've tried connecting my phone to my laptop, but I can't access the filesystem of my phone through my laptop. I can, however, boot my phone into TWRP recovery through a .bat file on my computer. The only thing I've managed to be able to do from there is wipe the phone and flash stuff. The only thing I've got on my phone that's useful is two .zips, the PA 4.4 zip and the Gapps that follow. As far as I can tell, the only thing I need to do to get my phone working again is to get my backup files back onto my phone somehow, but I cannot seem to get that working.
I've tried the ADB push command, but it can't detect my phone, so that's not working.
I'm wondering why the .bat works, as I can tell by the log that it is sending files to my phone! Somehow it manages to do it, but I cannot send my own files. Why is that? Also, looking at the log from previous times, It sent the files with speeds of several MB/s, but now it's only sending them at like 100-200KB/s. Is my SD card damaged?
I've read through a bunch of guides, and several of them states that the stuck boot animation is caused by the cache, so I tried wiping that. However, for some reason, it's begun to say "Error: Operation failed" when trying to wipe it again.
Help please
## Fixed it.
Could you post the .bat file that you used? Sorry if its a bit off topic but you are the only person that I can find with a similar problem as me and I have my phone stuck in the boot animation. I can't get my phone into recovery mode and was hoping that your .bat file could help me. I have a back up in twrp that I could use.
Related
I've been going through quite an ordeal with my Tab over the past few days.
It started with my Tab boot looping for no apparent reason, then I couldn't get fastboot to work, but now I solved my fastboot problems. I followed some instructions (here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) on how to use fastboot to get it working again, and i flashed that system image linked to in that post. And it worked, I had my Tab up and running again, but I noticed that my storage space total is now at 13GB; I remember it having 32GB total storage before this whole ordeal. I'm guessing I flashed the wrong system image to my device, so does anyone have the correct system image for the I/O Tab 10.1?
I tried this one: http://forum.xda-developers.com/showthread.php?t=1075993 and my device gets stuck in the boot screen (not even looping, it just stays on the "Samsung Galaxy Tab 10.1" screen)
Any help would really be appreciated.
use this to recover:
http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77
read the whole thing (quoted and unquoted).
you can get images here:
http://droidbasement.com/galaxy/sys-backup/hc_31
if you have media (/data/media (internal sdcard)), back it up prior (you will lose it).
that droidbasement link returned a 404 not found error.
fixed.
refresh.
let me upload raw fastbootable images also, for the first part.
check back in one hr.
done uploading.
Ok, I've got it all sorted out. Thanks for the quick response, Pershoot.
Here's a breakdown of how I got it working again...
First, I installed PDAnet as a shortcut to get the fastboot drivers, as soon as I installed it, fastboot started working.
Then I downloaded the files linked here: http://forum.xda-developers.com/show...&postcount=111
Then I followed the first half of Pershoot's instructions (http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77) using the files provided by novicejeep. I did all the fastboot stuff, booted into recovery, factory reset, reboot, but instead of getting a boot loop, my device booted up just fine. I had previously flashed these same files to get it working but those times my storage showed as 13GB for some reason, but now it's showing as 27GB. I'm guessing the factory reset corrected that issue (or maybe it was erasing before flashing each thing?).
The only downside now is that I'm back on 3.0.1, so what's the safest way to get up to 3.1 for a root user? I suppose I'll take my chances with System Update in the Settings.
Thanks Pershoot, novicejeep, kdietze3 and everyone else here on the forums
if you are on 3.0, then just use the restore method to 3.1.
you would have been on 3.1, if you would have used all 3.1 images, as outlined in my instructions from the sys-backup/hc_31 folder.
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
dracoaffectus said:
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
Click to expand...
Click to collapse
yea as outlined. then prceed on with the instructions, and when done, you will be sorted.
The new kernel did not like my tab. It crashed pretty hard when I plugged it in to charge. Now when I try to boot, it loops at the "glowing SAMSUNG" screen. I tried to restore with ODIN and it's still looping. Going to try this method.
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
Morning
I had a corrupt TWRP 2.8.6.1 and then removed it using flashify CWM. That removed the ROM AND recovery, Now I have an 'empty' phone with the secure boot message. I have tried what seems to be the only resolution http://forum.xda-developers.com/showthread.php?t=2432476 (back to stock) but the tool doesnt recognise my phone. I have the google drivers installed and the LG drivers and have switched between both. After the small white writing saying 'security boot error' the PC scans loads of drives before stopping. I then see my phone with the file 'image' in it. Within that are lots of scary looking files called adsp, cmnlib and modem. So there is some detection... However unfortunately (and perhaps critically) adb does not see the device.
This is clearly a serious issue and maybe beyond some of the biggest brains on here. However if someone does have an idea, could they help me (and guide me through it like I'm a 10 year old ) Otherwise this will probably become a fake phone for my 7 year old!
Any ideas please?
So I've been working on this thing for a while but maybe it's because I'm new to this whole there are a few issues I'm having in getting it restored.
Here's the story. I purchased a bricked LG G2 D800 (I fix phones so it's not my own personal phone). It goes to the LG logo when you boot and stays there. I don't know what firmware is on it. It does however have CWM and I can connect to it via ADB but I'll list my issues there below. It does also have download mode but my computer won't recognize it the phone when it's plugged in.
CWM:
OK, some of the issues I'm having here but just be because I'm still nooby and it's hard as hell finding a complete guide to this stuff for noobs.
Anyhoo, I have:
1) Gone into sideload to install the stock zip files; however, no matter what I do, ADB "cannot read <zip.file>". I've re-zip, tried a different zip, renamed the zip, tried a different zip, rebooted. I'm out of ideas there.
2) I tried pushing the zip and install from CWM. That didn't work either.
If the thought "why are you trying to go back to stock via adb" pops into your head and YOU actually know what you're talking about, it's probably because I don't.
DL Mode:
*Comp won't recognize
*Can I even do anything here if I never authorized USB bugging?
I'm kinda lost on what to do here. I know most methods of restoring back to stock are pretty simple but since I haven't been able to get DL mode to work or get that zip file to work in sideload, I'm kinda out of ideas.
Oh, another issue I've been having: WHERE THE HELL IS THE KDZ?? I have not been able to locate the KDZ for the d800 anywhere on the interwebs. Every link I've found takes me either to the cowshare place or elsewhere but everyone has only had the .zip file... and since I have no idea what the different is between the kdz and the .zip (I did spend some time researching that one but to no avail), I'm not sure if that's a problem or how to fix it.
Another idea I had that I haven't tried yet is flashing a bootloader. IIRC from when my VS980 was stuck after trying to install Cyanogenmod, a bootloader was the fix. However, since I don't know what software is on here, I think I can just cycle through a few until something works?
Anyhoo, any suggestions would be totally welcome here.
Hi guys!
I have made a serious mistake, and I feel so stupid! I was wondering if any of you awesome people at XDA would be able to save me.
I have an LG G2 vs980 Lollipop 5.0.2
So, all I wanted to do was change my startup screen to get rid of that boring LG logo and replace it with something neater. I went over to Google and found a guide on how to do this, and followed the steps 1 by 1. Everything actually worked out perfectly, but it wasn't until after I was locked out of my phone that I realized that I had used a startup image that was not compatible with my LG G2! (Total face palm!). Now, whenever I power my phone, it flashes that "neat" image that I replaced the stock one with - before the screen goes completely blank and I cannot do anything at all. That's not good!
So my question is this - Is there a way I can access my system folder without having access to my phone? I know EXACTLY what file I need to remove/edit to solve this problem! In fact, that is what is frustrating me the most. It's not some random error message out of the blue that I know nothing about. I know exactly what the problem is, I just don't know if I have access to the solution. I just really hope I don't have to wipe everything back to stock all because of a lousy startup image.
Is there a way to access the system folder on my phone so I can remove the bad file and replace it with the stock image so I can get my phone working again? If anybody can help me figure out the best method to solve this issue, I would be forever grateful! Thank you guys so much in advance!
Much appreciative,
Terri (Psyintz)
If you are rooted I assume you have also TWRP or CWM installed. TWRP has an integrated file explorer so you can delete these files. And you can try to push new files through ADB. Just google
android adb push while in recovery
Good luck!
Jan Philipp said:
If you are rooted I assume you have also TWRP or CWM installed. TWRP has an integrated file explorer so you can delete these files. And you can try to push new files through ADB. Just google
android adb push while in recovery
Good luck!
Click to expand...
Click to collapse
But I don't remember installing TWRP or CWM during the process. The guide I used to change my startup image just had me use some sort of "one-click rooting" application, before detailing which files I needed to backup and exchange in order to change my startup image. So I'm not very confident in the fact that I have either of those things installed, which makes me afraid to try and click on my factory reset button.
After finding a guide on installing TWRP via this ADP thing, I seem to get stuck early on in the process. When it asks me to open a command prompt and type "adb reboot bootloader" it returns the message "error: device (null) not found." I am not sure why it is not finding my device. Is it because my phone does not boot, so it is not able to connect to it?
I am beginning to lose faith in there being an option to solve this problem without just performing a factory reset, and losing all of my data. If I were to take this route, can I just use my phone's built-in option? By holding the correct keys, and then choosing to wipe all my data and return to stock?