Develop Bugs

[Bootloop] Installed Xposed Framework Module and..

Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?

codecrusher said:
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
Click to expand...
Click to collapse
hi, by original system image did you mean the stock system image from stock rom? if it is, you need to download the whole Asus Zenfone 2 Firmware from the Official Asus support website and follow either these two steps:
3.1 Tools Required:
Asus USB Drivers
ADB installed on your PC/Laptop
Asus Zenfone 2 Firmware from the Official Asus support website
3.2 Flashing stock Asus Zenfone 2:
Method 1:
Turn off your Zenfone 2
Go to recovery mode
Select apply update from ADB
Connect your zenfone 2 with USB cable to your PC/laptop
Open command prompt in Windows (in the same folder where ADB is located)
Check connection by typing adb devices in the command prompt.. If connection successful there will be a list of Zenfone 2 device.
Type
Code:
adb sideload file.zip (where file.zip is the file name of the Asus firmware)
Wait until the process is complete
Method 2:
Copy Zenfone 2 Firmware to the SD card
Enter Recovery mode
Select Update via SD card
Select firmware

codecrusher said:
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
Click to expand...
Click to collapse
Some modules have been known to cause issues, there is a thread with a list of known mods that are safe to use in Q&A I believe...

cangcan said:
hi, by original system image did you mean the stock system image from stock rom? if it is, you need to download the whole Asus Zenfone 2 Firmware from the Official Asus support website and follow either these two steps:
3.1 Tools Required:
Asus USB Drivers
ADB installed on your PC/Laptop
Asus Zenfone 2 Firmware from the Official Asus support website
3.2 Flashing stock Asus Zenfone 2:
Method 1:
Turn off your Zenfone 2
Go to recovery mode
Select apply update from ADB
Connect your zenfone 2 with USB cable to your PC/laptop
Open command prompt in Windows (in the same folder where ADB is located)
Check connection by typing adb devices in the command prompt.. If connection successful there will be a list of Zenfone 2 device.
Type
Code:
adb sideload file.zip (where file.zip is the file name of the Asus firmware)
Wait until the process is complete
Method 2:
Copy Zenfone 2 Firmware to the SD card
Enter Recovery mode
Select Update via SD card
Select firmware
Click to expand...
Click to collapse
Yes, with original image I mean the stock system image from the stock rom.
I'll try method 1 but I have a question before:
Since I'm able to boot the phone into boot mode (where it receives adb commands) but I'm not able to boot it into recovery mode (it tries to load something and then stops with error)....do you know if it is the same to send adb commands in boot mode instead that in recovery mode (and I refer in particular to the command: "adb sideload stockasusfw.zip")?
Thank you guys

codecrusher said:
Hi,
I have tested some xposed frameworks' modules and I have got a bootloop (the zenfone shows the background for a second and then reboot).
From the boot mode (power+volume buttons procedure) I have tried a factory reset but it says that there is an error and stops on the "dead robot"..
Now I've decided to flash the phone with its original system image and I've found this guide
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
At point III the guide says to use
Code:
fastboot flash system system.img
but only if you use Pre-ROOTed system image and then there is a link to the pre-rooted system image.
Where can I find an original system image?
I'm not an expert, I don't even know if this is the safest procedure to solve the bootloop....
please can someone help?
Click to expand...
Click to collapse
hmm.. i don't see the point to flash original system image if you want again to install Xposed.
Just reflash system.img preroot and install again your Xposed. That's all. (i've done that many times after trying some modules in Xposed getting me in bootloop)
Go in fastboot mode (power + volume UP) and fastboot flash system system.img and you're good to go to install again your xposed framework.
Preroot image is the same as the originale, but with SuperSu in addition.

ilos said:
hmm.. i don't see the point to flash original system image if you want again to install Xposed.
Just reflash system.img preroot and install again your Xposed. That's all. (i've done that many times after trying some modules in Xposed getting me in bootloop)
Go in fastboot mode (power + volume UP) and fastboot flash system system.img and you're good to go to install again your xposed framework.
Preroot image is the same as the originale, but with SuperSu in addition.
Click to expand...
Click to collapse
It's because prerooted image doesn't allow OTA updates.
However thanks, as I've said before this is my first bootloop and I was a little in panic.
Now that everything is clear I'm going to download and flash the system image.

In boot mode
Code:
fastboot flash system system.img
and it said something similar to this
Code:
target reported max download size of 518205818 bytes.
Invalid sparse file format at header magi fastboot
As I've said in a previous post, the phone did not enter into recovery mode because it got stucked on the "dead" robot. Now, don't know what it happens but after some minutes of "dead" robot, while I was surfing the net looking for solutions, it has finally loaded the recovery mode and from apply update from ADB I've tried
Code:
adb sideload blablabla.zip
the result was
Code:
r: device not found
After that...since I were into recovery mod, I've tried a wipe/factory reset and unexpectedly, the simplest thing has worked! I've got my phone back again.
I'm happy thought I don't understand the errors while flashing with adb and don't understand why the phone get at least 5 minutes of "dead" robot before entering into recovery mode...
Thanks for your support and for your patience

LG G3 Bricked / No ADB / No download mode / No recovery

Hi,
Since the rom ( http://forum.xda-developers.com/lg-g3/development/rom-resurrection-remix-lp-v5-5-5-t3198675 ) of my phone crashed. After reboot, the phone is blocked on LG logo. Now, i can't enter in recovery mode (or in the download mode) and when I start my phone, it's fixed on the LG for 5 to 10 minutes, and after that it goes to a terminal (started fastboot mode).
I have read several tutorials to use fastboot to flash the recovery to reinstall a rom, but i have a error when i tried to erase or flash the recovery partition.
I look on my phone, and this error appear : "failed to send erase grp start address".
what can i do to fix this error ?
Thanks.

up please

Use the "boot" command instead of "flash" and it should boot up into recovery or downloadmode, depending on which file you use

I tried but i am stucked on teamwin logo.
Which file do i use for download mode ?

Hard to tell, there are some laf.img files floating around on xda and google or even better, extract the laf.img from the stock kdz depending on your android version (for instance you flashed 6.0 you pick the 30b kdz and extract it with the firmware extraction tool)
I would suggest you to and try to use the boot command with them..
Be carefull, do not use the flash command until you found one that boots into downloadmode properly or you can loose your fastboot mode aswell
From then on you should be able to boot into the downloadmode and flash a new firmware via the lg flashtool

I need help please. What can i do to re install a rom ?

Does your PC recognise the port.?
I found tutorial under bender_007 signature. People seemed happy with tool.
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
Doesn't hurt to read and ask some questions.

no i can't connect my phone with port. I think, i nned to correct the error with fastboot. (remote : failed to erase partition)

th0was said:
no i can't connect my phone with port. I think, i nned to correct the error with fastboot. (remote : failed to erase partition)
Click to expand...
Click to collapse
Can you elaborate, how exactly your phone crashed, it is very unlikely that it will mess all the partitions just by crashing the rom?

The rom crushed twice, and now i can not access to recovery to install a new rom. I only have access to the fastboot command. Adb not working.
I tried to boot on recovery.img, but it's not working.
Thank for your help.
Regards,

Help please ?

Today i can connected to my phone with ADB when i tape this fastboot command : fastboot boot ./recovery.img.
I can too go into my phone as root with adb command : adb shell.
i tried to push flash_image on my phone and use it, but it donesn't work.
how can i flash my phone with adb command ?

H815: No recovery mode (bootloader unlocked, TWRP 3.0.1 installed)

Hey guys,
I'm trying to root my G4 loaded with MM 6.0. I cannot get into Recovery Mode no matter what I do.
I have tried the key combo (power+down, etc) - it does nothing. If I use adb reboot recovery, I just get the dead Android guy with the exclamation in red triangle. (which is perhaps a hint as to why the key combo doesn't work.)
I followed steps to unlock the phone's bootloader via LG's dev site (success) and I've installed TWRP 3.0.2-0-H815.img but I can't get into Recovery mode. **The phone continues to work fine** and I can get it into Download Mode.
After having no success with TWRP, I thought, f*ck it, since I've gone this far, let's go with CyanogenMod instead of stock, so I installed cm-13.0-20160415-NIGHTLY-h815-recovery.img
I was also able to use adb to push CM 13 (nightly build 20160415) and Gapps (arm64 6.0 20160416) successfully to phone, but it's obviously no use since I can't get to Recovery Mode.
I'm wondering if someone can please suggest a solution or at least a next step.
When I use fastboot flash recovery twrp-3.0.2-0-h815.img it takes 0.718s 'send recovery' and 0.282s 'writing recovery'.
[solved - probably Win10's no-ask driver update policy] New problem: After going back to TWRP, fastboot devices shows nothing and my device is showing up in Device Manager as LGE Mobile USB Composite Device, whereas I specifically changed it from the LG drivers I installed to Android ADB drivers. The device doesn't even list the Android ADB driver as an available option now. WTAF?!? Maybe this is more Win10 driver-auto-update malarkey?
OS = Win10x64
Kernal = 3.10.84
Build number = MRA58K
Software version = V20d-EUR-XX
Developer options are available
USB debug is enabled
OEM unlock is enabled
I'm using the stock USB cable
Additional question - tutorials say to back up NVRAM and IMEI before doing anything risky, but I can't get those without root. How does this make sense?
EDIT: NOTE: You should be using the arm64 version of Gapps on LG G4 H815.
Thank you very much to everyone who stops in to take a look at my questions.
All the best,
Dax.

Hi
I had the same problem with Win 10 not seeing my H815 properly (same device name in Device Mgr as yours) I reverted to the older Lge drivers, 4.0.3 if I remember correctly and the phone showed up properly and I was able to use LG UP to update/downgrade etc.
Like you I have since tried to install TWRP but I cannot new get root with Kingroot 480 although it worked previously on V81520D it does not now.
Sent from my iPad using Tapatalk

try fastboot boot recovery twrp-3.0.2-0-h815.img
then tap IMG instead of ZIP (bottom) -> install img and flash the twrp img

Hi Stransky, I reinstalled the adb-setup-1.4.2.exe package which also contains drivers and now ADB will see the phone (which is good), but Fastboot still says waiting for devices (bad). Thanks!
I also changed the default driver from 'LGE Mobile ADB Interface' to 'Android ADB Interface' (as per tutorial instructions).
Hi Bender_007, thanks so much for the tip, I'll try it as soon as I can get Fastboot working again. Cheers!

Okay, so I learned ADB is for Android or Recovery mode, Fastboot is for 'HBOOT' (bootloader) mode.
As expected:
adb devices returns "List of attached devices: LGH81579d3bc56 device".
If I use the command adb reboot-bootloader, phone restarts in bootloader mode.
Then adb devices does nothing, but fastboot devices returns "79d3bc56 fastboot".
When device is in bootloader mode, it shows up in Windows Device Manager as 'Marshall London Bootloader Device'.
Bender_007, the command "fastboot boot recovery twrp-3.0.2-0-h815.img" doesn't work. It's invalid syntax. "fastboot flash recovery twrp-3.0.2-0-h815.img" works as per original post.
Any other suggestions?

Hm, put the twrp inside the same folder where your fastboot and adb are. Then start command prompt in the very same folder and type fastboot boot twrp... And that should be it. That means if everything is normal and the system is bootable.
Pardon, fastboot boot twrp(whatever the name is)
Not: fastboot boot recovery twrp..
Sent from my LG-H815 using Tapatalk

Hi Bender_007, that's exactly where the .IMG files are already. No dice. :/

May I see this via teamviewer please ? (teamviewerQS via private message)
I´ll gladly help you (if it´s in my possibilities ofc)
@daxliniere
EDIT: 21.04.2016 - we have fixed this, had a nice talk, almost a beer. It´s nice to meet new cool people , keep it up my friend

I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?

madik_ said:
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
Click to expand...
Click to collapse
The best solution there is:
1. put adb, fastboot into a directory (let´s say c:\adb), put the twrp-3......img into the same folder
2. adb reboot bootloader
3. open command prompt, cd c:\adb
4. fastboot boot twrp-3.....img (where twrp-3....img is the actual name of the twrp img)
it will boot to twrp, now you can either copy the twrp img to the phone and flash it(it will ask where to flash - tap on recovery--don´t tap on boot)
You might have to tap on zip/img toggle to enable img flashing first
should you need more help just post in here

Yep that did the trick. thank you! I was able to load recovery with the fastboot boot twrp.. but didnt realize that i can install it by the loaded twrp lol. Now I can finally confirm 2x YES and it gets me into TWRP. thanks again!

Can I make one little tip for everyone else? Follow this guide to the end: http://www.technobuzz.net/unlock-lg-g4-bootloader/
Step 1 is the easiest way to install adb, fastboot and drivers in one go.

Same problem here:
Software version = V20d-EUR-XX, Developer options are available, USB debug is enabled, OEM unlock is enabled
I can boot into recovery via bootloader: fastboot boot twrp-3.0.2-0-h815.img but:
1. had I to allow to modify system partition modifications?
2. how can I boot in recovery from system? with adb I always get the red-triangle Android on its back und with hardwarekeys after shut down the devise, I#m coming to stock recovery: factory restet no/yes

1. Yes
2. While you are in twrp just flash the twrp IMG again via twrp itself. It has the option to flash img instead of zip.
Poslano sa mog SM-G930F koristeći Tapatalk

thx, a lot...
Now im running a full system update to exsdcard and afterwards I try to "re-"install the twrp in twrp-applikation.
When i boot into recovery at the moment, the "modify-dialog" is away...
But I will see after "re-"install the twrp how it works...
---------- Post added at 03:48 PM ---------- Previous post was at 03:00 PM ----------
UPDATE:
Did it, worked!!!
on system: "adb reboot recovery" leads to twrp!
there are no hardware-key-solutions to get to recovery...
with the hardware-keys (after shutdown -> power + vol down -> release power for a second when LG-logo pops up) I get to the factory reset no/yes dialog...

On the factory reset choose yes twice. Normal for lg
Poslano sa mog SM-G930F koristeći Tapatalk

I got nervous to choose yes the second time....

sejmand said:
I got nervous to choose yes the second time....
Click to expand...
Click to collapse
Install Quick Boot from the Play Store,you can boot straight to Twrp with it

fastboot erase recovery
fastboot flash recovery xxx.img (xxx=twrp.img)

Hello,
I am still struggling with my h815 on 7.0:
I am getting the error sign with "no commands".
I cannot force it to boot to the twrp but I can flash it (unknown command):
HTML:
student:~/Downloads$ sudo fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (32992 KB)...
OKAY [ 1.106s]
writing 'recovery'...
OKAY [ 0.931s]
finished. total time: 2.037s
student:~/Downloads$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.104s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.121s
using ubuntu 16.04.
Thanks for your feedback in advance.

Can not enter Recovery Mode

I'm right now in 2.20.40.198 (L). I can't perform Recovery Mode functions. Tried Factory Reset, but no use. Tried placing Firmware.zip in root folder. Update is recognized but on restart there is no change. I can enter the boot menu with the dead android, but when choosing Recovery Mode, the device just gets restarted.
Asus Flash tool throws this error " XXXXXXX_frp_request_server_log.txt (error 5: access is denied.)"
The device seems to be in Fastboot Mode. Shows this:
Product_Name - Z00A
Bootloader Version - unknown
IFWI Version - 0094.1069
Serial Number -
Signing -?
Secure_Boot - ?
ADB recognises the device but when entering "adb reboot bootloader" , I am taken to the same Fastboot Mode.
Help appreciated.

Anyone here who can troubleshoot?
Thanks

hellbraker said:
I'm right now in 2.20.40.198 (L). I can't perform Recovery Mode functions. Tried Factory Reset, but no use. Tried placing Firmware.zip in root folder. Update is recognized but on restart there is no change. I can enter the boot menu with the dead android, but when choosing Recovery Mode, the device just gets restarted.
Asus Flash tool throws this error " XXXXXXX_frp_request_server_log.txt (error 5: access is denied.)"
The device seems to be in Fastboot Mode. Shows this:
Product_Name - Z00A
Bootloader Version - unknown
IFWI Version - 0094.1069
Serial Number -
Signing -?
Secure_Boot - ?
ADB recognises the device but when entering "adb reboot bootloader" , I am taken to the same Fastboot Mode.
Help appreciated.
Click to expand...
Click to collapse
Maybe re install software was having same issue myself followed a guide on you tube I always hard bricked my device managed get it back

hellbraker said:
I'm right now in 2.20.40.198 (L). I can't perform Recovery Mode functions. Tried Factory Reset, but no use. Tried placing Firmware.zip in root folder. Update is recognized but on restart there is no change. I can enter the boot menu with the dead android, but when choosing Recovery Mode, the device just gets restarted.
Asus Flash tool throws this error " XXXXXXX_frp_request_server_log.txt (error 5: access is denied.)"
The device seems to be in Fastboot Mode. Shows this:
Product_Name - Z00A
Bootloader Version - unknown
IFWI Version - 0094.1069
Serial Number -
Signing -?
Secure_Boot - ?
ADB recognises the device but when entering "adb reboot bootloader" , I am taken to the same Fastboot Mode.
Help appreciated.
Click to expand...
Click to collapse
Hello there,
Did you manage to solve it ? I am in same trouble now and searching for help.

Problem Rebooting into Recovery

I am in the process of installing LineageOS 18.1 onto a Pixel 3 XL (I have done a Pixel 3 before with no issues). I am following the instructions from lineageos.org (https://wiki.lineageos.org/devices/crosshatch/install). It is specific instruction for the Pixel 3 XL. I have successfully completed the first number of steps but got stuck on the last one noted below:
Unlocking Bootloader (ALL COMPLETE)
enable OEM unlock
connect device to PC
adb reboot bootloader
fastboot devices
fastboot flashing unlock
reboot
re-enable usb debugging
Temporarily Booting a Custom Recovery
download a custom recover (lineage-18.1-20210803-recovery-crosshatch.img) - COMPLETE
connect device to PC - COMPLETE
adb reboot bootloader - COMPLETE
fastboot devices - COMPLETE
fastboot flash boot lineage-18.1-20210803-recover-crosshatch.img - COMPLETE (received msg that sending and writing to boot_a is okay)
reboot into recovery - INCOMPLETE
will not reboot into recovery, stays in fastboot mode
last line on fastboot mode screen says "no valid slot to boot" at one point it also said "error booting boot.img"
Any idea/suggestions on what would be the problem? I did try redoing the fastboot flash boot command an additional time and again it said it sent and wrote ok, however, still unable to reboot into recovery. I did not check the version of android on the phone before i flashed the lineage 18.1 recovery - could that be the problem? Might it be that the phone cannot run LIneage 18.1 because it is on android 10? (which I'm not sure how to check at this point). If this is the problem what would be the best solution - reflash with a lineage 17.1? Or, is there a way at this point to check and upgrade the android on the phone? Perhaps there is another problem entirely.