Related
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader
klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?
Did you solve the issue? Or is it still not allowing you to get into your F/W?
staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.
Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me
I do not know if this question has been brought up before, but I am in desperate need of an answer. I recently got my 6P and immediately proceeded to unlock the bootloader and flash TWRP to start loading custom roms. I decided to start use Pure Nexus with it's accompanying gapps package but when I go to reboot the device, I am stuck at the circles boot animation. I decide to try CM13 nightlies and the same problem occurs. After searching online for some time, I realize I needed to flash a SuperSU file from recovery that flashes a custom boot.img. I flash Version 2.66 and restart the device. After 5+ minutes on the boot screen, I decided I am stuck still. What do I need to do, I am unable to boot the device.
Thanks.
I'd use Nexus Root Toolkit to unbrick your phone just so that it is working to start with. Then follow the steps more closely for installing a rom. You'll be doing something wrong, I've had no issues!! Best of luck with this.
hmm I'm not sure. this is happening to me right now as I try to restore my backups... maybe has to do with twrp's system handling/mounting, but I just don't know.
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
After failing with installing different versions of TWRP om my tablet (There is no working version on TWRP for my model- system revert itself to the Stock recovery mode), at some point I noticed, that I can power on tablet and get to Welcome screen and start tablet configuration, but right after 20th seconds system freezes for few seconds and reboots over and over. If I just power on system and let it stay without touching screen it will reboots after 20 second.
If I go to the Recovery mode, there is not reboots. I did system hard reset in Recovery mode no help.
I thought it is problem with ROM, and flashed Stock Rom with Lenovo MOTO Smart Assistant. Same issue with reboots, then I tried some other ROM’s regions with same issue. Before I got this issue, other ROM’s used to work just fine.
QUALCOMM flash utility did not help as well.
I am just interesting is this issue with System board or it is software issue and I can fix this.
I have the same issue. I have been able to root through a patched boot image, but cannot get recovery to flash no matter what. It says all went successfully, but then always reboots. I have the 2GB version.
I just want to install an updated ROM since lenovo abandoned our devices.
BlinkySneaky said:
I have the same issue. I have been able to root through a patched boot image, but cannot get recovery to flash no matter what. It says all went successfully, but then always reboots. I have the 2GB version.
I just want to install an updated ROM since lenovo abandoned our devices.
Click to expand...
Click to collapse
I've just spent days trying to get my TB-X704V to flash. I finally found out how. The issue I ran into is the recovery mode never worked. I found one that did. Big caveat here. Once I flashed the recovery image, I could no longer boot the stock rom.
I found the recovery image looking for X704A, and ended up with the files at https://drive.google.com/file/d/1QyUGBPi-KZrhSVFLOCs3lHUZ59fpe9KL/view (not my files). This is Chinese/English version. You can change language in the menu.
Follow the directions on flashing it at the quick boot menu and unplug and go into recovery mode.
Download the latest lineage OS: https://androidfilehost.com/?fid=6006931924117916469
Install the OS. The initial boot will take a few minutes, but it will boot.
Most of what I found was in the thread https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
Thanks @yener90 for your work!
imrambi said:
I've just spent days trying to get my TB-X704V to flash. I finally found out how. The issue I ran into is the recovery mode never worked. I found one that did. Big caveat here. Once I flashed the recovery image, I could no longer boot the stock rom.
I found the recovery image looking for X704A.
Click to expand...
Click to collapse
Thank you so much, I was able to boot straight into TWRP using that Chinese/English image. I spent days last week unsuccessfully trying to boot my TB-X704V into the twrp-3.2.3-0-tb_x704l.img recovery image, but it never took no matter what I tried.
imrambi said:
I've just spent days trying to get my TB-X704V to flash. I finally found out how. The issue I ran into is the recovery mode never worked. I found one that did. Big caveat here. Once I flashed the recovery image, I could no longer boot the stock rom.
I found the recovery image looking for X704A, and ended up with the files at https://drive.google.com/file/d/1QyUGBPi-KZrhSVFLOCs3lHUZ59fpe9KL/view (not my files). This is Chinese/English version. You can change language in the menu.
Follow the directions on flashing it at the quick boot menu and unplug and go into recovery mode.
Download the latest lineage OS: https://androidfilehost.com/?fid=6006931924117916469
Install the OS. The initial boot will take a few minutes, but it will boot.
Most of what I found was in the thread https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
Thanks @yener90 for your work!
Click to expand...
Click to collapse
Thank you for all your help mate. This is exactly what I needed. You two are gentlemen and scholars.
Hello,
In a late-night act of utter stupidity, when over-tired, I re-flashed the boot recovery with TWRP and bricked my M3. It obviously can't now enter boot recovery.
I've used TWRP and successfully re-flashed custom roms on my original Mate, and changed regions. (Not in any way an expert, I know how to follow instructions.)
I was trying to convert my Chinese (I was living there) ROM to UK. It's tricky nowadays.
This was a stupid error when tired. Any way back?
I read somewhere that people with the right hardware can do it, but finding someone. I'm in Leeds, UK.
The pad does (did) what I need, and I'm not in a position to buy a new one. If it's dead, it's dead; and I can move on.
Cheers in advance for any input.
SOLVED
See my last post on this thread.
After using Multi Tool V8 to enquire into the machine I switched off and rebooted.
It came back with a "Wipe cache" and "Reset to factory settings" Huawei screen, so I did both and - It booted!
It had spectacularly failed to do anything but boot-loop since coming out of a very dead battery yesterday.
1) Boot recovery, OTA recovery, and dload recovery from SD were all unavailable after the original overwriting of the bootloader.
2) After being dead for months, all recovery options booted from power button plus vol- Vol+ and Vol+/- - but still bootlooping.
Then, suddenly it booted into wipe cache/factory reset screen.
Android 7, EMUI 5.1.3
I have no idea why.
Now fully working. (Including restarting)
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
qllkevuoi said:
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
Click to expand...
Click to collapse
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Update - Bootloader working after battery drain: Now what?
[Edit] Post redundant as it started working - see OP.
NwotNot said:
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Click to expand...
Click to collapse
Well...
After being without power for so long I turned the tablet on and it booted!
However, it then went into OTA and updated - rebooted - and locked the damned bootloader.
1) It's showing as rooted.
2) Boot loader is locked.
3) Fastboot & rescue mode comes up.
4) Recovery (OTA) still comes up but "Fails" this time.
I don't recall how I unlocked it last time. I don't ever rememebr an unlock code.
Status:
Fastboot reports it exists.
ADB reports "Null" not found. (ADB drivers installed).
Firmware version: CPN-AL00C233B078
Device name: CPN-AL00
Serial Number: Showing
IMEI: Showing
Bootloader state: LOCK
I have an old TWRP backup - don't know how to use it.
Solutions?
a) Any kind devs prepared to work with me and find the boot unlocker code for this 5-year old tablet?
b) Any other solutions now we know what's what?
I'm self employed without income in this pandemic and can't really afford to buy a new tablet. If I have to, it won't be Huawei.
(There's a T3 10.6" at £89, but I'm not biting - I need to sort out a budget tablet with at least the oomph of the M3.)
Any help much appreciated. :good:
David.