Due to some recent issues users have been having, Im posting this notice to warn users that using Clockwork Mod Recovery *MAY* render your phone unusable. IE: an expensive *but lightweight* brick.
This isn't an ANTI-ClockworkMod post but just a warning that some users have been having issues with the Recovery which has bricked their phones.
Hope this doesn't happen on your eris,
-CK
Related
To start off with I have had my phone rooted since my g1 in 2009. I did not hesitate to root my mytouch earlier this month and it was successful. Unfortunately, my phone would no longer boot (not turn on at all) after a week of being rooted. I am not sure if rooting caused the error but now I am afraid to root my replacement. I wanted to at least flash my backup but I am afraid to even root for that. Also I should add that I root to flash roms not because I think it's "cool". Can anyone give me advice on if I should root again?
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
tenbeau said:
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
Click to expand...
Click to collapse
Yeah, I had flashed the hd port after using the z port and that's when the issues started. I think I will root again and just try to be more careful even though i am pretty sure I followed all instructions.m
Sounds like to me it was just timing between phone hardware and your flashing. Unless you are screwing around with with the ROMs prior to flashing without knowing what your doing you should have no issues. If it was ROM related you would see these boards all lit up with people having the same issues...and you simply dont see that.
Hey guys, I've run into an issue while attempting to flash a custom rom to my i337. First off, I was successfully able to obtain root and have verified that I have su privileges. My issue is happening when I try to install any type of boot loader. I've tried the following methods to install a bootloader:
http://forum.xda-developers.com/showthread.php?t=2314494 (step 3- both methods)
http://forum.xda-developers.com/showthread.php?t=2297033
using odin to flash .img recoveries using this conversion method http://forum.xda-developers.com/showthread.php?t=2281287
Whenever I install any recovery and I try to boot into it, I boot into odin/download mode. After this happens I am unable to boot into the stock rom (or any rom for that matter) until I use this (http://forum.xda-developers.com/showthread.php?t=2360859) method to restore my current rom.
Additionally, I have been unable to perform a factory or soft restore since I've had this issue. I can't boot into recovery so I can't do a hard reset, but every time I attempt to restore within the android OS, I boot into odin mode....
It's become quite frustrating and I'm unsure of where to go next.
Additionally, additionally, I do believe that I have the MF3 update installed. I could be wrong, but I'm pretty confident I do.
I just got this phone a few weeks ago and I'm still learning the ropes here... so forgive me for my lack of knowledge on the subject
Thanks in advance for any input
If you have mf3 you can not flash roms or put on a custom recovery. In fact you'll lucky you haven't bricked your phone. Don't try any more until an exploit is found.
Edit, in the mean time, do some more reading and research. You need to know a lot more before you are ready to flash anything if the devs find away to put a custom recovery on.
I just don't understand why people that don't even have a basic concept of how their phone works would do something to it that could (and probably will) turn it into an expensive brick? Is it really to difficult to do a little reading first? It's forum rules, it's common sense, and it can save you a lot of time and trouble. I'm not trying to bust the OP's balls, but if you don't take a little time to be responsible for your own actions (searching and reading and reading some more), you get what you deserve. Being "new" is never an excuse, it's just more reason to do some reading. Everyone, don't touch your phone until you learn about what it is you are doing to it first!
Good luck to the OP, I hope you decide to read (at least) the pinned threads in the General section (and hopefully a lot more) before you do anything else to your phone.
Sad but true
Sent from my SAMSUNG-SGH-I337 using xda premium
HI GUYS !!BRICKING has been the term which all android lovers hate.after bricking our top notch device get reduced to a mere paperweight (or maybe can be used in place of bricks in ur house)..bricking has become very common these days and its happening by very small faults of ours which we many time ignore.
so guys in this thread i will be discussing how you may brick your phone,so please be carefull and avoid these scenarios as far as possible
[1] ROOTING
rooting has always been the top position holder when it comes to bricking phones mainly beacuse we are all tempted to gain control over our devices and end up bricking our devices. so as far as possible don't root your phone unless you cant live without rooting.if you want to root go to a well known website like xda developers and see the procedure carefully and see if your device is supported or not
[2]CUSTOM ROMS/KERNELS
never ever install/flash roms or kernels which are not meant for your device,many times if you are unlucky the recovery and fastboot files get corrupted and you cant even flash the stock firmware causing a hard brick which can be recovered only by a developer or changing the motherboard
[3] FORCE POWER OFF WHEN SYSTEM UPDATE IS IN PROGRESS
system updates are treats for us,they give nice new features.big system updates take time to install and we must have patience,many times we force power off our device when system update is in progress thinking that the process is stuck at some point.NEVER DO THAT. it will hard brick your device and may damage the motherboard beyond recovery
[4] BATTERY LOW WHILE INSTALLING A UPDATE
this issue is quite similar to above.android recommends charging your phone to 15% but i would say that CHARGE YOUR PHONE ATLEAST TO 50% before doing a update,if your phone goes off while flashing it might never come back
[5] INSTALLING SYSTEM UPDATE WHILE BEING ROOTED
this is the most common mistake many users make. NEVER UPDATE SYSTEM IF YOUR PHONE IS ROOTED
always un root and then do the update.
[6] FLASHING WRONG RECOVERY AND FASTBOOT WHILE INSTALLING STOCK FIRMWARE
never flash worng recovery with a firmaware.if your recovery/fastboot files get corrupted then it will be very difficult to save your device
[7] INSTALLING XPOSED FRAMEWORK/CUSTOM RECOVERY
xposed is a pretty well known feature and if you have rooted your device then you may try to install it but be carefull.THE METHOD OF INSTALLING XPOSED IS A BIT DIFFERENT FOR x86 DEVICES.
and the same goes for custom recoveries like twrp or cwm DONT JUST DOWNLAOD ANY RECOVERY YOU FIND AND FLASH IT.
the recovery files first need to be optimised for devices and then they are safe to flash.
[8]UPDATING THE SYSTEM WHEN THE PHONE IS ENCRYPTED
you should never perform a system update when your phone is encrypted.it may hard brick your phone..
always remove encryption and then perform system update
IF UNFORTUNATELY IF YOU HAVE COMMITED ANY OF THE ABOVE CRIMES THEN HOW SHOULD YOU SAVE YOUR PHONE??
REMEMBER THE GOLDEN RULE= IF YOU BOOT IN FASTBOOT YOU CAN SAVE YOUR PHONE, ELSE I DONT KNOW....just kidding
[1] IF YOU ARE ABLE TO BOOT INTO FASTBOOT= SEE THIS--http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
[2] IF YOU ARE NOT ABLE TO BOOT INTO FASTBOOT(maybe stuck on usb logo)--see this: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800 it is written by asus guys and will help you
and please note that not hitting thanks will lead to a zombie apoclypse dont forget to hit thanks
Ok, so I've been lost as far as for what is going wrong with my device, I managed to downgrade to VS99513b from the 14b update through kdz, and I got TWRP installed successfully, but when I install ANY custom rom made for my device it gives me graphical glitches on the Boot logo, and even when it boots into the actual OS itself?
I don't know what's causing this, I mean TWRP looks to be just fine while I'm flashing these ROMS I did make a back-up prior, but I'd prefer a custom firm if I can get it any suggestions, or any explanations would be nice
Ok, I found the issue
It had to do with the kernel somehow? I just successfully flashed a Rom, and repeated the steps with a previously "broken" rom the only change is my use of a Stock Kernel Mod zip which seems to fix the graphical bug entirely... why that is I don't know, but hell if it works IDC
ProtoPropski said:
Ok, I found the issue
It had to do with the kernel somehow? I just successfully flashed a Rom, and repeated the steps with a previously "broken" rom the only change is my use of a Stock Kernel Mod zip which seems to fix the graphical bug entirely... why that is I don't know, but hell if it works IDC
Click to expand...
Click to collapse
this has been discussed so many times is why no one is responding.
if you googled v20 and static screen you would have had 1000 posts discussing this or even when you read disclaimer on root.
The static is due to changing your aboot aka bootlaoder for the us996 unlock one, casuing ALL stock boot.img to display static. Fortunately months after root had been released the devs developed fixes to hide static and return a normalish boot experience. with the exception 1st boot takes a little longer.
The static can be overcome by locking screen after bootup, then covering the proximity sensor until 2nd screen falls asleep then unlock and use as normal.
This was the initial fix that was the ONLY way to use the device after root, but now most stock kernels being built include the fix, and dont require this.
Hope this helps, and i dont mean to be rude by my response but theres a ton of this info everywhere on the forum and these questions that have been asked 1000 times wont keep getting answered. Please use the search function or read the disclaimers us devs are putting out there before using the methods to gain root and be using cfw.
Team DevDigitel said:
this has been discussed so many times is why no one is responding.
if you googled v20 and static screen you would have had 1000 posts discussing this or even when you read disclaimer on root.
The static is due to changing your aboot aka bootlaoder for the us996 unlock one, casuing ALL stock boot.img to display static. Fortunately months after root had been released the devs developed fixes to hide static and return a normalish boot experience. with the exception 1st boot takes a little longer.
The static can be overcome by locking screen after bootup, then covering the proximity sensor until 2nd screen falls asleep then unlock and use as normal.
This was the initial fix that was the ONLY way to use the device after root, but now most stock kernels being built include the fix, and dont require this.
Hope this helps, and i dont mean to be rude by my response but theres a ton of this info everywhere on the forum and these questions that have been asked 1000 times wont keep getting answered. Please use the search function or read the disclaimers us devs are putting out there before using the methods to gain root and be using cfw.
Click to expand...
Click to collapse
I was looking up info on "LG V20 Graphical Glitched Boot Screens" prior to posting this, and in that process I had only found one dead post, trust me I looked guess the search term I used was too descriptive, or uncommonly used? thanks for the reply though, I kinda fixed it on my own (by accident) through patching in a Stock Kernel Mod through TWRP after writing a fresh VS995 custom ROM it's all good now, my last post wasn't a bump, it was a poorly explained solution lol
Sry, I'm still not use to how this forum is ran, I kinda bounce between forums like a drunk whore on prom night
Link To Kernel Mod Used | ModStock
Hey guys I just want to let you all know that after installing 1 new Rom (upgraded from MM to stock Nougat that worked great) and then messing it up (build.prop) and restoring my phone to backups in TWRP caused my phone to fail with black screen of death.
This is a direct result of restoring back and forth from MM and Nougat FULL TWRP backups. I think I restored backups about 4 times and the last time (5) it restored fine then went to reboot and then the phone was totally unresponsive. No fastboot, download mode, TWRP or IMEI screen, nothing whatsoever works. The only thing that does work on the screen is the battery ? when no battery inserted on USB.
I just want to put this out there so that people realize that they should be careful and not flash and restore and whatever else many times without possible consequences of damaging their LG G4 permanently.
Everything was working great when I first unlocked and flashed a upgrade to Nougat and I just had to mess with things and screwed it up. I figured from using Moto phones in the past that you could flash multiple different roms and restore as you please without any issues but not the LG G4...
Every thread about all the roms and kernels all say that you can damage your phone and it will break etc so this is not saying that I wasn't warned over and over before following different guides or procedures.
Thanks for all the fun and now the phone is off to LG warranty and fingers crossed and I will see what they say and post updates here.
Correlation does not equal causation. You may well have encountered ILAPO
As you, I tried a Nougat rom but I restored my phone to stock because I didn't have LTE. Sometimes, I had to restore more than once to get it back to stock (MM).
My LG G4 is the only cellphone I got so many problems to restore. When I had my HTC Sensation, I restored it so many times I can't count and it never bricked!
The effect can happen when you
... flash/restore a stock aboot after UsU'd
... flash/restore the bootloader stack but not completely
... have not taken care of the ARB! Especially when flashing and testing several stock ROMs.
All 3 types can be recovered by my sdcard unbrick if you know your highest flashed ARB. But LG will repair it anyways.
Sent from my LG-H815 using XDA Labs
obvious said:
Correlation does not equal causation. You may well have encountered ILAPO
Click to expand...
Click to collapse
Exactly I just hope my post makes people a little more careful than I was.
Well for all the LGE bashing and disappointment, I have to give props to the warranty service of LGE!!! Sent from BC to ON on friday and had the phone back in my hand with mainboard replaced by wednesday! So that's 5 days including the the weekend!
So now I am back unlocked running Nougat stock rooted. The only hickup was the phone is no longer carrier unlocked and restoring the modemst's didn't work because of the new IMEI. The company I purchased from (Easycell in Vancouver) gave me a new code in a few hours!
Now I am being very conservative on doing TWRP cache and dalvic wipes, and so far I have just flashed to stock Nougat and done one TWRP backup. I think that should do it for a while!
Cheers!
HAHA damn I permanently SIM locked the phone by screwing the code up! Restored backup of MM and unlocked the network. So letting phone cool down and then re-flash Nougat. I first tried to restore the EFS but didn't work. Well fingers crossed I just want stock Nougat and be done (at least for a while LOL)!
The title of your thread implies that multiple TWRP restores have "caused" your brick. I for one, have done multiple TWRP restores on my UsU unlocked H812 with not even the slightest issue arising as a result. The title of your thread is totally misleading IMO and not warranted.
I believe your problem lies solely with going off script somewhere, i.e., more likely a result of operator error for one of the reasons steadfasterX suggests in his post # 4 above. As obvious correctly notes in post # 2 , Correlation does not equal causation ...
Your thread would be better titled: "Be careful with what you are flashing with TWRP as you may not be able to restore properly when you have royally screwed up by flashing what you did".
sdembiske said:
The title of your thread implies that multiple TWRP restores have "caused" your brick. I for one, have done multiple TWRP restores on my UsU unlocked H812 with not even the slightest issue arising as a result. The title of your thread is totally misleading IMO and not warranted...
Click to expand...
Click to collapse
Good point! I didn't even realize I left out flashing of ROM's and yes it sure isn't a TWRP problem. I didn't flash all kinds of ROM's all carelessly, just stock a few times with some restores of backups.
I just wanted to try and prevent people from possibly having the same issue (I have warranty others might not) as I did with my particular device.
Cheers!
grantdb said:
Good point! I didn't even realize I left out flashing of ROM's and yes it sure isn't a TWRP problem. I didn't flash all kinds of ROM's all carelessly, just stock a few times with some restores of backups.
I just wanted to try and prevent people from possibly having the same issue (I have warranty others might not) as I did with my particular device.
Cheers!
Click to expand...
Click to collapse
I note that you flashed the LuPuSv2.4 kernel (I presume for the H811) to do your stock restore on the H812. While it did work when I flashed the same kernel, I felt the restore ran with higher than normal temperatures - it is possible, with the higher temperatures, that you did overheat and trigger ILAPO with one too many restores but I still feel it is more likely you flashed a rom other than those posted in steadfasterX's OP in the bootloader unlock thread that led to your brick whether because of the arb version or bootloader stack in the rom.
sdembiske said:
... but I still feel it is more likely you flashed a rom other than those posted in steadfasterX's OP in the bootloader unlock thread that led to your brick whether because of the arb version or bootloader stack in the rom.
Click to expand...
Click to collapse
For ROM's I only flashed was the v29a listed in steadfasterx's thread (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip), thats it no others. I can say the arb was 0 when I unlocked the bootloader however I didn't check it again after that but that ROM is supposed to be for any arb.
Anyways I am happy to be back on stock 7.0!
Peace!
the G4 is a proven dog, prone to bootloops and intense heat, even while idle.
Mine has had 3 refurb roundtrips to LG Texas, 2 in the last month; with perhaps 10 roms tried.
Now that I have it back, other than TWRP, I have it pretty close to OEM (20x) with no custom, just some hidden and disabled apps via Apex.
When I bought these phones they were pretty fresh to the market yet were half off. I think LG knew they had a dog and did their best to dump it and the V20 after.
My HTC Sensation had no such issues and my 5yo HTC M7 is still my back-up working admirably while the G4 was at refurb.
While I'm glad LG "refurbed" my phone I am very disappointed with LG. Prior to smart phones, the half dozen flips I bought were LG.
My wifes G4 was also refurbed, but because it got trashed. She paid for her refurb, which I suspect was a new phone.
It has never had any issues. My experience says that at least a couple of LG phones were released not ready for prime time.