Full credit to redditor qrtippadfhjlzcbmm for the instructions, I'm just reposting here. Link to reddit post at end.
I successfully rooted my Zenfone 3. It seemed worth posting since there weren't really any posts I could find verifying a recovery image. [for clarification that was from the post, not me magicmanfk]
1. Unlock the boot loader with the instructions / app from Asus
2. Download TWRP. Specifically twrp-3.1.0-0-Z01H-20170408.img ** [edit: also rename to twrp.img once downloaded]
3. Download SuperSU.
4. Reboot to fastboot by rebooting the phone, and pressing the down arrow during the unlock screen.
5. Flash the recovery image `fastboot flash recovery twrp.img`
6. I had to power cycle the phone completely to get TWRP running.
7. Reboot to recovery. If TWRP ever asks you something about not making the system read only don't swipe! Say not now.
8. Install SuperSU with steps 7 - 10 from the SuperSU site
** I'm generally wary about downloading recovery images from random places, but I found a link posted by shakalaca on the Asus forums (translated), so it seemed worth trying out.
Original post:
https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
Have you attempted to flash the newest ROM yet since being bootloader unlocked? Not sure if we can do it in TWRP or need stock recovery to do it.
Any roms available for the zenfone 3 xoom ? I would love some stock roms lol
DriveEuro said:
Have you attempted to flash the newest ROM yet since being bootloader unlocked? Not sure if we can do it in TWRP or need stock recovery to do it.
Click to expand...
Click to collapse
I have not personally done this because of exactly what you are asking. I believe you need stock recovery to do it, but this is from scouring what other people have done and I don't have a link. I'm waiting for the nougat update before doing it.
Justingaribay7 said:
Any roms available for the zenfone 3 xoom ? I would love some stock roms lol
Click to expand...
Click to collapse
Not yet! I'm hoping there will be soon though. It may help if there was a forum for the device, so if you haven't yet please make a post in the Device forum request page for it!
magicmanfk said:
I have not personally done this because of exactly what you are asking. I believe you need stock recovery to do it, but this is from scouring what other people have done and I don't have a link. I'm waiting for the nougat update before doing it.
Click to expand...
Click to collapse
You should be able to extract the stock recovery out of previous ROMs and flash it.
I'm with you though, waiting for Nougat update. Not bothering with this last ROM from late May that added pretty much nothing.
Hi. I'm the person from reddit.
I'm sure it's (some how) possible to apply an update after running this process. I realize now I should have done this, and then applied the May update, but I didn't. I will try to make it a point to post some instructions on how to do it when it comes out because I'm struggling with out Nougat.
Does anyone know how to get rid of the garbage Asus notification bar, and get the default Android one?
Do you know if you can relock the bootloader? Just curious
Dstrogee said:
Do you know if you can relock the bootloader? Just curious
Click to expand...
Click to collapse
Pretty sure you can't.
Also does anyone have the stock recovery img files?
DriveEuro said:
Pretty sure you can't.
Also does anyone have the stock recovery img files?
Click to expand...
Click to collapse
did you get any stock recovery.img?
Dstrogee said:
Do you know if you can relock the bootloader? Just curious
Click to expand...
Click to collapse
chardie said:
did you get any stock recovery.img?
Click to expand...
Click to collapse
No. Ended up returning Bootloader unlocked phone for a new phone. Waiting until I see others successfully unlock BL and flash stock ROMs.
DriveEuro said:
No. Ended up returning Bootloader unlocked phone for a new phone. Waiting until I see others successfully unlock BL and flash stock ROMs.
Click to expand...
Click to collapse
You can get the stock recovery from the converting cm to ww thread. The image there contains the recovery.IMG file.
Hi, I can not run the root, because by using the official unlock software, something is unsuccessful ... By running the software comes out a "unlocked" message without there being any wipe or restart of the smartphone. .. Does anyone have the same problem? I also tried to make a "factory reset" from recovery but the problem remains ...
steps how to relock bootloader in ZE553KL
Hi, i have rooted my asus zoom ZE553kl when i bought, i follow steps how to root asus ZE553KL in this thread and i succed
i delete so many rubbish preinstalled application that i dont need them, but now i want to relock bootloader again.
could you sir give me any tips how to relock ze553kl bootloader?
Thanks
I can't see the twrp file when device is ready to recovery. Some good soul may post a detailed step-by-step with screen shots, please? Yeah, I'm a noob.
Is this still working to root my Zenfone 3 Zoom w/ latest update?
Nougat
Does this work on android nougat in zenfone zoom s, sir?
magicmanfk said:
8. Install SuperSU with steps 7 - 10 from the SuperSU site
Click to expand...
Click to collapse
Currently the link does not work, but I managed to find it in the Internet Archive: steps 7 - 10 from the SuperSU site
Can I do the same procedure on the Nougat ?
rinampa said:
Can I do the same procedure on the Nougat ?
Click to expand...
Click to collapse
Yes, but I'd use the latest TWRP version and magisk instead of SuperSU (It gets the job done).
Also, update to the latest firmware so you can get the latest security patches.
Hi, i bought this phone.
Also you have a light halo in bottom of screen?
Thanks
Related
Hey XDA, can we talk? cause im about to cry man tears.
First off you are much better at android then I am, this isn't me trying to sound humble, I suck and the threat of bricking my toys scares me.
Today I found a way to get root access without unlocking my bootloader and I was thrilled, it was easy and it worked! I had root access and then decided I was going to try to install CyanogenMod 10 (latest nightly) and so I installed ROM Manager and downloaded CyanogenMod, when I tried to boot to recovery mode (hold down volume and power, then up volume) I would get the dead android with an exclamation point, every time.
So I decided to unlock my bootloader, I went searching and came across the ASUS official bootloader unlocker and it said the unlocker was for ICS and I have already upgraded the ASUS rom to jellybean, I decided to try the unlock device app anyway and now when I restart the words "this device is unlocked" show in the top left corner, I thought that meant the bootloader is unlocked but when I restart into recovery mode I still get the dead android.
I cant find any information anywhere about how to unlock an ASUS jellybean bootloader and I am only guessing that why I keep getting the dead android.
Anyway, if you can help thats awesome, I am usually the kind of guy that can read and find the answers but **** me if I cant find them anywhere, I was never good at the world of bootloaders, whether PC or Android and I am hoping to find a hand and learn something more here
Thanks
I know its my first time here to post but I have read loads of stuff off this site.
78 people read this already, one of you must be able to point my dumbass in the right direction?
bueller, bueller ...:crying:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
ArghMonkey said:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
Click to expand...
Click to collapse
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
flumpster said:
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
Click to expand...
Click to collapse
Sweet, im on it right now
Wow, there are TWRP threads everywhere, several downloads, I even did a search within the transformer prime subthread and cant find one version mentioned for the JB bootloader.
Ill keep looking ...
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
1: Can anyone tell me how I find exactly which bootloader I am running? I have JB installed (4.1.1)
2: So what version of TWRP do I need to download?
3: How would I install TWRP?
and yes, I am unlocked and rooted, help!
Download TWRP 2.5.0.0 for JB blob from here: http://teamw.in/project/twrp2/93
Rename to twrp.blob
Use command prompt on your computer to flash recovery to tablet using this command: fastboot -i 0x0b05 flash recovery twrp.blob
....................
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2038464
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
ArghMonkey said:
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
Click to expand...
Click to collapse
You can't use NVFlash because you are on the JB bootloader. You can't downgrade to ICS.
Great links!
Thanks for your help, I will report back once I try this
ArghMonkey said:
Great links!
Thanks for your help, I will report back once I try this
Click to expand...
Click to collapse
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
Click to expand...
Click to collapse
Ok, so I followed your link, I downloaded the Android SDK and when I opened it I see a million things, the Google USB Driver was highlighted so I installed it, are there other drivers im supposed to install before I go to the next step?!
Lavman72 said:
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Click to expand...
Click to collapse
Working on it right now, flashed twrp over, prime is starting up right now *fingers crossed*
and yes! it booted to stock, now to transfer over supersu ...
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
ArghMonkey said:
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
Click to expand...
Click to collapse
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Lavman72 said:
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Click to expand...
Click to collapse
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
ArghMonkey said:
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
Click to expand...
Click to collapse
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Lavman72 said:
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Click to expand...
Click to collapse
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
ArghMonkey said:
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
Click to expand...
Click to collapse
Rooted: Check
Unlocked bootloader: Check
Tired though, and it's late. So I'm going to hold off on the final steps.
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
octagonPerfectionist said:
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
Click to expand...
Click to collapse
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
livinginavacuum said:
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
Click to expand...
Click to collapse
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
download this: https://android.googleapis.com/packa...L.5cb0c625.zip
install ADB: https://developer.android.com/sdk/index.html (scroll down and download SDK tools only)
and sideload it by following these instructions: http://www.androidcentral.com/how-ma...r-nexus#slide2
note that these instructions were assuming you are on a mac, instead of doing a ./fastboot or ./adb command just type fastboot or adb, no need for the ./
also, you're sideloading the OTA, not flashing the factory image so don't unlock the bootloader and skip the part that talks about flashing the factory images. also iirc once you see the recovery screen with the error looking message, you should press volume-up first then power to bring up the menu? i remember running into a bit of a snag there when i did this last since it says to do it the other way around. anyway hopefully this will update it. if not, you're probably gonna have to flash the factory images, which would need an unlocked bootloader. SO, in case if you do need to unlock the bootloader (which will wipe the device), be absolutely sure to flip that little switch in developer options that allows OEM unlock, otherwise you might be left with a bricked device.
Click to expand...
Click to collapse
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
livinginavacuum said:
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
Click to expand...
Click to collapse
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
octagonPerfectionist said:
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
Click to expand...
Click to collapse
Your first and third link don't seem to work.
doitright said:
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Easier said than done for someone who has no clue. Is there a good youtube video?
livinginavacuum said:
Your first and third link don't seem to work.
Click to expand...
Click to collapse
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
octagonPerfectionist said:
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
Click to expand...
Click to collapse
First one doesn't work! LOL. I'm sure it's not you.
livinginavacuum said:
First one doesn't work! LOL. I'm sure it's not you.
Click to expand...
Click to collapse
haha fml apparently google doesn't like links to the ota zip well anyway just google "nexus 9 ota zip" and it's pretty easy to find.
I got a new Motherboard and daughterboard in my HDX Apollo. I was able to get TWRP on it, but it keeps saying i dont appear to have root. I tried installing the latest supersu but it apparently didnt work. Anyway, i have realized that i just keep getting myself into trouble playing with root. All i want is to get my 3rd gen back to 4.5.5.1 fire os and wait for the fire os 5 update for it(hopefully) Any help on how i can do that? Ive tried downloading the latest Kindle update for apollo, renaming the .bin to update.zip and transferring it over and installing it but it never boots further than the 'kindle' screen.
Thanks for your help, sorry to be a pain
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
Click to expand...
Click to collapse
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Sent from my SM-G920V using XDA-Developers mobile app
mhuck0625 said:
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Click to expand...
Click to collapse
mhuck0625 said:
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Click to expand...
Click to collapse
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Davey126 said:
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Click to expand...
Click to collapse
I installed TWRP using the method instructed here: http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
When i want to get to TWRP i press and hold Power + Vol UP until it rebootes into the Teamwin screen and TWRP. It is version 2.8.7.0 now(the instructions got 2.8.5.0 installed then i upgraded)
I dont remember what the graphic looked like when booting into TWRP but i know it said TeamWin. I can check when i get it charged back up enough to turn on. Ive had it sitting unplugged for days and the battery ran dead. I hope this is enough info to help get me pointed in the right direction. Thanks!
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Click to expand...
Click to collapse
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Cl4ncy said:
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Click to expand...
Click to collapse
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
mhuck0625 said:
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Click to expand...
Click to collapse
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Davey126 said:
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Click to expand...
Click to collapse
Ok, so i will need root to install ROMs then? How do i solve my problem unlocking the bootloader?
mhuck0625 said:
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
Click to expand...
Click to collapse
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Sent from my SM-G920V using XDA-Developers mobile app
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
mhuck0625 said:
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Click to expand...
Click to collapse
mhuck0625 said:
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
Click to expand...
Click to collapse
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Davey126 said:
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Click to expand...
Click to collapse
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
mhuck0625 said:
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
Click to expand...
Click to collapse
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Davey126 said:
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Click to expand...
Click to collapse
You have no idea how much i appreciate the help!
I look forward to hearing what you come up with!!
I would be happy just going straight back to full fire os - Stock EVERYTHING and not even worrying about running another OS. I just want to have a usable tablet again!
Hello from Australia,
I recently purchased the Redmi Note 4 (Global) and absolutely love it! After owning iPhone for the last 8 yrs I am finding it very refreshing. I am looking forward to being part of this Android community
My questions is this - I am very keen on rooting the device but have also found that there is a pending update to 8.5.4.0 (Miui) and 7.0 (Nougat). Will I still be able to root it after I update and if so where is the best guide for me to do this?
Many thanks
Waverley73
Waverley73 said:
Hello from Australia,
I recently purchased the Redmi Note 4 (Global) and absolutely love it! After owning iPhone for the last 8 yrs I am finding it very refreshing. I am looking forward to being part of this Android community
My questions is this - I am very keen on rooting the device but have also found that there is a pending update to 8.5.4.0 (Miui) and 7.0 (Nougat). Will I still be able to root it after I update and if so where is the best guide for me to do this?
Many thanks
Waverley73
Click to expand...
Click to collapse
yes, you can root it after updating to 7.0. First unlock bootloder. Install twrp recovery. and then flash SuperSu zip.
Note-Dont forget to flash lazyflasher-no-verify-opt zip after flashing twrp or you would go into bootloop.
[email protected]!$h said:
yes, you can root it after updating to 7.0. First unlock bootloder. Install twrp recovery. and then flash SuperSu zip.
Note-Dont forget to flash lazyflasher-no-verify-opt zip after flashing twrp or you would go into bootloop.
Click to expand...
Click to collapse
Hello, and many thanks for your quick reply. Good, I had this guide that I was going to follow but then found out about my pending update:
EDIT - sorry, had to edit the url link as I'm a new user. h t t p ://en.miui.com/forum.php?mod=viewthread&tid=667496
Do you think this is the right steps for me to follow? also, I have never flashed or tweaked an Android phone so don't know how to do the flashing of lazyflasher-no-verify-opt zip. I don't see that in the steps. How exactly do I do that? Do you have a link?
Thank you.
Waverley73 said:
Hello, and many thanks for your quick reply. Good, I had this guide that I was going to follow but then found out about my pending update:
EDIT - sorry, had to edit the url link as I'm a new user. h t t p ://en.miui.com/forum.php?mod=viewthread&tid=667496
Do you think this is the right steps for me to follow? also, I have never flashed or tweaked an Android phone so don't know how to do the flashing of lazyflasher-no-verify-opt zip. I don't see that in the steps. How exactly do I do that? Do you have a link?
Thank you.
Click to expand...
Click to collapse
steps given in the guide are almost correct.First unlock bootloader which is the biggest hassle in whole process. Probably you wont be able unlock bootloader in first few tries as mi unlock tool will probably stuck at 99% and show error "account not binded to device".You can wait a few days and try again but i dont think that will work. To solve this problem what i did was-
download miui developer rom version 7.2.16 link-http://bigota.d.miui.com/7.2.16/miui_HMNote4XGlobal_7.2.16_e6eed016d8_6.0.zip
Now go to updater app choose downloaded zip as update package. Now updater would start decrypting it and your phone will be updated to developer rom. Now when on developer rom go to updater app and there will be an ota for latest version, update.Now when on latest developer version try to unlock again using mi unlock tool. I dont know if it will work for you but it worked for me.
Now your bootloader is unlocked, go to mido section in xda forums and download twrp for redmi note 4. To flash twrp recovery, there are many ways. process given in your guide may also work.But what I did was downloaded "mini flasher" link-"https://forum.xda-developers.com/devdb/project/dl/?id=25193&task=get" install mini flasher.choose install twrp, browse to the recovery image you downloaded and it will automatically flash it and reboot your phone to recovery.
Now when your phone is in recovery mode coose 'install'
choose the lazyflasher zip file you earlier downloaded. now reboot. again go to recovery install SuperSu zip file(link given your guide) reboot. your phone will probably bootloop one time but dont worry it is fine. now when your phone reboots it is rooted.
Well I sucessfully updated the phone to Nougat and it was very easy.
Now I have tried to unlock the bootloader but keep getting this message:
您所在的IP申请次数超标
I have googled it and it says I have tried too many times from my IP address. But I haven't - this was the first time. I have tried 3 times, with the same result.
Does anyone know how to get around this problem?
Thanks
The nougat update eats to much ram I got only 1.3 GB free ram
You could try Miui 9 beta channel after miui 8.5 update without unlocking or rooting. Just had to download the miui 9 recovery rom package. Place it in folder named downloaded-rom. Backup your imp data before proceeding. Goto the updater app or settings about, tap three dot menu. Choose update and select the downloaded file. It will erase all your data and update to miui 9.
They release updates weekly. And battery backup is outstanding.
https://forum.xda-developers.com/showpost.php?p=73086754&postcount=124
Anyone able to help with this? I have read it is a common issue for it to incorrectly say you have had too many attempts but not really any conclusive answer as to how to get around the problem.
I am really keen on unlocking my bootloader. Thanks in advance.
Hey Guys,
what do you think is the best costum rom (stable) for the Mate 10 pro?
Is it possible to flash it with Pie 9.0.161?
Thanks for Help :victory:
Just wait for the ota update to pie.
that's definitely a worse rom. i'm on it right now.
wooley4766 said:
Just wait for the ota update to pie.
Click to expand...
Click to collapse
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Pie Update
HauAbDuLauch said:
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Click to expand...
Click to collapse
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
revjamescarver said:
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
Click to expand...
Click to collapse
but no custom
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
93starletgt said:
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
mirandam said:
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
Click to expand...
Click to collapse
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
93starletgt said:
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
Click to expand...
Click to collapse
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
mirandam said:
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
Click to expand...
Click to collapse
Thanks! Last question. If I would like to go back to stock using the All In One Tool, how can I flash stock recovery? And where can I find it? Many thanks for your help.
are there custom roms for the huawei mate 10 pro??
cause cant find it on xda.
mine is stock it works but the no status bar pull down on lockscreen is anoying ;( sometimes and that only the stock sms app show on the always screen on...