Hello people, I attempted the fix from this guide , but none of the available modified system images will boot my phone (model H1511). Right now I reverted to the factory image I downloaded from google and I'm stuck again at the google logo bootloop. How do I figure out what system image is the appropriate for my device? All the downloads I tried either got stuck at the Google logo for more than 1 hour and the others gave me a "Android system image is corrupted" type message prompting me to try again or to wipe data (already done many times). Any help or any info I can provide to help solve this issue? thanks a lot
Here is the info on the bootloader:
BL: angler-03.79
Baseband: angler-03.85
Product/Variant: ANGLER-VN2
...
...
Device is UNLOCKED.
margielamask said:
Hello people, I attempted the fix from this guide , but none of the available modified system images will boot my phone (model H1511). Right now I reverted to the factory image I downloaded from google and I'm stuck again at the google logo bootloop. How do I figure out what system image is the appropriate for my device? All the downloads I tried either got stuck at the Google logo for more than 1 hour and the others gave me a "Android system image is corrupted" type message prompting me to try again or to wipe data (already done many times). Any help or any info I can provide to help solve this issue? thanks a lot
Here is the info on the bootloader:
BL: angler-03.79
Baseband: angler-03.85
Product/Variant: ANGLER-VN2
...
...
Device is UNLOCKED.
Click to expand...
Click to collapse
Did you flashed the modified kernel or the modified boot.img from the guide ?
Were you able to boot into the recovery?
DevALT said:
Did you flashed the modified kernel or the modified boot.img from the guide ?
Were you able to boot into the recovery?
Click to expand...
Click to collapse
I took the modified boot.img provided there only, and I also tried the system image from the google site. Did I have to find a modified kernel too ? I just followed all the instructions in that tutorial and flashed to all those images to try as none booted for my device.
As for recovery, no modified images allowed me to boot into recovery either (it would just freeze), but I tried the twrp modified recovery and I was able to boot that.
You need the 4core kernel mod. Try that too.
Related
the problem is with Pepephone spanish carrier, i found a fix
http://www.elgrupoinformatico.com/s...droid-phone-android-con-pepephone-t16852.html
[SOLVED]
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??
orti13 said:
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??
Click to expand...
Click to collapse
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.
dhruvb14 said:
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.
Click to expand...
Click to collapse
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help
orti13 said:
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help
Click to expand...
Click to collapse
This is easy. Turn on phone with power and vol down buttom pressed. When on the bootloader screen plugin to computer and use fastboot to sideload custom recover.
(./fastboot sideload ziptosideload.zip)
hey
i tried unlocking the bootloader using recovery unlocking methods and through sp flash tool, rooting the android version 5.1 thorugh kingroot, then after installing the twrp.img it reboots and throw up an error showing as invalid .img file and install a lenovo.img itself and further it keeps restarting i tried the same with many twrp(recovery.img) files available in many links found in youtube and also in few threads of xda, but nothing working rather than landing up in the same boot error.
pl somebody help me out in the link with working custom boot loader .img and also with steps rather than facing the landing up in the same error.
Same problm
I will try to install recovery with flashify and my devices can't turn on
It will shows invalid boot.img
Help me.....
Sorry for my bad English
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
Thank you in advance for any help you can provide.
I successfully rooted my Zenfone 3 Max (ZC520TL) using Magisk, but wanted to restore the phone back to its factory firmware. I used the uninstall option in Magisk but this reported that it could not find the backup boot image. Unfortunately I then made the mistake of following unroot steps on other sites rather than this excellent resource. Long story short I somehow managed to lock the bootloader again so when I try to use fastboot to flash any image I get the error "FAILED (remote: not allowed in locked state)".
When I turn on the phone, on the ASUS splash screen it says...
Red State
Your device has failed verification and may not work properly
Your device will boot in 5 seconds
… ie boot loop.
Q) What can I do to get my phone usable again? I searched this site and found lots of info on how to unlock the bootloader and how to root, but nothing about how to stop the boot loop.
I do have access to the Recovery mode and see options such as "Apply update from ADB" and "Apply update from SD card" but I am unsure if these will help?
Thanks again for any help and/or links to solutions on this site that I missed.
I was caught in similar situation, due to unsuccessful flashing using asus flashtool, I ended up flashing stock firmware (not the raw firmware) via recovery and everything was back to normal.
Thank you... but...
sanctitude888 said:
I was caught in similar situation, due to unsuccessful flashing using asus flashtool, I ended up flashing stock firmware (not the raw firmware) via recovery and everything was back to normal.
Click to expand...
Click to collapse
Thank you @sanctitude888 so much for your help. I'm new to rooting but keen to learn. What's the difference between "stock" firmware and "raw" firmware? For example I can download the device firmware from ASUS and extract the boot.img file (ASUS no longer provides the recovery.img file) but is this considered "stock" firmware or "raw" firmware?
You also mentioned you flashed via recovery. In Recovery mode I see multiple options such as "Apply update from ADB", "Apply update from SD card", "Mount /system", etc. Could you please be more specific on how you did the recovery please?
Thank you for your help.
Kind Regards
Sorry for very late reply. Despite useful guides are there, they are pretty much scattered. Few posts or threads I could suggest as follows :
1. https://forum.xda-developers.com/zenfone-3/how-to/updated-unlock-relock-bootloader-t3749456
2. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-ze520kl-ze552kl-unofficial-t3738811
3. https://forum.xda-developers.com/zenfone-3/help/help-ze552kl-bootloop-flashing-t3820371
4. https://forum.xda-developers.com/zenfone-3/how-to/guide-how-to-root-zenfone-3-official-t3745650
Hi Everyone,
I have an issue with my Oneplus8 pro and below are the details
1. The device was working perfectly. I was interested to root the device and install a custom ROM.
2. The method used was to try and flash a patched boot image for the device but I think i landed up using a wrong boot image file.
3. The OS was on 10.5.10 if I remember correctly. I used a patched image file I suppose of an older firmware. Now restarts and goes to "QUALCOMM Crashdump mode". The only options are
a. reboot to fastboot mode
b. flash the TWRP for Oneplus 8 pro but that doesnt mount by storage so cant really transfer anything to flash again.
Requesting some help to fix the issue and apologies if i have not explained correctly.
Tried booting a stock boot image?
neverborn said:
Tried booting a stock boot image?
Click to expand...
Click to collapse
Hey,
Thank you for a quick repsonse. Yes, i had tried doing that and still the same error however while we speak, i just downloaded the msmDownloadtool and tried using it to flash a stock firmware and finally, i am so happy to see the device boot sucessfully
Thank you once again for tryin to help
Regards
Hello.
Clarify exactly how the procedure took place