Related
Greets,
I think I may have bricked my Droid Maxx but I'm hoping someone can verify before I deem it a paperweight. I was on SU-2-3.3 and used Sunshine on it to unlock it and then TWRP to root it. After fully booting up the phone and verifying root, I rebooted into TWRP and ran a full back up w md5. After that, I booted up the phone and used supersu survival mode and then took the OTA update. Now the phone boots to fastboot, but says "boot failed" under any of the options. It won't go into recovery nor will it normally boot up. I tried to use RSD to reflash to the latest version but it just said flash failed at the first file and says something about downgraded security, etc. So now, I can get into fastboot mode and the phone connects and is detected but won't let me flash anything... it was unlocked via Sunshine, but I may have borked it up somehow. Thoughts?
Try a more recent firmware but check your recovery
Sent from my D6616 using Tapatalk
I took the OTA... is there something more recent? Also, I've tried to flash other recoveries but I get "boot failed" at the fastboot menu.
ohhhh you must mean try and use a more recent firmware via RSD. I'll give that a shot
Ok i tried a newer firmware via RSD, now the fastboot mode shows "failed to read signatures for partition aboot" RSD fails at flashing partition gpt.bin
Since I seem to have a partition related error, would this LINK help my situation at all?
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
t3knokon said:
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
Click to expand...
Click to collapse
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
t3knokon said:
Since I seem to have a partition related error, would this LINK help my situation at all?
Click to expand...
Click to collapse
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
BladeRunner said:
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
Click to expand...
Click to collapse
Ok to clarify, after I unlocked via sunsine on 2-3.3, I rooted and I took the over the air so now I'm on the newer bootloader. Post those events I started to receive "failed to erase partition xxxx" I also just tried reflashing individual images from 4.4.4 su6-7 release and I still receive back "failed to erase... failed to flash... etc." I can get into fastboot mode but it seems crippled somehow.
crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
t3knokon said:
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
Click to expand...
Click to collapse
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
BladeRunner said:
well, he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet
....
Click to expand...
Click to collapse
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
crack.mech said:
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
Click to expand...
Click to collapse
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
t3knokon said:
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
Click to expand...
Click to collapse
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
BladeRunner said:
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
Click to expand...
Click to collapse
Thanks for that. I posted there as well... from a software standpoint, I'm curious to know what would be denying access to the partitions...
I messaged jcase and he looked at logs for the sunshine preinstall and they were clean. It's possibly a hardware failure unless someone else with bootloader knowledge, knows how to get around the partition permissions access. thoughts?
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
t3knokon said:
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
Click to expand...
Click to collapse
the prognosis is not good.
VBlack messaged me about shorting a pin to put the phone in Qualcomm Downloader mode... and then pushing software onto it to at least try to the partitions set up and get the bootloader in a manner which will allow for writing. If that doesn't work, there's nothing else to do. I read up on it extensively, and it's now a last ditch effort. I've never take apart a phone in that manner before, so it'll be a first for me.
Similar boat, here...using a programmer cord, I can flash a ROM onto the Maxx, but it stumble-boots into BP Tools mode after 3 or so failed 0-battery/unlocked bootloader warning screen loops. I can get it into bootloader with program cord, or first thing with factory cord. It won't charge at all, battery is new. Izzit hosed?
Sent from my XT1254 using XDA Free mobile app
Heya. I restored a full backup in TWRP, and I ended up bootlooping. I tried flashing stock firmware, and nothing has changed. I can access downloading mode, and I can flash TWRP and boot into that. Any help? I've tried everything I've came.
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Synz86 said:
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
I'll try reflashing the root thing. Thanks.
EDIT: Does not work.
No problem, good luck. Let me know if it works, took me a couple times.
Sent from my SM-J700P using Tapatalk
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Having the same problem!
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
DirtyPISTOLA said:
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
Click to expand...
Click to collapse
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
uberpyrit said:
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
Click to expand...
Click to collapse
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
chucksaysblah said:
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
messi2050 said:
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
Click to expand...
Click to collapse
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
No It's not
uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
DirtyPISTOLA said:
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
Click to expand...
Click to collapse
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
uberpyrit said:
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
Click to expand...
Click to collapse
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
Click to expand...
Click to collapse
trying to recreate the process now...
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
trying to recreate the process now...
Click to expand...
Click to collapse
You didn't did anything wrong , it's coffenandroid adb enabled is not working correctly , now try to flash stock recovery as i heard that twrp cause bootloop on j700p
messi2050 said:
No It's not
Click to expand...
Click to collapse
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Starchild2k said:
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Click to expand...
Click to collapse
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
messi2050 said:
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
Click to expand...
Click to collapse
Thanx Messi I am going to try it now
messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Starchild2k said:
Thanx Messi I am going to try it now
Click to expand...
Click to collapse
np , tell me if it works for you
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
uberpyrit said:
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Click to expand...
Click to collapse
I'm going to make one and upload it
The update is being forced on my phone even though I have the automatic update option turned off in developer options. the update gets forced, and downloads/installs with a message that says the phone will now restart, it is at this point that my phone boots into TWRP everysingle time. Is there anyhope for me or is my phone totally bricked.
Rooted using Dirty Santa Root method
Rom: [H910 (AT&T)][ROM + Kernel] NRD90M Modded NotSoStock ROM
Edit: issue has been resolved thanks to user Team DevDigitel's handy fastboot commands. currently going to freeze any and all system update processes in TB. Thanks for our help guys!
Put phone in Fastboot
Fastboot erase fota
Fastboot erase misc
Fastboot erase cache
Reboot
Team DevDigitel said:
Put phone in Fastboot
Fastboot erase fota
Fastboot erase misc
Reboot
Click to expand...
Click to collapse
Would this be a safe way to temporarily avoid the update even if we aren't rooted and have a locked bootloader?
ubergeek77 said:
Would this be a safe way to temporarily avoid the update even if we aren't rooted and have a locked bootloader?
Click to expand...
Click to collapse
Unless your device has Fastboot without rooting you wont be able to send commands.
Those comands will delete the directorys the update and info stay at.. For him he should do that then go in and freeze the update manager or remove it from device to avoid it happening again.
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
And it depends on what update and security patch it is. ZV5 didn't have the patch and was safe. The next update is to target blocking root from what the dirty santa dev had stated. I know many users reported all ok with ZV5 softwear and dirty santa atleast on the ls997 side of the v20.
If you are stock there isn't much you can do.. Look at the note 7. They can and did force many updates till the last one actually disabled it. And best believe this is gonna become normal.. Don't pay ur bill.. Boom.. Locked out of your phone and your stuff.. No more ill use it on wifi stuff.. Especially to the phones being leased or not fully paid for.. Can't stop them if you don't own it lol.
Team DevDigitel said:
Unless your device has Fastboot without rooting you wont be able to send commands.
Those comands will delete the directorys the update and info stay at.. For him he should do that then go in and freeze the update manager or remove it from device to avoid it happening again.
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
And it depends on what update and security patch it is. ZV5 didn't have the patch and was safe. The next update is to target blocking root from what the dirty santa dev had stated. I know many users reported all ok with ZV5 softwear and dirty santa atleast on the ls997 side of the v20.
If you are stock there isn't much you can do.. Look at the note 7. They can and did force many updates till the last one actually disabled it. And best believe this is gonna become normal.. Don't pay ur bill.. Boom.. Locked out of your phone and your stuff.. No more ill use it on wifi stuff.. Especially to the phones being leased or not fully paid for.. Can't stop them if you don't own it lol.
Click to expand...
Click to collapse
...but I do own it...
Is there any part of the DirtySanta guide that would put me at risk? I haven't lost hope yet, my device is still exploitable, but at this point it's like a ticking time bomb. One shutdown or reboot and I'm screwed. I still intend to do everything I can to root this phone.
ubergeek77 said:
...but I do own it...
Is there any part of the DirtySanta guide that would put me at risk? I haven't lost hope yet, my device is still exploitable, but at this point it's like a ticking time bomb. One shutdown or reboot and I'm screwed. I still intend to do everything I can to root this phone.
Click to expand...
Click to collapse
is there a kdz available for your device? if so then not much as long as it messes up on older software.
if there isnt a kdz then yeah a good bit more risk. (kdz is the lg restore file to go back) The ls997 has none, so when i did my lg,
it was 1 shot and from there foward everything is custom, no way to revert to stock and voided warrenty so its all a risk now.
expecially because i paid out 600+ to own this device and nothing is a guarantee, but im rooted an happy now.
unless you can find a way to delete the fota folder without root you are gonna have to keep doing what you doing to avoid a update.
Team DevDigitel said:
Put phone in Fastboot
Fastboot erase fota
Fastboot erase misc
Fastboot erase cache
Reboot
Click to expand...
Click to collapse
gonna give this a shot now
Team DevDigitel said:
Put phone in Fastboot
Fastboot erase fota
Fastboot erase misc
Fastboot erase cache
Reboot
Click to expand...
Click to collapse
comand adb reboot fastboot is just rebooting my phone as normal, should i use adb reboot recovery instead?
edit: dumb question, issue resolved
mmarsie said:
comand adb reboot fastboot is just rebooting my phone as normal, should i use adb reboot recovery instead?
Click to expand...
Click to collapse
No... You just removed the update. Phone should reboot as normal now and stop looping..
Go and disable or uninstall the update package for LG.
You can't do ota updates anymore now you are rooted etc.
It will just keep you in a twrp loop.
Team DevDigitel said:
Put phone in Fastboot
Fastboot erase fota
Fastboot erase misc
Fastboot erase cache
Reboot
Click to expand...
Click to collapse
Thanks for these commands brother! Totally resolved my issue, seriously cant thank you enough!
mmarsie said:
comand adb reboot fastboot is just rebooting my phone as normal, should i use adb reboot recovery instead?
edit: dumb question, issue resolved
Click to expand...
Click to collapse
mmarsie said:
Thanks for these commands brother! Totally resolved my issue, seriously cant thank you enough!
Click to expand...
Click to collapse
Been there and done it to.. Really gets you worked up hehe
No worries. Its actually been hard to Really brick this phone..
I've even tried some dumb sh.. And its still working.
But again if you have a kdz file at your softwear or newer available better grab it and have it.. Its a sure way to revert back to 100% stock and locked.. Without it you gotta stay away from anything crazy..
Twrp loops.. And Fastboot loops are common on this device.. So if it happens take a deep breath and work through it.
On my roms page I have a help me post under Changelog.. It has a few tips for when you get stuck.. Should work for all variants. It will grow as time passes with more info.
Good luck!!!!!!
I've tried every single method I can see online, from fastboot flashing, to the dload method, to flashing stock via fastboot and then attempting the dload method. Nothing works. Right now I'm on TWRP 3.1.1-0 and RR 7.1.2. I really need to go back as with custom roms the fingerprint reader refuses to work, and not having HWC is a big deal to me. I was on EMUI 5.0, and I can't seem to get back. Any attempt at the dload method always fails at 5% and the fastboot flashed method (Where you flash the recovery, system and boot.img via fastboot) refuses to boot, (Just sits on device booting screen for 15+ minutes and does nothing). I've spent about 5-6 hours on this and I just can't figure it out. Any help is appreciated (also if anyone would be so kind as to throw up a BLL-L22 EMUI 5.0 TWRP stock backup, I'd really appreciate it).
Have you tried DC phoenix?!
rommco05 said:
need to know your build number bln-l22cxxx?
Click to expand...
Click to collapse
bll-l22c636b370
PalakMi said:
Have you tried DC phoenix?!
Click to expand...
Click to collapse
Not paying for unlocking software I'm never going to use other than flashing stock. If I'm desperate I might but currently looking for a free way to restore stock as this is my hobby phone to mess with and not my daily driver.
YMNDLZ said:
Not paying for unlocking software I'm never going to use other than flashing stock.
Click to expand...
Click to collapse
Well, I suggested it in case nothing else worked
I do get your point
Rommco05 said:
Flash this two zips over twrp. After go to reboot and tap reboot recovery, probably you will be in stock recovery and here tap factory reset and after reboot. Now should be phone boot to Nougat
http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
Click to expand...
Click to collapse
Didn't work, ended with error 7. Here's the link for the recovery log: https://drive.google.com/open?id=0ByoIewGd_qk2b2ZGNTh5WVRFT0E .
Rommco05 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v87976/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Try this zips are B370
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
Have you OpenKirin twrp?
Click to expand...
Click to collapse
I do have TWRP OpenKirin 3.1.1-0. I wiped everything beforehand. and I'm going to try and flash the firmware.
EDIT: No go, error 7 once again. I might just stay on 7.1.2 as this is getting very frustrating.
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder
Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan
hello
no problem I would like to explain in detail but my english is very bad
Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again
En joy
You're welcome
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think
I thinked that's because of slots
Hi
buddy what exactly is the problem
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it
Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device
can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3
re-install the same rum without deleting or update it with adb sideload
tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(