Related
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link
If all else fails flash the google stock images
Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...
I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.
Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.
Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.
Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.
If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095
Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5
Stock LG D850 20F Lollipop 5.0.1
This thread is based on my original post found in the AT&T G3 Lounge Thread..
What's new is I've just packed 20F into a flashable zip for those with TWRP already installed. It's not much.. but I know many would prefer not to use ADB or terminal.
What's this thread have to offer?
Flashable/BUMP'd D850 20F "rom" (system/boot)
Flashable D850 20F modem
Stock D850 20F partition images
Patched/BUMP'd D850 20F boot.img
Manual directions for installing TWRP if already on 20F
Manual directions for installing 20F if flashable zips aren't your thing
The above mentioned can all be downloaded HERE ON CODEFIRE
Flashable "rom" directions:
1. Put D850_20F_Lollipop_Stock.zip and D850_20F_2.0.1.c1.13-00050_Modem.zip on sdcard
--For root: Also grab the SuperSU zip from Chainfire HERE
2. Boot into TWRP
3. Hit install button and select each zip file you need
4. Swipe to flash... done. Rom flash will take a bit.. be patient.
5. Reboot phone when rom, modem, root is flashed. First Lollipop boot may take up to 5 minutes.
In some cases you may need to wipe cache/dalvik/data(factory reset) in TWRP if the phone gets stuck on boot animation or if things just aren't acting right. To avoid data loss be sure to use something like Helium or Titanium Backup prior to upgrading to Lollipop. TWRP backups/Nandroids don't hurt either.
Having issues with internal sdcard permissions afterwards? Having issues with downloads not saving? You may need to fix your sdcard permissions. In terminal emulator or adb shell enter:
Code:
su
restorecon -FR /data/media/0/
Some have mentioned external sdcard issues.. not sure if anyone has way to fix that? Maybe same command as above only pointing to ext-sd?
MD5:
85460a3ce5d0259477d2f03c64e867e9 D850_20F_Lollipop_Stock.zip
df2564aa824b35dbaf8bd886b5210b4a D850_20F_2.0.1.c1.13-00050_Modem.zip
Below I am including my original directions for manually flashing Lollipop.. whether completely stock and already on 20F... or already rooted/BUMP'd/TWRP'd.
You do not need to pay attention to any of this below if you are just flashing the rom above... these are the original manual directions only. #learn2read
If you want TWRP just downgrade aboot.img and laf.img to KK.. then BUMP'd TWRP will work. Must be rooted to be able to flash TWRP obviously. If not already rooted -- Root with THIS METHOD HERE or use THIS ONE-CLICK METHOD if typing an ADB command scares you.
If rooted and on stock 20F Lollipop follow #1
If already TWRP'd/BUMP'd on KitKat (or using AOSP) and want to manually update to rooted stock 20F follow #2
#1
Download D850 TWRP HERE and rename to twrp.img. download stock KK aboot and laf images HERE. Stick all 3 on root of internal sdcard. You'll also have to flash a patched stock 20F boot.img so that the Lollipop system still boots when using the downgraded aboot.img/laf.img. You can download the patched boot.img HERE. Stick it in the root of your internal sdcard.
Now issue the following commands with ADB shell. If using terminal app on phone do not use the "adb shell" command:
Code:
[SIZE="2"]adb shell
su
md5 /sdcard/aboot.img (confirm md5 = 348064a6d4f8d5b7d3eeec79d86de5bd before proceeding)
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/patched-20f-boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot[/SIZE]
You are finished and can now reboot back into the rom. You are now rooted, BUMP'd and TWRP'd on Lollipop!
#2
If already TWRP'd/BUMP'd and you want to upgrade manually to 20F Lollipop... download the patched boot.img HERE and stick it on the root of your internal sdcard.. along with the 20F modem.img and system.img. (@timmytim[/MENTION] shared system.img in the lounge thread HERE so be sure to thank him)
You may or may not have to "factory reset" in TWRP. YMMV.
[If flashing system.img you must be in TWRP, not the rom, while issuing these commands]
[May need the "Koush Universal ADB" drivers to get ADB goin' in TWRP]
Code:
[SIZE="2"]adb shell
su
dd if=/sdcard/patched-20f-boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system[/SIZE]
If flashing 20F system via this method you will also need to root since the system.img is stock. Download SuperSU zip from Chainfire HERE and flash the zip in TWRP AFTER flashing the system.img. You are finished and can now reboot back into the rom. You are rooted, BUMP'd and TWRP'd on Lollipop.
Click to expand...
Click to collapse
I used the method 1 since I am already on lollipop rooted. Is this method bumped o mean the bootloader is unlocked?
Sweet first in second in
autoprime said:
Stock LG D850 20F Lollipop 5.0.1
Click to expand...
Click to collapse
I used the method 1 since I am already on lollipop rooted. Is this method bumped o mean the bootloader is unlocked?
Testing now, wish me luck!
****UPDATE****
Downloading files: about 5min
Needlessly moving files to External SD: about 5min
Flashing all three files at once: about 4min
First Boot: about 7min
Optimizing apps YMMV
I wiped nothing
Began this method on Bumpd' 850 from this ROM http://forum.xda-developers.com/att-lg-g3/development/rom-liquidsmooth-v4-0-d850-12814-t2966409 rooted ('natch)
Right on nice job ???
Running On New Deadly Venom Note 4 v1.0
TonyStark said:
Sweet first in second in
Click to expand...
Click to collapse
you can still be first! feel free to remove netomel's first post (post #2) since he's gone and posted it yet again in post #4 as well.
:good:
netomel said:
I used the method 1 since I am already on lollipop rooted. Is this method bumped o mean the bootloader is unlocked?
Click to expand...
Click to collapse
Following method #1 downgrades your bootloader so that BUMP works. If you did method one(#1)... you are BUMP'd/TWRP'd...
BUMP = G3 unlocked bootloader method.
Any kernel's (and roms with new kernels) flashed thru TWRP on your phone will need to be BUMP'd from here on out unless you go back to 100% stock.. including proper bootloader. Most custom zips should already be pre-BUMP'd so that should not ever be a worry.
Anything that needs to be discussed further about BUMP or unlock does not belong here.
gpgon said:
Testing now, wish me luck!
Click to expand...
Click to collapse
Good luck! I don't have a D850 so wasn't able to test :fingers-crossed:
freaksavior said:
deodexed or odexed?
Click to expand...
Click to collapse
100% stock system.
no specified odex/deodex = odex
jaybird38 said:
If I flash this on a stock backup will I still be able to restore stock 4.4 or my cm 12 ROM.just don't want to loose them.
Click to expand...
Click to collapse
louvass said:
noob question. I am rooted kk can I just flash the Rom, modem and su..and I'll be good ? Thank you for bringing us this.
Click to expand...
Click to collapse
Yes to both of the above questions. @jaybird38 to make restoring 4.4/aosp nandroids effortless.. be sure to backup the modem as well. you may or may not need to reflash KK modem when using 4.4 roms. @louvass yes, that's exactly what the flashable zips are for.
rob219 said:
if im already on 5.0.2 illusion rom or any other 5.0.2 rom can't i just flash the rom and modem?
Click to expand...
Click to collapse
yes that's exactly what the directions say... flash rom zip, modem zip and supersu zip.
sandro100 said:
Hi my play store won't download anything, just stays stuck on downloading any help please
Click to expand...
Click to collapse
this can sometimes be fixed by running the following commands in terminal emulator or adb shell:
Code:
su
restorecon -FR /data/media/0
and perhaps a reboot after.
daw41 said:
@autoprime can you share the md5 of the rom zip and modem zip it continues to fail in twrp for me i just want to make sure I have a good copy
Click to expand...
Click to collapse
gordec said:
Can't get pass boot logo after 2 flashes. Can someone post the MD5 for the ROM? I feel the download was complete. Coming from Illusion AOSP ROM.
Click to expand...
Click to collapse
85460a3ce5d0259477d2f03c64e867e9 D850_20F_Lollipop_Stock.zip
df2564aa824b35dbaf8bd886b5210b4a D850_20F_2.0.1.c1.13-00050_Modem.zip
In teh future I may reply to people using this post rather than making a new post just to say "yes" or something...
Sorry to sound noob by it needed to be clarified since I did not see it anywhere but I suspected it was BUMP"d just wanted to be sure before start flashing away roms
deodexed or odexed?
edit: thanks for the update. I assumed it was odexed but wanted to verify. I'll hold off until there is one deodexed for modular packages then.
Flashed and booted up into the setup. Thank you very much!
Next challenge is to port D85520i and get it to pass security checks!
Great work, mate.
Just a heads up, thought most will already know this. Started process at ~100% and ended at 90% battery. Major heat increase during optimization (expected) and debilitating lag for the first ~10min (also expected.) Device is slowly settling down after a reboot.
***UPDATE***
Also probably no surprise to anyone but me, I had to reinstall busybox (even though I did a dirty flash)
Any advantage of the stock LG lollipop? I went straight to CM12 when I got the phone. Wonder if I should try stock out.
gordec said:
Any advantage of the stock LG lollipop? I went straight to CM12 when I got the phone. Wonder if I should try stock out.
Click to expand...
Click to collapse
I mean think about it ....... Stock camera which is always on point ... And now you have a rooted stock lollipop so you can use a lot of root access apps. Maybe XPOSED modules... There are advantages in stock rooted lollipop. Its user preference. I am on Illusion but will probably make a backup of this for safe keepings
Sent from my LG-D850 using XDA Free mobile app
shayneflashindaily said:
I mean think about it ....... Stock camera which is always on point ... And now you have a rooted stock lollipop so you can use a lot of root access apps. Maybe XPOSED modules... There are advantages in stock rooted lollipop. Its user preference. I am on Illusion but will probably make a backup of this for safe keepings
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah. I'm on Illusion too. It's pretty much bug free at this point.
gordec said:
Any advantage of the stock LG lollipop? I went straight to CM12 when I got the phone. Wonder if I should try stock out.
Click to expand...
Click to collapse
tbh, the only thing Stock got on AOSP is the camera. If you want a flawless camera experience then Stock, if you don't mind the average photos and limited options with the camera then I'll stay on AOSP
Appart from the aosp experience that you may like, there are some extra features packed in stock roms such as a better camera, remote controller, dual view, knock code, one handed operation, circle case support and so on... The better camera and remote controller itself are two of my most used features on the phone so stock lollipop is not an option but I have to admit that aosp lollipop has its strong points too such as a more cleaner interface, more battery life, more updated OS... So, it's a decition only you can make.
If I flash this on a stock backup will I still be able to restore stock 4.4 or my cm 12 ROM.just don't want to loose them.
Sent from my LG-D850 using XDA Free mobile app
noob question. I am rooted kk can I just flash the Rom, modem and su..and I'll be good ? Thank you for bringing us this.
eortizr said:
tbh, the only thing Stock got on AOSP is the camera. If you want a flawless camera experience then Stock, if you don't mind the average photos and limited options with the camera then I'll stay on AOSP
Click to expand...
Click to collapse
Exactly this. I've been hoping for cloudy for a long time, but I think i'm about to go back to a stock rom. I use my camera a lot, who doesn't, but the AOSP roms just don't quite cut it. If you do get something like CM, use the Lenovo camera, much better images.
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
dekraan said:
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
Click to expand...
Click to collapse
First off, this thread probably belongs in Q/A.
Moving on:
I've run all 3 provided ROMs, Carbon as my daily driver and Lineage and RR for testing various things. They all work pretty well.
For stock recovery & ramdisk, download your current firmware (or if you've run other Treble ROMs as well, the version that corresponds to your current build number in Settings / System / About Phone) using Firmware Finder - you only need the main update.zip for this. You'll also need one of the utilities for extracting them. There's Huawei Update Extractor (I think that's what it's called anyway) for Windows, or https://github.com/marcominetti/split_updata.pl for Linux / Mac. Extract the ramdisk and recovery ramdisk images and there you go.
Installing those is a matter of rebooting into the bootloader and running:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash ramdisk ramdisk.img
(The name for recovery_ramdisk.img may vary a bit - the windows app will extract it as RECOVERY_RAMDIS.img.)
From there, just follow their instructions. If you have any problems, hit up the Telegram chat linked off the site, someone will be willing to help.
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
dekraan said:
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
Click to expand...
Click to collapse
Like I said in my original reply, my daily driver is Carbon; the Lineage builds I've only run briefly because NFC wasn't enabled, but the CarbonROM builds there have it. I use Google Pay every day, so it's kind of a requirement for me.
With that said, the only thing that's got issues for me is the camera app, and most of the blame for that is with Huawei. It generally works, but it'll close & restart often when switching modes or trying to start a recording.
I know there are various other minor issues with recording video in all 3, again because Huawei. (They put together bum codecs, and then patched the system side of the EMUI media stack to deal with the bum codecs, instead of fixing the codecs.)
Also worthy of mention (especially because I see people asking about this all the time): there is no VoLTE support. The devs are aware of it. Unless you're on a network that is pure LTE, it's mostly a non-issue. If you are, it's probably a deal breaker.
Getting on from there, they're all clean Android experiences, without the overbearing weight of EMUI. They don't try to pull some of the things EMUI did - the final breaking point for me was when it insisted on terminating apps in the background regardless of how much you might actually be using them. (In my case, AdGuard as a VPN service.)
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
talpur1 said:
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
Click to expand...
Click to collapse
Some comments before, Huawei Firmware Extractor. Extract system.img from the stock rom you used before flash Lineage.
Flash stock system.img in fastboot.
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
talpur1 said:
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
Click to expand...
Click to collapse
Go to settings in the app and disable CRC checking. (Bug in the app.)
I was on OldDroid's OpenKirin, but today switched to Carbon Beta 2 from https://openkirin.net/download/. This installed without problems and I did a hard reset as part of installation. The earlier version worked very well, except there were a few bugs. I haven't found any bugs in this ROM yet.
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
jellmoo said:
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
Click to expand...
Click to collapse
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
irony_delerium said:
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
Click to expand...
Click to collapse
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
mcc2005 said:
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
Click to expand...
Click to collapse
TWRP only works right on a Huawei device if you're either decrypted or running EMUI. (On a custom ROM, with an encrypted device, TWRP doesn't even start up - it locks up at the splash screen.)
Factory reset using stock recovery. Only using stock recovery. The OpenKirin team will not support any other configuration.
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
mcc2005 said:
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
Click to expand...
Click to collapse
And the reason why I say anything is because the 2 most common problems I see are:
1) "I'm on Jio, where's my VoLTE?"
2) "I used TWRP and (it's not working | I screwed up | it's broken)".
The response to the first is universally, go back to stock.
The second, restore your entire stock firmware and then follow the instructions exactly as they are written.
With root, you can back up your apps with Titanium. I haven't had good luck with backing up settings with Titanium and after attempting to restore settings, I usually wind up wasting an hour or two and then factory-resetting and just reinstalling the apps. Now I don't even bother backing up settings, but just back up my apps. Even then two or three seem to be botched but uninstalling/reinstalling those will fix that problem. (It isn't always the same ones, either; not sure what causes this). This approach avoids the pain of configuring apps, e.g. travel app usernames and passwords, as well as preserving messages and the like. The biggest nuisance for me is that I carry around 40 unread Amazon books, which have to be sent to the phone (and I'm not so good at remembering which ones I've already read out of the more than 500 in my account), and I carry a bunch of google offline maps, which have to be manually recreated. Lastpass helps with login information too.
In my most recent (Carbon B2) install, I didn't bother with the backup but installed everything fresh and I had a fully functioning phone with 99% of the configuration I like within 2 hours, since I'd been pretty careful to put all the passwords and so on for my roughly 80 apps into a secured text file, as well as backing up my Nova launcher settings.
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Caguayote said:
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Click to expand...
Click to collapse
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
irony_delerium said:
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
Click to expand...
Click to collapse
do you know where can i download the stock ramdisk and recovery partition for mate 9 i was running 8.0.0.369 sorry i put 360
im stuck on twrp splash screen and i cant go to access my backup file to restore and i only access fastboot mode
but my phone says unlocked then frp says lock thanks for all your help
Now i'm using android 7.0. based rom aur 2.3, if i want to install that stock android rom, do i have to flash android 8 based twrp?
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said