Okay, so my phone's label is "P700" from "LG", I was flashing my rom with all the sucess to slimroms, but I decided to try a new one and basically I went to recovery options, deleted the /system and /data, what I didn't know is that /data is my sdcard, after doing that I was pretty much stuck in recovery mode, then I clicked on sideload and I was stuck in sideload, trying doing sideload from windows, but adb didn't recognize it, now after restarting my phone and plugging it into windows for 4 hours straight and downloading drivers, my adb finally see's it, once the adb started seeing it - I reboteed my phone into recovery because before it didn't work, anyway I end up with blank screen, and before I had just LG logo, now after putting the battery out and inside - my phone causes every windows system to restart with the error - IRQL_NOT_LESS_OR_EQUAL, maybe some of you experienced this, maybe not, I was wondering if I could somehow format my phone, reinstall kernel, reinstall rom and recovery system from Ubuntu, since adb still recognizes it and I think it won't crash Ubuntu.
Related
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
So my phone had an issue earlier this morning where it would go through the entire boot process successfully until it got to the lock screen and then after a few seconds of displaying the lock screen( no touch response) it would go back into the booting process starting with the lg logo. So I thought it was just the rom messing up (sky dragon 3.0.1) so I re-installed it. Long story short after a few tries and some messing around it didn't work and now I have no operating system to go to or install. Is there a way that I can get a rom onto the phone through twrp recovery so I can install it? Or am I just missing something really obvious.
Thank you
The easiest thing to do would be to pull the sd card, load your rom .zip on it, pop it back in. Boot into twrp and wipe and install.
If you don't have a SD card but the phone is recognized by your computer when in TWRP, use adb push rom.zip /sdcard then flash.
SewperSawsed said:
So my phone had an issue earlier this morning where it would go through the entire boot process successfully until it got to the lock screen and then after a few seconds of displaying the lock screen( no touch response) it would go back into the booting process starting with the lg logo. So I thought it was just the rom messing up (sky dragon 3.0.1) so I re-installed it. Long story short after a few tries and some messing around it didn't work and now I have no operating system to go to or install. Is there a way that I can get a rom onto the phone through twrp recovery so I can install it? Or am I just missing something really obvious.
Thank you
Click to expand...
Click to collapse
there is an adb sideload function in the advanced menu of twwrp.
if you dont have adb, grab it from my Reference thread in general, and extract it.
place your rom and gapps in the adb folder,
right click anywhere in the folder, not over a file,
select open command prompt here,
start adb sideload on your phone by swiping the bar to the right,
in the prompt, type adb devices, to ensure your phone is seen by adb,
if not, install both drivers from the Reference thread and try again,
after connection confirmation,
type, adb sideload name-of your-rom-here-with-no-spaces.zip (if your rom name has spaces, rename the file removing them first)
then enter
it will take a little bit, when finished, restart sideload on the phone, then repeat the process with your gapps, and any other files you need to flash.
when finished, reboot, and you should be all set.
Hi all,
I tried to back up my samsung galaxy ace and when accessing the playstore the device froze and upon a battery pull
started to get stuck on the samsung logo or a continual system reboot without ever making it into android. I tried a long battery pull, rebooted the system and wied the cache partition none of which worked.
I was hoping to get the text messages and contacts off the internal storage so these can be transferred to a new phone.
Since then I have downloaded the SDK kit for google and downloaded the ADB drivers and can access ADB from a command prompt window.
I am hoping to be able to use ADB to use the "pull" command to retrieve files from the internal storage but when using the ADB devices command the phone does not show up so doing anything with ADB is not an option.
When I put the phone in download mode windows recognised it with an exclamation mark. I downloaded Kies and then windows started associating it with a CDC driver (whatever that is) but I cannot force windows to see the ADB driver.
I have tried manually pointing it to the ADB driver stored within the SDK ...folders but it just won't see it.
Further, I downloaded Clockworkmod for the galaxy ace as I hoped that it would give me options to boot into nandroid and get the files that way. It said the upgrade of firmware worked but now unless I force download mode when starting up, the phone goes straight in to the reboot system now, apply update etc menu but then says"E:failed to mount /system (Invalid argument)" twice and that's it.
I do not have usb debug enabled.
So, help needed please all you kind people out there. How I make windows see the ADB drivers or get it to recognise the phone for ADB access or is there any other way I can get these files off, by installing CWM I've only played around with the boot software and not the actual OS so the data should still be there, am I right?
These texts messages are more than important , both they and the contacts are crucial.
This all happened when I was trying to back up the data and now I can't.
I don't need to spare the phone just the data, surely someone somewhere can get at it?
Thanks
mr_stupot said:
Hi all,
I tried to back up my samsung galaxy ace and when accessing the playstore the device froze and upon a battery pull
started to get stuck on the samsung logo or a continual system reboot without ever making it into android. I tried a long battery pull, rebooted the system and wied the cache partition none of which worked.
...
When I put the phone in download mode windows recognised it with an exclamation mark. I downloaded Kies and then windows started associating it with a CDC driver (whatever that is) but I cannot force windows to see the ADB driver.
I have tried manually pointing it to the ADB driver stored within the SDK ...folders but it just won't see it.
Click to expand...
Click to collapse
Sounds similar to what happened to me, although on my LG G4. The phone randomly froze and then from there only would bootloop the LG screen, never making it to the Verizon screen. It turned out that components came loose within the phone which caused the boot to fail, as it was a known G4 issue.
What happened with my phone is that my computer wouldn't recognize it as anything other than my processor, and I could only stay in Download mode for about 1 minute before power off. Recovery mode literally had no effect other than "power off".
Personally, I wasn't worried about my data, so I sent it off to be repaired, but while searching around I found this post (can't post links yet, sorry):
Code:
forum.xda-developers.com/att-g4/general/lg-g4-stuck-bootloop-rma-solution-t3279690/post67131904#post67131904
This may be a way to get the data off, BUT ONLY IF you are suffering from the same issue. I'm sorry to say, but it is probably NOT the same issue, but seeing how no one has responded yet I figured I'd through you a lifeline. It's a possibility.
Best of luck to you though, and sorry I couldn't really answer the question.
Previously, I had this phone rooted, and running CM12 with an open source gapps setup, with no problems. I also had TWRP installed, and an SD card with a copy of my ROM as I liked it, and my data.
Everything worked, and I was able to update my Android version and expand functionality quite a bit, which was useful while traveling abroad.
The other day however, when seconds before I had been using it as my hotspot, I tripped over the charging cord and dropped the phone quite hard on tile.
It broke into pieces, with the back coming off and the battery coming out.. The display is fine. I thought I killed it entirely, but I took the battery out and left it alone for half a day, and when I came home, I realized that it would:
1. Charge
2. Boot to recovery
3. Boot to download
This gave me some hope.
However, doing anything else would result in a bootloop.
I booted into recovery in preparation to re-flash my rom, and TWRP was not able to mount my SD card, and would not recognize my data there.
Additionally, when I tried to wipe everything but my SD card, TWRP failed to mount all partitions, as if something got corrupted.
When I tried to repair or change the file system type, this too failed. I cannot seem to get TWRP to recognize any storage. It says the phone is empty, with no internal, no external, and no OS.
Just a bunch of red "failed" lines every time I try to do something through the recovery.
I checked my SD card externally using an adapter on my mac, to make sure it was not corrupted. All my data is still there, including the backup of my ROM. However, since the phone will not recognize it, it's useless, and I can't find an Odin flashable .tar version of the CM12 ROM for this phone, plus when I tried to convert a copy to the correct file type, it failed to flash.
I tried to flash a copy of the stock rom (metroPCS version) to begin with, that I had saved on my computer.... which worked before when I messed up my initial flash. This time, It will flash successfully per Odin, but cause a bootloop.
Odin will still recognize my device... but adb from my mac terminal will not recognize it when I have the device connected or I would try to rebuild the file system that way.
I feel like I am going in circles and running out of options, or missing something..(possibly several things) but... I don't want to give up on this phone just yet, even if I had to demote it from daily driver use in the end ... any advice would be appreciated.... Thank you sooooo much!
Edited to add: I got ADB to recognize the device and ran a restore command, based on a file I had locally. This is what happened:
localhost:~ user$ adb restore ~/Downloads/cm-12-20150319-UNOFFICIAL-gardalte.zip
Now unlock your device and confirm the restore operation.
/sbin/sh: /sbin/bu: not found
Also adb remount resulted in a failed output.
Lastly, it appears abd only works in terms of recognizing my device when I am in recovery.
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"