Related
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
Credits go to @nlooooo for starting this thread!
WARNING
I’m not responsible for bricked devices, all you do is on your own responsibility. Most of the processes I’ll mention will work with some vital parts of your phone, so if you don’t have enough courage or until you don’t understand all the things you should do I recommend not to get involved with this.
Click to expand...
Click to collapse
Ok, there's a tool for almost all of that. Tool is updated, but you need to be sure to click the button for the right recovery, explanation below.
1. UNLOCKING OF BOOTLOADER
Everything starts with this. Unlocking of bootloader will allow you to make changes to some critical partitions of your phone (boot, system and recovery) and will allow you to flash custom recovery that can be used for installing of custom roms, mods and all kind of flashable zips. However, it won't s-off your phone, and other critical partitions (bootloader, radio) remain inaccessible.
So, I won't explain how to do that. Why? Because if you successfully unlock bootloader on your phone it means that you received enough knowledge for the rest of the process and you're qualified to go further.
This process will factory reset your phone (erase data partition) so backup your stuff before you proceed.
Ok, now go to htcdev.com, register your account, go to unlock bootloader section, for the device choose 'All other supported models' and follow the instructions carefully everything is explained in details. Pay attention to 'Required resources' on the first page after confirmation - you need Android SDK platform tools Java Runtime Environment and HTC Sync installed and there are all needed links. Files mentioned in step 5 you will find in Android Bundle zip you downloaded in folder adt-bundle-windows-x86_64\sdk\platform tools.
Here are some useful links about Android SDK platform tools, you won’t be needing most of it but it won't be bad to read.
http://developer.android.com/tools/help/adb.html
http://android-dls.com/wiki/index.php?title=ADB
http://android-dls.com/wiki/index.php?title=Fastboot
http://wiki.cyanogenmod.org/wiki/fastboot
Remark: once unlocked bootloader can be relocked but can never be locked again. This can be done issuing command from fastboot:
fastboot oem lockThis means that on the top of you bootloader screen you’ll have a sign RELOCKED instead of LOCKED, which is a notice to HTC that you unlocked it once. Plus they have data about all users that requested unlock_code so they can deny your warranty whenever they want.
If you’ve successfully unlocked your phone bootloader we can proceed to the next step.
Click to expand...
Click to collapse
2. CUSTOM RECOVERY INSTALLING
- Go to this address:
http://forum.xda-developers.com/showthread.php?t=2502327There you can find custom recoveries for DesX. Some of them have a few bugs but they are generally functional. Download one of your choice, rename it to recovery.img and put it on the root of c: drive on your PC. Before downloading, read the thread linked to carefully, as it is important to check your hboot before installing a custom recovery.
Remark: you can use recovery image provided in WindyCityRockr's tool.
- Go here:
http://download.chainfire.eu/370/SuperSUdownload SuperSU, connect your phone to PC and put it somewhere on your phone sd card.
- Do not disconnect your phone from PC, reboot phone to fastboot on one of this ways :
1. choose restart from power menu and when the screen comes off wait for the buttons to turn off and immediately push volume down, the phone will boot to bootloader, then select fastboot from bootloader menu
2. issuing command
adb reboot-bootloaderfrom command prompt that will take you directly to fastboot
- once you’re in fastboot mode open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash recovery c:\recovery.img
fastboot reboot-bootloader
fastboot erase cache
The second and third commands are not quite necessary but they don’t harm and leave your phone with no trails of previous recoveries. Now you can disconnect your phone from your PC.
Click to expand...
Click to collapse
3. BACKING UP STOCK ROM
Now it is really important to backup your stock ROM. Dependent on your CID and hboot version, you can't use RUU to get back to stock, especially if your phone is branded by your carrier. Also, RUUs are only available for ICS bootloader (hboot 1.24 and lower). For JB there are only nand backups for a few CIDs uploaded by some nice xda members. So if you definitely want to be able to get back to stock any time, you'll have to backup your current configuration first. That's done by:
Reboot your phone to recovery
Backup -> Select all partitions -> Swipe to BackupThat will take some time. After that's finished, you should make a copy of that backup somewhere safe (it's located on the sdcard in folder TWRP, just copy the whole folder somewhere).
Click to expand...
Click to collapse
4. ROOTING YOUR PHONE
- From fastboot menu choose bootloader and then recovery to reboot phone to recovery
- If you successfully boot to recovery choose options:
Install zip from sd card
Choose zip from sd cardNavigate to UPDATE-SuperSU-vx.xx.zip you stored on sd card and choose it. Once the installation is finished reboot your phone. Now you should see SuperSU app in app drawer and your phone is rooted.
Click to expand...
Click to collapse
5. CUSTOM ROMS INSTALLING
There are already quite a few ROMs available for our device. But watch out... many of them are discontinued, mostly the CM ROMs as well as the ROMs based off CM. Go here for the index:
http://forum.xda-developers.com/showthread.php?p=35735267#post35735267That’s the Index thread I created for all user to track development for our device. There you’ll find roms that can be installed.
I have to emphasize that every chef gives an instruction how to install his rom, so here I’ll just give you the basics for custom rom installing using custom recovery.
- Download the rom of your choice and put it on the sd card of your device
- Unpack boot.img from rom.zip and put it on the root of c: drive on your PC
- Reboot phone to recovery
- Choose option ‘wipe data/factory reset’
- Choose option ‘wipe cache partition’
- Choose option ‘advanced’ and in next menu choose ‘wipe dalvik cache’
- Go back to main menu and choose ‘install zip from sd card’ and then ‘choose zip from sd card’
- Navigate recovery to rom zip you put on sd card and choose it
- Wait until the installation is finished
- Reboot your phone to fastboot and connect it to your PC
- Open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash boot c:\boot.img
fastboot reboot-bootloader
fastboot erase cache- Reboot your phone
The last few steps are needed since there is no way to s-off our device, so boot.img included in rom.zip has to be flashed separately via fastboot.
Remark: don’t ever forget for the golden rule of flashing ‘Always make a nand backup before you flash something'.
Click to expand...
Click to collapse
6. S-OFF
As S-OFF makes your device vibrating 7 tmes on each boot, you should really think about if you need it. If you are not sure about it, then it's not for you. If you still want to do it, go here:
http://forum.xda-developers.com/showthread.php?t=2630531
http://forum.xda-developers.com/showthread.php?t=2667156Use the first link to get to the files needed to do your S-OFF. In the second link you'll find the things you can do after the S-OFF procedure including downgrading the hboot in order to install RUUs etc.
Click to expand...
Click to collapse
Ok, I did what I had promised, all suggestions and corrections are more than welcome.
All this came as 2 years experience with HTC phones (had Desire and Incredible S before), unlocking, rooting and taking their guts out .
Sources and links posted:
- HTC Developers site
- WinDroid HTC Desire X Toolkit v2.1 made by WindyCityRockr
- Android Developers site
- Cyanogen Wiki site
- SuperSU made by Chainfire
- Thanks to ckpv5 for nand ICS backup thread
- Thanks to Izzy Stinson for pointing me to things not explained enough
- Sources for recoveries can be found in my recovery thread
- Thanks to GtrCraft for the idea to include the backup of stockrom
- Thanks to nightwalkerkg and the rumrunners team for getting us the S-OFF
- Again thanks to ckpv5 for the S-OFF tutorial
Going back to stock for official update
Now to say more about a reverse part. The point of this is to make your phone available for official updates, and make it possible to do. Thanks to Ranalakshay36 and Bedroom we have information that you can apply OTA without need to relock bootloader on the phone. However, relocking is still mandatory if you want to install a fresh new rom using RUU.
The first important thing for this is: PEOPLE, MAKE A NAND BACKUP OF STOCK ROM BEFORE REMOVING OF ANY APP FROM SYSTEM OR INSTALLING A CUSTOM ROM!!! This will make this process much easier to do.
RECEIVING AND OFFICIAL UPDATES INSTALLING
Part one:
Ok, you just unlocked bootloader and rooted your phone (no custom rom installed), but you received a notification that you have an official update available and you want to install it. No problem at all if you didn't touch the apps on system partition (some of them are necessary for official support), and all you have to do are these 2 things:
1. Reinstall stock recovery - I attached it. Remember the part about custom recovery? The process for this is the same:
- download recovery I attached, rename it to recovery.img and put it on the root of c: drive on your PC
- reboot phone to fastboot
- connect it to a PC
- open command prompt and guide it to the folder where you have adb platform tools installed
- issue commands
fastboot flash recovery c:\recovery.img
fastboot reboot-bootloader
fastboot erase cache
Now your phone should be ready to apply official update.
Click to expand...
Click to collapse
Part two:
1. You installed a custom rom, however you made a nand backup of your intact stock rooted, so all you need is to restore your nand backup and go to "Part one", that will do a thing.
2. You installed a custom rom, however you didn't make a nand backup of your intact stock rooted, or you deleted some important files from system partiton. So, you're almost scre**d. I said almost because you can ask some of your geeky friends to borrow you his nand backup that you can use for restore.
The best option is to revert back to stock using RUU, but that's currently limited only for devices with Europe based firmware. Here is the thread I made where you can find info about 1.18.401.1 RUU and CID compatibility and a way to check CID of your phone to make sure you can use it:
Get CID and RUU 1.18.401.1 Compatibility
RUU Download page
To run RUU you need to relock your bootloader. This is how you can do it:
- reboot phone to fastboot
- connect it to a PC
- open command prompt and guide it to the folder where you have adb platform tools installed
- issue command
fastboot oem lock- the phone should restart automatically and you'll have a sign RELOCKED on the top of bootloader screen.
After you successfully relock bootloader you can run RUU directly from fastboot. With earlier HTC models there was I a way to bypass CID checking and use any RUU to revert back to stock using a GoldCard, but someone told me that it's not possible with Desire X.
Remark: once you relock bootloader it can be unlocked again in the same way you did it for the first time, and, of course, it will factory reset you phone. Also, going in this order is mandatory, cause if you relock bootloader before you flash stock recovery, you won't be able to do that with relocked bootloader
Click to expand...
Click to collapse
If you can't run a RUU because of incompatible CID, you have to have a nand backup ready for restoring or else to find one in the forums. Here is a thread with different nand backups incompatible from the RUUs:
ICS nandroid backups
Follow the instructions in the above thread to restore your backup.
Click to expand...
Click to collapse
Credits:
- Cobje - stock recovery img from latest update (1.18.xx)
http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
- Ranalakshay36 and Bedroom for the intel.
Reserved once more...
Nice on nlo, will hopefully stop alot of the questions
Good job writing this tutorial!
One small remark: unlocking bootloader via htcdev will hard-reset the device so all data on the phone will be lost. Might be useful to mention this so users can back-up as much as possible on an un-rooted device.
nightcrow said:
Good job writing this tutorial!
One small remark: unlocking bootloader via htcdev will hard-reset the device so all data on the phone will be lost. Might be useful to mention this so users can back-up as much as possible on an un-rooted device.
Click to expand...
Click to collapse
Thanks, forgot about that while I was writing all this stuff.
I can imagine it's quite a story
Anyway well done and it will definitely be useful to the ones that are about to dive into the rabbit-hole.
thanks for the tutorial! very easy to understand and very simple. :good::good::good:
thanks for the tutorial! nice Job men.:good:
a very well written master piece tutorial. absolutely easy use of english as well without most technical jargon. keep up the good work.
here after m gonna redirect such noob questions to this page.
ayyu3m said:
a very well written master piece tutorial. absolutely easy use of english as well without most technical jargon. keep up the good work.
here after m gonna redirect such noob questions to this page.
Click to expand...
Click to collapse
When an English gentleman says that's an easy use of English I somehow get delighted...
Updated, added flashing boot.img via fastboot for custom roms installing.
thx man, its very helpful for noobs like me who cant follow every thread
there is one more thing i need you help to do it .. how to install busybox ?
I tried all the market apps but i keep getting they same problem "failed to install, try other version or different location"
AxR979 said:
thx man, its very helpful for noobs like me who cant follow every thread
there is one more thing i need you help to do it .. how to install busybox ?
I tried all the market apps but i keep getting they same problem "failed to install, try other version or different location"
Click to expand...
Click to collapse
Try here, here you can find it as a flashable zip.
http://forum.xda-developers.com/showthread.php?t=1929852
nlooooo said:
Try here, here you can find it as a flashable zip.
http://forum.xda-developers.com/showthread.php?t=1929852
Click to expand...
Click to collapse
it worked !! thx
any idea how to keep the changed font after restarting ? it appears the system revert any change i do
I have one question, after I done process 1 and 2, can I factory reset again from the settings without losing root and still keep bootloader unlocked?
Sent from my HTC Desire X using xda app-developers app
Izzy Stinson said:
I have one question, after I done process 1 and 2, can I factory reset again from the settings without losing root and still keep bootloader unlocked?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Of course you can, factory reset deletes only data partition while all others stay intact, and Superuser app is located on system partition, while bootloader can't be accessed from there, only from fastboot.
nlooooo said:
Of course you can, factory reset deletes only data partition while all others stay intact, and Superuser app is located on system partition, while bootloader can't be accessed from there, only from fastboot.
Click to expand...
Click to collapse
thanks. and one last question. you gave 3 links to download for cwm recovery. which of those three are the best cwm for you?
For me the best is 4ext, but it's not released yet for our device.
I would go with Claudyy's version.since it doesn't have a screen shift bug.
nlooooo said:
For me the best is 4ext, but it's not released yet for our device.
I would go with Claudyy's version.since it doesn't have a screen shift bug.
Click to expand...
Click to collapse
so i guess im gonna download clauddy cwm then.
so it is CWM-protou.img, i should rename it to recovery.img right?
sorry for asking so many questions, i dont like to make mistakes when doing this kind of things.. :silly:
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
shatterstar78 said:
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
Click to expand...
Click to collapse
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Restorer said:
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Click to expand...
Click to collapse
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
shatterstar78 said:
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
Click to expand...
Click to collapse
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Restorer said:
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
I can't tank you enough for your help in pointing me in the right direction. I'm now back up and running:good: The first guide got me close, but did not fully unbrick, so I got creative. I will list the steps I took to maybe help others out.
1. First you need Fastboot get it here(http://matthill.eu/content/downloads/transformerprime-unlock/fastboot.zip)
1b. You will need the Universal_Naked_Driver found here (http://matthill.eu/content/downloads/transformerprime-unlock/Universal_Naked_Driver_0.72.zip)
1c. Unzip the drivers somewhere, if at any point during this guide Windows detects your tablet as an unknown device, point it to this location for the drivers.
2. Unzip fastboot.zip somewhere preferably in C:\ (I found that folder names with spaces can cause problems)
3. Download the official update for your device from Asus. Make sure you get the right one, US, EU, WW, etc.
4. Unzip the update twice so that way you have a blob file.
5. Place the blob file into your fastboot folder.
6. Open a command prompt and navigate to your fastboot folder and enter the fallowing commands.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This next command will take the longest. Also you will notice the green RCK icon will stop flashing and you will have a blue progress bar, This is normal. Do not run the last command(reboot) until the green RCK logo starts flashing again and the blue progress bar is full.
fastboot -i 0x0B05 flash system c:\fastboot\blob (your path may vary depending where you placed the fastboot folder)
Now that all is done run the last command.
fastboot -i 0x0B05 reboot
If you are back up and running congratulations you are unbricked, but if you are stuck at the white Asus logo follow the next additional steps. Only do this if you are not fully booting up after the first part of this guide.
1. You will need a microsd card(32G max) and has to be formatted to Fat32.
2. Next you are going to take the Asus update you downloaded above, and unzip it ONLY ONCE and rename it to EP201_SDUPDATE.zip
3. Place the newly renamed EP201_SDUPDATE.zip on your sdcard, make sure its on the root directory and not in a folder.
4. Now reboot to fastboot (Hold Power and Volume Down) Press Volume Up when the white text at the top appears.
5. When the fastboot menu comes up with RCK icon selected press Volume up.
6. Go have a beer, this will take some time. Do not touch anything, when it is done the Asus configuration wizard will be displayed.
7. Congratulations you are now hopefully fully unbricked.
Some Tips:
1. Make sure you have "Show File Extensions" enabled in Windows, if not then when you rename the update to "EP201_SDUPDATE.zip" it will actually be "EP201_SDUPDATE.zip.zip".
2. Use Windows 7 if possible, Windows 8 just causes problems.
3. Disable Windows UAC or run fastboot as administrator.
4. Use a stock OEM data cable.
5. Make sure you have a fully charged tablet, cant stress this enough if your battery dies during this process, then you are in some serious trouble.
Credit goes to Buster99 for discovering the first part of this guide.
Bricked my prime
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
maze44 said:
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
Click to expand...
Click to collapse
Did you do a NVflash backup before all of this happened? If you did you can follow this guide to unbrick http://forum.xda-developers.com/showthread.php?t=2538028
I think the problem is "TWRP v2.7.1.0". I'm going to look more into it to see if I can figure what the problem is.
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
dangoon said:
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
Click to expand...
Click to collapse
Well I made some progress, I figured out why I could not mount partitions. Turns out that when I hit "Format Data" and thought that it froze, well it did not freeze it just takes really long to finish(~30min). Now I can install it, but no matter what I try it all ways gets stuck at the 4 penguins on the latest version or the bootanimation on the older version. I have tried every combination of twrp recovery's, kernals and varies versions of the rom, but still no luck. I have tried probably every rom available for this tablet and this is the only rom that just refuses to install. From the sounds of some of the problems this rom has I really don't want to use it, but now im so pissed off that I have to figure out why the hell this thing is not working I just cant quit.
[UPDATE]
Ok got it all squared away. Everything all up and running. The second part of my problem (getting stuck at bootanimation) was caused by doing a factory reset before flashing. So the correct way to flash it is...
1. Make sure you are on the Hairy Bean Bootloader.
2. Make sure you are using a 2.7 TWRP.
3. First Format Data. (It will take long, about 30mins)
4. The go into Advanced Wipe and check everything except SDCard.
5. When it's finished reboot, If all went well you should only be at the bootanimation for about 5mins.
Also if you get the four penguins after reboot, then you did something wrong.
Perfect
Legthy, but OMG thank you very much,
thought I was screwed..
I had to do the second part as well, now I get the Asus Setup , to finalize .
Great work, Thanks again.
Madd Macc
MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?
This guide is obsoleted, please visit the new updated thread here!
Heloo there , can you post step by step this tutorial , thx before.
Supernyams said:
Heloo there , can you post step by step this tutorial , thx before.
Click to expand...
Click to collapse
That will be much appreciated
Sent from my SKW-A0 using Tapatalk
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
3. Download SKYW1907040OS01MP3 Stock Factory Image (link above from OP) and move update.zip to “ota” directory in your phone.
4. Press update OTA, after reboot, BS 2 will jump into recovery mode ask for factory reset. Do it or BS 2 won't boot properly.
5. Please allow BS 2 to finish first step of boot up, with least setting up as possible.
6. Go to setting and System update, perform update from S01MP3 to S01MP4, then reboot.
7. Repeat step 5.
8. Repeat step 6 to perform update from S01MP4 to S01MP5, then reboot.
9. Repeat step 5.
10. Turn off the phone and quickly enter Fastboot mode.
11. Perform unlock bootloader by 2 CMD command from above:
Fastboot oem bs_unlock
Fastboot oem bs_unlock_critical
Click to expand...
Click to collapse
12. Restart BS 2, BS 2 will ask for factory reset in Recovery mode. DO IT. (It's very important step cause the BS 2 will stuck at logo if you skip this step).
13. Repeat step 5 (wait until the BS 2 fully operation, enter home launcher, with minimum setting up from beginning). THIS STEP IS ALSO IMPORTANT.
14. Download 2 boot files from OP
Stock_boot.img
boot.img
Click to expand...
Click to collapse
15. Check slot_a or slot_b contain your boot original file by cmd command:
fastboot getvar current-slot
Click to expand...
Click to collapse
- If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
fastboot flash boot_a boot.img
Click to expand...
Click to collapse
OR
- If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Restart BS 2 after flash boot.img
16. Go to XDA and download and install Magisk Manager.
In any cases that BS 2 stuck or can not boot, please enter fastboot mode and flash stock_boot.img from above; repeat Step 5, and reflash boot.img.
-----------------------------------------------------------------------------------
Now Black Shark 2 is rooted with magisk. ^_^ .
---------- Post added at 09:30 AM ---------- Previous post was at 08:45 AM ----------
But i've lost the wifi function. Stock_boot has wifi but boot.img doesn't have. Could you provide a fix for that? Thanks
tuannghia1985 said:
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
...
Click to expand...
Click to collapse
It seems that you just lost your stock rom. If your region is same as his, your phone would be updated to SKYW1911121OS01MP5 already. It seems that it was not, so you flashed the MP3 and updated to MP5, which is not for your region and there could be mismatched functions. And you lost both slots, which contain your stock rom/region info. You need to use the factory image to backup your own stock rom, or need to follow the sequence exactly, not reversed.
wga0 said:
It seems that you just lost your stock rom. If your region is same as his, your phone would be updated to SKYW1911121OS01MP5 already. It seems that it was not, so you flashed the MP3 and updated to MP5, which is not for your region and you lost both slots, which contain your region stock rom. You need to use the factory image to backup your own stock rom, or need to follow the sequence exactly, not reversed.
Click to expand...
Click to collapse
I've figured by myself, use your stock_boot.img and patch manually with Magisk Manager (v7.5). Magisk Manager return for me a "magisk_patched.img" and by flashing that new file, the wifi is return again. I don't know why but it works for me. Thanks for replied.
I can't update mp5 from mp3, I unlock it now. what should I do?
tuannghia1985 said:
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
3. Download SKYW1907040OS01MP3 Stock Factory Image (link above from OP) and move update.zip to “ota” directory in your phone.
4. Press update OTA, after reboot, BS 2 will jump into recovery mode ask for factory reset. Do it or BS 2 won't boot properly.
5. Please allow BS 2 to finish first step of boot up, with least setting up as possible.
6. Go to setting and System update, perform update from S01MP3 to S01MP4, then reboot.
7. Repeat step 5.
8. Repeat step 6 to perform update from S01MP4 to S01MP5, then reboot.
9. Repeat step 5.
10. Turn off the phone and quickly enter Fastboot mode.
11. Perform unlock bootloader by 2 CMD command from above:
12. Restart BS 2, BS 2 will ask for factory reset in Recovery mode. DO IT. (It's very important step cause the BS 2 will stuck at logo if you skip this step).
13. Repeat step 5 (wait until the BS 2 fully operation, enter home launcher, with minimum setting up from beginning). THIS STEP IS ALSO IMPORTANT.
14. Download 2 boot files from OP
15. Check slot_a or slot_b contain your boot original file by cmd command:
- If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
OR
- If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
Restart BS 2 after flash boot.img
16. Go to XDA and download and install Magisk Manager.
In any cases that BS 2 stuck or can not boot, please enter fastboot mode and flash stock_boot.img from above; repeat Step 5, and reflash boot.img.
-----------------------------------------------------------------------------------
Now Black Shark 2 is rooted with magisk. ^_^ .
---------- Post added at 09:30 AM ---------- Previous post was at 08:45 AM ----------
But i've lost the wifi function. Stock_boot has wifi but boot.img doesn't have. Could you provide a fix for that? Thanks
Click to expand...
Click to collapse
Very Nice tutorial.
tuannghia1985 said:
I've figured by myself, use your stock_boot.img and patch manually with Magisk Manager (v7.5). Magisk Manager return for me a "magisk_patched.img" and by flashing that new file, the wifi is return again. I don't know why but it works for me. Thanks for replied.
Click to expand...
Click to collapse
I would've asked you to do the same. Good that it worked for you.
a51711a said:
I can't update mp5 from mp3, I unlock it now. what should I do?
Click to expand...
Click to collapse
reflash update.zip as the above tutorial instruct you.
KM7 said:
Happy new year everyone!
Since many of you have issues with Black Shark 2 Global, I decided to share my findings with you.
Unlock Black Shark 2 Global Bootloader Commands:
Code:
Fastboot oem bs_unlock
Fastboot oem bs_unlock_critical
Root
Important: Update to SKYW1911121OS01MP5 before rooting.
Check current SLOT:
Code:
fastboot getvar current-slot
If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
Code:
fastboot flash boot_a boot.img
OR
If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
Code:
fastboot flash boot_b boot.img
Full OTA Global Factory Image - Fix any issues with the phone and restore it to factory state. This also fixes OTA updating issues.
Dial this from your phone
Code:
*#*#1027#*#*
Start updating your device. You might need to this twice!
Enjoy!
Click to expand...
Click to collapse
It works on Chinese Rom? I would like change from CN to global
I have a bs2 pro Chinese version and I am so disappointed I thought this phone could be customized with custom ROMs and kernels and still nothing ...... I'll never but a black shark product again
Black Shark 2 China rom can do?
tuannghia1985 said:
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
3. Download SKYW1907040OS01MP3 Stock Factory Image (link above from OP) and move update.zip to “ota” directory in your phone.
4. Press update OTA, after reboot, BS 2 will jump into recovery mode ask for factory reset. Do it or BS 2 won't boot properly.
5. Please allow BS 2 to finish first step of boot up, with least setting up as possible.
6. Go to setting and System update, perform update from S01MP3 to S01MP4, then reboot.
7. Repeat step 5.
8. Repeat step 6 to perform update from S01MP4 to S01MP5, then reboot.
9. Repeat step 5.
10. Turn off the phone and quickly enter Fastboot mode.
11. Perform unlock bootloader by 2 CMD command from above:
12. Restart BS 2, BS 2 will ask for factory reset in Recovery mode. DO IT. (It's very important step cause the BS 2 will stuck at logo if you skip this step).
13. Repeat step 5 (wait until the BS 2 fully operation, enter home launcher, with minimum setting up from beginning). THIS STEP IS ALSO IMPORTANT.
14. Download 2 boot files from OP
15. Check slot_a or slot_b contain your boot original file by cmd command:
- If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
OR
- If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
Restart BS 2 after flash boot.img
16. Go to XDA and download and install Magisk Manager.
In any cases that BS 2 stuck or can not boot, please enter fastboot mode and flash stock_boot.img from above; repeat Step 5, and reflash boot.img.
-----------------------------------------------------------------------------------
Now Black Shark 2 is rooted with magisk. ^_^ .
---------- Post added at 09:30 AM ---------- Previous post was at 08:45 AM ----------
But i've lost the wifi function. Stock_boot has wifi but boot.img doesn't have. Could you provide a fix for that? Thanks
Click to expand...
Click to collapse
Black Shark 2 China Version can do that?
Anyone know abd command to relock the bootloader for bs 2? For warranty purpose (Just in case). Thanks in advance.
wga0 said:
It seems that you just lost your stock rom. If your region is same as his, your phone would be updated to SKYW1911121OS01MP5 already. It seems that it was not, so you flashed the MP3 and updated to MP5, which is not for your region and there could be mismatched functions. And you lost both slots, which contain your stock rom/region info. You need to use the factory image to backup your own stock rom, or need to follow the sequence exactly, not reversed.
Click to expand...
Click to collapse
Bro can i have your patched boot.img?what is your region?
Flauros7 said:
Bro can i have your patched boot.img?what is your region?
Click to expand...
Click to collapse
You can see my region at this post. If you leave your revision(or ota link is better) at there, I will find the factory images for your region. Recently, Magisk is updated too often, every weeks. It seems that it's better to patch the stock image by yourself.
KM7 said:
reflash update.zip as the above tutorial instruct you.
Click to expand...
Click to collapse
I TRY IT,Still showing the latest system,can't updates
Hi!
I need help to switch r.o.m w from global to china one because the global one has notification issue and it is pale rom no customization no updates. But I noted that the global rom get very high score on benchmarks I got 462,872 points on antutu benchmark . if some one could try this bench mark on the china rom to see what score they will get, also the over clocking is turned off by default, I think I turned on then did the test you have to dial a secret number to allow over clocking apparently.
Thank yo for your time
Anyone have the China ROM I have retail modes ROM that preventing adb fastboot unlock seems hydra may be my only hope
Just made a new account to confirm the rooting process works. Thank you to KM7, tuannghia1985, wga0, and everyone else for discussing this. The steps I've done were a bit different but I'll try to put it here anyway in case anyone is wondering... (for reference, I'm using Black Shark 2 Global Version just bought a few hours ago)
Prerequisites:
- Your Black Shark 2 must be Global Version. (I haven't tried for China Version yet, might make a separate tutorial if I get my hands on one)
- You will need to prepare Android SDK Platform Tools to execute the needed ADB and Fastboot commands for rooting your device.
- You will also need to be familiar with Command Prompt, or at least comfortable with inputting/copy-pasting commands there.
- You must be ready to forfeit your device in the event that you make a mistake from what's written below. Of course, I cannot be held liable for bricked devices. I am merely restating the procedure I've used for rooting my Black Shark 2 device.
Tutorial:
0. Backup all your files, data, media, etc. You will 100% have to do a factory reset at some point during the rooting process, deleting all user data in your phone.
1. Download the SKYW1907040OS01MP3 Stock Factory Image from OP's post (1.4 GB). It should be named update.zip. Then move the downloaded file to the folder named "OTA". You will find it together along with all the major folders in your internal storage such as "Android" and "Downloads".
2. Dial "*#*#1027#*#*" (without the quotes) on your phone app. A System Update interface should show up, giving you options to adjust the OTA server and to do a local update.
3. Click on the Local Update Button and you should see a percentage in red text pop up. Wait for it to reach 100%.
4. After it reaches 100%, it will tell you to reboot your phone. Now reboot your phone normally.
5. After it reboots, it will go back to your home screen (and not to recovery mode, at least for my version). Go to Settings > System > System Updates.
6. Check the build number (e.g. SKYW1907040OS01MP3) your phone will update to. Two things should happen, in order:
i. You update from "S01MP3" to "S01MP4"
ii. You update from "S01MP4" to "S01MP5"
Once you finish updating from "S01MP4" to "S01MP5" (as long as your current version number ends in S01MP5, you're good), proceed to Step 9. Otherwise, repeat Step 7 and 8.
7. Scroll to the bottom of the update notes and click Update. Ensure your phone is connected to the Internet, and let it download the update.
8. Once the phone downloads it, after a short while, you'll be offered to reboot your device to apply the changes. Reboot the phone, and wait til the phone returns to your home screen and finishes applying the system update entirely.
Notes: During my first try, my update notes were first in Japanese and asked to install around 300 MB. After it finished downloading, it told me the update either failed or got corrupted. Afterwards, the update notes were all typed in English.
9. Patch the stock_boot.img downloaded from OP's post using the latest version of Magisk Manager downloaded from the Magisk GitHub page.
10. You will eventually get another image file named "magisk_patched.img" in the same directory as stock_boot.img (assuming you don't change the filename of the patched image file). Transfer the file to your PC with ADB and Fastboot ready, and place the file inside the platform-tools folder.
11. Activate "Developer Mode" (around 8 taps on About Phone > Build number should do the trick) and enable both "OEM unlocking" and "USB debugging".
12. Connect your phone to your PC via MTP (adjust this via the notification that pops up when you connect it), and click OK when a pop-up appears on your phone for USB debugging.
13. Open Command Prompt inside the platform-tools folder (i.e. cd C:\Users\...\platform-tools) and input the following command in your command prompt:
adb reboot bootloader
Click to expand...
Click to collapse
14. Your phone should then turn off then boot up into what's called Fastboot Mode. Input the following command next:
fastboot oem bs_unlock
Click to expand...
Click to collapse
and:
fastboot oem bs_unlock_critical
Click to expand...
Click to collapse
15. Restart the phone normally by inputting this command:
adb reboot
Click to expand...
Click to collapse
16. Your phone should go into the logo like a normal reboot, and then suddenly give you an option to either do a Factory Reset, or Cancel. Choose the Factory Reset, and wait for your phone to boot up normally again.
17. Set up your device minimally, then FULLY repeat Steps 11, 12, and 13. Reopen Command Prompt if necessary.
Note: if you've been doing things correctly up to this point, the "OEM unlocking" option should be unselectable, as it will say "Bootloader has already been unlocked".
18. Your phone will boot up again in Fastboot Mode. This time, input the following command:
fastboot getvar current-slot
Click to expand...
Click to collapse
19. Command Prompt will then respond with the following:
current-slot: a
Click to expand...
Click to collapse
or:
current-slot: b
Click to expand...
Click to collapse
Take note of this for the next step
20. Take note that if you changed the filename of the patched image file in Step 10, you will have to adjust the next set of commands accordingly. If your current slot is at "a", then input the following command:
fastboot flash boot_a magisk_patched.img
Click to expand...
Click to collapse
Otherwise, if your current slot is at "b", then input the following command instead:
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
21. Restart your phone normally by repeating Step 15.
22. Install Magisk Manager again from Step 9, and confirm that your phone has indeed installed Magisk, and is now rooted.
Congratulations! You've made it to the very end of the tutorial. If you have any questions, feel free to reply to this post and I will respond as soon as I can. Thank you!