Related
Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.
Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk
#2
will this wipe internal storage ? or only data partition?
For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.
so if i flash this i will still have twrp once rebooted?
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.
simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.
This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.
so can we flash this via twrp?
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.
Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times
Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.
This is fully a noob helping guide , Am just trying myself to help noobs instead of explaining them each time .
Method 1 :
Make a twrp backup soon after unlocking boot loader .
Am not going to explain how to unlock bootloader and also twrp flashing ,you can search different threads available in the same section .
Soon after unlocking bootloader , Just boot twrp before flashing it .
This can be done this way , Once you unlocked bootloader .
Upon firstboot ,just goto developer options and enable USB debugging and then Open the folder where you had setup minimal fastboot (Mfastboot v2 google for it) . You should have it as you can't unlock bootloader without minimal fastboot .
In any empty space in minimal fastboot exrracted folder , just press shift+right click and select "Open command prompt here" .
Now copy twrp recovery to Mfastboot folder .
Connect your phone to PC.
In command prompt type the below command
adb reboot bootloader
Hit enter ,
Now your phone reboots to bootloader .
Now type this command .
mfastboot.exe boot twrp.img
(Just rename the recovery to twrp.img before flashing )
Now just take a backup and keep it safe somewhere to access when required .
This is easy , but many may loose their twrp backup for some reasons or forgot to take a backup before stepping to custom ROMs , move to Method 2 if your in such group .
Method 2:
Download update.app from official site .
Extract and put dload folder in root of sdcard .
Power off the phone and press vol up+ vol down and power .
It will now fully flash stock ROM with all stock files .
(This method requires stock recovery so keep in mind to flash stock recovery before trying to update as twrp can't perform these tasks )
Method 3:
Its not hard and not easy too but you required to download some tools .
Huawei update extractor tool (google for it)
Once downloaded open the tool and choose the path where you placed update.app in your PC .
Now the tool opens update.app .
Extract system.IMG and boot.IMG from update.app
Put them in the minimal fastboot folder.
Boot your phn to fastboot using command adb reboot bootloader .
Now connecting your phone to PC in bootloader mode , type the below commands
mfastboot.exe flash system system.img
mfastboot.exe flash boot boot.img
mfastboot.exe reboot
That's it you are on stock ROM.
Method 4:
Flash the stock rom flashable zip posted by devs in your device specific threads and flash it .
Fully for noobs : METHOD 5:
Download the twrp backup posted in device specific threads and put it in sdcard and restore it. Its easy though .
Now your device is ready for flashing official updates "if you get them"[emoji14].
i try every method here and i found myself anytime with modaco custom rom in name build its normal ? ( sorry for my bad english )
yddek971 said:
i try every method here and i found myself anytime with modaco custom rom in name build its normal ? ( sorry for my bad english )
Click to expand...
Click to collapse
Cache & Cust partitions need wiping and reflashing. Had the same issue when I reverted a Modaco rom back to stock.
Easiest method for L21 users is to flash this stock ROM: http://www.modaco.com/forums/topic/377002-r3-custom-rom-starter-template-honor-5x-kiw-l21-b130/ then replace TWRP with the stock recovery image from http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
yes, the rom says "custom rom starter template" but it's the stock B130 UK ROM repackaged into a flashable ZIP. Much easier than messing around extracting system images.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
I should mention one thing. If you have gone back to stock after a custom ROM then you may find the internal storage partition is the wrong size. Just do a full factory reset from Settings to resolve this.
flibblesan said:
Cache & Cust partitions need wiping and reflashing. Had the same issue when I reverted a Modaco rom back to stock.
Easiest method for L21 users is to flash this stock ROM: http://www.modaco.com/forums/topic/377002-r3-custom-rom-starter-template-honor-5x-kiw-l21-b130/ then replace TWRP with the stock recovery image from http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
yes, the rom says "custom rom starter template" but it's the stock B130 UK ROM repackaged into a flashable ZIP. Much easier than messing around extracting system images.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
I should mention one thing. If you have gone back to stock after a custom ROM then you may find the internal storage partition is the wrong size. Just do a full factory reset from Settings to resolve this.
Click to expand...
Click to collapse
oh thanks i see the r3 updated to format partitions rather than delete so i dont need to wipping cust and cashe ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
i just need to flash this rom ?
yddek971 said:
oh thanks i see the r3 updated to format partitions rather than delete so i dont need to wipping cust and cashe ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
i just need to flash this rom ?
Click to expand...
Click to collapse
Yes, if you just flash that rom then you'll be fully restored to stock, but with TWRP still in place. If you flash the stock recovery.img after then this will put the phone completely at stock and you should be able to apply future updates as the rom is completely untouched.
flibblesan said:
Yes, if you just flash that rom then you'll be fully restored to stock, but with TWRP still in place. If you flash the stock recovery.img after then this will put the phone completely at stock and you should be able to apply future updates as the rom is completely untouched.
Click to expand...
Click to collapse
thanks a lot !
gopinaidu77 said:
This is fully a noob helping guide , Am just trying myself to help noobs instead of explaining them each time .
.
Click to expand...
Click to collapse
All the TWRP Backups in my Back to stock Guide include stock recovery
And also using the dload/update.app method does not delete your data but it will replace your custom recovery / boot.img and you can take OTA update afterwords
clsA said:
All the TWRP Backups in my Back to stock Guide include stock recovery
And also using the dload/update.app method does not delete your data but it will replace your custom recovery / boot.img and you can take OTA update afterwords
Click to expand...
Click to collapse
Yeah , thats what i mean device specifix threads .
And thanks for your repository , all the stuff in one place :cheers:
Hi Gopi,
Please help me getting back to stock on my L-22.
I am planning to go back to stock of L-24 available as (KIW-L24-B151-Stock (Boot.img - System - System/Priv-App Only)) posted by clsA.
1. Which method to follow????
2. Do I need to go back to stock Recovery???? If yes, then how??? where is stock recovery of L-22 posted?????
Please guide me I can cook it.
3. otherwise B140.debloated version -2. I tried to install through TWRP. NO success but a bootloop. is it ok this way???
Thanks in advance.
@subodhverma21 , L22 already got b150 update and i posted ota link .
Try downloading stock twrp backup posted by me and restore it along with stock recovery and then install ota .
Sent from my KIW-L22 using XDA-Developers mobile app
gopinaidu77 said:
@subodhverma21 , L22 already got b150 update and i posted ota link .
Try downloading stock twrp backup posted by me and restore it along with stock recovery and then install ota .
Sent from my KIW-L22 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks man,
It worked. Now on stock with update 150 installed.
Sent from my KIW-L22 using XDA-Developers mobile app
When I try the dload folder method on the root of my SD card the process fails. Can someone please advise what to do? I am L21
Hello,
I have exactly the same problem on a KIW - L21 . Did you find a solution?
Sorry for my english, I'm french.
Thank you
faisalsiddiqui said:
When I try the dload folder method on the root of my SD card the process fails. Can someone please advise what to do? I am L21
Click to expand...
Click to collapse
newic2001 said:
Hello,
I have exactly the same problem on a KIW - L21 . Did you find a solution?
Sorry for my english, I'm french.
Thank you
Click to expand...
Click to collapse
it's a known issue the L21 update seems to be corrupt their are many posts about it
can you install a rom with TWRP ?
If yes this Rom will get you back to stock >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Hi I went from Cm13 to stock with emui 2.0 by restoring my twrp backup before I flashed my first huawei gr5 custom rom.
Now i am trying to restore back to stock rom to fully use OTA updates. Here's what I Did:
1. Restore twrp backup (emui 2.0 not rooted)
2. Flash system img and boot.img via adb using img file from update.app also by using update extractor.
Now i realized that im still in twrp. Do i need to flash recovery img first? Then can i do updates without problem? Or do i need to use the update.app via dload updating too?
good work bro, helps a lot of ppl @gopinaidu77
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
s4h1k0 said:
Hi I went from Cm13 to stock with emui 2.0 by restoring my twrp backup before I flashed my first huawei gr5 custom rom.
Now i am trying to restore back to stock rom to fully use OTA updates. Here's what I Did:
1. Restore twrp backup (emui 2.0 not rooted)
2. Flash system img and boot.img via adb using img file from update.app also by using update extractor.
Now i realized that im still in twrp. Do i need to flash recovery img first? Then can i do updates without problem? Or do i need to use the update.app via dload updating too?
Click to expand...
Click to collapse
try restoring though twrp
clsA said:
it's a known issue the L21 update seems to be corrupt their are many posts about it
can you install a rom with TWRP ?
If yes this Rom will get you back to stock >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Click to expand...
Click to collapse
@gopinaidu77
Hello sir
Does method 3 will have to be done with unlocked bootloader or locked one?
Because nexuse devices need unlocking the bootloader before flashing factroy images
NAROUTO said:
@gopinaidu77
Hello sir
Does method 3 will have to be done with unlocked bootloader or locked one?
Because nexuse devices need unlocking the bootloader before flashing factroy images
Click to expand...
Click to collapse
Of course unlocked one.
gopinaidu77 said:
Of course unlocked one.
Click to expand...
Click to collapse
Bro
I want your help please?
I tried to flash stock rom. I first extracted update.app .then flashed stock recovery via fastboot and tried to flash stock rom from dload folder in my memory card but always fail to install/and stuck with 5% . Then tried fastboot to flash the rom but error cannot load system.img but boot.img and recovery.img flashed successful.
I am stuck now and don't know why flash system partitions from Adb fails and from stock recovery fail @clsA
Help
NAROUTO said:
Bro
I want your help please?
I tried to flash stock rom. I first extracted update.app .then flashed stock recovery via fastboot and tried to flash stock rom from dload folder in my memory card but always fail to install/and stuck with 5% . Then tried fastboot to flash the rom but error cannot load system.img but boot.img and recovery.img flashed successful.
I am stuck now and don't know why flash system partitions from Adb fails and from stock recovery fail @clsA
Help
Click to expand...
Click to collapse
Your update.app fail to flash at 5% right ?
Its easy .. Goto settings/storage and set sdcard as default .
And then try dload method .it will get flashed now
Hello,
somehow I had a problem that many apps force closed after doing something, so I tried flashing opengapps - worst idea. I started the phone and nothing worked because I always get force close on Setup Assistent.
I were on Cydras Rom (https://forum.xda-developers.com/le-pro3/development/rom-google-edition-cydras-t3514742). So now I tried overflashing it again but somehow it says successfully installed and also "cant unmount system: volume not found". The system image is now about 900mb big, the zip 1.3gb - can't be possible. It doesn't but and stuck on the first Leeco screen. Now I tried sideload: failed - invalid command..
Well, I tried getting another rom and put it on phone by MTP in TWRP.. Same problem - TARS causes boot into Recovery and CM13 by Superluminal doesn't even flash: stuck on "patching system image unconditonally".
Has someone a solution or more like is there any system image I can flash through fastboot?
Or could someone make one? PLEASE!
I think somehow the system can't be mounted...
Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?
Somehow I tried this twrp backup: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
Now I can't mount storage, because it's encrypted... -.-
I have x720 and I don't really know what caused the FCs, the last I remember was uninstalling Android WebView.
Now I have to try to get access to storage again..
## bootloader is unlocked
dark_prince said:
Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?
Click to expand...
Click to collapse
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?
Grossoshop ROM is fastboot installable.
Presterin said:
Grossoshop ROM is fastboot installable.
Click to expand...
Click to collapse
Link?
idragonx said:
Link?
Click to expand...
Click to collapse
Sure, here you go: http://blog.grossoshop.net/leeco-x720-grossoshop-rom-italiano-ota/
idragonx said:
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?
Click to expand...
Click to collapse
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...
dark_prince said:
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...
Click to expand...
Click to collapse
How to reformat? I tried wiping all & make it ext4 in TWRP.
Sideload doesn't work: * failed to read command: Invalid argument
Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)
dark_prince said:
Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)
Click to expand...
Click to collapse
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"
idragonx said:
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?
Presterin said:
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?
Click to expand...
Click to collapse
I used this from the post: https://mega.nz/#!tUkUQJwZ!h3tniWVWlSiYJICadW7MuEdYLDFKfNmNcEOBQ-eL1JM
dark_prince said:
Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"
Click to expand...
Click to collapse
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot
#####
I GOT IT.
Finally - https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
It could do it using fastboot - oh god thanks. Now I try to flash my custom rom.
idragonx said:
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot.
Click to expand...
Click to collapse
mD5 verified?
Alright try this. Get latest CM13 build from teamsuperluminal website and also get the x720 patch from there too. Then in TWRP (while connected to USB) go to advanced wipe > cache + system + dalvik + data.
Open downloaded CM13 zip in 7-zip file manager, go to META-INF > Android folder and extract only the updater_script file. (Should be in that or in a subwoofer). Keep the 7-zip opened and dont close it.
Open the updater_script file in notepad++ and remove first line which starts with "assert". Save
Then drag drop it back into 7-zip( in the same folder structure.) Close 7-zip after
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.
dark_prince said:
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.
Click to expand...
Click to collapse
Thank you very much for your help, but finally I found the 18s from grossoshop with the BATCH - it could fastboot load the system.img partially and now it boots <3
Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...
dark_prince said:
Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...
Click to expand...
Click to collapse
Well, but I can't flash back my cydras ROM
Imho it should work now to go back to stock. Download official Chinese firmware zip file (not OTA) and rename it to update.zip
Put it in internal storage (not into any folder)
Go to fastboot and flash stock recovery.
Then boot into stock recovery and apply update.zip
Result should be profiting.
idragonx said:
Well, but I can't flash back my cydras ROM
Click to expand...
Click to collapse
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson
thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again
david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:
david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!
Hello,
I tried to flash the RessurectionRemix ROM and it was working well except the LTE so I decided to get back to EMUI.
Problem, i took the backup of bluesmoothie and flashed it but the phone never finish to boot.... (I didn't wipe anything, i thought that the restore function of TWRP was doing everything, am I wrong ?)
Moreover, the TWRP recovery can't access the content of my ext sdcard where the RR ROM is located and even if i put this rom to internal storage, i got the ERROR 7 (this is for deive: can; you have generic_a53)
Do you know what can I do to :
- Come back to EMUI
- Unroot the phone
- Re-lock the bootloader
The files of the TWRP backup are located on the sdcard, if i wipe data/system/cache, will it delete these files ?
Infos :
- Bootloader unlocked
- TWRP of Garak (but still have ERROR 7 now)
Thank you very much
First you need to flash the stock recovery in fastboot. After that you need to put the update.app in a folder called dload in your internal storage.
wangdaning said:
First you need to flash the stock recovery in fastboot. After that you need to put the update.app in a folder called dload in your internal storage.
Click to expand...
Click to collapse
Okay but where can I find the stock recovery ?
Then, do i have to flash it via ADB like i did with TWRP ?
After that, where can I find the "update.app" that you are talking about ?
If i'm right, you're telling me that i can't go back to EMUI without flashing the stock recovery ?
That is correct. First use firmware finder to get the update.app. There is a firmware extractor tool for Huawei firmware. Use it to extract the recovery.img and flash with fastboot.
wangdaning said:
That is correct. First use firmware finder to get the update.app. There is a firmware extractor tool for Huawei firmware. Use it to extract the recovery.img and flash with fastboot.
Click to expand...
Click to collapse
First of all, thank you very much for your anwser, it's very kind of you.
If i understood everything, that's what i have to do :
- Download one of the Huawei firmwares with Huawei Finder (Better get the B100 or another one ?)
- Extract the recovery.img with the update.app from Huawei Finder
- Flash the stock recovery with ADB
Then :
- I put the update.app that i get through the Huawei Finder in the dload folder of the internal storage (If i flash the stock recovery, will I be able to put files in the storage ?)
- I reboot the phone in recovery and normally, it should install the EMUI rom
At the end, my phone will no longer have a custom recvery, bootloader unlocked and root status ?
iSpeeX said:
First of all, thank you very much for your anwser, it's very kind of you.
If i understood everything, that's what i have to do :
- Download one of the Huawei firmwares with Huawei Finder (Better get the B100 or another one ?)
- Extract the recovery.img with the update.app from Huawei Finder
- Flash the stock recovery with ADB
Then :
- I put the update.app that i get through the Huawei Finder in the dload folder of the internal storage (If i flash the stock recovery, will I be able to put files in the storage ?)
- I reboot the phone in recovery and normally, it should install the EMUI rom
At the end, my phone will no longer have a custom recvery, bootloader unlocked and root status ?
Click to expand...
Click to collapse
Yes, that's correct. But you have to put update.app in dload folder on your SD card as far as I know. That's how I did it.
I couldn't find B100 on Firmware Finder and I've got relocked bootloader on Nougat.
Yes, you will need to copy the update.app to internal storage in TWRP, then flash the stock recovery. After flashing you need to hold all three buttons when booting (just like getting into TWRP. After update you will have no custom recovery, no root, and it should lock bootloader.
wangdaning said:
Yes, you will need to copy the update.app to internal storage in TWRP, then flash the stock recovery. After flashing you need to hold all three buttons when booting (just like getting into TWRP. After update you will have no custom recovery, no root, and it should lock bootloader.
Click to expand...
Click to collapse
I did everything, now it's booting but it's VERY VERY LONG... I'll wait and pray
iSpeeX said:
I did everything, now it's booting but it's VERY VERY LONG... I'll wait and pray
Click to expand...
Click to collapse
If it doesn't boot, then boot in recovery and do a factory reset and then it should boot. It happened to me and that's what I did.
#Henkate said:
If it doesn't boot, then boot in recovery and do a factory reset and then it should boot. It happened to me and that's what I did.
Click to expand...
Click to collapse
I still have the warning message "your phone is unlocked", is it normal ?
When i boot into recovery it's displaying "eRecovery" and ask me to download the new update of recovery but it fails when getting the package. I can only reboot and turn off :/
Thank you as always
iSpeeX said:
I still have the warning message "your phone is unlocked", is it normal ?
When i boot into recovery it's displaying "eRecovery" and ask me to download the new update of recovery but it fails when getting the package. I can only reboot and turn off :/
Thank you as always
Click to expand...
Click to collapse
You shouldn't have that message anymore.
Are you sure that the update.app got installed? @wangdaning told you to put it on dload folder in internal memory. I don't know if that is right or if it works, but I've put it in dload folder on sdcard when I've installed update.app.
#Henkate said:
You shouldn't have that message anymore.
Are you sure that the update.app got installed? @wangdaning told you to put it on dload folder in internal memory. I don't know if that is right or if it works, but I've put it in dload folder on sdcard when I've installed update.app.
Click to expand...
Click to collapse
Well i wasn't in front of it when it finished and I just did it : the update stops at 5% and then the phone reboot....
Do you know what do I have to do ? I took the recovery from the last B350 on huawei firmware finder
EDIT1 : but this time in recovery i can Reboot, Wipe factory reset, Wipe cache
iSpeeX said:
Well i wasn't in front of it when it finished and I just did it : the update stops at 5% and then the phone reboot....
Do you know what do I have to do ? I took the recovery from the last B350 on huawei firmware finder
EDIT1 : but this time in recovery i can Reboot, Wipe factory reset, Wipe cache
Click to expand...
Click to collapse
You can read in this post the steps I've used to relock the bootloader and get update (official I guess) through Settings > System update. Just "click to show content".
#Henkate said:
You can read in this post the steps I've used to relock the bootloader and get update (official I guess) through Settings > System update. Just "click to show content".
Click to expand...
Click to collapse
The problem is that the phone doesnt finish to but anymore... i can't do things in menu.
When you talk about SD card, it's the external sd card ? Because i don't have access to it anymore, but i have the partition SD Card
When you installed the B340 update, you seen the percent growing up and had a "success" message ? Because, for me, the update is stuck at 5% and then it reboot the phone
iSpeeX said:
The problem is that the phone doesnt finish to but anymore... i can't do things in menu.
When you talk about SD card, it's the external sd card ? Because i don't have access to it anymore, but i have the partition SD Card
When you installed the B340 update, you seen the percent growing up and had a "success" message ? Because, for me, the update is stuck at 5% and then it reboot the phone
Click to expand...
Click to collapse
Yes, I mean external sdcard.
Reinstall TWRP and restore bluesmoothie's backup and then flash the stock recovery again.
I didn't have any issues with installing the B340 firmware. It was installed successfully.
Try to follow the steps I've used. You shouldn't have any problem.
#Henkate said:
Yes, I mean external sdcard.
Reinstall TWRP and restore bluesmoothie's backup and then flash the stock recovery again.
I didn't have any issues with installing the B340 firmware. It was installed successfully.
Try to follow the steps I've used. You shouldn't have any problem.
Click to expand...
Click to collapse
Okay i'm going to try it right away
My external sd card doesnt show up anymore when i connect it to my PC, i don't know why
I mentioned internal SD card because you said your external was not recognized, but you might try putting the dload folder on external. I have done it both ways. Sometimes the update through stock recovery is finicky. If it doesn't finish run it again. Also, make sure your USB is disconnected, as may Huawei users have mentioned this causes it to freeze. If it still fails, try dloading a different update from firmware finder.
Did it work?
I didn't have so much time these days but I did it and it worked for the 1st part (flash bouesmoothie's backup). Tomorrow I'll do the final step! Thank you again
Here I am :
1 : flashed stock recovery from B350 and i don't have the "unlocked" message anymore !
2 : The update B350 made it, "update success"
3 : It doesn't boot for now
4 : The boot doesn't end
-----
1 : flashed TWRP recovery, launched a factory reset in the same time
2 : Phone booting again on B100
-----
1 : flashed stock recovery from b350
2 : flashed b350 update
3 : Everything is fine !
Thank you for your help !!!