Develop Bugs

AOKP B30 Bootloop, wipe doesnt help

Hi!
Downloaded and clean flashed AOKP B30 and gapps, came from M4. Got into a bootloop. Went into recovery, wiped, still bootloop. Pushed an original image to the phone via Gnex Toolkit. Still bootloop!!
Now I have no idea what to do....
Please help!!

CWM cant find my sdcard either it seems!
If I try going into stock recovery, I get an android with a triangle.

Step 1: Take a deep breath. Your device is fine (although your data is probably gone).
Recovery cannot find /sdcard because there is likely an issue with your data partition, where /sdcard resides. The best thing to do is flash the stock images again. I recommend you do it manually so you can actually see what you are doing, instead of using a toolkit. Follow this procedure and you will be fine. And flash back CWM. (The android you are seeing with the red exclaimation point IS the stock recovery. To access the menu from there, repeatedly press volume up and power until you see the menu.)

Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.

eivi91 said:
Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.
Click to expand...
Click to collapse
Knowing is half the battle.. nexus is pretty brick proof
Sent from my francoPhone

[Q] TWRP + OTA update = bootloop! help needed!

Hello everyone,
Today showed up on my Gpad an update that automatically started to download.
So I thought ''if it is downloading, why don't I give it a try?''
Big mistake.
I am rooted with TWRP 2.7.0.0 and stock 4.4.2 rom..
My Gpad after I press confirm it tried to reboot. After the device shut down and try to power on, it stuck in a bootloop on TWRP.
Every time I try to power it off and then power it back on it starts on TWRP and stay there even if I press reboot on TWRP it does the same loop.
After this idiotic move of mine I would like to have help from someone who knows how to restore the device..
Also is there any way to restore the device in TWRP or to do the update manually from the file that is already downloaded in my device
(from TWRP)?
Any help would be very very appreciated!

alekos1992 said:
Hello everyone,
Today showed up on my Gpad an update that automatically started to download.
So I thought ''if it is downloading, why don't I give it a try?''
Big mistake.
I am rooted with TWRP 2.7.0.0 and stock 4.4.2 rom..
My Gpad after I press confirm it tried to reboot. After the device shut down and try to power on, it stuck in a bootloop on TWRP.
Every time I try to power it off and then power it back on it starts on TWRP and stay there even if I press reboot on TWRP it does the same loop.
After this idiotic move of mine I would like to have help from someone who knows how to restore the device..
Also is there any way to restore the device in TWRP or to do the update manually from the file that is already downloaded in my device
(from TWRP)?
Any help would be very very appreciated!
Click to expand...
Click to collapse
Did you not make a back up after rooting your tablet? If so, simply restore from your backup.

generally, it is advised that before you update a rooted device's ROM, to create a nandroid backup first, just to be sure. As OTA's from non-OEM's aren't as stable as OEM's, nor do they provide warranty if you get stuck in a boot loop. To fix the issue, download your ROM image to the "root" of your microSD, go to recovery, wipe cache/dalvik cache, then try to install the ROM image. If it still fails, I'm afraid you may need to do a fresh install (wipe the device fully, before making a fresh install of your ROM.). This should fix your problem, though you loose your data. Unfortunately, thats one of the risks of modifying our devices. One that I had to learn the hard way (by hard, I mean hard brick).
At any rate, hope this helps.

Thanks for the quick reply guys!
I have not made a backup of my files.
So now I'm downloading slimkat for a little change..
(also is there a way to create a backup of my files with TWRP and restore them on Slimkat?)
[UPDATE]
I wiped cache / dalvik and then install the Slimkat ROM but the same problem persists, then I did a factory reset from TWRP
and then install the ROM, but still the same
Is there any way to unroot your device from the PC?

alekos1992 said:
Thanks for the quick reply guys!
I have not made a backup of my files.
So now I'm downloading slimkat for a little change..
(also is there a way to create a backup of my files with TWRP and restore them on Slimkat?)
Click to expand...
Click to collapse
I don't have my tablet with me to check for you, however, I am pretty sure I found a file explorer within TWRP. Perhaps you may be able to copy from there. Explore the tool abit its quite user friendly and well made. Otherwise, you can make a nandroid backup to create a full backup of your system and try to extract from PC via WinRAR (if the backup is in tar), or some explorer app... see below for details:
http://forums.anandtech.com/showthread.php?t=2262350
or this one:
http://forum.xda-developers.com/showthread.php?t=2099493
hope this helps

jarod004 said:
I don't have my tablet with me to check for you, however, I am pretty sure I found a file explorer within TWRP. Perhaps you may be able to copy from there. Explore the tool abit its quite user friendly and well made. Otherwise, you can make a nandroid backup to create a full backup of your system and try to extract from PC via WinRAR (if the backup is in tar), or some explorer app... see below for details:
http://forums.anandtech.com/showthread.php?t=2262350
or this one:
http://forum.xda-developers.com/showthread.php?t=2099493
hope this helps
Click to expand...
Click to collapse
Thanks for the tip, I'm sure it will help me in a future failure!
I have already done everything you said without succeeding anything ,so I'm trying to un-brick it with LG's support tool
and I can not get it to recognize my connected Gpad, so I put manually the model and serial number but still it can't see any connected devices...
Now I'm 100% stuck :/

alekos1992 said:
Thanks for the tip, I'm sure it will help me in a future failure!
I have already done everything you said without succeeding anything ,so I'm trying to un-brick it with LG's support tool
and I can not get it to recognize my connected Gpad, so I put manually the model and serial number but still it can't see any connected devices...
Now I'm 100% stuck :/
Click to expand...
Click to collapse
sorry for what happened. have you tried to wipe all data, and all cache then try to do a fresh rom installation? I am not sure why LG cannot see your device. But a wild guess is its something about your recovery because its no longer stock perhaps???
if you can reach recovery, you should be able to fix the issue by wiping all the data (except external SD), wiping all cache (including dalvik), then install your custom ROM. Have happened to me already although different cause from yours but I was still able to restore it although I did loose all my data. But as I said before, its the price to pay for tinkering with our devices.

Hello guys,
Same problem for me, Stock 4.4.2 with TWRP, the OTA update make my GPad boot only on TWRP, no way to get my system back.
I try this one : http://forum.xda-developers.com/showthread.php?t=2772902
Successful My GPad is booting correctly on Android !

Damn!! I read to late your answer, I install a couple of minutes ago the complete stock 4.4.2 V50020d from LG's support tool.
In a previous post I said I was stuck but not really.. I forgot that I have to press volume + and volume - while connectiong the USB cable to enter download mode
But everyone having the same problem with me should really give a try to what JaymZ37 said above.
Peace to everyone and thanks for your replies!

Soloution for Boot Loop problem on LG Gpad V500
alekos1992 said:
Hello everyone,
Today showed up on my Gpad an update that automatically started to download.
So I thought ''if it is downloading, why don't I give it a try?''
Big mistake.
I am rooted with TWRP 2.7.0.0 and stock 4.4.2 rom..
My Gpad after I press confirm it tried to reboot. After the device shut down and try to power on, it stuck in a bootloop on TWRP.
Every time I try to power it off and then power it back on it starts on TWRP and stay there even if I press reboot on TWRP it does the same loop.
After this idiotic move of mine I would like to have help from someone who knows how to restore the device..
Also is there any way to restore the device in TWRP or to do the update manually from the file that is already downloaded in my device
(from TWRP)?
Any help would be very very appreciated!
Click to expand...
Click to collapse
Yesterday its hapen to me the same ptoblem.......
after searching i fount the soloution and they work perfect !!!!
>>>>>>>
I saw this thread: http://forums.androidcentral.com/gen...load-mode.html
"What worked for me was from the TWRP terminal command to the Root folder and was type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
(they have space on ....... dd_if=/dev/zero_of=dev....... only)
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
(the same here)
then hit enter and reboot."
<<<<<<<<<

Here's the original solution given in our forum:
[FIX] Installed TWRP and now you're stuck after OTA?
And the additional command was given in this post by brentkhack:
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
got help from the IRC xda-devs for the second step to complete the fix.
Click to expand...
Click to collapse

heliox said:
Here's the original solution given in our forum:
[FIX] Installed TWRP and now you're stuck after OTA?
And the additional command was given in this post by brentkhack:
Click to expand...
Click to collapse
Oh man that worked, just about to give my tablet to gran dad and got stucked, thanks for this!

Need help.Bootloop!

Hi there all, I need your help.
I decided to sell my Note 2 and as I tried to factory reset the phone for the new owner- it lead to bootloop witch I don't know how to get out of.
Basically it's N7105 model, unlocked and rooted. TWRP recovery and CyanogenMod 13. Was working totaly fine.
Before factory reseting I've read that to completely clean the data you should encrypt the phone and that will scramble the data. So I went and did that.
After I went to factory reset ,but it did nothing and just rebooted. Apparently it's some known bug in CM13, it's not working -many people experience it. And also there is no way to decrypt the data.
So now where I've made a mistake: I went to TWRP and saw one backup from the times I've installed TWRP and rom, and without thinking I pressed to restore.
But that backup was made when I've installed TWRP but OS was stock.
So now it goes through TWRP saying unable to mount data partition and then boots (not fully) to original Samsung OS but with an error: "Encryption failed. Unable to complete encryption due to interuption. Perform factory data reset (erasing all your data) before use. After resetting, try encrypting device again".
And one button to reset the device. If I press that it will go through the TWRP again as above. I can charge the phone and I can press Vol buttons.
I tried to connect with pc through ADB but looks like no devices are found. And in my Device Manager threre is an Yellow Exclamation mark on the phone line saying "The device cannot start". So that's the situation. Is there I can try before canceling sale?
Thanks for your help!
Paul

Did you try to flash the phone with a stock ROM in Odin?

Big thanks!
I did and it's all good!
What a wonderful program Odin- who created it?
Do you know if I lost root after flashing it?
Thanks!

Yes, flashing a stock ROM will remove root.
Odin is a Samsung product: https://en.wikipedia.org/wiki/Odin_(firmware_flashing_software)

[Q] LG G4 H811 Stuck in Recovery (TWRP) Loop

I was running the latest version of TWRP and a rooted version of the LG G6 port. Everything was stable and worked fine. So I was ready to give it back to its owner who I had modded it for. I went into the settings menu of the phone and did a standard factory reset to remove my account that was logged in so I could test the phone out before giving it to the owner. well when it finished resetting and rebooted, its been stuck in a boot loop ever since.
Tried just clearing both Dalvik Cache and Cache, to no avail. Tried Reflashing the rom and starting over. Still nothing. Tried flashing a different rom. Still nothing.
So what else can I try? and also if its the only thing I can do, rest it all the way back to stock factory everything. How do I do that on this phone. What program do I need and what files. and whats the steps to complete the process.
Thank you in advance for all help that is given

i factory reset in twrp and turned on developers options after first boot then reflashed twrp i always forget backup lol or delete it or use kdz you flashed before anyway i can help i will if you still need

if you have tried to flash the same custom rom or another is still not working, flashes with the program "lg up", you will need a kdz file,and the corresponding drivers. if with that you can not watch this tutorial before doing anything.
if you have a backup made with twrp, it flashes again.
https://forum.xda-developers.com/g4/help/unbrick-lg-g4-brick-hs-usb-qdloader-t3542785
during this process you will have to disassemble the back of the phone, (plastic) you do not need to remove the motherboard completely from the phone, anyway if you can enter download mode try with lg up tool.
if you need help around here we are.

Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?

Silicon Knight said:
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Click to expand...
Click to collapse
Can you get into download mode?
Also, it's possible you have been hit by the bootloop

2017 LG G4 Stuck in Boot Loop?

I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.

threehappypenguins said:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
Click to expand...
Click to collapse
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.

sdembiske said:
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
Click to expand...
Click to collapse
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.

threehappypenguins said:
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
Click to expand...
Click to collapse
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.

sdembiske said:
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Here's what I've done now at this point. I tried creating and flashing a 2 core boot image via fastboot, and then flashing the 2 core TWRP. Still bootloop.
I flashed the v29a N modem and UsU kernel for my device (H812), then went to TWRP and flashed stock N ROM again. Still bootloop.
I flashed N stock modem again, then baseband package for my model. Still bootloop.
I'm about to extract my MM modem and flash that.
Beyond that, I don't know what to do. I had zero issues with the UsU method originally and everything went fine and has been fine for the last couple of months since I did it.

Well, roadblock again. I attempted to extract modem from the kdz with SALT in FWUL, and after a while, I get a popup window that says: "This KDZ has an ARB of: arb-detect-error" and then it says "Select partition(s) to EXTRACT:"
Except there are no partitions to select. And my only options are "Deselect All" "Extract" and "Abort." If I try "Extract," I get the error, "No partition selected or abortioned by user."
I did make sure I had the latest version of SALT.

Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Code:
fastboot flash modem modem_32768.img
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.

threehappypenguins said:
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
Click to expand...
Click to collapse
Read about the ilapo it can't be fixed by software it may just help to enlenghten life.
Sent from my OnePlus 6T using XDA Labs