Originally Posted by shabbat
"Hi, here are the steps ï followed: after unlocking the bootloader then installing twrp 3.0.2 (by the method D_Cow) and then rooting the phone by flashing superSu :
1- first backup the stock rom then
2-wipe cache, data, system
3-flash V10_H901_V20L_Update_P1.zip
4-flash V10_H901_V20L_Custom_DeBloated__02_Tweaked_P2-signed.zip
5-flash @Eliminater74's last kernel :Nebula_1.0.1-alpha_v10_20161217_170023.zip
6-Reboot
7-Debloat by uninstalling only all apps that begin with "google"
(I hate google apps, they always drain the battery a lot so I always delete all google stuff)
8-Restore all my apps
9-Install greenify
10-Flash xposed-v87-sdk23-arm64.zip
That's all
Sent from my LG-H901 using XDA Free mobile app"
Click to expand...
Click to collapse
So I already had unlocked bootloader and twrp 3.0.2-0 with a older rooted stock rom, followed steps 1-6, all three flashed 100% and it looked like it was booting fine until google logo appeared. Screen went black like the battery was pulled and now it seems like its hard bricked and cant get it to do anything. I have tried holding vol up + power, vol down + power, vol up plug in usb to my computer also vol down then usb and nothing happens, no vibration and pc doesn't detect my phone, adb reboot recovery error: no devices/emulators found. Time to buy a new phone?
If you're still under warranty you *can* ask for a warranty replacement, but if you don't tell them you bricked it, you're technically commiting fraud. I can't suggest that you commit fraud. You could use your insurance. If you're out of warranty, I think you should be able to jump. Don't know how a bricked phone influences that for sure, I know for normal damage like a broken screen, they make you get a replacement first.
Волк said:
If you're still under warranty you *can* ask for a warranty replacement, but if you don't tell them you bricked it, you're technically commiting fraud. I can't suggest that you commit fraud. You could use your insurance. If you're out of warranty, I think you should be able to jump. Don't know how a bricked phone influences that for sure, I know for normal damage like a broken screen, they make you get a replacement first.
Click to expand...
Click to collapse
I went to the t mobile store and told them I tried to do a software update and the phone stopped working and they said it is a common problem with LG devices and its under warranty so I got a refurbished one 2 days ago. Came with 20L, just rooted with the dirtycow method with magisk su, once I install xposed i'll be happy. Is 20L the latest version?
Related
Hi all. I've had my SGS2 for probably 4 or 5 months now, and I was told by ATT that I can take my phone back to a warranty center and get it exchanged.
My issue is that the phone doesn't detect when the charger is removed. In addition, I'm unable to boot the phone unless it's plugged into a USB port.
Now for the real problem. I was rooted, and I used creepy's guide on how to get the phone ready for warranty replacement. Everything seemed to work fine, but when the phone rebooted, I started getting force closes on google services. Because of this, I'm unable to proceed through the initial setup.
I'm 99% sure I need to do a factory reset, but I'm unable to do this through any of the usual mediums. I obviously can't do it from the menu in the phone since I can't get there, and I'm unable to boot into recovery. When I hold vol up/down and power, I never get the initial boot screen - it just goes straight into Odin every time.
Any ideas on how I can factory reset this phone any other ways? I realize I can *probably* just take it back to ATT how it is now, but I want to be sure that I wipe it to remove any remaining traces of rooting. Hopefully I can get this figured out today, so I don't have to be without a working phone!
Thanks!
Well you can get into Odin which is good. I know you said it doesn't recognize the charger, but does Odin recognize your phone when it's plugged in during download mode? If so, just flash back to stock and don't even bother with the set up.
Yeah, Odin is fine. I flashed back to stock using the zip in this thread, and that's how I got where I am now.
I won't have any warranty issues if I take it back like this? Basically, once I flash the zip here, there's no evidence of rooting? I never tripped the flash counter or anything.
Yeah, if youre on stock firmware and there is no app called "superuser" on your phone, youll be fine.
Interesting I had a similar issue just recently and it got worse over time.. I actually keep the extra best buy warranty just because they will do a no questions asked swap. But this makes me wonder.....
Sent from my SAMSUNG-SGH-I777 using xda premium
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
daveyp225 said:
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
Click to expand...
Click to collapse
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
I can't help you that
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
Re install your drivers then try again
Sent from my SCH-I545 using XDA Free mobile app
Sounds like a total brick to me. There are jtag services. I bought the equipment myself to jtag for a hard brick but my warranty company decided the replace my phone after all so I didn't have to use the equipment. Mine did the same exact thing. Wouldn't even get warm when plugged into the charger.
So, I'm im at a loss here... I haven't done anything to my phone today other than turn on the Webserver at Boot function in Adaway, which I'm guessing is the culprit here... but based on my inability to fix that, which I've fixed Xposed issues before, I'm not confident.
so I'm bootlooping on LG screen primarily, phone was working fine next minute it was off and wouldn't turn on. Took battery out, etc... thought it was the batteries at first, charged both fully, continued troubleshooting. Rebooted a few times it'd boot, show my unlocked Bootloader screen, continue as if going to TMO screen, back to LG screen.
So I tried to boot into TWRP via Factory Reset method. I follow the prompts and then the screen locks, randomly the bootloader unlocked dialogue reappears.
Computer previously recognized device via ADB, now it does not, even with updated drives and ADB/Fastboot. Had the device install itself a few times when plugged in, did not help.
I was able to boot into Fastboot one time, while in there I thought maybe it's an issue with TWRP, so I reflashed TWRP 3.0.1 through fastboot and ran fastboot with the twrp image command... screen locked and nothing happened.
I'm not sure what to do at this point without Fastboot being accessible through computer or regularly through manual method. TWRP is pretty much,... man I don't even know where TWRP is at this point it hasn't made a single appearance in this troubleshooting session.
Any ideas I'm missing?
LGv10
Lollipop 5.1.1, Rooted, Xposed v85 TWRP 3.0.1
If you can get fastboot working again try to just boot twrp rather than flashing it
fastboot boot nameofrecovery.img
Other than that try using lgUP to flash rooted MM if you can get pc to recognize phone
Sent from my LG-H901 using XDA-Developers mobile app
demkantor said:
If you can get fastboot working again try to just boot twrp rather than flashing it
fastboot boot nameofrecovery.img
Other than that try using lgUP to flash rooted MM if you can get pc to recognize phone
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
hey bud - thank you for responding. I actually by the grace of god, just got my phone to boot into fastboot mode again. It wouldn't even turn on since I wrote this post so I've just been browsing for alternatives. Literally on the LgUp page as we speak thinking that's going to have to be the route I take even if I lose all my data... at least I won't have a brick. I ended up using a method I've been trying all day, it's weird how it's hit or miss on when it works... held volume down and plugged in USB, not sure why it's working randomly even tried other computers, ports, cables... anyway thanks !
demkantor said:
If you can get fastboot working again try to just boot twrp rather than flashing it
fastboot boot nameofrecovery.img
Other than that try using lgUP to flash rooted MM if you can get pc to recognize phone
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
I Knew i was going to leave something out, if I flash rooted MM, couldn't that make things worse if I'm on TWRP for LP. I'll read the instructions on the up page, but at first glance I didn't see them talking about specific recoveries like on the eliminator thread..
You can follow toungkick's method and flash the .tot and kdz to get rooted mm, this will include the proper recovery
Choice is yours on the method but this way is smooth and rooted MM is great on this phone
But yeah, data will be wiped,
If you manage to make it into recovery you can try and dirty flash current ROM on top (no wipe) and see if that fixes things first so you don't loose any data
Sent from my LG-H901 using XDA-Developers mobile app
demkantor said:
You can follow toungkick's method and flash the .tot and kdz to get rooted mm, this will include the proper recovery
Choice is yours on the method but this way is smooth and rooted MM is great on this phone
But yeah, data will be wiped,
If you manage to make it into recovery you can try and dirty flash current ROM on top (no wipe) and see if that fixes things first so you don't loose any data
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm honestly losing my mind over this one, I've gotten into Fastboot several times but never long enough to flash much of anything. LGUP won't recognize device and the method to get it to recognize the device by removing the battery isn't work. So I tried manually flashing images in Fastboot and also tried Nexus Root Toolkit as a last ditch effort.
The further I've gotten is flashing TWRP again, and reflashing a boot image...
Believe it or not I just booted into TWRP, it wasn't easy at all but the phone finally went through following the factory data reset method... I was in there for maybe 7 seconds and then screen went black and phone powered off.
I'm getting to the point where, since it fully booted once, booted into fastboot, booted into TWRP, I'm not convinced this isn't hardware related? But I'm not an expert there.
The only way, literally that I can get it into Fastboot is to take the battery out entirely, hit power a few times to drain it, hold volume down insert cable... the screen comes on with the battery indicator but it flashes a red question mark and I simultaneously throw the battery in while holding down volume... and fastboot boots right up ... I only have a few minutes each time and even though things are successfully clashing (I also erased the cache) nothings working.
I was in TWRP long enought o know that it appears all my data is still in there, was hoping to get to Xposed to delete... maybe I'll look into the xposed uninstall zip and see if that helps but really.... wondering if my batteries got screwed up somehow with these new cables I'm using. never read anything quite like this one
Closing loop here. Phone bricked for sure. Got replacment on warranty. Back up and running rooted MM tho with jun method.
klark1kent said:
Closing loop here. Phone bricked for sure. Got replacment on warranty. Back up and running rooted MM tho with jun method.
Click to expand...
Click to collapse
What happened to the original phone?
Phone died on me, and now I'm stuck on the LG logo. Not actually fully booting.
dinggus said:
What happened to the original phone?
Phone died on me, and now I'm stuck on the LG logo. Not actually fully booting.
Click to expand...
Click to collapse
I was never able to get it to boot. Even tried flashing through lgup and it would never make it through.. I took it to tmobile and got it replaced through warranty. Cost 5 bucks. You can manually boot into fastboot or download mode and flash images if your phone will stay on long enough
Im afraid my phone did the same thing. Ive done all of what you mentioned. I guess i have no other choice but to go to T-Mobile and exchange it. You say it only costed you 5 bucks? How is that..? I thought after you void its warranty ... U'd pretty much be stuck wid ****.???
lokz831 said:
Im afraid my phone did the same thing. Ive done all of what you mentioned. I guess i have no other choice but to go to T-Mobile and exchange it. You say it only costed you 5 bucks? How is that..? I thought after you void its warranty ... U'd pretty much be stuck wid ****.???
Click to expand...
Click to collapse
I found this page (https://guidebelajar.blogspot.com/2015/12/guide-to-flash-bricked-bootloop-lg-v10.html?m=1) and am currently in the process of 'refurbishing' via LGUP.
I was able to get into download mode using the following method
"Now turn your LG V10 H900 (AT&T), H901 (T-MOBILE), VS990 (VERIZON) phone off, then click continuously on the up volume and connect your phone to your PC, "
lokz831 said:
Im afraid my phone did the same thing. Ive done all of what you mentioned. I guess i have no other choice but to go to T-Mobile and exchange it. You say it only costed you 5 bucks? How is that..? I thought after you void its warranty ... U'd pretty much be stuck wid ****.???
Click to expand...
Click to collapse
Man I'm sorry I must have notifications off... It was covered though the manufacturer warranty so they only charged me 5
Sent from my LG-H901 using XDA Labs
Explains this... Glad I wasn't crazy but damn LG
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Sent from my LG-H901 using XDA Labs
I was playing with it, wanted to root it and boot into twpr, but before i could do any of that, i was stuck in recovery mode! First time i restarted it into recovery to figure out how to get into twpr, i got to this screen, entered my pin 3362 and proceded to next menues, didnt find what i wanted so i selected enter to recovery again, phone restarted got to this screen again, but now my touch screen isn't working! I cant type anything! And i cant get past it! I can sthut it down, restart it, go to fast boot mode, but everything leads me to this recovery screen again where my touchscreen isnt working and i cant type my pin or anything!
DAMN THESE CHINESE SOFTWARE ENGINEERS.... i will give my phone back using warranty claim, hopefuly those morons wont fix it and ill just get a new one.... but maybe they will just give me big .I. because i live in corrupt country where law means nothing, so i wanna try my luck here.... anyone have any idea how to fix this?
I'm a newby in this things, once i menaged to unbrick my old chinese phone elephone P something, it took days of googleing trials and errors, but i menaged to install new android version which wasnt supported by my elephone.... but microphone didnt work tho xD So yall need to explain things to me in details coz im pretty noobish, but i can menage....
Man... this sucks so much..... how bad could these engineers be, i cant be first person this happened to, and this is surely a bug that isnt fixed, and i kept my phone up to date.
Happens to me as well. You can still use the volume keys to navigate around; however, you may not be able to go back once you select something. Unfortunately the only way I got around it was by installing a diff recovery, either twrp or the pixel experience recovery kronflux uses.
Don't use twrp on this phone.
Seriously. Do not.
Also, that's not recovery. That's your bootloader menu and only works through using your volume keys and the power button.
(Side note, warranty won't cover a modified device and attempting to turn in a device that's been altered can hurt later attempts at using your warranty for legit concerns.)
ninjasinabag said:
Don't use twrp on this phone.
Seriously. Do not.
Also, that's not recovery. That's your bootloader menu and only works through using your volume keys and the power button.
(Side note, warranty won't cover a modified device and attempting to turn in a device that's been altered can hurt later attempts at using your warranty for legit concerns.)
Click to expand...
Click to collapse
There are 2 pictures, second one is bootloader, yes i navigate using volume buttons, first one is recovery that asks me for password, which i can't type, because ''screen'' stopped working, and i cant get pass these screens. Did you even read my post or just saw it with left eye and decided to type a comment so i have to repeat what i allready said?
Anyways, i returned phone under warranty, and i didnt get to root it with twpr even tho that was what i was trying to do, but phone bugged out on me beforehand. Hopefully they wont give me any problems because i did ''install'' twpr in os, but that probably means nothing as it doesnt really do anything at that point.
I was following tutorials i found for this specific phone, probably bullcrap generic articles, i wont try to root it again because it seems like a problem, **** oneplus....
But, if they dispute my claim and ask for money, they wont get any, i will ask them to return the phone to me and i will manually flash it completely or whatever, and get it working. I was refraining from doing so because its under warranty and i didn't want to **** it up.
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Aks said:
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Click to expand...
Click to collapse
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
suhas2k said:
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
Click to expand...
Click to collapse
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
suhas2k said:
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
Click to expand...
Click to collapse
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
tom1807 said:
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
Click to expand...
Click to collapse
Yes, for past 8 months I was updating with root using adb side load so yes, both fastboot & adb drivers are properly installed.
Lughnasadh said:
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
Click to expand...
Click to collapse
Looks like you are right, it's ARB issue.
I did try contacting the B2X Service Centers in India and they only service now 6a but not the 6.