Okay, so I rooted my wife's LG C800 (T-Mobile MyTouch Q), with the hopes of finding a decent custom ROM. No luck, went back to stock. Didn't unroot. OTA comes out today. Wife doesn't know any better, and tries the OTA update. Now can't get out of recovery. I've cleared Dalvic (although get an error message "E:unknown volume for path [/sd-ext]", it still says wipe successful), format system, format cache, factory resent and re=flash the stock ROM several times. Still will only boot to ClockworkMOD. I have tried manually flashing the boot.img. Same thing. I tried manually flashing system.img, but it says it's too big. Any ideas would be GREATLY appreciated.
Thanks,
Wulf
Stock Recovery
greowulf said:
Okay, so I rooted my wife's LG C800 (T-Mobile MyTouch Q), with the hopes of finding a decent custom ROM. No luck, went back to stock. Didn't unroot. OTA comes out today. Wife doesn't know any better, and tries the OTA update. Now can't get out of recovery. I've cleared Dalvic (although get an error message "E:unknown volume for path [/sd-ext]", it still says wipe successful), format system, format cache, factory resent and re=flash the stock ROM several times. Still will only boot to ClockworkMOD. I have tried manually flashing the boot.img. Same thing. I tried manually flashing system.img, but it says it's too big. Any ideas would be GREATLY appreciated.
Thanks,
Wulf
Click to expand...
Click to collapse
On a side note, any ideas how to go back to stock recovery on the LG C800?
Thanks in advance!
I have the exact same problem
Any help would be appreciated.
Thanks
Any luck yet Greowulf?
ng1and said:
Any luck yet Greowulf?
Click to expand...
Click to collapse
Nope, ended up having to replace it. Unlike my HTC Doubleshot, this LG C800 just doesn't have a robust dev community. I think I'll keep her on the stock recovery and ROM until we can afford a better phone. . .
Bummer
Guess I'll have to do the same thing. I'm going to try taking it to a store but I doubt they'll help since it's jailbroken. I'll update when I do.
Thanks for letting me know.
I have the same problem
Hi, i have the same problem, but when i flashed the original recovery that i downloaded from de clockwork mod recovery post my phone died, now when i turn it on it does the same thing (it always boot to recovery) as before but with the original recovery, when it tries to boot the original recovery it doessen´t do anything and restarts which starts the same process again (boot in recovey for 1 second and restarts), any idea to get my phone back???
Update on my problem
Hello i´ve manage to put my phone in S/W Upgrade mode but i try to use the LGMobile Support Tool to restore my phone to its original state, in this process it stops about twelve seconds in and tells me that an error ocurred and it cant continue with the process, i´ve tried fastboot keys to but in that mode but it boots directly into recovery mode and stays in a loop of reseting and going in to recovery mode (in this mode i can't do anything on my pc because it appears and disapears to fast), the only way i´ve managed to use pc tools is by putting it in S/W Upgrade, in my pc i can see a serial port, a modem and a Lg android phone, but in cmd using "adb device" nothing appears, any idea on what to do next?
mr arrieta said:
Hi, i have the same problem, but when i flashed the original recovery that i downloaded from de clockwork mod recovery post my phone died, now when i turn it on it does the same thing (it always boot to recovery) as before but with the original recovery, when it tries to boot the original recovery it doessen´t do anything and restarts which starts the same process again (boot in recovey for 1 second and restarts), any idea to get my phone back???
Click to expand...
Click to collapse
Ok, if you have this problem plss never restore to the original recovery before solving it, if you flash your original recovery you might end up worst, all you have to do in this case is restoring the backup you made when installing clockwork mod, if you are like me and never did one or erased it later on, i´ve been trying to see how to fix my phone, and the closest i am of making it work is flashing CyanogenMod through CWM then i enter fastboot mode and make it boot from the extracted boot image from the CyanogenMod .zip file, i dont have a permanent fix, but ill keep you posted.
Partial solution
Hello, i foud i very nasty solution but it works for now is the only way i know to fix Lg c800 bootloop, this was only tested with Cyanogen mod 9 latest nightly, to force always your phone to boot os and not the recovery i repaced the phone's recovery.img with the boot.img contained in the cyanogen mod .zip file, here's a step by step guide.
1. Download latest nightly Cyanogen mod 9 for lg c800 release .zip
2. Flash this image with the clockworkmod recovery
3. In recovery mode connect your phone to the pc and with adb and fastboot installed
4. Reboot your phone to fastboot mode typing: "adb reboot bootloader"
5. Once in fastboot (lg logo with black screen) type: "fastboot flash recovery boot.img", for this to work you must have your boot.img extracted from the cyanogen mod9 zip file in the same directory as your adb and fastboot .exe
6. Reboot your phone typing: "fastboot continue"
And when this is finished your phone boots drectly to your installed Cyanogen mod 9 firmware, there are some side effects to this fix, because it is no final, the side effects are:
1. Your phone does not have recovery now, if you boot it in recovery mode or normal mode it always boots to your Cyanogenmod 9 ROM, you can always boot your recovery manually from the pc in fastboot by typing "fastboot boot recovery.img", for this to work you must have your recovery.img extracted from the Clockwork recovery zip file in the same directory as your adb and fastboot .exe
2. This fix only works for custom roms, if you try this with a stock 2.3.6 o 2.3.4 Rom your phone wont boot and you will have to start over, it only worked for me with Cyanogen mod 9.
I hope you can take back to live your phones as i did, if you're stuck in bootloop and dont have clackwork mod installed into your device, you have to flash a custom kdz rom that contains clockwork recovery an then do what´s on the guide, i have a custom kdz to do this but have no place or time to upload it, as soon as i con i will post it.
---------- Post added at 04:59 PM ---------- Previous post was at 04:24 PM ----------
PLSSSS be aware that if you do this wrong (by using a stock rom instead of cyanogen mod 9) and dont have the .kdz that flashes clockwork recovery to your phone, you might end up worst than before, but in my experience i always had adb acces to the phone when using cyanogen mod 9, to restore your phone if something goes wrong and you have adb acces type:
"adb reboot bootloader"
"fastboot erase recovery"
"fastboot flash recovery recovery.img", for this to work you must have your recovery.img extracted from the Clockwork recovery zip file in the same directory as your adb and fastboot .exe
"fastboot continue"
and your are done, now you have cwm recovery installed in your phone and stuck in bootloop again.
Plss if you don't have adb acces flash this kdz image (this is pending, i'm uploading it but i think it will be available on tuesday), is a custom rom that mounts clockwork recovery and other usefull stuff to recover your phone in this method (this kdz wot fix your bootloop problems, only mounts clockworkmod recovery to your phone so you can follow the guide, flash roms and have a adb acces)
ng1and said:
Bummer
Guess I'll have to do the same thing. I'm going to try taking it to a store but I doubt they'll help since it's jailbroken. I'll update when I do.
Thanks for letting me know.
Click to expand...
Click to collapse
Don't take it in, call in. They'll walk you through trouble shooting and mail you a new one if it's still in warranty. LG will do the same if you're not with T-mobile, but you'll have to pay for shipping
Link
this is the link for the kdz image i made: https://www.dropbox.com/s/p4ozl5wwdtwsub0/V10V_00 mia CWM y Cianog.kdz, this one installs clockworkmod to your phone's recovery, flash it to follow the guide i posted before.
Has anyone found a full solution? I am stuck just like the first post, i can get to cwm recovery but it is stuck in a continuos loop back to recovery. I haven't tried mr arrieta still as i need a full solution to this. I have backup in my sdcard of the original recovery i took from flash boot, a copy of the stock rom that is rooted and the lastest Cyanogenmod 9.
I tried using a zip I found called exitrecovery.zip but it didn't work. Should i try to install the original recovery with the stock rom and try to do a factory reset with LG PC Suite software??
I would really appreciate some help here.
I have my father's MyTouch Q that was rooted and is now in a boot loop. It only stays active (as far as being connected by usb) for about 2-3 seconds so I don't have enough time to put it into fast boot or really do anything with it unless I can figure out how to keep it active longer. I have tried many of the possible fixes and yet I am still banging my head against this desk. I would appreciate any help on this matter.
BigDv said:
I would really appreciate some help here.
I have my father's MyTouch Q that was rooted and is now in a boot loop. It only stays active (as far as being connected by usb) for about 2-3 seconds so I don't have enough time to put it into fast boot or really do anything with it unless I can figure out how to keep it active longer. I have tried many of the possible fixes and yet I am still banging my head against this desk. I would appreciate any help on this matter.
Click to expand...
Click to collapse
To keep active longer you need to put you'r phone into S/W update mode by pressing E+volup+pwr, in this mode you can flash via KDZ updater the .kdz file i compiled and published, if you complete correctly this steps your phone should be booting into cwm recovery from there you have to flash the latest cm9 nightly and via fastboot replace your recovery with the boot.img contained in the cm9.img.
when you finish this process you should have a phone that has no recovery mode but always boot into the rom directly, that is how i've been using my phone till i have time to find a solution with recovery mode.
---------- Post added at 12:46 AM ---------- Previous post was at 12:37 AM ----------
Altaflux said:
Has anyone found a full solution? I am stuck just like the first post, i can get to cwm recovery but it is stuck in a continuos loop back to recovery. I haven't tried mr arrieta still as i need a full solution to this. I have backup in my sdcard of the original recovery i took from flash boot, a copy of the stock rom that is rooted and the lastest Cyanogenmod 9.
I tried using a zip I found called exitrecovery.zip but it didn't work. Should i try to install the original recovery with the stock rom and try to do a factory reset with LG PC Suite software??
Click to expand...
Click to collapse
Hello i've tried all solutions you can find on the internet and none seem to work, i restored original backups, tried zip files, etc... the probles is that if you flash the stock recovery you will end up worst because you will have to us the kdz programer to recover the CWM and your phone will be in a bootloop of 3 seconds in which you can do less.
for now there is no full solution, since i think i am the only one working on this and i don't have the time for this project, when i bricked my phone i needed a fast solution and that is what i have and posted.
my solution makes your phone to boot always into the OS partition so your phone will always work, but you will not have a recovery.
Update
Hello, i've learned a lot of stuff since last time, but i have no solution yet, i'm hoping some one will read this and help me get to a solution since i've read a lot and there are still lots of stuff i cant seem to make out (@chui101).
First i tried a couple of solutions i found online for fixing CWM recovery loop after ota, but one of them bricked my phone even worst, i ended up in a qualcom high speed conection with black screen and no GUI, i thought my phone was dead forever (i've felt that way a lot lately but it always seems to find the way to come back to life ), i managed to get my phone back to life with QPST and some files i got out a KDZ file, but i was still in the CWM recovery loop.
I continued my research and found out that it is mostlikely fault of the misc partition that stores data between phone modules, so i got my phone partition table and began looking in the original boot.img and recovery.img files to find any piece of information i could get my hands on, since this phone has very little info out there and tried to find any comand that would reset the ota update flag that began all this, in this process i bricked my phone fastboot mode and had to do a full brick and fix with QPST since KDZ didn't seemed to do the trick, here is what i got so far as partition table goes:
mmcblk0p1 ----->
mmcblk0p2 ----->
mmcblk0p3 ----->
mmcblk0p4 ----->
mmcblk0p5 ----->
mmcblk0p6 ----->
*mmcblk0p7 -----> boot
mmcblk0p8 ----->
mmcblk0p9 ----->
mmcblk0p10 ----->
mmcblk0p11 ----->
mmcblk0p12 ----->
mmcblk0p13 -----> rmt storage
mmcblk0p14 -----> rmt storage
*mmcblk0p15 -----> system
*mmcblk0p16 -----> data
*mmcblk0p17 -----> recovery
*mmcblk0p18 -----> cache
mmcblk0p19 -----> rmt storage
mmcblk0p20 -----> wifi pemission root
mmcblk0p21 -----> DivX cache
mmcblk0p22 ----->
mmcblk0p23 ----->
mmcblk0p24 ----->
*mmcblk1p1 -----> sd card
I cant seem to locate which one is the misc partition yet, my theory is that if i can identify this partition some one that has a working lg c800 Mytouch Q cand back up this partition for me as a misc.img and with it i could restore my phone to a correct working state, since i foud online a nandroid backup but it didn't fixed my loop.
Other Approach
Another option i thought is to mod an original boot.img to boot directly to the kernel img and trigger a new OTA from there with the unrooted phone and original recovery, but i cant seem to make this right, since i unpack the original boot.img and then without changing anything i repack it and only by doing that the newboot.img doesn't do anything it freezes on the LG logo of the fastboot mode.
I'm using boot kitchen.rar i found online which uses split_bootimg.pl to get out kernel and ramdisk from image, then 7Zip to extract ramdisk.gz and its content, then repacks it with mkbootfs.exe and with mkbootimg.exe, the command i'm using for making the boot image is:
"mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-new.gz -o newboot.img --base 0x00200000"
but ive tried with --cmdline option (using the comand line message it gives me when extracting, and my mkbootimg.exe does not recieve the --base comand), and tried in different order but newboot.img doese't work.
Any ideas, any developers, any mod? any something????
LG myTouch Q (C800) Stuck on LG Logo Fix Solution !
:good: :good::laugh:
mobiletek909 said:
:good: :good::laugh:
Click to expand...
Click to collapse
Will this make me lose root or relock the phone?
Related
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
liqdnitro said:
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
Click to expand...
Click to collapse
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Batesinc said:
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Click to expand...
Click to collapse
I Did A Lg Update Tool Fix Brought It Back To Life
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Yoyomah20 said:
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Click to expand...
Click to collapse
man the same thing happende to me, the only way i could partially recover my phone was flashing clockwork mod and from there install Cianogenmod 9, then in recovery mode conected to the pc via cable and typed:
"adb reboot bootloader"
once in Fastboot mode typed:
"fastboot boot boot.img"
where boot.img is the file contained in the cyanogenmod .zip file, doing this i managed to boot the rom and use my phone, the problem is that anytime it restarts it gets stuck in the boot loop again, and i have to repeat the process for it to boot again, i think is a bootloader problem since i have virtually done anything else, i think that the OTA update from tmobile changes something on the bootloader and it forces recovery/update boot always, and since the OTA never was completed it never got back to it's original state, its´s just my theory, i´m looking into it, but for now my phone works!.
Solution
I found a solution for the lg c800 bootloop, se my post: http://forum.xda-developers.com/showpost.php?p=39453347&postcount=10
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
choubeyaakash77 said:
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/oneplus-x/general/oos-2-2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
If you can enter in fastboot mode, flash the recovery from fastboot command. Flash blu_sparks recovery, it's better
seems you can still go to TWRP recovery? just flash the OOS 2.2.0 full ROM.
choubeyaakash77 said:
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
Obviously...
You told the phone to boot to TWRP by flashing it to 'Boot' and that's exactly what is happening.
Just reflash your ROM and you're good to go.
choubeyaakash77 said:
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
Click to expand...
Click to collapse
If you didn't know what you were doing, why ask before doing it?
You always have to flash the recovery .img from fastboot mode via adb. Not flashed by twrp.
Reference thread :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Maybe, just flash from adb the OLD recovery.
From this recovery, reinstall your Save.
Then install new recovery via ADB.
Or flash full ROM, then reflash, VIA ADB, the OLD recovery.
Then same as above. Restora + new recovery.
Boot your phone into fastboot mode, connect it to the PC, in adb directory, open cmd promote, type
fastboot flash recovery twrp. img
Click to expand...
Click to collapse
(replace twrp. img to the recovery img you downloaded, and put it under the adb directory). Or you can type
fastboot boot twrp.img
Click to expand...
Click to collapse
, the phone will then boot into the recovery you downloaded, where you can flash a new rom. DON'T flash recovery from recovery!
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
And if you want restore the backup on th sdcard, you might need change the storage location to sdcard in TWRP recovery,
Thanks all you guys. I'm back on with OOS 2.2.0. Had to download the complete ROM and flash it through TWRP.
I didn't wanted to download a whole almost 1 GB zip, so I tried to search for the original OxygenOS boot.img to flash it to boot. It might have worked if I hadn't completely wiped out my OS by wiping /system. Plus its almost impossibe to find that file online...
Anyway, had a nice experience screwing things up and getting back up better than before. Had fun. Learned stuff...so probably I'm not a newbie to rooting anymore.
Thanks guys for your support.
Here's the ROM I downloaded (for future reference) : https://www.androidfilehost.com/?fid=24389512218017971
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
FixFaier said:
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
Click to expand...
Click to collapse
fking hell.
this helped me a lot.
thx man :good:
Thank you so much. For now just gonna be content witht the stock rom.
Hi guys, after 10 hours of trying to get my P760 to life I finally, as a last resort, decided to open this threadh. Heres the deal, my friend gave me his P760 which was stuck at the boot logo, I firstly tried to fix it with LG mobile support tool but it got stuck at 15% after countless tries. Then I tried fixing it with Lg flash tool but it also gave me some errors "omap factory download fail lg p760". After that I couldnt access S/W mode anymore nor did the phone turn on, only black screen. When I connect it to my pc it just makes sounds of new device connected/disconnected. I tried this fastboot method http://forum.xda-developers.com/showthread.php?t=2292828 but couldnt make it work. Is the phone completely dead or is there anything more I can try? Any help is appreciated, thank you very much.
What was done to brick it in the first place?
Sent from my KYOCERA-C6745 using Tapatalk
I am not sure, my friend brought it to me and he didnt know the reason. Anyway I managed to get into fastboot on another computer and i tried to flash x loader and uboot with the bulit in options and i get the following error "FAILED (remote partition doesnt exist). What can I do next? Thank you for the reply.
EDIT I have tried to get the phone in S/W mode using this guide http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4 but I couldnt do it.
I am sure I have to flash something in fastboot so it would be great if someone could point me to exactly what. Thanks again.
EDIT 2 I tried to flash xloader and u boot from post #7 http://forum.xda-developers.com/showthread.php?t=2242444 and it gave me the remote partition error failed again. Is the phone "officially" dead?
My experience with this phone is that it is basically unbrickable, at least software wise, thanks to omap4boot. Fastboot is basically telling you the partition you specified doesn't exist. Check you are using the correct syntax. It should be fastboot flash u-boot u-boot.img and fastboot flash x-loader x-loader.img (I am assuming the files are named u-boot.img and x-loader.img).
Another possibility is that the partition table of the phone somehow got corrupted. In my opinion this is very unlikely, but it could happen if the phone is disconnected while flashing the GTP table with LGFlashTool. Let's hope that's not the case.
Good luck.
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Maha23 said:
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Click to expand...
Click to collapse
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
EdwinMoq said:
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
Click to expand...
Click to collapse
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Maha23 said:
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Click to expand...
Click to collapse
I'm seeing you using lelus method to fastboot...
1) Be sure you are in fastboot whith this command: fastboot devices
2) if the l9 is still in lg logo, just flash a recovery img into boot and recovery partition:
a) fastboot flash boot recovery.img
b) fastboot flash recovery recovery.img3)reboot the device, it must enter in recovery mode by force.
4) once in recovery just flash a custom rom as you wish
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
lecorbusier said:
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
Click to expand...
Click to collapse
Thanks for the reply. How do I perform the force hard reset? Yes, I couldnt get fastboot to work on win 10, on win 7 it works flawlessly.
Sent from my LG-D855 using XDA-Developers mobile app
Hello,
I have exactly the same problem with my p760, fastboot works so far but remote partition error and the phone stays always completely black.
Is there someone who has a new idea to fix it?
Hey,
I found this: http://massimoronca.it/2016/03/17/fastboot-failed-remote-partition-does-not-exist.html
but i dont really understand it, can someone help me?
Maha23 said:
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
readme again... try to flash a recovery.img into the boot partition
fastboot flash boot recovery.img
and then reboot... this foce the l9 to enter in recovery and then you can fotmat partitions in wipe options
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
Elsewhere you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
Hard reset is 10s power.
Such a swap of recovery and kernel could have happened after unbricking the phone, when the key combo for fastboot produces the LG recovery. That's why I flash stock twice, then it's right again & ready to root, install TWRP etc.
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Maha23 said:
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Click to expand...
Click to collapse
you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
puntoazul said:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Srsly?
recovery partition image on boot?
Probably true. That would explain the strange behaviour of the key combos during boot, after unbricking the phone for the first time. The recovery has replaced the kernel, but the phone can still boot. Strange. Fastboot is unavailable, and the key combo for the recovery shows the "dead droid" and performs a factory reset.
Groszexxx said:
Srsly?
recovery partition image on boot?
Click to expand...
Click to collapse
Yes... is an effective method to boot by forced on TWRP or other recovery and then proceed to format all partitions and flash any rom consecutively. After flashing any rom the boot partition is rewrited by the boot.img of the rom.
I did this before on my own L9 for repair and other friends devices. Is totally safe
By the way, I'm not in warn
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/