Hi guys. I have a small problem with my LG L7.
My phone had stock rom with prerooted v10k rom. (no unlocked bootloader,no cwm)
I tried to flash the bootloader from the L7CWM.zip bat,and there was no error.
I didn't flash the recovery from the .bat,i installed it from ROM Manager and everything well.
Now the phone works,but if i try to enter recovery i get a this error:
Secure booting error!
Cause: boot certification verify
Why? I thought the bootloader was unlocked.
ROM Manager says I have the ClockworkMod 6.0.2.8,but I can't boot on it.
Solved. I just reflashed the bootloader 2 times,installed the cwm from the .bat and then again from ROM Manager.
Now everything works very well,i was just stupid trying to install the recovery from ROM Manager directly
Nik2468 said:
Solved. I just reflashed the bootloader 2 times,installed the cwm from the .bat and then again from ROM Manager.
Now everything works very well,i was just stupid trying to install the recovery from ROM Manager directly
Click to expand...
Click to collapse
Ive got the same problem.
What exactly did you do? Could you describe whole process step by step?
Thanks
Have same problem.Had version v20d, flashed cwm and cianogen mod, but had no signal.
Cant install v10k Homero2 via kdz , always get error wparam100 lparam1002 .
Tried with stock europian v10k but same error.
Can instal normaly v20D, but now cant get to CWM secure booting error
Can normaly flach and use v20D but i want to go to cianogen mod.
What should I do ?
SOLVED
Again installed cwm, on other computer and made it.
Then instaled V10K but Russian version via KDZ, than via CWM installed CM10 and all works well for now.
I dont know what should I do.
I have v10K rooted, downloaded CWM package, pluged my L7 via USB cable, USB debbugging activated,
then I run "flash_bootloader.bat", something blinks on PC screen (cant see or read because it is very quick), and nothing happens.
Restarted the phone, and nothing. Trying also "flash_recovery.bat", the same result.
Doing something wrong?
Help, please..
Run flash_bootloader script in cmd, then read what it says.
Sent from my Sensation using xda app-developers app
thanks, but
cmd window disappear very quick.. cant see or read anything
First open cmd (from 'Run' in menu Start) then run this script via cmd.
Sent from my HTC Sensation Z710e using xda app-developers app
CMD says:
adb push emmc_appsboot.bin /data/local/tmp/emmc_appsboot.bin
cannot stat 'emmc_appsboot.bin': No such file or directory
c:\l7cwm\adb shell su -c "dd if=/data/local/tmp/emmc_appsboot.bin of=/dev/block/mmcblk0p5 bs=4096"
/data/local/tmp/emmc_appsboot.bin: cannot open for read: No such file or directory
but "emmc_appsboot.bin" file realy is in directory L7CWM..
SO, WHAT NOW ??
needhelp_l7 said:
CMD says:
adb push emmc_appsboot.bin /data/local/tmp/emmc_appsboot.bin
cannot stat 'emmc_appsboot.bin': No such file or directory
c:\l7cwm\adb shell su -c "dd if=/data/local/tmp/emmc_appsboot.bin of=/dev/block/mmcblk0p5 bs=4096"
/data/local/tmp/emmc_appsboot.bin: cannot open for read: No such file or directory
but "emmc_appsboot.bin" file realy is in directory L7CWM..
SO, WHAT NOW ??
Click to expand...
Click to collapse
It needs to be in /data/local/tmp/ directory.
Sent from my HTC Sensation Z710e using xda app-developers app
ok, i moved it to that directory.. NOW CMD SAYS:
c:\l7cwm\adb shell su -c "dd if=/data/local/tmp/emmc_appsboot.bin of=/dev/block/mmcblk0p5 bs=4096"
64+1 records in
64+1 records out
264960 bytes transferred in 0.693 secs (382337 bytes/sec)
c:\l7cwm\adb reboot
THAT IS IT ?? ive got unlocked bootloader ??
EDIT == YES !! SUCCESS ! tested, it works!
thank you (mrjabol61) for helping me )
How did you solve the problem?
I do not have any /data/local/tmp/ directory! Where should I find it?
arkantos91 said:
How did you solve the problem?
I do not have any /data/local/tmp/ directory! Where should I find it?
Click to expand...
Click to collapse
Read from post #9 to #11
Sent using Tapatalk
Sorry I don't understand.
I also tried to create manually those directories in the phone and put the apps boot.bin file in it... but the same error shows in cmd .
Are there any other ways to unlock the bootloader?
Inviato dal mio Nexus 5 utilizzando Tapatalk
Related
Hi Everynone,
Well, this is my forst post here so if I'm doing anything wrong sorry. I will accept any tip to how use the forum as best I can.
Ok, goins into de point: it is my first time using custom roms, rooting and all other stuff with my Acer. I started using the ICS stock leak:
Acer_AV041_A500_0.009.00_WW_GEN1
Now I'm using Acer_AV041_A500_0.014.00_WW_GEN1 from:
http://forum.xda-developers.com/showthread.php?t=1524736
Also, I'm using the ICSRoot version 3.1 (to have root) from:
http://forum.xda-developers.com/showthread.php?t=1520469
And to finish I used this to installing bootloader/fix recovery:
http://forum.xda-developers.com/showthread.php?t=1522384
As everyone can see I'm a noob, but I can learn a little fast
I'm doing all this to try install this rom:
ICS 4.0.3 FLEXREAPER-R5 for CWM or RA recovery flash
http://forum.xda-developers.com/showthread.php?t=1517181
Now I think that all I need is install the RA recovery or CWM. I tried to install the CWM by Android Market using the ROM Manager, but when I do it the system give me a message "rom manager a500 does not have supported clockworkmod recovery".
Can someone help me to install CWM or RA Recovery? Can be showing me some guide (I tried, but I not found).
Regards,
Cristiano Santos
Brazil - SP
Ok,
Less noob now: I saw that I have RA Recovery installed when I did the process from "HowTo Installing the unlocked bootloader and fixing broken recovery in leaked ICS".
The problem is: I can't enter in RA Recovery, unless opening a CMD from my notebook and using the commands:
Code:
adb reboot bootloader
fastboot boot recovery.img (using the recovery_thor17_403.img inside the nvflash directory).
When I use by this way I can enter in Recovery and, for example, make backup from actually nvran to sdcard. But I can't enter using the "Power button + Sound button". If I do it come the "Dead Android with exclamation" in the screen
Any tip?
Same question.
Does anybody can access to CWM recovery with the "volume-/power" command after having used the jm77's method for fixing their bootloader "issue"?
exodusevil said:
Ok,
Less noob now: I saw that I have RA Recovery installed when I did the process from "HowTo Installing the unlocked bootloader and fixing broken recovery in leaked ICS".
The problem is: I can't enter in RA Recovery, unless opening a CMD from my notebook and using the commands:
Code:
adb reboot bootloader
fastboot boot recovery.img (using the recovery_thor17_403.img inside the nvflash directory).
When I use by this way I can enter in Recovery and, for example, make backup from actually nvran to sdcard. But I can't enter using the "Power button + Sound button". If I do it come the "Dead Android with exclamation" in the screen
Any tip?
Click to expand...
Click to collapse
Did you properly flash the modded bootloader blob? Because only flashing a modded recovery will not work
Sent from my A500 using Tapatalk
SOLVED!!!
castafiore said:
Same question.
Does anybody can access to CWM recovery with the "volume-/power" command after having used the jm77's method for fixing their bootloader "issue"?
Click to expand...
Click to collapse
SOLVED!
The problem is: when you use the guide to install the CWM/RA have a file (/system/recovery-from-boot.p) that as "strra" told "reflashing stock recovery whenever you boot into android"!
What you have to solve:
Open the Terminal Emulator inside the tablet and do:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
cd /system
mv recovery-from-boot.p recovery-from-boot.p-BKP
[CODE]
Copy "recovery_thor17_403.img" the (is inside the nvflash-A500.zip from the original jm77 thread), open a CMD in your laptop/PC and do
[CODE]
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery recovery_thor17_403.img
That's it! Now we have the RA Recovery!
Don't make a mistake: I'm a completly noob! All I have done was used the all information in this order:
- Installed the ICS from:
http://forum.xda-developers.com/showthread.php?t=1524736
- Rooted using:
http://forum.xda-developers.com/showthread.php?t=1520469
- CWM/RA Recovery using:
http://forum.xda-developers.com/showthread.php?t=1522384
- And to finish used the trip from our buddy "strra" from here:
http://forum.xda-developers.com/showpost.php?p=23223347&postcount=14
Thanks for ALL INCREDIBLE GUYS AND GIRLS here from XDA. I know that I'm a noob (but now I'm a little less lol). Thanks for:
- vache
- blackthund3r
- jm77
- yaworski
- strra
blackthund3r said:
Did you properly flash the modded bootloader blob? Because only flashing a modded recovery will not work
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Thank for the tip you blackthund3r, but the problem was it:
http://forum.xda-developers.com/showpost.php?p=23223347&postcount=14
As our frind "strra" told: "it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android".
Thank you so much you incredible work blackthund3r. I used another hands-on guide to get root, but your ICSRoot is so far easer!
exodusevil said:
Thank for the tip you blackthund3r, but the problem was it:
http://forum.xda-developers.com/showpost.php?p=23223347&postcount=14
As our frind "strra" told: "it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android".
Thank you so much you incredible work blackthund3r. I used another hands-on guide to get root, but your ICSRoot is so far easer!
Click to expand...
Click to collapse
Okay that did cross my mind. I suppose its the flash-recovery.sh script which I initialises the flash process? And no problem I'm such glad it has helped people =)
Sent from my A500 using Tapatalk
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
juckeyy said:
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
Click to expand...
Click to collapse
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
gee2012 said:
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
Click to expand...
Click to collapse
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
gee2012 said:
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
Click to expand...
Click to collapse
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
gee2012 said:
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
Click to expand...
Click to collapse
Hmm, couldnt find my adapter. Is there no way to flash in the stock rom with odin?
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Hmm wow seems like a long process but i'll try it.
Thanks!
samersh72 said:
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
Click to expand...
Click to collapse
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
gee2012 said:
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
Click to expand...
Click to collapse
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
thank you my friend
Click to expand...
Click to collapse
Wait one minute bro.
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
Click to expand...
Click to collapse
Hey when I type in adb devies it says mine is unauthorized :/
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
-Edit- also with usb debugging disabled the serialnumber is shown.in recovery.
juckeyy said:
Hey when I type in adb devies it says mine is unauthorized :/
Click to expand...
Click to collapse
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
gee2012 said:
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
Click to expand...
Click to collapse
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
samersh72 said:
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
Click to expand...
Click to collapse
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
juckeyy said:
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
Click to expand...
Click to collapse
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
samersh72 said:
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
Click to expand...
Click to collapse
I did still didnt work. Now I managed to get a ROM into my SD-card so now i'll boot custom recovery and try to install.
lets hope for the best!
Hey again!
Just wanna thank everybody for the help. I solved everything with flashing in stock ROM with odin.
I'll try again tomorrow with other ROM:s
Thanks, Joakim.
had same problem
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
fezz64 said:
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
Click to expand...
Click to collapse
Is it the same with other roms?
Make sure the download is not corrupted.
Wipe data, cache and dalvic after flashing the rom, reboot
sent from my Galaxy
So I wanted to upgrade to twrp 2.6.3.3 and I dont know why for some reason when I went to their page I saw these instructions and thought I'd try them
_______________________________________________________________
Download the above file and place it in /sdcard on your device. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Make certain that you get this command right. Typing the wrong number could result in a brick!
_______________________________________________________________
Now everytime i try to reboot into recovery it does some kind of boot verification check errors and just turns off. I flashed cwm and it says it flashed recovery ok but I cant boot into recovery. What have I done? :0
Not even my lg flash tool works right. I get to the ready part and click the arrow, I put my device in download mode and plug in the usb cable to the pc and then in the lg flash tool it says download fail, device model is different?
Try reflashing 2.6.3.2...I'm having issues with new version too.
Sent from my VS980 4G using xda app-developers app
Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Parinibbana said:
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Click to expand...
Click to collapse
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Phoost said:
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Click to expand...
Click to collapse
Thanks for the hint, but in fact I did not forget about it. I did replace the original one.
Parinibbana said:
Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Click to expand...
Click to collapse
Give this a try. It sounds like it will help.
http://forum.xda-developers.com/showthread.php?t=2582142
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Stuck in bootloop but can push files using adb-commands
I would like to add, that I can push files to the device over adb when I am inside CWM-recovery. I can even flash ROMs, but all that doesn´t help, since afterwards I will still be in bootloop.
If I knew which files are corrupted causing the device not to get beyond the LG-bootlogo, then I could replace the corrupted files over adb.
Any ideas?
Parinibbana said:
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Click to expand...
Click to collapse
I would try to use the method i suggested to restore your Download mode, I can confirm that it will work. Then use download mode to flash the factory *.kdz or *.tot file to your device via the LG recovery tool. I'm not an expert at this, but i think you should focus on getting download mode working, then you can restore your phone to stock fixing whatever partition is broken and keeping your phone from booting. This will get your phone back to a factory stock and booting condition, then work on modding it to the way you want.
As a side note If TWRP is not available for your device i would assume you could just substitute CWM in its place. This really doesn't matter if your only trying to get to download mode to restore your phone.
Have you tried ADB Sideload?
MK45A said:
Have you tried ADB Sideload?
Click to expand...
Click to collapse
No, what is it? How would ADB sideload help in my situation?
Do I even need it, since I can flash any ROM successfully from within normal CWM-mode and have full access to adb-commands from within CWM. But whatever ROM I flash, afterwards I am still stuck in bootloop.
How could sideload help with that?
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
In CWM, look for something like 'ADB Sideload' and then enable it.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
ADB sideload lets you push roms from your pc using command prompts to your phone.
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Have you tried out LG FlashTool?
MK45A said:
Have you tried out LG FlashTool?
Click to expand...
Click to collapse
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Parinibbana said:
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Click to expand...
Click to collapse
Can you write down the whole error or provide screenshots?
MK45A said:
ADB sideload lets you push roms from your pc using command prompts to your phone.
Click to expand...
Click to collapse
I see. This means, I don´t need to push the zip file to /sdcard/ beforehand, but can flash it directly from the laptop, right?
Here is a screenshot.
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Parinibbana said:
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Click to expand...
Click to collapse
Today I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted.
Finally unbricked my phone.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
Parinibbana said:
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/show....php?t=2451696
Click to expand...
Click to collapse
Interesting. Thanks for the feedback.
Download minimalabd https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Run this in adb
copy and past
adb shell
and also
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
and also past on cmd
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
This fixed my phone
NP
Hi Guys,
I had some problems with my beloved zenfone 2. Now i can´t enter in bootloader and recovery, but phone boots normaly.
The thing is it seems the partitions are cracked. My last hope was flashing a new recovery and bootloader with the images i got from this thread: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 using some programs to flash direct from phone (Tried with "recovery flasher" and "rom installer") but on "rom installer" app shows #ERROR: cannot locate recovery partition:
The history was : I rooted my phone using the zenfone toolkit, then started a wipe cache partition, which didn´t work and i forced off. After that i can´t made any adb connection - i can go to bootloader but doesn´t find my device and can´t write anything - , but i made TWRP recovery work using the "tethered recovery" as show in http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 and flash the original stock rom. ADB/fastboot still don´t work. After that i entered in TWRP again using the same method and inserted Superuser.zip there, rooting my device. After root i lost Bootloader, but still can go to recovery (using TWRP and CVM programs which have the option "reboot to recovery"), which was still useless since it recognize my phone but adb sideload still don´t work. I even tried the MOFD_update thing - copying the entire rom to sd card and renaming to MOFD update but it shows it can´t update. Then i tried to flash TWRP using the TWRP app and the only thing i did it was lost my recovey too.
Now when i try to go to bootloader only shows the UsB logo (the trident), The same happen if i try to go to recovery by apps.
I think i´ll have to fix partitions mannually, using only phone, but i have no ideia how. Can anyone know what can i do?
Thanks in advance
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Trident logo means brick phone...be careful nextime
Mononon said:
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Click to expand...
Click to collapse
Thanks Anyway. One thing i don´t understand is why my phone is booting normal. I know i´ll have issues when an update come, but it´s booting normaly
pato2015 said:
Trident logo means brick phone...be careful nextime
Click to expand...
Click to collapse
I hope i will have nextime...
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
ityoung said:
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
i´m trying to flash recovery.img from android. I can boot only for sistem. I can´t boot to bootloader or recovery. I´m trying a lot of apps which says it can flash a recovery from a running android, but none of them works
I also tried the Shuame like you said on another thread, but it doesn´t work. Thanks for your help
It might be possible to do something from a terminal window on your phone, but you would need to take advice from someone who knows what they are doing as I'm only theorizing rather than speaking from any position of knowledge.
Sent from my ASUS_Z00AD using Tapatalk
Is your bootloader unlocked?
dodongobongo said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. The problems started on my second boot after rooting, i had no chance to unlock bootloader too. I think if i had i can flash a custom recovery using TWRP or CVM apps and flash everything else again, but no, i can´t do that either.
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you Sooo much.
Now i have my recovery back, is there a way i can get bootloader back again using commands like that ? (and one bootloader i can use adb\fastboot ?)
I assume now i can use adb/sideload or MOFUPDATE.zip way (inserting an flashable rom with this name in my memory card so the system will flash like an update when i enter in recovery), but i don´t know what exactly i need to do (and what archives i have to use) to have a bootloader again, considering all ways to unbrick zenfone 2 needs fastboot. If i do that with stock Asus rom i can download from asus site will i have bootloader (and acess to fastboot) again? I´m afraid to do that and lose my root acess and still have no fastboot option. With root at least i can use terminal. I´m really afraid of flashing something that really hardbrick my phone since i have no fastboot, only root.
Can i unlock bootloader using terminal ? Maybe it´s safe if i unlock bootloader and then wipe TWRP using only TWRP app. After that i can flash other rooms and always have TWRP to fix if something goes wrong.
Sorry if i´m bothering. And thank you soo much for your help
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you again. Sorry about my insecurities, but i´m still worry. I rooted my phone at first time using the rootkit, one step there says i have to click "checkbeforeaction.bat" which will say i can go with root if i see 1234567ABCDEF as my phone. After that i can´t use adb anymore.
I don´t know why my phone changed to 1234567ABCDEF, i´m not sure if this is the reason i can´t use ADB. After recover my recovery yesterday (thanks for you) i checked "adb devices" on sideload and still shows 1234567ABCDEF. Still afraid to flash a stock rom and the only thing will change is i lost my root.
Maybe it´s a silly questions, but To use sideload i need a .img or a .zip file ? the stock room will flash stock recovery and stock bootloader again? Will i see 1234567ABCDEF again? Can i sideload a pre-rooted room ?Can i sideload just droidboot.img, boot.img and recovery.img? will it be placed on correct place on my phone? I´m really afraid of doing something wrong again.
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
i don´t understand your last phrase "&abt that serial no i think its fine"
You said never flash anything with your bootloader locked. I didn´t unlock my bootloader
Can i flash the image from this thread (item 3.1 method 1) ? http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Didn´t work to...
Shows on computer:
"error: protocol fault <no status>
On phone
"you need adb 1.0.32 or newer to sideload to this device.
installation aborted.
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/last_locale
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/command
I´m pretty sure i have the correct adb
yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Other thing that can be important:
When on adb sideload, if i request adb devices shows :
Emulator-5554 offline
0123456789ABCDEF sideload
Thats not my phone, again. What is that 012345ABCDEF thing ? can i fix that ?
Try using diff pc
& i forgot to mention u should unroot before flashing
Sent from my Karbonn A1+ Super using XDA Free mobile app