Related
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol : http://forum.xda-developers.com/showthread.php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
[/COLOR]
MaE_sTrO said:
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol http://forum.xda-developers.com/show....php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
Click to expand...
Click to collapse
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
thoctor said:
[/COLOR]
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
Click to expand...
Click to collapse
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Roberto Nigel said:
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
Click to expand...
Click to collapse
Thanks Roberto
that's the exact way i tried to disable write protection, and that's when it all went wrong, but i retried it now it went smooth, but i think it didn't work , is there anyway to make sure if it's enabled or not ?
MaE_sTrO said:
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Click to expand...
Click to collapse
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
thoctor said:
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
Click to expand...
Click to collapse
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
MaE_sTrO said:
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
Click to expand...
Click to collapse
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
thoctor said:
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
Click to expand...
Click to collapse
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
MaE_sTrO said:
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
Click to expand...
Click to collapse
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
Click to expand...
Click to collapse
Just flashed TWRP.
tried to update binary same thing happend but now i see in TWRP when it tries to update it says no MD5
thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
Click to expand...
Click to collapse
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
MaE_sTrO said:
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
Click to expand...
Click to collapse
No problem , Don't worry about the permissions for now. The MD5 is the checksum that verifies the file isn't corrupt but if you got it from the chainfire site your fine. Try to update the binary thru twrp or in the SuperSU app and select your recovery as the way you want to update and see what happens.
Also did you have MD5 check enabled in TWRP? I do in mine for file verification but just wondering what yours was set to when you got that notice. It shouldn't stop SuperSU from flashing either way it's just a file verifier.
---------- Post added at 12:56 AM ---------- Previous post was at 12:18 AM ----------
the binaries are what SuperSU uses to get and maintain root . If they are incomplete or corrupt then they have to be reflashed over with an uncorrupted version. That is usually why people keep getting the notice to update the binaries and when they do they can't because they are not complete or corrupt and need to be totally removed i.e. reflashing, which you did, or unrooting from the SuperSU app itself and redownloading again from the play store. This is what I've read on several help sites for this issue. Just wanted to pass along the why not just the what.
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
MaE_sTrO said:
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
Click to expand...
Click to collapse
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
thoctor said:
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
Click to expand...
Click to collapse
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
MaE_sTrO said:
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
Click to expand...
Click to collapse
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom when I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_ul European version
Better than what I first linked us this forum page from Nukaru a few posts down in this forum for the stock a5_ul. He had links to both the stock recovery and stock rom file with detailed instructions on how to get the stock rom back on your phone. I know it works because he had a problem and figured all this out himself then wrote a detailed tutorial on how he fixed his. Link below.
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835/page2
thoctor said:
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom even I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_up European version
Link to stock lollipop rom below
https://www.androidfilehost.com/?fid=23991606952595166
Click to expand...
Click to collapse
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
MaE_sTrO said:
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
Click to expand...
Click to collapse
No, hold off on that first link I have a better one buddy. Just edited it above. No, "relocked S on" is what it's supposed to say so your fine but don't lock it yet or if you already did unlock it using the same unlock token you used on htc developers to unlock it in the first place . Then you flash back your stock recovery. Then relock your bootloader. Then you flash back your stock rom in that order.
thoctor said:
No hold off on that first link I have a better one buddy. Just edited it above. No relocked S on is what it's supposed to say so your fine but don't lock it yet orv I'd your already did unlock it using the same unlock token you used on htc developers to unlock it in the first place .
Click to expand...
Click to collapse
Alright downloading now...
Hello everyone.
I am newbie here.
I own t-mobiles lg g3 and updraded to marshmallow as the ota updates became available. But due to certain reasons, i wanted to install custom rom. The primary hurdle was rooting the device. Through trial and error method i have now successfully installed the fulmics 5.3.
I want to share my experience in this regard.
Device : d851 ( t-mobile lg g3)
Software veesion : 6.0 official marshmallow.
Root :-
Through mobile's browser, google for kingsroot. Download and install. ( donot reboot as this is temporary root, one the cell is rebooted the device will regain its previous status).
download twrp.image for d851 and save in sd card.
Now download flashify from play store and open the app. It will give three options. Select the first option ( browse image file or some thing like this) and select the twrp file you have recently downloaded. The flash will b completed in few seconds.
Congratulations, you have installed twrp.
Download a copy of custom rom ( fulmics 5.1 recommended) and save in sd card.
Now reboot the device in recovery mood ( either by turning off the cell, and then pressing simultaneously volume down+ power button, as the lg logo appears, release the power key and again press it. You will see two options, select the YES twice.
In recovery mode, first select wipe, advance wipe, system and then slide to wipe. Once done, go back and install the custom rom. After the successful installation, dont select the reboot option. Instead go back and again select wipe, factory reset.
congratulations, rom has been installed.
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
Enjoy the new custom rom.
Thanx.
Sorry for poor presentation and, offcourse, my weak english.
Man! Thanks for this! I have been looking everywhere for a way to do this and you are all the help I needed! Thank you!!!
If i may ask you, where can we get the modem and which one do you recommend? I have tried this and always i get the imei, baseband and number unknown
Enviado desde mi LG-D851 mediante Tapatalk
imrock666 said:
If i may ask you, where can we get the modem and which one do you recommend? I have tried this and always i get the imei, baseband and number unknown
Enviado desde mi LG-D851 mediante Tapatalk
Click to expand...
Click to collapse
google for this
downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/30D/LG-D85130D-Flashable.Modem.zip
Sure could have saved a lot of time if I had found this first.
I did install TWRP using a kingroot temporary root, got lost in a boot loop installing Fulmics 5.1 lost my data connection and imei information and finally downgraded back to stock Marshmallow feeling blessed to have restored my data connection. Had just finished transferring the flashable modem zip over to the SD card with an idea that I would try to move the mountain once more when I stumbled across your post which is priceless with the wealth of solutions to the problems I've had to overcome with the install. Flashify was the route to go. Lost TWRP on last flash and was just about to go through my torturous route of installing Fulmics 5.1 from scratch (root/adb/twrp/rom/bootable modem/etc.. Instead in the time it took to sign up so I could thank you for the easiest directions to this LG G3 D851 nightmare, I'm up an running on Fulmics 5.1 with full data connection. Your method eliminated a lot of the problems introduced by going the other route. Also you highlighted the main things. The factory reset is crucial and with the tricky temp root of Kingroot, it's easy to get stuck. Same with SuperSU flash/WRP and the modem flash. This should be a sticky on most sites related to LG G3 because it is the simplest way to go.
Jesus christ! Is this the only way to root my t-mobile D851? Seems like this is a dangerous way to live! Lol. But Really...
thank you, i will try it could you please give me fulmatic 5.3 room link for (d851)
Thanks for sharing
I am a newbie and do not have much experience with rooting or installing flash. But I followed your instruction and installed the fulmics.. I am struggling to flash the modem file. Can you please provide step by step instruction to do that pls. I am using flashify app
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
I am no expert either, but I believe you need to flash it in TWRP. Boot in to TWRP recovery and flash the modem zip. TWRP recovery-> Install-> modem zip-> reboot when finished
KingoRoot just seems shady to me, I wouldn't touch it personally. Here's what I did (just yesterday), from Stock MM Unrooted:
Downgrade back to original factory stock image: http://www.androidexplained.com/downgrade-lg-g3/
Root (used PurpleDrake "manual" method as auto script didn't work): http://lgg3root.com/lg-g3-root/how-to-root-lg-g3/
Once rooted, install SuperSU & TWRP Manager from Play Store
From TWRP Manager install latest version of TWRP
Boot into TRWP and do a factory reset/clear cache; flash ROM (Blisspop for me, but same general steps should apply for any ROM) and Gapps from TWRP; factory reset/clear cache again for good measure
Edit: Data works with 20B modem.
How to prevent apps from being unistalled in stock rom? In other roms u can lock the package installer .
In stock simply u just hold and drag the app to unistall button . installation of an app can be locked but unistallation cant be locked . is there anyone to solve the issue . sorry for bad english
i flashed another kernel and it is not that good... is it possible to find the kernel and just flash it ? without reflashing the rom?
KingRoot is not working for me, says Root Failed, somebody know why? What can i do?
Shady282 said:
i flashed another kernel and it is not that good... is it possible to find the kernel and just flash it ? without reflashing the rom?
Click to expand...
Click to collapse
You should be able to get the stock kernel back by "dirty flashing":
-boot into recovery (twrp)
-flash ROM *without* wiping anything.
Not to lecture, but this can all be prevented by following this simply advice:
-ALWAYS take a backup before flashing anything/customizing this or that.
-ALWAYS double and triple check that the ROM/Kernel/Whatever you're flashing is for your SPECIFIC MODEL and CARRIER.
Happy modding
Semi Fahid said:
Hello everyone.
I am newbie here.
I own t-mobiles lg g3 and updraded to marshmallow as the ota updates became available. But due to certain reasons, i wanted to install custom rom. The primary hurdle was rooting the device. Through trial and error method i have now successfully installed the fulmics 5.3.
I want to share my experience in this regard.
Device : d851 ( t-mobile lg g3)
Software veesion : 6.0 official marshmallow.
Root :-
Through mobile's browser, google for kingsroot. Download and install. ( donot reboot as this is temporary root, one the cell is rebooted the device will regain its previous status).
download twrp.image for d851 and save in sd card.
Now download flashify from play store and open the app. It will give three options. Select the first option ( browse image file or some thing like this) and select the twrp file you have recently downloaded. The flash will b completed in few seconds.
Congratulations, you have installed twrp.
Download a copy of custom rom ( fulmics 5.1 recommended) and save in sd card.
Now reboot the device in recovery mood ( either by turning off the cell, and then pressing simultaneously volume down+ power button, as the lg logo appears, release the power key and again press it. You will see two options, select the YES twice.
In recovery mode, first select wipe, advance wipe, system and then slide to wipe. Once done, go back and install the custom rom. After the successful installation, dont select the reboot option. Instead go back and again select wipe, factory reset.
congratulations, rom has been installed.
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
Enjoy the new custom rom.
Thanx.
Sorry for poor presentation and, offcourse, my weak english.
Click to expand...
Click to collapse
I did this but got stuck on the LG logo boot screen. What am I doing wrong?
Hello,
I've tried everything that the internet has to offer so far and still can't get the newest version to install on my phone without failing somewhere in the installation process.
I feel like asking for help isn't of much use, because it could be everything.
I tried resetting the phone completely with this guide: http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
After that I wanted to install the update again, and still no success.
Next time you make a thread regarding an issue be kind enough to tell us the state of your phone to the best of your knowledge, whether its working or not? does it show the oneplus logo or not..... these things matter plenty!
judging from the what you have mentioned in your post, your main issues is not being able to install the latest update.
try these steps
1. download this file https://www.androidfilehost.com/?fid=24591000424945019 [thanks to namman bhalla for his thread, http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870]
2. copy and paste it onto your phone.
3. now boot into your phones recovery twrp preferred
4. from there choose the option which says..... click install new zip. and select the zip that you downloaded....
it should work if it doesn't, give us a detailed description of what and all you have done with your phone whether you have unlocked the bootloader, whether there is a custom recovery installer and most importantly whether you have nandroid backup of your device.
ajaysoranam said:
Next time you make a thread regarding an issue be kind enough to tell us the state of your phone to the best of your knowledge, whether its working or not? does it show the oneplus logo or not..... these things matter plenty!
judging from the what you have mentioned in your post, your main issues is not being able to install the latest update.
try these steps
1. download this file https://www.androidfilehost.com/?fid=24591000424945019 [thanks to namman bhalla for his thread, http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870]
2. copy and paste it onto your phone.
3. now boot into your phones recovery twrp preferred
4. from there choose the option which says..... click install new zip. and select the zip that you downloaded....
it should work if it doesn't, give us a detailed description of what and all you have done with your phone whether you have unlocked the bootloader, whether there is a custom recovery installer and most importantly whether you have nandroid backup of your device.
Click to expand...
Click to collapse
I tried using that method and it failed, I can get into recovery just fine and my bootloader is unlocked because I flashed twrp
I have a backup I made in twrp.
I got the official support tool (MsMDownloadTool) and I could restore my phone to 3.1.2 but it still crashes apps and is very unstable.
If I now try to install the update again, or try to flash the full OxygenOS 3.2.1 or 3.1.2 I get the Error 7 ("system partition has unexpected contents").
I dont get this error because the system partition couldnt have been modified, because I didnt even start the phone , I just got into recovery and tried updating it.
I'm losing my mind on this.
Sorry if that was a ramble and isn't understandable
calm down!
boot into twrp, wipe system ,data, cache, dalvik. now try flashing the latest full rom i.e. 3.2.2.
try this and let me know....
if it didn't work give me step by breakdown of what you did.....
DeadlyVirez said:
I tried using that method and it failed, I can get into recovery just fine and my bootloader is unlocked because I flashed twrp
I have a backup I made in twrp.
I got the official support tool (MsMDownloadTool) and I could restore my phone to 3.1.2 but it still crashes apps and is very unstable.
If I now try to install the update again, or try to flash the full OxygenOS 3.2.1 or 3.1.2 I get the Error 7 ("system partition has unexpected contents").
I dont get this error because the system partition couldnt have been modified, because I didnt even start the phone , I just got into recovery and tried updating it.
I'm losing my mind on this.
Sorry if that was a ramble and isn't understandable
Click to expand...
Click to collapse
Hi there,
I have a Huawei Rio L02, Australian Vodafone version.
I wanted to root my phone so I could use the gyroscope feature.
I was following a guide and managed to unlock the bootloader and install TWRP and SuperSU ok, upon trying to install cyanogenmod I got error 7 and it said to wipe the system which i did and still got error 7. (I did not realise at this time the stock firmware needed to be updated to marshmallow before installation) so I wiped the files again and didn't realise until it was too late I had system checked. Now I can access TWRP, but I can not figure out how to install any firmware on the device.
- I have tried multiple stock firmwares
- I have tried the forced update and fastbootloader methods
- I have tried manually installing the files using TWRP
I had a backup file, but unfortunately did not back it up to my pc before wiping my system, stupid and a noob mistake I know.
If anyone has a Nandroid backup of the stock system that would be fantastic (If you can use a same model, but different devices backup)
Any Ideas? Is there an old version of cyanogenmod i could install without any O.S. on the device and would this allow me to update to the newer cyanogenmod?
Would really appreciate any assistance.
Thank you
Easiest way IMO would be to download stock firmware, put it on sdcard in dload folder.
Turn off the phone. Press and hold Vol_ & Vol+, press power button. Huawei firmware update will start. You'll have stock firmawer without root and twrp.
That's why I always keep, stock firmware on sd card in dload folder so can quickly flash stock firmware if something goes wrong
I have Honor 7x BND-L24 (USA version) which is stuck at a screen which says:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Before this screen I had EMUI 5.1 with Android 7.0 installed version BND-L24C567B150CUSTC567D001 and TWRP custom recovery. I wanted to do OTA update so went and installed stock recovery and that somehow damaged my boot image. After factory reset it goes to the screen mentioned above. I can't even turn it off anymore.
I can still boot into fastboot mode, I can still go into recovery by holding both volume buttons and power button but the install always fails and brings me back to the same error screen. Is there any way to fix the boot image error?
Fastboot flashing does not work anymore and gives errors:
Code:
fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (15170 KB)...
OKAY [ 0.395s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.406s
The bootloader is unlocked:
Code:
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
I have also seen in the forums that a dload method (creating a dload folder in the sd card and adding UPDATE.APP file into it) could be used to recover, but it always stops at 5% and fails. Maby I am doing it wrong because the stock ROM has two .zip files (update.zip and update_full_BND-L24_hw_usa.zip) and they both have the UPDATE.APP file in it. If someone could give me a guide on how to propertly use the dload method I would like to try it.
Any additional comments or solutions to try unbricking the phone will be appreciated. Thank you in advance.
P.S. after searching the xda forums it seems that for the dload method I would require a specific rom called the service ROM dload. I have tried searching for it but could only find it for BND-L21, if anyone has a service ROM for BND-L24C567 (USA version) please give me a link, I would like to try the dload method with it.
SOLVED !!!
Thread can be closed. If anyone need the solution on how to fix this issue just send me a message.
Hey how'd you fix it dude? I accidentally broke my boot image and im getting the same error as you did. the only thing i can do is use root shell in stock recovery. I'm trying to figure out how to flash twrp (Ice cream sandwich) to recovery2 but so far no luck.
Can you help me out?
Kr1msonReaper said:
Hey how'd you fix it dude? I accidentally broke my boot image and im getting the same error as you did. the only thing i can do is use root shell in stock recovery. I'm trying to figure out how to flash twrp (Ice cream sandwich) to recovery2 but so far no luck.
Can you help me out?
Click to expand...
Click to collapse
Is your bootloader unlocked and frp unlocked?
if yes then:
Get the stock recovery, boot, system and etc. by going into the OpenKirin website, there is a nice guide there in the support section on how to download and extract the stock recovery and boot images and etc.
Hold down the volume down key and plug in the usb cable. Use fastboot to flash in the stock recovery.
flash them using "fastboot flash" command with the adb and fasboot tool.
if not then:
download Chimera tool.
Pay for 3 day trial (~12 eur)
Do system restore in the application, worked for me. BND-L24 USA version, I now have EMUI 9.1.0 by installing BND-L21 9.1.0.141(C432E2) ROM using the Chimera tool.
Hope this helps.
DBxda7x said:
Is your bootloader unlocked and frp unlocked?
if yes then:
Get the stock recovery, boot, system and etc. by going into the OpenKirin website, there is a nice guide there in the support section on how to download and extract the stock recovery and boot images and etc.
Hold down the volume down key and plug in the usb cable. Use fastboot to flash in the stock recovery.
flash them using "fastboot flash" command with the adb and fasboot tool.
if not then:
download Chimera tool.
Pay for 3 day trial (~12 eur)
Do system restore in the application, worked for me. BND-L24 USA version, I now have EMUI 9.1.0 by installing BND-L21 9.1.0.141(C432E2) ROM using the Chimera tool.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the advice! I repeated the process you provided and so im not bricked, I have all the partitions of ice cream sandwich. The only problem is, the dload method and upgrade from sd card thing stops at 5% and when i use dload, it says image verification failed, because i was trying to upgrade to Nougat. I have the bootloader and stock recovery though. How did you upgrade to pie after doing this?
Also how is pie? maybe I'll install the pie rom for L21 and use english. I actually intall the AL10 once haha. It was horrible. Almost nothing worked and it tried to prevent booting into recovery or bootloader.
Thanks!
-Kr1msonReaper
Kr1msonReaper said:
Thanks for the advice! I repeated the process you provided and so im not bricked, I have all the partitions of ice cream sandwich. The only problem is, the dload method and upgrade from sd card thing stops at 5% and when i use dload, it says image verification failed, because i was trying to upgrade to Nougat. I have the bootloader and stock recovery though. How did you upgrade to pie after doing this?
Also how is pie? maybe I'll install the pie rom for L21 and use english. I actually intall the AL10 once haha. It was horrible. Almost nothing worked and it tried to prevent booting into recovery or bootloader.
Thanks!
-Kr1msonReaper
Click to expand...
Click to collapse
dload method does NOT work on this particular phone. I have tried it multiple times.
Best way is to find the ROM that works for your phone. I have tried a lot of the ROMs for this phone including all of the ones in the OpenKirin website, like the Ressurect, Lineage and etc. those do not work, it just bootloops. But the L21 worked perfectly, only issue is that you need to flash every partition (system, boot, recovery, ram_disk and etc.) and then do a factory reset. If you do not do a factory reset after the installation in will not boot.
Just go to Firmware finder, get EMUI 9.1 ROM, extract all .img files and flash them in using fastboot.
Good luck!
DBxda7x said:
dload method does NOT work on this particular phone. I have tried it multiple times.
Best way is to find the ROM that works for your phone. I have tried a lot of the ROMs for this phone including all of the ones in the OpenKirin website, like the Ressurect, Lineage and etc. those do not work, it just bootloops. But the L21 worked perfectly, only issue is that you need to flash every partition (system, boot, recovery, ram_disk and etc.) and then do a factory reset. If you do not do a factory reset after the installation in will not boot.
Just go to Firmware finder, get EMUI 9.1 ROM, extract all .img files and flash them in using fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for the advice! I'll try it soon, but as far as i know, from here in ice cream sandwich, it says image verification failed when flashing recovery and other partitions except not system or boot and others for some reason.
Actually I've previously installed RR and Lineage ROMs--maybe you forgot that they must not be flashed in TWRP? Anyway, thanks! Pie sounds like it must be the best option here. I'll go ahead and install it. Oh, and just so you know, the dload method can work on the Honor 7x but you have to flash a patched version of the recovery called BND-RECOVERY-NoCheck.img, except I only have the oreo one so it can't help me.
Thanks!
- Kr1msonReaper
DBxda7x said:
dload method does NOT work on this particular phone. I have tried it multiple times.
Best way is to find the ROM that works for your phone. I have tried a lot of the ROMs for this phone including all of the ones in the OpenKirin website, like the Ressurect, Lineage and etc. those do not work, it just bootloops. But the L21 worked perfectly, only issue is that you need to flash every partition (system, boot, recovery, ram_disk and etc.) and then do a factory reset. If you do not do a factory reset after the installation in will not boot.
Just go to Firmware finder, get EMUI 9.1 ROM, extract all .img files and flash them in using fastboot.
Good luck!
Click to expand...
Click to collapse
Hi, I have a BND-L34 (mate se) and could use some help. I'm not very good with rooting but I followed the directions found here
https://www.desinerd.co.in/how-to-huawei-mate-se-root-twrp-recovery/
which was mentioned from this XDA post about unlocking the bootloader and rooting
https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
So I was able to write the TWRP from the guide on the "recovery_ramdisk" but not the second partition like the guide mentioned. So if try to boot into TWRP I get an error 11 and error 2.
Phone appears to be working otherwise.
I suspect that if I were to ever factory reset the phone I would be in the same situation as you were. Could you tell me how you flashed the EMUI 9 files? Like what the commands were? thanks in advance.
teatimecrumpet said:
Hi, I have a BND-L34 (mate se) and could use some help. I'm not very good with rooting but I followed the directions found here
https://www.desinerd.co.in/how-to-huawei-mate-se-root-twrp-recovery/
which was mentioned from this XDA post about unlocking the bootloader and rooting
https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
So I was able to write the TWRP from the guide on the "recovery_ramdisk" but not the second partition like the guide mentioned. So if try to boot into TWRP I get an error 11 and error 2.
Phone appears to be working otherwise.
I suspect that if I were to ever factory reset the phone I would be in the same situation as you were. Could you tell me how you flashed the EMUI 9 files? Like what the commands were? thanks in advance.
Click to expand...
Click to collapse
@teatimecrumpet we have the same phones . . . .
Ok so, first, are you on Oreo or something lower? If you're on oreo I have the proper TWRP img for the ramdisk partition. If you flashed your TWRP to recovery but not recovery_ramdisk, I recommend reflashing the stock recovery and then flashing mine to ramdisk. But you shouldn't worry, you can't even factory reset anyway, if you've overwritten your recovery. So if you say your phone's fine now it should continue to work. I have not yet upgraded to Pie like @DBxda7x suggested, but I will soon.
In any case, here's the TWRP you must flash to the ramdisk.
-Kr1msonReaper
OreoTWRP: https://www.dropbox.com/s/ztzh7hejp3j9fuz/BND_twrp_true_Oreo.img?dl=0
Kr1msonReaper said:
@teatimecrumpet we have the same phones . . . .
Ok so, first, are you on Oreo or something lower? If you're on oreo I have the proper TWRP img for the ramdisk partition. If you flashed your TWRP to recovery but not recovery_ramdisk, I recommend reflashing the stock recovery and then flashing mine to ramdisk. But you shouldn't worry, you can't even factory reset anyway, if you've overwritten your recovery. So if you say your phone's fine now it should continue to work. I have not yet upgraded to Pie like @DBxda7x suggested, but I will soon.
In any case, here's the TWRP you must flash to the ramdisk.
-Kr1msonReaper
OreoTWRP: https://www.dropbox.com/s/ztzh7hejp3j9fuz/BND_twrp_true_Oreo.img?dl=0
Click to expand...
Click to collapse
Hey Krimson, thanks for the reply. It's been awhile since I had that error...it's a bit hazy. But I'm on oreo now and am trying to either downgrade back to nougat or try to flash oreo again. Reason being the phone was working fine but now my GPS doesn't really work and I can't pick up any satellites and I kind of need google maps to work.
I tried to use hisuite to upgrade to the newest firmware and downgrade to nougat but no luck it just boots to TWRP.
When I first rooted I know I flashed recovery and recovery2 (but recovery2 turned out to be erecovery on oreo...I remember it was a pain trying to figure out.)
I can't seem to find a simple guide to follow and like I said I'm not very good with this. Do you think you could give me the commands to either flash what you have or do the pie update? I'm totally fine going back to stock and then trying to root Nougat again.
Thanks!
teatimecrumpet said:
Hey Krimson, thanks for the reply. It's been awhile since I had that error...it's a bit hazy. But I'm on oreo now and am trying to either downgrade back to nougat or try to flash oreo again. Reason being the phone was working fine but now my GPS doesn't really work and I can't pick up any satellites and I kind of need google maps to work.
I tried to use hisuite to upgrade to the newest firmware and downgrade to nougat but no luck it just boots to TWRP.
When I first rooted I know I flashed recovery and recovery2 (but recovery2 turned out to be erecovery on oreo...I remember it was a pain trying to figure out.)
I can't seem to find a simple guide to follow and like I said I'm not very good with this. Do you think you could give me the commands to either flash what you have or do the pie update? I'm totally fine going back to stock and then trying to root Nougat again.
Thanks!
Click to expand...
Click to collapse
Hey, I know it's been a while, it is pretty hazy. I actually got into a situation where i bricked my phone from trying to downgrade from Pie to Nougat directly. Don't EVER do that. If you're on Oreo now, I know that there are some guides on how to use HWOTA to downgrade to nougat pretty easily. Here's the link:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649