Database Users

[TUT] Getting a clean 4.1.1 Experience - Steps to Flash Stock 4.0.4 and then 4.1.1

First up, let me tell you that doing this is not necessay to get the OTA or having a smooth JB experience. The JB OTA installs without a wipe which means the data is preserved.
UPDATE: Google has put up the full image for 4.1.1 [i9023, i9020a and i9020t] . Now you do not need to clean flash ICS and then JB. Follow the part 1 of the guide below and flash the JB image instead of ICS. Nothing more to it.
Thanks anshumandash for pointing it out
That being said, I wanted to have the real stock image on my Nexus S and then Upgrade to JellyBean. Below are the steps that I took.
Go to this GoogleAndroidImages page and download the appropriate image for your phone & download. Since mine is an international version a.k.a I9023, I chose that ROM.
The download will be a tar.gz file. Use a utility like 7Zip to uncompress it. The tar.gz will have a .tar file inside and the /tar file will have a folder. Extract the folder to your PC. For my download, the folder was named soju-imm76d
Next Steps will wipe your phone, completely
Reboot your phone into bootloader mode.
Open a command prompt, navigate to the folder in step 2.
Enter the below commands, the image file names are for my download, modify it to the file names in your folder before running (I assume that you have fastboot working)
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip​
After the last step, the phone reboots and takes you to the initial setup screen.
Additionally, I reflashed CWM and the the JellyBean OTA along with superuser. Below are the steps for that
Download the OTA from google server. This thread by oldblue910 is kept updated with the latest updates. Currently it has OTA's for I9023 and I9020A
Download the superuser from androidsu website. This is the RC version 3.2
Download the latest clocworkmod recovery touch-version non-touch-version
For simplicity sake, put all the files downloaded at a single folder
Reboot phone into bootloader mode.
Open a command prompt and go to the folder in step 4.
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img​
Now using the vol down key choose to go to recovery.
There, using the options, navigate to the install zip from sdcard and first install the OTA and then the superuser zip file.
Reboot. You now have rooted JB
PS: I additionally did a fastboot oem lock and fastboot oem unlock back to back to wipe my sdcard too
Reason for this post?
Originally Posted by dEris
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images
Click to expand...
Click to collapse

Whats the difference/benefits between ur "way" and just flashing JB zip with proper clean install?
thanks in advance ;-]

greg2826 said:
Whats the difference/benefits between ur "way" and just flashing JB zip with proper clean install?
thanks in advance ;-]
Click to expand...
Click to collapse
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images.

I think this was the exact way I did it as well:thumbup: I must have skipped one step during the process though because my "SD" didn't get wiped.

turchs
This doesn't apply to the i9020a Nexus S
-_-

karleeezy said:
This doesn't apply to the i9020a Nexus S
-_-
Click to expand...
Click to collapse
Yes it does! I9020A OTA in the thread below!
http://forum.xda-developers.com/showthread.php?t=1736645

dEris said:
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images.
Click to expand...
Click to collapse
ok got it
my thanks went 2 u

Couldn't you just do a factory reset after installing the OTA package?

Thank you, your tutorial was helpful. Needed to go back to stock.

FirePoncho86 said:
Yes it does! I9020A OTA in the thread below!
http://forum.xda-developers.com/showthread.php?t=1736645
Click to expand...
Click to collapse
Got it! Thanks, dude!

jithinsarath said:
First up, let me tell you that doing this is not necessay to get the OTA or having a smooth JB experience. The JB OTA installs without a wipe which means the data is preserved.
That being said, I wanted to have the real stock image on my Nexus S and then Upgrade to JellyBean. Below are the steps that I took.
Go to this GoogleAndroidImages page and download the appropriate image for your phone & download. Since mine is an international version a.k.a I9023, I chose that ROM.
The download will be a tar.gz file. Use a utility like 7Zip to uncompress it. The tar.gz will have a .tar file inside and the /tar file will have a folder. Extract the folder to your PC. For my download, the folder was named soju-imm76d
Next Steps will wipe your phone, completely
Reboot your phone into bootloader mode.
Open a command prompt, navigate to the folder in step 2.
Enter the below commands, the image file names are for my download, modify it to the file names in your folder before running (I assume that you have fastboot working)
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip​
After the last step, the phone reboots and takes you to the initial setup screen.
Additionally, I reflashed CWM and the the JellyBean OTA along with superuser. Below are the steps for that
Download the OTA from google server
Download the superuser from androidsu website. This is the RC version 3.2
Download the latest clocworkmod recovery touch-version non-touch-version
For simplicity sake, put all the files downloaded at a single folder
Reboot phone into bootloader mode.
Open a command prompt and go to the folder in step 4.
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img​
Now using the vol down key choose to go to recovery.
There, using the options, navigate to the install zip from sdcard and first install the OTA and then the superuser zip file.
Reboot. You now have rooted JB
PS: I additionally did a fastboot oem lock and fastboot oem unlock back to back to wipe my sdcard too
Click to expand...
Click to collapse
Well written. I'm sure you helped hundreds of stressed out newcomers with this. :laugh:

chronophase1 said:
I must have skipped one step during the process though because my "SD" didn't get wiped.
Click to expand...
Click to collapse
yeah.. the fastbbot oem lock and fastboot oem unlock after the 4.0.4 flash wipes the SD
rhadrio said:
Couldn't you just do a factory reset after installing the OTA package?
Click to expand...
Click to collapse
The OTA is essentially an upgrade, it builds atop the existing ICS 4.0.4 rom. I had so much mods on top of my rom that I wasnted to have a clean start. Besides, there has been multiple reports of an error 7 in case of non stock or certain moded roms.
karleeezy said:
Got it! Thanks, dude!
Click to expand...
Click to collapse
Glad I could help
I am already missing the various tweaks I had on the CM9 RC2 and other mods

jithinsarath said:
yeah.. the fastbbot oem lock and fastboot oem unlock after the 4.0.4 flash wipes the SD
Click to expand...
Click to collapse
Thanks for the tutorial. Thinking of doing the update this way. I have a i9020a rooted with 4.0.4 and when I try to do OTA update I got signature verification error in CWM 5.8.0.2.
For the wipe, from what I understand, you just execute the lock command above which wipes the SD and then unlock it with the second command? Sorry total newbie on this.

That is exactly what i did when the OTA zip pacage first showed up here on xda. Good guide. Im rocking mine with simple kernel

I followed the first part of the guide to restore to stock, and then did the OTA update. It all went well except one little catch: after the OTA update for 4.1.1, I flashed the CWM 6.0.0.7, and then realize that I forgot to copy the root zip file onto SD. Had to reboot the phone and copy the file over. After that I go into bootload mode again and try to go to recovery, ends up with a red exclaim mark and phone is locked. Had to do a battery pull, restart the phone, and then reflash that CWM image, and immediately after that, go to recovery and do the root zip install. Not sure why is that. Have not tried to do the recovery again but I'm glad that I'm now on JB and rooted. Thanks OP !

I keep gettin status 7 error.
When i install the OTA through the phone itself (by letting it restart the phone and install it) i get the exclamation mark.
Im on Stock 4.0.4 and not rootet. Is there anyway to install this OTA without fully wipe it?

d960 said:
Thanks for the tutorial. Thinking of doing the update this way. I have a i9020a rooted with 4.0.4 and when I try to do OTA update I got signature verification error in CWM 5.8.0.2.
For the wipe, from what I understand, you just execute the lock command above which wipes the SD and then unlock it with the second command? Sorry total newbie on this.
Click to expand...
Click to collapse
The lock command just lock the bootloader, it is the unlock command that will wipe the SD. It will also ask you for a confirmation on your phone's screen...
d960 said:
I followed the first part of the guide to restore to stock, and then did the OTA update. It all went well except one little catch: after the OTA update for 4.1.1, I flashed the CWM 6.0.0.7, and then realize that I forgot to copy the root zip file onto SD. Had to reboot the phone and copy the file over. After that I go into bootload mode again and try to go to recovery, ends up with a red exclaim mark and phone is locked. Had to do a battery pull, restart the phone, and then reflash that CWM image, and immediately after that, go to recovery and do the root zip install. Not sure why is that. Have not tried to do the recovery again but I'm glad that I'm now on JB and rooted. Thanks OP !
Click to expand...
Click to collapse
when you rebooted the phone to copy the su.zip, the OS restored the oroginal recovery. That's why you got the red exclamation mark. To get the CWm, you can flash it again in fast boot, go into recovery and then ask the CWM to reboot.. if it is 6.0.0.7, before reboot it will ask for the recovery to be made overwrite proof (a nice new feature in v6), choose yes and you are good to go..

alireza_simkesh said:
I keep gettin status 7 error.
When i install the OTA through the phone itself (by letting it restart the phone and install it) i get the exclamation mark.
Im on Stock 4.0.4 and not rootet. Is there anyway to install this OTA without fully wipe it?
Click to expand...
Click to collapse
Status 7 error comes when you have some kind of custom rom or may be some core mod applied to your rom. I am not aware of a way to get this proceed without full wipe: You can try the below though:
1. Flash the stock 4.0.4 for your phone without data wipe (you can wipe the dalvik cache though). This will make sure you are on the "stock".
2. Try the OTA
or you can backup using titanium backup, and then follow my guide. Restore the apps after flashing 4.0.4 and the try OTA.
It will be good it you take a nandroid backup before doing either of the above.

jithinsarath said:
Status 7 error comes when you have some kind of custom rom or may be some core mod applied to your rom. I am not aware of a way to get this proceed without full wipe: You can try the below though:
1. Flash the stock 4.0.4 for your phone without data wipe (you can wipe the dalvik cache though). This will make sure you are on the "stock".
2. Try the OTA
or you can backup using titanium backup, and then follow my guide. Restore the apps after flashing 4.0.4 and the try OTA.
It will be good it you take a nandroid backup before doing either of the above.
Click to expand...
Click to collapse
Flash image or zip?

ironia. said:
Flash image or zip?
Click to expand...
Click to collapse
OK, I'm confused now
As I understand, flashing the .img WILL wipe out the apps & data.
However, I have flashed the CM9 nightlies zip multiple times without loosing the data. Here we are dealing with a stock zip, so I am not sure. You can try the zip method after taking a nandroid backup.

Android 5.1 rolling to LG G Pad 8.3 (Google Play Edition)

https://twitter.com/mathbaliver/status/585232627877163009
Link to OTA file: http://android.clients.google.com/p...-LRX21P.L004_user-LMY47O.L002_user_update.zip

Just got the notification last night! Will try to update today, but I need to unroot and undo a few other system partition modifications first. Looking forward to this!

Very cool! Happy with cm12 rom now, but might try it.... Or wait for cm12.1!

5.1 is nice. Much smoother than 5.0. Hadn't been using my g pad much since picking up a nexus 6 because of the relative lag but 5.1 has made it comparable.

I tried installing it a couple times, but it doesn't install. Tells me I'm still on 5.0.
Is it because I'm rooted? If so, how do I go about getting it updated? Download from the OP's link and flash via TWRP?
TIA.

http://forum.xda-developers.com/showthread.php?p=57114292
I used the method to go back to 4.4.4 and then did the 5.0 update, then 5.1 update.

Another option for users with TWRP installed to get to 5.1: http://forum.xda-developers.com/showpost.php?p=59976617&postcount=43
This avoids using the TOT restore, and lets you do the upgrade without wiping /data

Thanks for that. I found that even with restore recovery unchecked I still lost TWRP, but it wasn't hard to put it back on again.
Now I'm up and running in 5.1 and I didn't lose any of my data! Cheers!

Rocket321, do I need to rename the download to a .zip extension? TWRP isn't picking it up.

rocket321 said:
Another option for users with TWRP installed to get to 5.1: http://forum.xda-developers.com/showpost.php?p=59976617&postcount=43
This avoids using the TOT restore, and lets you do the upgrade without wiping /data
Click to expand...
Click to collapse
needtoride said:
Rocket321, do I need to rename the download to a .zip extension? TWRP isn't picking it up.
Click to expand...
Click to collapse
That's a TWRP nandroid backup. You need to put it in the folder your TWRP creates when you make a backup, and restore from it.
Sent from my VK810 4G

needtoride said:
Rocket321, do I need to rename the download to a .zip extension? TWRP isn't picking it up.
Click to expand...
Click to collapse
Unzip the 7z file with 7-zip and then copy to the twrp subfolder where backups go. I guess there are also archive apps you could use to extract on your device directly.
Once you do that, boot to twrp and tap restore.

[n910c] go back to stock rom from cm13. [bootloop/ imei/network problem fixed 100%]

MY GUIDES TOWARDS VICTORY:-
FR34K-B1B0
vaskodogamagmail
HmanA6399
Peontikos_Desmos
I am truly very much grateful to you guys! Owe you!!!
TOOLS YOU NEED:-
EFS PROFESSIONAL (PC) [Get it here!]
TWRP Recovery Installed Phone [Get it here!]
BUSY BOX PRO (APK) [Get it Here!]
ODIN (PC)
N910C PIT FILE (FIND ONE FOR YOUR EXACT PHONE MODEL!)
APPROPRIATE STOCK ROM. (AS PER YOUR CURRENT BASEBAND VERSION!)
ROOT EXPLORER PRO (APK).[Get it here!]
Okay, Now carefully follow my instructions.
BOOTLOOP FIX
Make a TWRP NANDROID BACKUP of your current properly working ROM [eg: CM13].
Make sure that your phone is rooted. Then, Install Busybox (Run the application and then install busybox) and Root Explorer in your current custom ROM (Don't forget to grant root permissions).
In Root Explorer, Go to root (R/w mode enabled), Enter EFS folder, Copy the following files to your SD card.
imei (folder)
.nv_data.bak (file)
(Keep these two things safe somewhere, Because you will need it later to fix your IMEI)
In your phone settings, make sure 'USB debugging' is enabled from 'Settings->Developer Options->'.
Run 'EFS Professional' on PC. (On your PC, Make Sure that you have installed 'Samsung USB Drivers' from here & 'Google adb USB drivers' from here.)
Connect the phone to PC, Grant root access to your PC by confirming the dialog box showing up in the phone.
On EFS Professional, Go to "Samsung Tools" tab , Go to "Other tools" and select "Format EFS Folder" then click "Execute".
Power off the phone, Reboot into TWRP Recovery.
Wipe all data/factory reset.
Power down the Phone and Reboot into 'Download' mode.
Start ODIN on PC and Connect the Phone.
In Odin, Load the 'PIT' File, Check 'Re-partition' and Load your Stock ROM file to AP. Click Start to flash the stock firmware.
VOILA!! ONCE FLASHING IS DONE, YOUR PHONE WILL BE AUTOMATICALLY REBOOTED INTO YOUR STOCK ROM WITHOUT ANY FRUSTRATING BOOTLOOPS !!!!!!
NOW YOU PEOPLE WILL BE FACING A 'NOT REGISTERED ON THE NETWORK' PROBLEM. DON'T WORRY! LET'S FIX IT! FOLLOW MY LEAD!
EFS / IMEI FIX
Boot to your new stock ROM.
Install BusyBox (Run the application and then install busybox) and RootExplorer.
Start 'root explorer', Go to root ((R/w mode enabled), Go to EFS folder
Delete all the files and Restart the phone.
Again repeat 'Step 3'.
Now you will see some files again. Now, carefully delete only the 'imei' folder and 'nv_data.bin' file.
Make two copies of your previous ROM backup file ".nv_data.bak" into the new ROM's EFS folder and rename it to "nv_data.bin" and "nv_data.bin.bak" respectively.
Finally, Reboot the Device.
THATS IT! YOU NOW GOT YOUR NETWORK BACK!!! ENJOY THE STOCK ROM!!!!
(Keep a TWRP Nandroid backup of your Stock ROM. It will help you out from other troubles in the future!)
Hit 'Thanks' If I helped you out!! Ask for more assistance!
Cheers!
Arun

Grrrrr8??
Sent from my HTC Desire 820s dual sim using Tapatalk

Can anyone confirm this works?
I attempted this method with not much luck in the end

Same, when i open the EFS folder / copy it with Root Explorer, and it say need Root Access. When i press okay the phone is rebooting. Please someone help me.

I'm glad you got your phone back!
But I still don't know what the EFS folder has to do with the bootloops. I guess we should try the following
1- Make an EFS backup in your CM13 rom (just in case) but don't delete anything.
2-Go to recovery and wipe data cache and dalvik.
3-Reboot in download mode and connect your phone to your pc, then open ODIN.
4-Load your .PIT file and tick 'Repartition". Add your stock TW 5.1.1 rom and flash everything
5-Wait until it boots and check if you have signal.
I've used CM12 and reverted to stock Lollipop doing these steps (even without repartitioning) and worked just fine but maybe CM13 partitioning is different. Can anyone follow these steps and report what happend? Remember to make an EFS backup (as I said, just in case) before.

AlStarsKyz said:
Same, when i open the EFS folder / copy it with Root Explorer, and it say need Root Access. When i press okay the phone is rebooting. Please someone help me.
Click to expand...
Click to collapse
Give me more details about your phone, So that I can help you!

ColtD said:
Can anyone confirm this works?
I attempted this method with not much luck in the end
Click to expand...
Click to collapse
Tell me what happened for u. I will assist you.

galaxynote2 said:
I'm glad you got your phone back!
But I still don't know what the EFS folder has to do with the bootloops. I guess we should try the following
1- Make an EFS backup in your CM13 rom (just in case) but don't delete anything.
2-Go to recovery and wipe data cache and dalvik.
3-Reboot in download mode and connect your phone to your pc, then open ODIN.
4-Load your .PIT file and tick 'Repartition". Add your stock TW 5.1.1 rom and flash everything
5-Wait until it boots and check if you have signal.
I've used CM12 and reverted to stock Lollipop doing these steps (even without repartitioning) and worked just fine but maybe CM13 partitioning is different. Can anyone follow these steps and report what happend? Remember to make an EFS backup (as I said, just in case) before.
Click to expand...
Click to collapse
You can't simply restore a lollipop backup into marshmallow. Trust me, It won't work.

arunkrishnanr said:
Give me more details about your phone, So that I can help you!
Click to expand...
Click to collapse
What can i say to you?

AlStarsKyz said:
What can i say to you?
Click to expand...
Click to collapse
Where do you face the problem while doing this method?

arunkrishnanr said:
Where do you face the problem while doing this method?
Click to expand...
Click to collapse
When i'm open the EFS folder with Root Explorer, my phone got reboot automatically. And i try to copy it too and it's still rebooting. I got that after receive the verification root and i press ok, and i my phone reboot it self automatically.

AlStarsKyz said:
When i'm open the EFS folder with Root Explorer, my phone got reboot automatically. And i try to copy it too and it's still rebooting. I got that after receive the verification root and i press ok, and i my phone reboot it self automatically.
Click to expand...
Click to collapse
Try again. Use CF root to properly root your stock ROM. And then flash TWRP Recovery. Then setup busybox and root explorer in your stock rom. Make a backup of your EFS folder by copying it somewhere safe.
I used this method and I worked fine for me.

arunkrishnanr said:
Try again. Use CF root to properly root your stock ROM. And then flash TWRP Recovery. Then setup busybox and root explorer in your stock rom. Make a backup of your EFS folder by copying it somewhere safe.
I used this method and I worked fine for me.
Click to expand...
Click to collapse
Btw, i got this problem only on CM13, but when in stock it's working to open the EFS folder.

At least credit me

FR34K-B1B0 said:
At least credit me
Click to expand...
Click to collapse
May I ask why?

arunkrishnanr said:
May I ask why?
Click to expand...
Click to collapse
May i ask help me?

arunkrishnanr said:
May I ask why?
Click to expand...
Click to collapse
Because you're using the method I found?

FR34K-B1B0 said:
Because you're using the method I found?
Click to expand...
Click to collapse
Yes! Im sorry.. you are the one who helped me in the end.. i will credit u for sure..

AlStarsKyz said:
May i ask help me?
Click to expand...
Click to collapse
Sure. First of all, if your phone model is N910C and you are facing the problem, I would recommend you to try again my methods carefully. If you are facing any difficulty, Please let me know!

AlStarsKyz said:
Btw, i got this problem only on CM13, but when in stock it's working to open the EFS folder.
Click to expand...
Click to collapse
If your stock rom is working, then all you have to do is to follow the steps in the 'IMEI Fix'. Try that! But I hope you have made the backup from cm13.

Help with rooting nougat mate 8 + Question

Warning: This is probably gonna be a long post and may have typos.
Now, let's cut to the chase.
I'm currently on my Mate 8 emui.4, I had my phone rooted a while ago with TWRP and SuperSu. After rooting, I had the nougat update and I updated without knowing that it would remove TWRP and my root access. That was not the only problem! I couldn't switch on my Bluetooth. Also I lost the update option from the about phone location. I tried searching it in the search bar and clicking on the update button but, nothing would open up. And.. Yes, it was an official update. I tried to root it with the usual method but, it got me into a bootloop. I tried most TWRP versions but, it didn't seem to work! Either there would be no recovery (just a Black screen with some text) or the options inside the TWRP recovery wouldn't work. So I rerolled back to Mate 8 marshmellow. Now I don't have root, no TWRP or unlocked bootloader. So my question is if I should root my current phone version of emui.4 and be satisfied by it by unlocking bootloader now and rooting it, or update my phone to Mate 8 nougat again? If you're suggesting I update to nougat please provide me with ALL the necessary files to root Nougat and please guide me through. And provide me with the information on what to do in the worst case scenario too.. Please .

@Devil Chan
I think you should make like that:
Download the new firmware without to install it
Unpack the bigger file in a dload folder created on the external sd. You must to have a big file (more than 1 GB), inside you should find an update.app file, you put this one on the dload folder
Unlock bootloader
Install insecure boot for your current firmware (B200)
Install twrp
Reboot to twrp
Wipe - factory reset
Format data
Power off your phone
Install new firmware via the 3 buttons combo
After installation, make a factory reset via erecovery
Power off the phone and reboot to bootloader
Install Decrypted data boot for the B560
Install frd-twrp
Reboot to the twrp
Format data
Reboot to the twrp
Install update data of NXT-L29C185B560, I think you also have it in the downloaded files of your new firmware
Install supersu EMUI 5.0
Reboot system - normally fully rooted
For the 1 & 2, I think the files are like I said, if no, don't make this tuto. You shall see otherwise.
For the 4, it's the little issue. You must to recover a stock boot B200 and I could make you the insecure boot or Decrypted data boot, it's almost the same.
For the root questions, we can continue here.
This may seem very complicated but don't worry, it's not!

[[/QUOTE]
franzyroy said:
@Devil Chan
I think you should make like that:
Download the new firmware without to install it
Unpack the bigger file in a dload folder created on the external sd, you must to have a big file (more than 1 GB), inside you should find an update.app file, you put this one on the dload folder
Unlock bootloader
.....
Install supersu EMUI 5.0
Reboot system - normally fully rooted
For the 1 & 2, I think the files are like I said, if no, don't make this tuto. You shall see otherwise.
For the 4, it's the little issue. You must to recover a stock boot B200 and I could make you the insecure boot or Decrypted data boot, it's almost the same.
This may seem very complicated but don't worry, it's not!
Click to expand...
Click to collapse
First of all thank you so very much for replying,
I'm sorry, I'm a newbie. I have a few questions.
Where do I download the firmware from? link me to it please?
What is insecure boot? Flash using fastboot? Link?
7 and 8, Factory reset doesn't format data? Using erecovery or TWRP?
What's frd-twrp? How do I install it?
Step 10 and 18, after installing the new firmware, why would I need to update it? How do I update it?
Can you make me the insecure boot? I don't know how to use it? Do I just flash it with fastboot?
Sorry got asking so many questions.. I feel really bad asking this many.

I can't answer now, I try to answer you later.

franzyroy said:
I can't answer now, I try to answer you later.
Click to expand...
Click to collapse
Ok, later then..

Devil Chan said:
Where do I download the firmware from? link me to it please?
What is insecure boot? Flash using fastboot? Link?
7 and 8, Factory reset doesn't format data?
Using erecovery or TWRP?
What's frd-twrp? How do I install it?
Step 10 and 18, after installing the new firmware, why would I need to update it?
How do I update it?
Can you make me the insecure boot?
I don't know how to use it? Do I just flash it with fastboot?
Click to expand...
Click to collapse
Your first screenshot, you can update it there.
Insecure boot is a boot.img which enable you to decrypt your data folder. It's necessary to root. You flash it with fasboot, ok.
Yes, Factory reset doesn't format the data
TWRP
it's a unofficial twrp for Nougat. You flash it with fasboot
Because you should format the data before
Via TWRP if it's really like I think (obtained files in the update)
Yes if I've the stock boot. Normally you can recover it via ADB
Yeah

franzyroy said:
Your first screenshot, you can update it there.
Insecure boot is a boot.img which enable you to decrypt your data folder. It's necessary to root. You flash it with fasboot, ok.
Yes, Factory reset doesn't format the data
TWRP
it's a unofficial twrp for Nougat. You flash it with fasboot
Because you should format the data before
Via TWRP if it's really like I think (obtained files in the update)
Yes if I've the stock boot. Normally you can recover it via ADB
Yeah
Click to expand...
Click to collapse
If I update from the location of the screenshot, won't it update automatically?
Possibly final question, I get files for step 10 from the screenshot location.. But, where do I get the file for step 18 that I have to install with twrp?

Devil Chan said:
If I update from the location of the screenshot, won't it update automatically?
Possibly final question, I get files for step 10 from the screenshot location.. But, where do I get the file for step 18 that I have to install with twrp?
Click to expand...
Click to collapse
Normally no.
Normally it proposes you at least 2 files, one bigger than 1 GB and another smaller than 1 GB. First is update and second is update data

franzyroy said:
Normally no.
Normally it proposes you at least 2 files, one bigger than 1 GB and another smaller than 1 GB. First is update and second is update data
Click to expand...
Click to collapse
1. So I have to place the first on in dload and second one update with TWRP?
2. In case I mess up something... I just have to reroll back to marshmellow using dload with the older update data. Right?
? Thank you so very.. Very.. Very much for you time
I'm sorry for asking so many questions! Again..

Devil Chan said:
1. So I have to place the first on in dload and second one update with TWRP?
2. In case I mess up something... I just have to reroll back to marshmellow using dload with the older update data. Right?
Click to expand...
Click to collapse
The first should be update.app file extracted to the big file (above 1 GB), you will put it in dload. The second will be a zip what you will install with the TWRP.
Via dload method, yes!
Show me files once downloaded in order to be sure!

franzyroy said:
The first should be update.app file extracted to the big file (above 1 GB), you will put it in dload. The second will be a zip what you will install with the TWRP.
Via dload method, yes!
Show me files once downloaded in order to be sure!
Click to expand...
Click to collapse
Where will the downloaded update be located?

Devil Chan said:
Where will the downloaded update be located?
Click to expand...
Click to collapse
Look to the internal SD... certainly there!

franzyroy said:
Look to the internal SD... certainly there!
Click to expand...
Click to collapse
Thank you found them. An update.zip and an update_data_full. Can you get me the B200 insecure boot?

Devil Chan said:
Thank you found them. An update.zip and an update_data_full. Can you get me the B200 insecure boot?
Click to expand...
Click to collapse
Fine

@Devil Chan
Look that! This is the decrypted boot img of your build.

franzyroy said:
@Devil Chan
Look that! This is the decrypted boot img of your build.
Click to expand...
Click to collapse
Thank you for all your help.

Devil Chan said:
Thank you for all your help.
Click to expand...
Click to collapse

Working root for honor 8 pro

This is only for Honor 8 Pro (DUK-L09)​
DISCLAIMER​YOUR WARRANTY IS NOW VOID. IN NO WAY AM I RESPONSIBLE FOR THE EFFECTS YOU INFLICT ON YOUR MOBILE DEVICE BY FOLLOWING THE BELOW PROCEDURE. IMPROPER USAGE OF THE METHOD MIGHT END UP BRICKING YOUR DEVICE AND RENDERING IT UNUSABLE.
PLEASE BACKUP ALL YOUR DATA BEFORE PROCEEDING.​
Purpose of this thread is to provide a working rooting method for the Honor 8 Pro. Flashing Phhsuperuser doesn't grant SYSTEM WIDE root permission.
Functions like granting -rw permissions to apps demanding them for accessing /system partition was disabled, TWRP backup wouldn't work.
With this method, you will be able to operate the phone will proper root privileges.
INSTALLATION INSTRUCTIONS
1. UNLOCK BOOTLOADER​
Assuming you have a Huawei ID, use THIS PAGE to get your Unlock code.
Once you have that, enable USB debugging on your device from Developer options menu.
Make sure "Allow OEM unlock" option is selected.
Use the following set of commands via ADB/Fastboot:
adb device (this should recognize your device)
adb reboot bootloader (this will boot your phone into fastboot mode)
fastboot oem unlock *unlock key* (the part between * is where the unlock key goes)
The device will restart and then perform factory reset itself.
2. INSTALL CUSTOM RECOVERY IMAGE (Source : TWRP Thread by OldDroid)​
Download TWRP recovery image from HERE
Rename the downloaded file to recovery.img
Copy it to the ADB folder that you are using.
Use the command "adb reboot bootloader" like in Step 1 to boot into Fastboot mode.
Flash the recovery using "fastboot flash recovery recovery.img" command (without quotes)
You have now flashed a custom recovery onto your phone.​
3. ROOTING
Download Magisk installer zip file from THIS LINK . I had personally used v 13.3 .
Copy it to your SD card(I would suggest you to use a external card).
Switch off your device.
Boot into recovery mode by pressing Volume Up and Power Button together.
Once in, swipe to allow modifications.
Go to Wipe - Format Data
Then Go to Reboot- Recovery
You should be back into the recovery mode. Go to Install menu - Select storage - Install the Magisk zip that you downloaded.
Once it is flashed, you can Reboot to system.
Note: To confirm system wide root access, you can reboot to recovery and try to take a Nandroid backup. It should now be possible.​
If anyone happens to run into a bootloop or soft bricks the device, THIS THREAD by @aKp1 will come in handy.
Thanks to @OldDroid for his TWRP thread.

I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.

Going back to Stock = Unrooting
devilrulz4ever said:
I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.
Click to expand...
Click to collapse
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.

amulbaby said:
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.
Click to expand...
Click to collapse
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?

devilrulz4ever said:
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?
Click to expand...
Click to collapse
Don't worry . It's the same. File name doesn't matter.

amulbaby said:
Don't worry . It's the same. File name doesn't matter.
Click to expand...
Click to collapse
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Sent from my Honor 8 Pro using XDA Labs

adriansticoid said:
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Click to expand...
Click to collapse
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.

amulbaby said:
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.
Click to expand...
Click to collapse
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Sent from my Honor 8 Pro using XDA Labs

Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem

adriansticoid said:
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Click to expand...
Click to collapse
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.

rexinriot said:
Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem
Click to expand...
Click to collapse
Yes magisk will solve your problem. Phhsuperuser doesn't allow you to grant permissions to any app that tries fiddle with system partition. If you are already rooted , go back to stock and follow the steps outlined.

amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
Dafuuuuq. I waa scared all along because of that. I didn't know things changed in Honor 8 Pro. Thanks a lot.
Sent from my Honor 8 Pro using XDA Labs

amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.

devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You flashed Magisk while encrypted?
Sent from my Honor 8 Pro using XDA Labs

devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.

adriansticoid said:
You flashed Magisk while encrypted?
Click to expand...
Click to collapse
Have you managed to root your device using Magisk yet?

amulbaby said:
Have you managed to root your device using Magisk yet?
Click to expand...
Click to collapse
Not yet. Maybe I'll try tomorrow.
Sent from my Honor 8 Pro using XDA Labs

amulbaby said:
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.
Click to expand...
Click to collapse
I wiped data, flashed Magisk v13.3 and then v14 after a successful boot (without wipe).

Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..

rexinriot said:
Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..
Click to expand...
Click to collapse
Stay with 130. Surprisingly, rooting by this method still allows OTA to come in.