Greetings. I was trying to root my Nexus 9 and was hoping to make it faster by flashing a custom ROM on it (PureNexus).
I failed with everyone now it's stuck on a bootloop (Google logo), and when I try the Power + Vol Down button and go to Recovery (OpenRecoveryScript loop on TWRP 3.0 happens)
I have no idea on what to do first, I've tried installing ADB drivers but I can't seem to get into Recovery long enough to install fastboot + adb.
I was using Nexus Root Toolkit when this all happened. Any professional people that root here? Mind helping me with my problem? Thank you!
I'm no dev but you need to boot power+vol up for fastboot
And extract the factory image from google and press the flashall.bat/sh (win/Linux) to get back to stock.
whowatchlist said:
I'm no dev but you need to boot power+vol up for fastboot
And extract the factory image from google and press the flashall.bat/sh (win/Linux) to get back to stock.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you!
Start with this, http://forum.xda-developers.com/nex...ader-flash-t3035153/post58956577#post58956577
It's best to learn how to flash factory images without the use of a tool kit. That way when you run into problems you'll know what to do.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Start with this, http://forum.xda-developers.com/nex...ader-flash-t3035153/post58956577#post58956577
It's best to learn how to flash factory images without the use of a tool kit. That way when you run into problems you'll know what to do.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Currently doing this as we speak. I'll let you know what happens. Thanks a bunch
jd1639 said:
Start with this, http://forum.xda-developers.com/nex...ader-flash-t3035153/post58956577#post58956577
It's best to learn how to flash factory images without the use of a tool kit. That way when you run into problems you'll know what to do.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I did this step by step and I fixed it! Though I want to flash to Pure Nexus. Do you have any tips?
You'll want to flash the latest twrp using fastboot. (Google teamwin nexus 9) Then download pure nexus Rom and gapps of your choice to your phone. Boot into twrp and do a wipe first. The default wipe is fine. Flash the rom and then flash gapps. Also, read the faq on the pure nexus thread. I believe there is something there about the vendor.img
Sent from my Nexus 9 using XDA-Developers mobile app
papaketchup said:
I did this step by step and I fixed it! Though I want to flash to Pure Nexus. Do you have any tips?
Click to expand...
Click to collapse
You'll want the latest vendor image, extract it from the latest stock image found here:
https://developers.google.com/android/nexus/images
You can flash it using TWRP
I fixed all the problems. Thank you everyone!
Related
Hello..i just got my nexus 9 recently and the version is 5.0.1..im thinking of rooting it but does the method of rooting is the same as 5.0?
Hope to root it asap.thank u
mijiey said:
Hello..i just got my nexus 9 recently and the version is 5.0.1..im thinking of rooting it but does the method of rooting is the same as 5.0?
Hope to root it asap.thank u
Click to expand...
Click to collapse
Flash twrp on using fastboot. Then flash supersu 2.4 in twrp.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash twrp on using fastboot. Then flash supersu 2.4 in twrp.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Are there any link or instruction that i can be direct to? Thank you
mijiey said:
Are there any link or instruction that i can be direct to? Thank you
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll setup adb and fastboot on your pc.
Download the twrp image file from here
http://techerrata.com/browse/twrp2/volantis
Download supersu 2.4 to your device from here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
Boot your device into the bootloader and with it connected to the pc open a Windows command window in the same directory as the twrp.img is in. Then run the command
fastboot flash recovery twrp.img
(Note. Use the full name of the twrp.img that you downloaded)
Then boot into recovery, it'll be twrp now, and install supersu
Sent from my Nexus 5 using XDA Free mobile app
Thanks man..will look into it..really appreciate your help
about help
well write up mate
https://dl.twrp.me/angler/
So flash, much excite, such new. Wow.
Edit - I know I sound weird but I don't like dirty flashes. I always reboot into bootloader, fastboot erase recovery and then fastboot flash recovery twrp.img ( I rename it twrp.img for short) then boot into it. I have done this for years on BL unlocked devices and never had a problem flashing twrp. It's just ME, but I think it is fun typing the stuff, and it assures me that I have a clean state and am not dirty flashing anything! Also, on others phones I use RASHR instead of flashify. Once again, personal preference but have had better luck.
XDA Thread updated
And backs up with finger print
^ That's great news.
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
synnyster said:
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
Click to expand...
Click to collapse
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
I flashed via fastboot after I updated to the newest android February security patch.
synnyster said:
I flashed via fastboot after I updated to the newest android February security patch.
Click to expand...
Click to collapse
Okay you're on stock?
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
Gytole said:
Okay you're on stock?
Click to expand...
Click to collapse
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
synnyster said:
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
Click to expand...
Click to collapse
Fastboot erase recovery, then reflash twrp recovery, boot into recovery and reflash systemless root.
No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM...
You gotta:
"Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
OP's method seems like the best bet though...
Sent from my Nexus 6P using Tapatalk
"No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM..."
That's cause you're use to flashing zips people make flashable, i'm old school and use img's hahaha "LET'S MAKE FLASHING FUN!" Shutup Gytole...
Just out of curiosity has anyone tried flashing twrp as boot? I also have a thread in the tmobile G3 section and I almost wonder if thats why they bork their phone...lol
Just did it on my girlfriends G3 through twrp and was like, "they totally flashed it as boot...."
Used twrp manager from Google store was simple and easy
ROADKING17 said:
Used twrp manager from Google store was simple and easy
Click to expand...
Click to collapse
Way to deviate from the norm! Haha
Gytole said:
Way to deviate from the norm! Haha
Click to expand...
Click to collapse
Takes all kinds...
Sent from my Nexus 6P using Tapatalk
No need for this thread, as there is a TWRP thread in the development forum.
Thread closed.
hi
i have an honor 7 from switzerland and i tried to install on him the PLK-AL10 6.6.1 - B651 full, ofcurse the instalation was stuck on 19% and i can't go to recovery,
what i can do to fix these?
thanks
update, i can't get the product ID (to find this, open the dialler and enter *#*#1357946#*#*) - cause i don't have dialer..and system....
what you advice me to do next?
First of all, I would guess you have a model PLK-L01, not AL10. Anyway, we need more information if we should help you. What does "can't go to recovery" mean exactly? What have you tried? What happens and what does not happen when you try? What happens when you connect the phone to a PC ?
Not sure if of any use, but try to connect the phone to a PC via USB Cable, then press volume UP and Power to boot into eRecovery, a second (and I think identical) recovery. Maybe that works? If you make any progress, try the Honor 7 MultiTool.
Let us know if you can make any progress.
yes its PLK-L01
i worked on the day with these and finally what i did is that i put the update.app into the micro sd card and than start the device + vol up+vol down and than the device probebly tooks the update.app that i add to the sd card and installed him correctly.
the case was that i probebly install at the first time locally version for AL10 and than i start MultiTool but the multitool request to open the bootloader in order to install the bootloader something that needs the productID that i can get if i have a dialer and enter *#*#1357946#*#* but i don't have any dialer since i don't have any system so...i don't know how, but it's worked as i wrote from the sd card
So you managed to install the UPDATE.APP package??
yes
Sent from my Nexus 6P using Tapatalk
I7210I said:
yes
Click to expand...
Click to collapse
Good.
Sent from my Huawei PLK-L01 using XDA Labs
I7210I said:
yes
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just don´t forget, if you root the device, you must first unroot, flash stock recovery.img and boot.img and THEN update to whatever stock ROM version available.
no i won't be root the device,
i just want to know that now he is ok with stock rom(these i know) stock recovery and stock recovery, how can i know that for sure?
Sent from my Nexus 6P using Tapatalk
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/honor-7/development/unsupported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
LoRikU said:
Hello everyone! I'm new on XDA and this is my first thread.
So, I've been messing around with my Honor 7 lately. I've flashed a custom recovery (TWRP), flashed a custom ROM (Unofficial CM13 for Honor 7: https://forum.xda-developers.com/ho...upported-cyanogenmod-13-honor-7-plk-t3542627) and root (SuperSU) and I've started to regret all of my decisions so I would like to take a fresh start (AKA flashing the STOCK ROM/Firmware)
Now, before anyone starts redirecting me to other (similar) threads, I've tried a lot. I tried to flash the stock recovery (a lot of different versions) but still when I try to boot into the stock recovery, my phone just reboots. I tried to do the force update thing (holding both power + & - buttons: http://www.gogorapid.com/flash-stock-rom-huawei-honor-7/), but this combination just boots my phone into TWRP. Could it be that I'm doing something wrong or that I'm missing something, like some requirements that are not being met? Please help me, I would appreciate it a lot! Thanks in advance.
Click to expand...
Click to collapse
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
It seems that you didn't flash the stock recovery properly.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
LoRikU said:
Thanks for the reply!
Could it be? I booted my phone into bootloader (unlocked) and flashed stock recovery with adb using the command "fastboot flash recovery recovery.img". I tried a variety of versions (from B100 up to B330 I think), but none of them seemed to work. What am I doing wrong?
Click to expand...
Click to collapse
did you tried the offical TWRP of ypur device?
venugopalu007 said:
did you tried the offical TWRP of ypur device?
Click to expand...
Click to collapse
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
LoRikU said:
Hey,
Sorry for the slow reply, I'm currently on vacation. Euh I already have TWRP installed right now, I just don't know how to install the stock recovery.
Click to expand...
Click to collapse
Grab the stock recovery file for your device. You can flash inside TWRP itself.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Koriki extract the firmware using huaweiupdateextractor
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
Koriki?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Koriki?
Click to expand...
Click to collapse
Loriki is user name of op
Sorry my keyboard auto corrected it to koriki
venugopalu007 said:
Download stock recovery and boot your phone to fastboot and
in command --- Fastboot flash recovery xxxfilenamexxx.img
Click to expand...
Click to collapse
I tried that, read my second post on this thread. It didn't work, I didn't know which version I had to use. I ended up with a bootloop on various versions as mentioned in one of my first posts.
adriansticoid said:
Grab the stock recovery file for your device. You can flash inside TWRP itself.
Click to expand...
Click to collapse
Alright, I will try this. As soon as I get back home since the wifi here sucks.
venugopalu007 said:
Koriki extract the firmware using huaweiupdateextractor
Click to expand...
Click to collapse
I planned on doing this though I don't know where I can get the firmware for my H7... Could you perhaps provide me a link? It would be very kind of you (+ The wifi here sucks, so I will try downloading firmwares when I get home)
When attempting to flash TWRP through Odin I get a message on the screen that says, “Only official released binaries are allowed to be flashed(RECOVERY)”, after I hold the volume up, Bixby, and power buttons. Does anyone know why??
1. I have OEM Unlock on, but it somehow bypassed 7 days when I flashed from 8.0 to 9.0 Pie. It was not there until I flashed.
2. Download page says, “OEM LOCK: OFF”.
3. I have flashed back to stock 9.0 Pie firmware each time it failed and OEM Lock was still on the whole time.
4. I have even tried to trick to set the date back a month from latest security check date.
Not sure what I am doing wrong... Even though it says OEM is unlocked, do I still have to wait 7 days?
Thanks in advance.
JTM206 said:
When attempting to flash TWRP through Odin I get a message on the screen that says, “Only official released binaries are allowed to be flashed(RECOVERY)”, after I hold the volume up, Bixby, and power buttons. Does anyone know why??
1. I have OEM Unlock on, but it somehow bypassed 7 days when I flashed from 8.0 to 9.0 Pie. It was not there until I flashed.
2. Download page says, “OEM LOCK: OFF”.
3. I have flashed back to stock 9.0 Pie firmware each time it failed and OEM Lock was still on the whole time.
4. I have even tried to trick to set the date back a month from latest security check date.
Not sure what I am doing wrong... Even though it says OEM is unlocked, do I still have to wait 7 days?
Thanks in advance.
Click to expand...
Click to collapse
I wanted to know if you are only rooting the device or installing update ROMs or not.
If you are installing ROMs then you don't need to root your device there is another way too.
Sent from my P5 mini using premium XDA app
PrashannaGP said:
I wanted to know if you are only rooting the device or installing update ROMs or not.
If you are installing ROMs then you don't need to root your device there is another way too.
Sent from my P5 mini using premium XDA app
Click to expand...
Click to collapse
I am trying to run Magisk to hide the app to play PokémonGO with a joystick. Want to root it because it seems like the safest way.
JTM206 said:
I am trying to run Magisk to hide the app to play PokémonGO with a joystick. Want to root it because it seems like the safest way.
Click to expand...
Click to collapse
then you have to download stock rom for your device and also TWRP and replace the recovery file with twrp recovery and flash the recovery.img (downloaded recovery.img) for your device not stock rom with sp flash tool and flash the SuperSU.zip from twrp and again install magisk and its module. Done:good::good:
You are not supposed to allow it to boot with full stock firmware, ever. You should have intercepted the reboot and immediately flashed, twrp, magisk and the kernel patch.
pauaxe said:
You are not supposed to allow it to boot with full stock firmware, ever. You should have intercepted the reboot and immediately flashed, twrp, magisk and the kernel patch.
Click to expand...
Click to collapse
Yes but we can only do one thing. That is to unlock bootloader and then flash twrp from fastboot using
fastboot flash recovery ---------.img
fastboot reboot
adb devices
adb reboot recovery
press on INSTALL
select MAgisk.zip
reboot.
Done
Sent from my [device_name] using XDA-Developers Legacy app
PrashannaGP said:
Yes but we can only do one thing. That is to unlock bootloader and then flash twrp from fastboot using
fastboot flash recovery ---------.img
fastboot reboot
adb devices
adb reboot recovery
press on INSTALL
select MAgisk.zip
reboot.
Done
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Well if he is getting "Only official released binaries are allowed to be flashed(RECOVERY)" then he'll probably have to wait it out for 7 days anyway. That's why I said he shouldn't have let it boot, to avoid waiting 7 days.
Also there is no fastboot for Samsung phones.
pauaxe said:
Well if he is getting "Only official released binaries are allowed to be flashed(RECOVERY)" then he'll probably have to wait it out for 7 days anyway. That's why I said he shouldn't have let it boot, to avoid waiting 7 days.
Also there is no fastboot for Samsung phones.
Click to expand...
Click to collapse
Yes. That's right . Patience is important
Sent from my [device_name] using XDA-Developers Legacy app