Related
Hello Guyzzz!!!!!
A Great Newzz for ALL!!!!! First the recovery was not compiled by me!
But NOW I am BACK with a FULLY WORKING RECOVERY AND FULLY COMPILED BY ME :good:
We have now a FULLY WORKING CLOCKWORKMOD RECOVERY v5.0.2.8.
The CLOCKWORKMOD RECOVERY is TESTED on :-
1. LG OPTIMUS 3D MAX P725
2. LG OPTIMUS 3D MAX P720H
I HELD NO RESPONSIBILITIES FOR BRICKED PHONES. YOU MAY TRY ON P720 BUT AT YOUR OWN RISK.
Credit Goes to :-
1. I, Me and Myself ( For taking the initiative,compiling testing and removing all bugs )
2.. Cynogenmod for the SOURCES.
3. P720H tester ZOOM.
According to me, the CWM RECOVERY is fully working.
HERE ARE THE STEPS TO INSTALL THE CWM RECOVERY :-
Download the CWM RECOVeRY FINAL.zip from the link given below :
http://www.mediafire.com/?p59d9ppjlhkcp67
Copy the cwm5.0.2.8.img on the ROOT OF THE SDCARD not the External SDCARD ( Root of SDCARD means not in any folder )
The BIGGEST REQUIREMENT IS YOUR OPTIMUS 3D MAX should be ROOTED!!!
Now download ANY TERMINAL EMULATOR from the GOOGLE PLAY!!!!!
You can try this :-
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
And install it.
Type the following commands in TERMINAL EMULATOR :-
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/cwm5.0.2.8.img of=/dev/block/mmcblk0p6 bs=4096
Once complete.
Turn off your phone.
1st hold 3d key then volume down button and at last power button.
Keep holding till the LG LOGO appears and leave when it appears.
You will enter the CWM Recovery
Proof of the Recovery :-
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
lordasphyxia said:
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
Click to expand...
Click to collapse
Happy to help you.
"HITTING THANKS WILL ENCOURAGE ME MORE":good:
Eklovya said:
IT TOOK MORE TIME TO DEVELOP THIS RECOVERY THAN THE TIME YOU WILL TAKE TO JUST " HIT THANKS".
Click to expand...
Click to collapse
dude you are not developed this recovery, it's created by me, you only unpacked my recovery using kitchen , that not call develop
Where did i mentioned that I DEVELOPED???
I clear mentioned that you compiled and i removed all bugs...
Sent from my LG-P725 using xda premium
Thread for this exists from original dev
http://forum.xda-developers.com/showthread.php?t=1889468
Thread closed
Edit: Thread reopened for a newly compiled version
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
TommyX235 said:
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
Click to expand...
Click to collapse
Try doing a factory reset.!!!
Sent from my LG-P725 using xda premium
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
TommyX235 said:
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
Click to expand...
Click to collapse
Install LG SUPPORT TOOL IN PC.
KEEP YOUR PHONE IN DOWNLOAD MODE.
CONNECT TO PC.
OPEN LG SUPPORT TOOL.
IN TOOLS SELECT RECOVER PHONE.
INPUT YOUR IMEI.
AND WAIT FOR THE RECOVEY PROCESS TO FINISH.
ALL WILL BE DONE SAFELY AND YOU WILL GET THE PHONE WORKING
Sent from my LG-P725 using xda premium
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
TommyX235 said:
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
Click to expand...
Click to collapse
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
TommyX235 said:
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
Click to expand...
Click to collapse
Can you come on chat? So that i can help you!!
Sent from my LG-P725 using xda premium
can this tutorial work on ICS su870?
joseph168 said:
can this tutorial work on ICS su870?
Click to expand...
Click to collapse
Nop this will not work. As the bootloader is locked for su870
Sent from my LG-P725 using xda premium
LG P725 CWM Problem
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Andrelius1 said:
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Click to expand...
Click to collapse
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
CWM problem
Eklovya said:
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
Click to expand...
Click to collapse
Thanks a lot! Its strange that in any instruction not says this way of use CWM, i read a lot differents cwm instructions, but the always the same - use power off key ot use 3d button.
Who don`t how to use CWM menu :
"properties button" - up
"home button" - down
"back button" - back
"search button" - ENTER
Cannot select options in cwm
Hi Eklovya,
Brilliant job done!!
I have successfully rooted and installed CWM following your method.
However, when i go boot to CWM, I can use the volume buttons to highlight the options (I wanted to backup), but I am not able to select the options. i tried the power button and the 3D button, no go. What do i do?
I just exchanged my P920 and got myself this P725 today!!!
schubeir
EDIT: my bad!!! found the solution in the post just above!!!!
schubeir
(possibly long post , I will try to make a post at least a little fun to read).
Guys, I humbly come before you, kneeling and desperate, trying to solve my problem .
I've serarched XDA and a lot (!!) of others forums and comunities to revive my P720H (LG optimus 3D Max in Brazil).
I am not a complete noob in custom firmwares for Android, but this time, the LG phone gave me a hell of a headache (and almost a divorce, for the 3 days going too late to bed, trying to solve it).
I will explain what happened and what I've already tried to do and the results.
Causes:
I've tried to install ClockworkMod in my P720H because it still was in Android 2.3.6 (I think).
I've successfully rooted the phone using this thread: http://forum.xda-developers.com/showthread.php?t=1886057 with the SuperSU app on GooglePlay.
When I asked CWM app to reboot in recovery mode (to wipe things and install the .zip file on the sdcard root) things got bad.
My phone could not get passed the LG logo anymore.
So far we have a cause: CWM app did something to the phone. I am not able to boot the recovery menu nor to pass the LG logo on the screen.
Over the communities we may find that it's a common issue.
It is important to say that I am able to enter the 'S/W updating' state. When I connect the phone to the computer, holding VOL+ and placing the battery, I got the S/W screen.
What can I do? In several posts (even here in xda) we may find 3 or 4 different solutions to restore the phone. I think I've already tried everything, but I am sure that the steps became fuzzy in my read and I mixed the solutions in the end.
Drivers:
- I have already the drivers installed: When I connect the phone (with or without battery and with or without vol+ pressed) my Device Manager recognizes everything. I don't have any component marked as 'unknown device' or with exclamations points or anything. This is a good thing, I guess. I had to install more than one thing to solve every driver problem. I don't remember exactly, but I think that the LGDriver-something and the omap4430 something too.
Solutions:
- I have tried the LG Support Tool and so far it appears to be the closest to a solution that I've reached. With the phone connected (in S/W mode or no), I insert the IMEI and the software recognizes the model and starts downloading something (500mb approx.). But after decompressing, during the installation phase, it gets stuck at 4%. I waited for more than 20min and still got nothing better than 4%. It appears to be a common issue too.
- The LG_FlashTool (version 1.2) does not work either. In fact, it does not even recognizes the phone. I've changed the COMport to 41 (according to some guide) on Windows Device Manager and chose the port 1 on LGFlashTool. Even after selecting the kdz, bin and fls files, the software does not connect to the phone. I don't have a screenshot here, but I've seen here in xda that the software displays the model of the phone on the top and a READY message on port 1. Mine does not do it.
- KKDZ_FW_UPD_EN: I've tried this one but it does not even start working. The interface is not that good, so I don't know where I may be failing. I need to 'read phone information' or not? What do I have to chose on each combobox? How to proceed?
And why the hell is there so much .exe on this thing? Do I have to run a apache server to do something?!
- OMAP4BOOT: This one connects to the phone and works, I think. But I don't know its purpose. It's just to place the phone on 'S/W updating' mode? If so, it's useless, because I can enter it easily. If no, maybe I am missing something. Either way, I don't have a version for the P720H. If I remeber correctly, it proposes P999, P760, P870, ... I choose P760 to test it and it works (apparently, again).
- SmartFlashTool: I don't remember if I have already tried this one. As I said, it was too much already.
- NVFlash: I've found it only to G2X, so I didn't know if I should try forcing it to my model. I can give it a try if you help me.
Other softwares and downloads:
KDZ:
- V10B_00 and V1A_00: found today and downloaded for my model and country (will try to extract things and use it later).
- LG_P725_V10F_00: I was using this one until yesterday, because I didn't have the one to P720H
- LGP700AT-01-V10d-232-03-SEP-11-2012+0.dz : Found in an indian repository of some kind of LG data leak. Apparently is useless. DZextract gave me nothing.
DLL: LGP720_20120330_LGFLASHv1377: Needed in some of the softwares above (LG FLashTool? I don't remeber).
BIN and FLS: LGP725_LG_P725_V10F_00_AP.bin and LGP725_LG_P725_V10F_00_CP.fls, extracted from LG_P725_V10F_00.kdz. I don't know, but I should try extracting these from the V10A_00, because apparently is the correct one for my model/country (I am not in my house right now).
Well... :crying:
tl;dr version:
I am facing a LG logo boot loop in P720H. I've tried to reboot CWM in recovery mode but it didn't work. I've tried several approaches but I don't even know what is the point of each one. I found that this is the best topic to use, because is one of the fews that covers the P720H.
I have all those softwares and almost 5gb of downloaded material (kdz, img, bin, exe, ...) but I don't know what I am supposed to use.
In the end, I want my P720H in android 4.x if possible. If not, I just want the crap 2.3.6 again. :crying:
Can you help me? I am not a total noob in custom firmwares and roms, and I am willing to pass all the information that I can :fingers-crossed:
Hello everyone,
I have a stable (but not perfect) CWM Recovery for Huawei U8730 (T-Mobile MyTouch Q by Huawei), no random reboot at all and combo key to boot into recovery.
It might work on Huawei U8680 (Huawei MyTouch).
download link : http://www.mediafire.com/download/5t1odtgo5vwt12p/recovery.img
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power"
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
Thanks to mattlgroff for his base and Tomm13b for his help to debug the recovery.
Now it's time to unbrick some device and start to build custom rom
PS : backup option only save system
new version available but still have system mounted and can't be unmounted, wipe work
If someone can take a look,go go
magikstar said:
Hello everyone,
I have a stable and fonctionnal CWM Recovery for Huawei U8730 (T-Mobile MyTouch Q by Huawei), no random reboot at all and combo key to boot into recovery.
It might work on Huawei U8680 (Huawei MyTouch).
download link : http://www.mediafire.com/download/6oko0f0ar8u29d8/recovery.img
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power"
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
Thanks to mattlgroff for his base and Tomm13b for his help to debug the recovery.
Now it's time to unbrick some device and start to build custom rom
Click to expand...
Click to collapse
This is great. I will try it today. If someone with u8680 will post his image folder i will apriciet (sorry for my english)
Sent from my LG-P700 using xda premium
Crazygrouzin said:
This is great. I will try it today. If someone with u8680 will post his image folder i will apriciet (sorry for my english)
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
you can try mine https://app.box.com/s/nb4w8g32ygnxnykvkqv7
will try to provide you flashable rom as possible i can
magikstar said:
you can try mine https://app.box.com/s/nb4w8g32ygnxnykvkqv7
will try to provide you flashable rom as possible i can
Click to expand...
Click to collapse
I dont have rom in my phone. Why they arent realesing the last firmware? Such a stupid company
Sent from my LG-P700 using xda premium
---------- Post added at 10:08 PM ---------- Previous post was at 09:57 PM ----------
Crazygrouzin said:
I dont have rom in my phone. Why they arent realesing the last firmware? Such a stupid company
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
I see u are good in developing. U can see inside the firmware that u post. Maybe u can change t_mobiles codes.
Sent from my LG-P700 using xda premium
Crazygrouzin said:
This is great. I will try it today. If someone with u8680 will post his image folder i will apriciet (sorry for my english)
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
try this:
use my image folder
replace boot.img by this one http://www.mediafire.com/download/tdun853avx6ttmv/boot.img
replace recovery.img by the one of cwm
download the rom (it's a rom for u8730 but might work on u8680, it's just to unbrick your device) http://www.mediafire.com/download/12d850ze9sdzb6j/hwu8730_signed.zip (deleted)
flash the rom with full wipe
and tell me if it works
Crazygrouzin said:
I dont have rom in my phone. Why they arent realesing the last firmware? Such a stupid company
Sent from my LG-P700 using xda premium
---------- Post added at 10:08 PM ---------- Previous post was at 09:57 PM ----------
I see u are good in developing. U can see inside the firmware that u post. Maybe u can change t_mobiles codes.
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
i'm not a dev but i try to help
magikstar said:
try this:
use my image folder
replace boot.img by this one http://www.mediafire.com/download/tdun853avx6ttmv/boot.img
replace recovery.img by the one of cwm
download the rom (it's a rom for u8730 but might work on u8680, it's just to unbrick your device) http://www.mediafire.com/download/12d850ze9sdzb6j/hwu8730_signed.zip
flash the rom with full wipe
and tell me if it works
i'm not a dev but i try to help
Click to expand...
Click to collapse
Sadly i cant get in cwm whatever i do. Damn....
Crazygrouzin said:
Sadly i cant get in cwm whatever i do. Damn....
Click to expand...
Click to collapse
volume up + power don't work on your device ?
magikstar said:
volume up + power don't work on your device ?
Click to expand...
Click to collapse
Nope, sadly no. Still blue screen after huawei logo. Probably i need u8680 image folder. Not u8730
Help moving image file.
magikstar said:
Hello everyone,
I have a stable CWM Recovery for Huawei U8730 (T-Mobile MyTouch Q by Huawei), no random reboot at all and combo key to boot into recovery.
It might work on Huawei U8680 (Huawei MyTouch).
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power"
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
Thanks to mattlgroff for his base and Tomm13b for his help to debug the recovery.
Now it's time to unbrick some device and start to build custom rom
PS : backup option only save system
Click to expand...
Click to collapse
Pardon me for sounding like an idiot, but how do I put the new recovery in that folder? Do I have to use adb or should I have some drive appear on my computer when I plug the phone in via usb? Note that I'm running Windows 7 64 bit and I already have my U8730 rooted. I'm not sure if that makes a difference or not. Thanks for the help.
---------- Post added at 12:22 PM ---------- Previous post was at 12:16 PM ----------
I'm using root browser after booting my device normally. I have found the folder and recovery.img. can I simply replace it by copy and paste since I already have my device rooted?
Viper_Prime said:
Pardon me for sounding like an idiot, but how do I put the new recovery in that folder? Do I have to use adb or should I have some drive appear on my computer when I plug the phone in via usb? Note that I'm running Windows 7 64 bit and I already have my U8730 rooted. I'm not sure if that makes a difference or not. Thanks for the help.
---------- Post added at 12:22 PM ---------- Previous post was at 12:16 PM ----------
I'm using root browser after booting my device normally. I have found the folder and recovery.img. can I simply replace it by copy and paste since I already have my device rooted?
Click to expand...
Click to collapse
download link : http://www.mediafire.com/download/6oko0f0ar8u29d8/recovery.img
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power" and connect your device to your computer with usb cable
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
magikstar said:
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power" and connect your device to your computer with usb cable
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
Click to expand...
Click to collapse
I have the file and such. However, once I put it into pink screen mode, I don't know how to put the recovery.img into the image folder.
Viper_Prime said:
I have the file and such. However, once I put it into pink screen mode, I don't know how to put the recovery.img into the image folder.
Click to expand...
Click to collapse
copy / paste the file recovery.img
magikstar said:
copy / paste the file recovery.img
Click to expand...
Click to collapse
I believe I've found the issue. When I plug my phone into the computer it lists as an unknown device under usb devices in device manager. I cannot get the drivers to work, thus preventing my computer from accessing the phone. Do you know where I can get the correct drivers.
---------- Post added at 01:17 PM ---------- Previous post was at 01:01 PM ----------
I've found the drivers from Huawei. I installedthem, even rebooted my computer, yet the phone still appears as an "unknown device" any suggestions? Also, if the recovery becomes damaged when I update it, will the phone be able to boot normally without a recovery? If so, I have a workaround method to change the recovery without using my computer at all.
---------- Post added at 01:52 PM ---------- Previous post was at 01:17 PM ----------
Crazygrouzin said:
Sadly i cant get in cwm whatever i do. Damn....
Click to expand...
Click to collapse
Remove the battery, then try again.
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
magikstar said:
copy / paste the file recovery.img
Click to expand...
Click to collapse
I did this within the Android OS using root browser. I still get the pink screen when I boot into recovery. Is that supposed to happen or did it not work properly?
---------- Post added at 02:09 PM ---------- Previous post was at 01:56 PM ----------
magikstar said:
Hello everyone,
I have a stable CWM Recovery for Huawei U8730 (T-Mobile MyTouch Q by Huawei), no random reboot at all and combo key to boot into recovery.
It might work on Huawei U8680 (Huawei MyTouch).
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power" and connect your device to your computer with usb cable
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
Thanks to mattlgroff for his base and Tomm13b for his help to debug the recovery.
Now it's time to unbrick some device and start to build custom rom
PS : backup option only save system
Click to expand...
Click to collapse
Also, Is this ClockworkMod 2.x or 3.x?
Viper_Prime said:
I believe I've found the issue. When I plug my phone into the computer it lists as an unknown device under usb devices in device manager. I cannot get the drivers to work, thus preventing my computer from accessing the phone. Do you know where I can get the correct drivers.
Click to expand...
Click to collapse
for the driver, you can get it http://sigmakey.com/nfs/content/6104/file/Huawei_U8680_U8730_U8800_U8860.zip
if you can't copy/paste in pink screen mode use root explorer to replace recovery.img
I hope you guys don't mind a quick question!
Recently, I rooted my 8730. Through the use of titanium backup, I got rid of the Genius Search. I restored it, rebooted the phone and now I'm stuck in a boot loop, where the phone boots up, gets right up to the little android guy flying upwards, then restarts.
First, I tried booting through the use of the power button + volume up, but even though I factory reset my phone, it'd still be stuck on the loop. I tried going the download route, replacing the image and using the CWM recovery in order to factory reset my phone, even going as far as replacing the whole image folder.
Is there anything that I can do?
Thanks a bunch for the patience and help!
Skooty said:
I hope you guys don't mind a quick question!
Recently, I rooted my 8730. Through the use of titanium backup, I got rid of the Genius Search. I restored it, rebooted the phone and now I'm stuck in a boot loop, where the phone boots up, gets right up to the little android guy flying upwards, then restarts.
First, I tried booting through the use of the power button + volume up, but even though I factory reset my phone, it'd still be stuck on the loop. I tried going the download route, replacing the image and using the CWM recovery in order to factory reset my phone, even going as far as replacing the whole image folder.
Is there anything that I can do?
Thanks a bunch for the patience and help!
Click to expand...
Click to collapse
try this https://rapidshare.com/#!download|1...|0|1|referer-CF9A4B09B03719BE92F1BA187D726313
Crazygrouzin said:
try this
Click to expand...
Click to collapse
So I take this, put it in the root of the SD card, access CWM and choose "Apply update from .zip"? When I do, it says "Finding update package, Opening update package, Installing update, Installation aborted"
Is there anything I can do to get around the abortion?
Also, if I try power + volume up/down to go straight to the software upgrade, it unpacks it fine, but right as it gets to the installation part it fails as well.
Thank you so much for the link, by the way!
Huh, maybe it's because while rooted, I uninstalled a handful of bloatware, like twitter/amazon mp3/genius search and a handful of other things. I backed them up, but unfortunately that doesn't count for much anymore!
Skooty said:
So I take this, put it in the root of the SD card, access CWM and choose "Apply update from .zip"? When I do, it says "Finding update package, Opening update package, Installing update, Installation aborted"
Is there anything I can do to get around the abortion?
Also, if I try power + volume up/down to go straight to the software upgrade, it unpacks it fine, but right as it gets to the installation part it fails as well.
Thank you so much for the link, by the way!
Huh, maybe it's because while rooted, I uninstalled a handful of bloatware, like twitter/amazon mp3/genius search and a handful of other things. I backed them up, but unfortunately that doesn't count for much anymore!
Click to expand...
Click to collapse
Just reporting back here!
I ended up fixing it by using a firmware upgrade 2.3. I took out my SD card, put it into a USB adapter, downloaded the 2.3 firmware (I can't post links, please feel free to send me a message for the link),put the dload folder for that firmware to the root of the SD card, held volume up/down + power button and forced an upgrade.
For those trying to fix the u8730 like me, there's a very specific firmware for it, it wasn't even in the manufacturer site. So again, please feel free to send me a message for it! In case I don't respond, in rapidshare, the title of the firmware is:
.
HUAWEI_U8730_firmare(U8730_Android_2.3_V100R001C85B845_America_TMO_05010TQM).rar
Has anyone figured out how to delete the bloat that's in the /cust dir
Sent from my T-Mobile myTouch using xda app-developers app
magikstar said:
Hello everyone,
I have a stable CWM Recovery for Huawei U8730 (T-Mobile MyTouch Q by Huawei), no random reboot at all and combo key to boot into recovery.
It might work on Huawei U8680 (Huawei MyTouch).
download link : http://www.mediafire.com/download/6oko0f0ar8u29d8/recovery.img
to install it, boot your device into download mode (pink screen) by pressing "volume up and down + power" and connect your device to your computer with usb cable
put the recovery.img downloaded before in your image folder to replace your original recovery.img
pull out the battery and replace it
boot your device by pressing "volume up + power" and you must be in recovery mode.
navigate : volume keys
validate : photo key
return : power key
Thanks to mattlgroff for his base and Tomm13b for his help to debug the recovery.
Now it's time to unbrick some device and start to build custom rom
PS : backup option only save system
Click to expand...
Click to collapse
thanks bro ,it works like magic :good:
I replaced build.prop and restarted. Then black screen and led lightning from color to color. I did factory hard reset to...
Something to do with it?maybe with a pc?
Thx!
Have your tried the methods described in this thread? http://forum.xda-developers.com/showthread.php?t=2799647
LG G3 Verizon Stuck on splash screen
sic0048 said:
Have your tried the methods described in this thread? http://forum.xda-developers.com/showthread.php?t=2799647
Click to expand...
Click to collapse
Can this work for the Verizon version VS985?
Im having the same Problem, I tried changing the Speaker volume levels with Root Explorer and now my phone will not boot from
the Verizon splash screen.
Any help would be great thanks.
This might be your only option... Without a proper build prop I believe the lg flash tool won't recognize the phone as any varient of the G3. Youre only choice might be to flash tot file thought fastboot itself. Only way to get to fastboot is as described in this thread
http://forum.xda-developers.com/showthread.php?p=54270708
Make sure to read up on this though. I'm not familiar with how lg doesn't allow booting into fastboot easily.
Sent from my LG-D850 using XDA Premium 4 mobile app
Ghost401 said:
Can this work for the Verizon version VS985?
Im having the same Problem, I tried changing the Speaker volume levels with Root Explorer and now my phone will not boot from
the Verizon splash screen.
Any help would be great thanks.
Click to expand...
Click to collapse
pull your battery... wait 15 seconds.... put it back in.
hold power button and down key at the same time until you see the lg splash screen, then let go for a second, and immediately hold the same two back bezel keys until you see "factory reset"... your phone will work afterwords but will be back to square one... its a shame, but its got to be done if you don't have a custom recovery.
Its also Possible to make an update.zip with just the build.prop in it. Copy it to sdk/platform-tools and then use adb to sideload the zip to replace the build.prop and fix your misinformed tinkering... if youre on the stock recovery you would probably need a signature on the zip for it to flash, which is troublesome.
what model is your G3?
if usb debugging is not enabled and your pc is not authorized... you are buggered (excuse the pun)
B4rnzEE said:
pull your battery... wait 15 seconds.... put it back in.
hold power button and down key at the same time until you see the lg splash screen, then let go for a second, and immediately hold the same two back bezel keys until you see "factory reset"... your phone will work afterwords but will be back to square one... its a shame, but its got to be done if you don't have a custom recovery.
Its also Possible to make an update.zip with just the build.prop in it. Copy it to sdk/platform-tools and then use adb to sideload the zip to replace the build.prop and fix your misinformed tinkering... if youre on the stock recovery you would probably need a signature on the zip for it to flash, which is troublesome.
what model is your G3?
if usb debugging is not enabled and your pc is not authorized... you are buggered (excuse the pun)
Click to expand...
Click to collapse
Thanks a lot bro,I have the Verizon VS985,
I do not mind starting from scratch as long as i can get my phone back up and running lol i will try the factory restore method. Hope this works.
:fingers-crossed:
---------- Post added at 03:13 PM ---------- Previous post was at 02:45 PM ----------
B4rnzEE said:
pull your battery... wait 15 seconds.... put it back in.
hold power button and down key at the same time until you see the lg splash screen, then let go for a second, and immediately hold the same two back bezel keys until you see "factory reset"... your phone will work afterwords but will be back to square one... its a shame, but its got to be done if you don't have a custom recovery.
Its also Possible to make an update.zip with just the build.prop in it. Copy it to sdk/platform-tools and then use adb to sideload the zip to replace the build.prop and fix your misinformed tinkering... if youre on the stock recovery you would probably need a signature on the zip for it to flash, which is troublesome.
what model is your G3?
if usb debugging is not enabled and your pc is not authorized... you are buggered (excuse the pun)
Click to expand...
Click to collapse
Thanks bro but that Did not work, The only option was turn off, safe mode, reset Factory Data, and power off.
Ghost401 said:
Thanks a lot bro,I have the Verizon VS985,
I do not mind starting from scratch as long as i can get my phone back up and running lol i will try the factory restore method. Hope this works.
:fingers-crossed:
---------- Post added at 03:13 PM ---------- Previous post was at 02:45 PM ----------
Thanks bro but that Did not work, The only option was turn off, safe mode, reset Factory Data, and power off.
Click to expand...
Click to collapse
Reset factory data
B4rnzEE said:
Reset factory data
Click to expand...
Click to collapse
I did and all it does is reboots and gets stuck at the Verizon splash screen..
Ghost401 said:
I did and all it does is reboots and gets stuck at the Verizon splash screen..
Click to expand...
Click to collapse
1) go to download mode
2) install this and download the correct .kdz file for your phone
-Modelnumber is ...
-serial number is your imei number
- wait until the download is done
3) run the lgflashtool2014.exe from this zip
-Select type= cdma
-phone mode= Diag
-reset time=33000
-Should be like this when You run it
-select kdz file= is where you need to find the kdz file you just downloaded(step 1)
-then press cse flash
-in the now pop-up window select start
-select your language
-ignore error (cannot connect to lg server)
-check progress on phone up to 100% then boots in recovery installs and restarts
-wait untill it goes to the welcom screen then you can unplug
-now the most inportant step Like my post
to enter download mode do this:
--You must switch off the device to start the process.
--Then press and hold the “Volume Up” and connect the USB cable from phone to PC.
--Use the original USB cable. Because, other device’s cable may not be detected in the Computer. So, only we recommend it to use the original-- one that you got it when you bought the phone.
--Wait for the driver installation on PC.
--Then you will get the download mode screen in your phone.
--That’s it.
suljo94 said:
I don't have the links to the tread where I got these from but lets just hope I don't get banned.
1) go to download mode
2) install this and download the correct .kdz file for your phone
-Modelnumber is ...
-serial number is your imei number
- wait until the download is done
3) run the lgflashtool2014.exe from this zip
-Select type= cdma
-phone mode= Diag
-reset time=33000
-Should be like this when You run it
-select kdz file= is where you need to find the kdz file you just downloaded(step 1)
-then press cse flash
-in the now pop-up window select start
-select your language
-ignore error (cannot connect to lg server)
-check progress on phone up to 100% then boots in recovery installs and restarts
-wait untill it goes to the welcom screen then you can unplug
-now the most inportant step Like my post
to enter download mode do this:
--You must switch off the device to start the process.
--Then press and hold the “Volume Up” and connect the USB cable from phone to PC.
--Use the original USB cable. Because, other device’s cable may not be detected in the Computer. So, only we recommend it to use the original-- one that you got it when you bought the phone.
--Wait for the driver installation on PC.
--Then you will get the download mode screen in your phone.
--That’s it.
Click to expand...
Click to collapse
Im Sorry but im an idiot man, I open the tool but there is no option to download anything.
I see a section for Version and open kdz. but not to DL anything, sucks! lol
Ghost401 said:
Im Sorry but im an idiot man, I open the tool but there is no option to download anything.
I see a section for Version and open kdz. but not to DL anything, sucks! lol
Click to expand...
Click to collapse
so typing in
VS985
(your imei)
pressing save doesn't work
suljo94 said:
so typing in
VS985
(your imei)
pressing save doesn't work
Click to expand...
Click to collapse
Thank you For your time and help bro, I was able to restore the firmware through a different tool and used the DLL + TOT files.
so far so good, setting now,
I'll make sure I flash a custom Recovery this time. lol
Ghost401 said:
Thank you For your time and help bro, I was able to restore the firmware through a different tool and used the DLL + TOT files.
so far so good, setting now,
I'll make sure I flash a custom Recovery this time. lol
Click to expand...
Click to collapse
you cant flash a recovery (bootloader is locked)
try rooting (IOroot)
then install this kind of recovery it doesn't replace you recovery but you can flash and backup(tru the app
suljo94 said:
you cant flash a recovery (bootloader is locked)
try rooting (IOroot)
then install kind of recovery it doesn't replace you recovery but you can flash and backup(tru the app
Click to expand...
Click to collapse
I suggest you remove that link asap.
Sent from G3
Tarzan- said:
I suggest you remove that link asap.
Sent from G3
Click to expand...
Click to collapse
done but why ?
suljo94 said:
done but why ?
Click to expand...
Click to collapse
I think you put the wrong link there because one of the files in your folder was a cracked apk, thought to give you a heads up
Tarzan- said:
I think you put the wrong link there because one of the files in your folder was a cracked apk, thought to give you a heads up
Click to expand...
Click to collapse
okee here is a fixed link
it is an app that boots into a cmw-like recovery
Bro,you saved my phone.Thank you so much.
JB sediKERNEL for the LG F3Q (codenames: FX3Q, D520)
This is the JB stock Kernel build from the LG source code.
It is modified to be able to boot on a unlocked bootloader (loki) and may contain other features in the near future.
Current features (always for the latest version):
Same as stock but build from the sources
Compatible with the locked bootloader (means loki'ed)
XATTR enabled
SELinux enabled
dmesg will provide human readable timestamps (too)
KEXEC patches available (but not applied(anymore))
Will ignore crappy LG bootloader args
Will not do a AUTOMATIC HIDDEN factory reset when kernel panics occur
Will not enforce LG signed image anymore
AROMA flashing ZIP file available! This will flash the sediKERNEL into the right place (boot partition of course ) and wipe dalvik cache for you.
With this no "adb shell + dd" etc are needed anymore. Just flash the ZIP in twrp (read the instructions at the bottom of this post).
Take a preview look at the attached images (see bottom of this post!) of the installer process - as you can see this is really easy and straight forward, isn't it?
magic key feature for booting into recovery instead of normal boot! This superseedes all the problems regarding how to reach the recovery mode when the system is damaged!!
Usage instructions:
Power on the device
when you see the LG logo the first time do NOTHING!!
When the screen goes black THEN press Volume UP + Volume DOWN. Both the same time and hold them pressed.
Release the buttons when the screen goes black again
Wait. You will see the LG logo a third time and then you will see the recovery screen!
If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.
No hacks anymore, no special installation instructions to workaround things, not breaking or damaging data or anything. Just using those keys and be happy!
Known issues (always for the latest version):
High (always for the latest version):
None (known)
Medium (always for the latest version):
None (known)
Minor (always for the latest version):
When booting up while the USB cable is connected you will see the charger image instead of boot directly - even when there is enough battery capacity. Simply press power button or boot without the cable connected.
Version >= 2.0: in rare situation when you use the magic key press (vol up+down) to boot into recovery a kernel crash can occur when you have not followed the instructions step by step. This is not a problem of the kernel! It is because of a timing issue of the hook used to get into recovery when you press the magic keys too early. Simply follow the instructions and you should be fine. If you still see a crash let me know and try it again it should really work the described way.
Development progress
sediKERNEL v3.0
Current progress:
Building a custom kernel without stock initrd (that means building an own initrd which works. atm I use the custom compiled Kernel + stock initrd)
Latest stable version: sediKERNEL v2.0
Download:
USE THAT ON YOUR OWN RISK!
ZIP flashable file (see instructions at the OP thread): sediKERNEL
DD Image file (see instructions at the OP thread): really? ok if you don't like AROMA open the ZIP and use the /kernel/sediKERNEL...lok file
Changelog:
For changelog see Changelog post
Previous versions:
see Changelog post
Installation Instructions (all versions)
Pre-Requirements (both methods)
Bravery & the will to change things for a better world
You should have rooted the device
You need either CWM (not my preferred choice) or TWRP installed (TWRP is highly recommended)
Method1: Based on ZIP (AROMA installer)
DO A BACKUP! For example execute: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img <- This will backup your current boot partition to your external SD card.
If you have adb installed (install it here if you like: @lifehacker) the command would be:
adb shell "su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img"
Download the sediKERNEL ZIP file
Extract that ZIP on your PC.
Copy or push BOTH files to your F3Q (the ZIP you extracted + the MD5 file).
You can do this by mount the F3Q normally and use MTP or adb if you like:
e.g when in booted stock ROM: "adb push ZIPfile /storage/external_SD/" & once again for the md5 file: "adb push MD5file /storage/external_SD/"
Reboot into recovery (e.g. execute: "adb reboot recovery")
Flash the ZIP & enjoy the magic
Done
Method2: Based on DD
DO A BACKUP! For example execute: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img <- This will backup your current boot partition to your external SD card.
If you have adb installed (install it here if you like: @lifehacker) the command would be:
adb shell "su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/STOCK_boot.img"
Download the sediKERNEL Image file
Put that image file to your F3Q (e.g when in booted stock ROM: "adb push imagefile /storage/external_SD/")
Reboot into recovery (e.g. execute: "adb reboot recovery")
execute: dd if=/storage/external_SD/your-uploaded-imagefile of=/dev/block/platform/msm_sdcc.1/by-name/boot
wipe dalvik cache (IMPORTANT!). Example: "adb shell mount /data and then: adb shell 'rm -R /data/dalvik-cache' " when recovery has booted up.
Done
Sources:
My current kernel setup of the fx3q sediKERNEL build can be found here: kernel_lge_fx3q_aosp
.
XDA:DevDB Information
[KERNEL][STOCK/AOSP][JB] sediKERNEL for LG Optimus F3Q, Kernel for the General Discussion
Contributors
xdajog, joel.maxuel
Source Code: https://github.com/xdajog/kernel_fx3q_aosp
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v2.0_build28
Stable Release Date: 2015-05-13
Created 2015-05-19
Last Updated 2015-05-19
Changelog
sediKERNEL v2.0 (build28)
Enhancements:
Busybox (busybox_nonselinux_1.23.1) added to initial ramdisk (to get all the commands needed for the magic recovery boot keys)
Toolbox added (to get a working reboot command for the magic recovery boot keys)
added magic key press detection for booting into recovery! This superseedes all the problems regarding how to reach the recovery mode when the system is damaged!!
Usage instructions:
Power on the device
when you see the LG logo the first time do NOTHING!!
When the screen goes black THEN press Volume UP + Volume DOWN. Both the same time and hold them pressed.
Release the buttons when the screen goes black again
Wait. You will see the LG logo a third time and then you will see the recovery screen!
If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.
ing those keys and be happy!
AROMA flashing ZIP file available! This will flash the sediKERNEL into the right place (boot partition of course ) and wipe dalvik cache for you. Enjoy
Fixes:
sediKERNEL version string was not optimal
Version was "Unavailable" at "About Phone" --> "Software Version" --> "Kernel Version". This was because the regex awaits "()" to filter out the correct version string. So the fix was to add build details into brakes and double escape CONFIG_LOCALVERSION string. Using EXTRAVERSION within the Makefile brakes Kernel module build when used.
Download:
USE THAT ON YOUR OWN RISK!
ZIP flashable file (see instructions at the OP thread): sediKERNEL v2.0
DD Image file (see instructions at the OP thread): open the ZIP and use the /kernel/sediKERNEL...lok file
sediKERNEL v1.5
Enhancements:
removed all kexec patches and kexec support because we do not need it atm (I want to avoid issues)
added version string to kernel (uname -a)
Fixes:
may fixes kernel crash in rare situations (kexec related)
Download:
USE THAT ON YOUR OWN RISK!
DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.5_build6.img
ZIP flashable file (see instructions at the OP thread): N / A
sediKERNEL v1.2
Enhancements:
Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Will not enforce LG signed image
Fixes:
This may fixes LG security errors (need feedback..)
May fixes a problem booting custom ROMs
Download:
USE THAT ON YOUR OWN RISK!
DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.2_26.img
ZIP flashable file (see instructions at the OP thread): N / A
sediKERNEL v1.0
Enhancements:
Same as stock but build from the sources
Compatible with the locked bootloader (means loki'ed)
XATTR enabled
KEXEC patches applied !
SELinux capable
Booting successful (tested on stock ROM)
Wi-Fi (tested on stock ROM)
Fixes:
TWRP is not unhappy anymore because of missing xattr and selinux
Download:
USE THAT ON YOUR OWN RISK!
DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.0.1.img
Reserved 2
IN THE MEANTIME YOU COULD USE THIS POST FOR ANOTHER THANKS CLICK
I appreciate all the work being done.
Would this be a solution to "Security Error" bootloops I am getting with my de-bloated ROM?
joel.maxuel said:
I appreciate all the work being done.
Would this be a solution to "Security Error" bootloops I am getting with my de-bloated ROM?
Click to expand...
Click to collapse
Possible but if you still getting security error bootloops when using this kernel then it may has something to do with a removed LG app.
It depends at which stage that security error occurs. If it appears directly when booting up it should not occur with sediKERNEL but if it booting up and you see the error then first it should be app related.
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
Possible but if you still getting security error bootloops when using this kernel then it may has something to do with a removed LG app.
It depends at which stage that security error occurs. If it appears directly when booting up it should not occur with sediKERNEL but if it booting up and you see the error then first it should be app related.
Click to expand...
Click to collapse
Yeah, the error I received using the stock kernel threw before the boot animation occurred, but after the LG logo.
I read somewhere that the Security Error comes up when you even remove Videos.apk. Hopefully that is kernel related and will go away with sediKERNEL.
joel.maxuel said:
Yeah, the error I received using the stock kernel threw before the boot animation occurred, but after the LG logo.
I read somewhere that the Security Error comes up when you even remove Videos.apk. Hopefully that is kernel related and will go away with sediKERNEL.
Click to expand...
Click to collapse
Well there are 2 stages where the LG logo will be displayed:
1) When powering on the device -> that is a static LG Logo and is shown shortly after powering on
2) When booting the Kernel -> that is the same looking LG Logo but there is a little little animation on it
I think that you will receive that Security Error after stage 1 and before stage 2 so when booting the kernel and that should be fixed using sediKERNEL.
xdajog said:
Well there are 2 stages where the LG logo will be displayed:
1) When powering on the device -> that is a static LG Logo and is shown shortly after powering on
2) When booting the Kernel -> that is the same looking LG Logo but there is a little little animation on it
I think that you will receive that Security Error after stage 1 and before stage 2 so when booting the kernel and that should be fixed using sediKERNEL.
Click to expand...
Click to collapse
Oh okay. It must be ROM based then. Because I think I did get to stage 2 before the security error threw.
joel.maxuel said:
Oh okay. It must be ROM based then. Because I think I did get to stage 2 before the security error threw.
Click to expand...
Click to collapse
nevertheless it would worth to try the sediKERNEL
xdajog said:
nevertheless it would worth to try the sediKERNEL
Click to expand...
Click to collapse
Agreed. I will hold off until v1.5 is released since that one looks more promising.
joel.maxuel said:
Agreed. I will hold off until v1.5 is released since that one looks more promising.
Click to expand...
Click to collapse
Code:
Latest available version
sediKERNEL v1.2
Enhancements:
Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Will not enforce LG signed image
Fixes:
This may fixes LG security errors (need feedback..)
May fixes a problem booting custom ROMs
Ok no appologies anymore try it
So I noticed a couple things over the past few days with the kernel.
The first is minor. When doing a reboot from recovery you need to make sure the USB cable is disconnected. The impact is that the phone goes to charge mode if the cable is still connected.
The other, well, gives a real good reason to have the really bulletproof method with TWRP. The hotkeys to the bootloader no longer work. I was testing an AOSP keyboard with my ROM (think I know what to do now) when the setup wizard crashed continually, leaving me soft bricked. Luckily download mode still works.
So tonight I am using the spare, until I get the F3Q rooted, recoveried, and restored (again).
Not to complain, I really appreciate all the work done, thought you would want to know any drawbacks with the current version.
Sent from my MyTouch 4G Slide
joel.maxuel said:
The other, well, gives a real good reason to have the really bulletproof method with TWRP. The hotkeys to the bootloader no longer work.
Click to expand...
Click to collapse
Many thx for your feedback!
Hm interesting. I use method 2 and the hotkeys are still working. AFAIK those hotkeys are integrated in the bootloader and that one will never be touched by any method. Strange..
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
Hm interesting. I use method 2 and the hotkeys are still working. AFAIK those hotkeys are integrated in the bootloader and that one will never be touched by any method. Strange..
Click to expand...
Click to collapse
There are so many hotkey variations across brands I lose track of the combo (keys pressed, how long). But I did try pwr +vol-dn, pwr + vol-up, even the three finger salute. Sometimes holding until the first LG logo shows, other times until the boot animation comes up (that's when I know I am screwed). I could still be doing it wrong...
Where is the bootloader stored anyway? Could it be that the opportunity for loading the bootloaders factory reset is during the kernel loading stage? TWRP kernel could still have those functions/flags. With a flipped boot and recovery image noted in method 2, that would make sense why your setup works.
Sent from my MyTouch 4G Slide
joel.maxuel said:
There are so many hotkey variations across brands I lose track of the combo (keys pressed, how long). But I did try pwr +vol-dn, pwr + vol-up, even the three finger salute. Sometimes holding until the first LG logo shows, other times until the boot animation comes up (that's when I know I am screwed). I could still be doing it wrong...
Where is the bootloader stored anyway? Could it be that the opportunity for loading the bootloaders factory reset is during the kernel loading stage? TWRP kernel could still have those functions/flags. With a flipped boot and recovery image noted in method 2, that would make sense why your setup works.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
The trick is to take out the battery , pressing vol+down and power while putting back the battery again. This will work 100%.
Any tries without putting out the battery may not work.
The bootloader is in "aboot" partition and i do not think it will have to do with the kernel. The reason why I can say that for near sure is that:
I tried to grab the key pressed while booting up which will be done in the init process. You can define things within an init script also key presses but they do not work while _booting_! They will work when booted up only so I tried to find out any other methods. The most meaningful would be to do that manually by writing a program to grab the key events. But at least I can say that I found no ressources about doing that other then described.
Because of that and because the bootloader steps into factory reset before kernel loads I do not think that there is anything kernel related. I think that the battery pull out will work in any case...
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
The trick is to take out the battery , pressing vol+down and power while putting back the battery again. This will work 100%.
Any tries without putting out the battery may not work.
The bootloader is in "aboot" partition and i do not think it will have to do with the kernel. The reason why I can say that for near sure is that:
I tried to grab the key pressed while booting up which will be done in the init process. You can define things within an init script also key presses but they do not work while _booting_! They will work when booted up only so I tried to find out any other methods. The most meaningful would be to do that manually by writing a program to grab the key events. But at least I can say that I found no ressources about doing that other then described.
Because of that and because the bootloader steps into factory reset before kernel loads I do not think that there is anything kernel related. I think that the battery pull out will work in any case...
Click to expand...
Click to collapse
Okay, just to make things weird, I had an opportunity to do the trick. It did not work, and I had to use the LG tool again.
It seems to bypass those keys pressed. Luckily download mode still works, or else I'd be screwed royally.
So going off-topic, why did I kill my phone again? Well, it all has to do with the LG Keyboard (onscreen) failing. With the ROM I have posted, it's "Unfortunately, LG Keyboard has stopped" over and over again. Yesterday, I made a version of the ROM with the AOSP Keyboard APK replacing the Lucky Goldstar version. Same problem, except this time it's "Unfortunately, AOSP Keyboard has stopped" over and over again. Okay, so I finished the setup wizard, turned on developer mode, fired up ADB, deleted the AOSP Keyboard from the /system/app folder and installed it as a userapp. No problem. So I thought, hmmm, would this APK work if I fire it in the /system/apps/bootup folder and let it install as a userapp when the ROM first boots?
I was going to test that theory, but when I rebooted into recovery (with the debloated ROM without any keyboard apps), wiped userdata and cache, I mispelled recovery when I issued the adb shell command "reboot recovery". That made it reboot into system, and things went downhill once I could not get past the LG Setup Wizard that was continually crashing.
So, LG tool'ed back to stock, rooted, recoveried and I thought, before I restore my precious backup I should try the ROM I created, answer that question once and for all. I wiped userdata and cache, rebooted back into recovery (spelling correct this time), flashed it, rebooted, and....
AOSP Keyboard crashed once (or more), in between all the LG Setup Wizard force closes. So I backed out and restored everything (again). I now have two pieces of homework:
Find a way to have developer mode on by default, so I can make (potentially) changes to the ROM if I am in this situation again.
Investigate if LG Setup Wizard is even needed, as it is really annoying me right now. If it's not, consider it gone!
Solve these two, and I should have something a lot closer to beta.
joel.maxuel said:
Okay, just to make things weird, I had an opportunity to do the trick. It did not work, and I had to use the LG tool again.
It seems to bypass those keys pressed. Luckily download mode still works, or else I'd be screwed royally.
Click to expand...
Click to collapse
hm... yea download mode should work always as this is totally independent from that. But the main difference in the latest sediKERNEL is that it completely ignores the bootloader arguments.
I thought always that the "Factory Hard Reset" screen was/is hardcoded within the bootloader but your tests showing that this can not be (fully) true. You should at least SEE the screen where you need to confirm the factory reset then. Well that could mean it either checks for the existence of kernel or this screen IS from the kernel itself! At least the last one could be tracked I will investigate that theory because if that is the case then there would be a hook where we could load TWRP instead e.g...
...
Update: Ok search is over. There is no trace found withing the kernel sources or the end result which contains the factory hard reset strings.
That said I think the LG factory reset needs a working kernel available...
That is my theory but could be "easy" verified/declined by following those steps. Maybe if you get into that situation again you could try?
deleting partition "boot" (dd /dev/zero..). If factory reset is still showing fine (it could be enough to still have a kernel in recovery). If not well then we need a working kernel/boot image to reach factory reset and you can ABORT HERE..
Then flash sediKERNEL to the boot partition and verify that it is booting.
from there delete the recovery partition (dd /dev/zero..).
Try to get into the factory reset again. If the screen "Factory Hard Reset" is displayed fine (it could be enough to either have a kernel in recovery or in boot). If not then we need a working kernel/recovery image to reach factory reset and you can ABORT HERE..
boot into system again
Now the wicked part: delete recovery partition and boot partition (dd ..) --> THIS MEANS: SOFT-BRICKING! but it is the only way to say it for absolutely sure (if the above both tries still showing the factory reset)..
turn out the battery. try to open the factory reset.
If the screen "Factory Hard Reset" is displayed that would be a clear decline of my theory!
If you do not see the screen "Factory Hard Reset" then it means we need a working kernel / boot / recovery partition in order to reach the factory reset screen!
well and now you need to use the download mode again to unbrick the device of course..
So going off-topic, why did I kill my phone again? Well, it all has to do with the LG Keyboard (onscreen) failing. With the ROM I have posted, it's "Unfortunately, LG Keyboard has stopped" over and over again. Yesterday, I made a version of the ROM with the AOSP Keyboard APK replacing the Lucky Goldstar version. Same problem, except this time it's "Unfortunately, AOSP Keyboard has stopped" over and over again. Okay, so I finished the setup wizard, turned on developer mode, fired up ADB, deleted the AOSP Keyboard from the /system/app folder and installed it as a userapp. No problem. So I thought, hmmm, would this APK work if I fire it in the /system/apps/bootup folder and let it install as a userapp when the ROM first boots?
I was going to test that theory, but when I rebooted into recovery (with the debloated ROM without any keyboard apps), wiped userdata and cache, I mispelled recovery when I issued the adb shell command "reboot recovery". That made it reboot into system, and things went downhill once I could not get past the LG Setup Wizard that was continually crashing.
So, LG tool'ed back to stock, rooted, recoveried and I thought, before I restore my precious backup I should try the ROM I created, answer that question once and for all. I wiped userdata and cache, rebooted back into recovery (spelling correct this time), flashed it, rebooted, and....
AOSP Keyboard crashed once (or more), in between all the LG Setup Wizard force closes. So I backed out and restored everything (again). I now have two pieces of homework:
Find a way to have developer mode on by default, so I can make (potentially) changes to the ROM if I am in this situation again.
Investigate if LG Setup Wizard is even needed, as it is really annoying me right now. If it's not, consider it gone!
Solve these two, and I should have something a lot closer to beta.
Click to expand...
Click to collapse
In order to turn on the usb debugger mode: within your ROM zip file modify this file "/system/build.prop"
Code:
persist.service.adb.enable=1
Optionally:
if you want to do root commands over adb I/you could modify in the "default.prop" file which is within the kernel's initrd:
Code:
ADD: ro.secure=0
REMOVE (if exist): ro.debuggable=0
Regarding your keyboard FCs:
I remember that I had the same issues within my Captivate ROM I build. There I tried to add the Kii Keyboard to the stock ROM image and that resulting in the same FC's you describing. My solution was to use another keyboard (in my case it was a samsung one) so I would suggest that you could try around with another keyboard instead of the AOSP one...
Good luck
xdajog said:
hm... yea download mode should work always as this is totally independent from that. But the main difference in the latest sediKERNEL is that it completely ignores the bootloader arguments.
I thought always that the "Factory Hard Reset" screen was/is hardcoded within the bootloader but your tests showing that this can not be (fully) true. You should at least SEE the screen where you need to confirm the factory reset then. Well that could mean it either checks for the existence of kernel or this screen IS from the kernel itself! At least the last one could be tracked I will investigate that theory because if that is the case then there would be a hook where we could load TWRP instead e.g...
...
Update: Ok search is over. There is no trace found withing the kernel sources or the end result which contains the factory hard reset strings.
That said I think the LG factory reset needs a working kernel available...
That is my theory but could be "easy" verified/declined by following those steps. Maybe if you get into that situation again you could try?
deleting partition "boot" (dd /dev/zero..). If factory reset is still showing fine (it could be enough to still have a kernel in recovery). If not well then we need a working kernel/boot image to reach factory reset and you can ABORT HERE..
Then flash sediKERNEL to the boot partition and verify that it is booting.
from there delete the recovery partition (dd /dev/zero..).
Try to get into the factory reset again. If the screen "Factory Hard Reset" is displayed fine (it could be enough to either have a kernel in recovery or in boot). If not then we need a working kernel/recovery image to reach factory reset and you can ABORT HERE..
boot into system again
Now the wicked part: delete recovery partition and boot partition (dd ..) --> THIS MEANS: SOFT-BRICKING! but it is the only way to say it for absolutely sure (if the above both tries still showing the factory reset)..
turn out the battery. try to open the factory reset.
If the screen "Factory Hard Reset" is displayed that would be a clear decline of my theory!
If you do not see the screen "Factory Hard Reset" then it means we need a working kernel / boot / recovery partition in order to reach the factory reset screen!
well and now you need to use the download mode again to unbrick the device of course..
Click to expand...
Click to collapse
Hopefully I don't end up in that situation again. However if I do, I still wouldn't be able to complete the test anyway because I would have no way of issuing (root) console commands. If I did, I could just execute my backup (I dd my partitions for this reason) restore plan (and get out of the mess easily).
Then I re-familiarized myself with this:
Code:
Enhancements:
Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Click to expand...
Click to collapse
What if the strings are in aboot, but the kernel flags merely throw the kernel into aboot if triggered by the hot-keys?
xdajog said:
In order to turn on the usb debugger mode: within your ROM zip file modify this file "/system/build.prop"
Code:
persist.service.adb.enable=1
Optionally:
if you want to do root commands over adb I/you could modify in the "default.prop" file which is within the kernel's initrd:
Code:
ADD: ro.secure=0
REMOVE (if exist): ro.debuggable=0
Regarding your keyboard FCs:
I remember that I had the same issues within my Captivate ROM I build. There I tried to add the Kii Keyboard to the stock ROM image and that resulting in the same FC's you describing. My solution was to use another keyboard (in my case it was a samsung one) so I would suggest that you could try around with another keyboard instead of the AOSP one...
Good luck
Click to expand...
Click to collapse
I will try the build.prop suggestion. It won't give me superuser (maybe you could do the default.prop modification?), but I could still install apks, which would have gotten me out of at least one mess. Although su would be nice. Could you integrate the modified default.prop into your kernel? :fingers-crossed:
As for the keyboards, I wonder if it's a permission thing. I will have to look at that when I get home. To be honest, I didn't look at what the permissions are set to (should be rw-r--r--), and I could/should rename the file to LatinIME.apk. There may also be a old library that is getting in the way. I also have a line on a different keyboard. Looks nice, just in the process of asking permission to use it first (based off of Google Keyboard).
sediKERNEL v1.5 released
Maybe the last version I release because no testing device anymore from now on:
sediKERNEL v1.5
Enhancements:
removed all kexec patches and kexec support because we do not need it atm (I want to avoid issues)
added version string to kernel (uname -a)
Fixes:
may fixes kernel crash in rare situations (kexec related)
Download:
see OP !
cheers
xdajog
i have LG Optimus L5 last year for 3 month. and some developed on him.
Not good phone the L3-L5-L7 phones LCD Quality is very low
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Markieboy said:
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Click to expand...
Click to collapse
Have you checked your Google account on a PC or other device ? check all is well there first
Lol flash twrp and install any rom.
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
diagonals said:
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
Click to expand...
Click to collapse
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hello, i have exactly the same issue battery health is like 65 percent when i look at accubattery and it crashes often wen battery is lower than 25% or so. It closes and never opens. Enters a boot loop. Sometimes it shuts down and enters boot loop too. Here is information that i see at download mode :
hTC download mode
*** LOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
RADIO - [email protected]
OpenDSP - v.20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017, 12:18:15(857212)
system info
show barcode
bla bla
Security checking falied GT_CONNECT_FAI
L
Security Warning
if you flash this phone with any rom bla bla
SD Mounted
OTG NOT MOUNTED
File NOT FOUND
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
i'd say pay for the s-off, there's no other way to fix your phone. but i still think your board is cooked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Sorry for taking so long to respond. This is the RUU.zip you should use. You can follow the instructions a few posts back, just use this download instead of the one linked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
Are you saying they replaced those? on the house? I'm
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
The question is, what were doing on that phone to cook all these? Mining Bitcoin?