[GUIDE][BOOTLOADER][KK 4.4.4] TILAPIA KTU84P- 4.23 Flash Image Instructions - UPDATE

[GUIDE][BOOTLOADER][KK 4.4.4] TILAPIA KTU84P- 4.23 Flash Image Instructions - UPDATE - Nexus 7 3G Android Development

For the moment, I have no way for making a zip file for flash the bootloader and the radio for the N7 3G+
We can do via Fastboot, and it's really easy, but you must come back to Stock recovery if you want to flash the radio.
1. Download The ADB and Fastboot Tools: platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
2. Download The bootloader 4.23 Image File: Bootloader-tilapia-4.23.img - md5: 5bdb2e87370cdb1a7ea14bb0c3e21390 - size: 2.1MB
3. Download the radio-tilapia Image file: Radio-tilapia-1231_0.18.0_0409.img - md5: 64920d406852d92b478c3ab17383ecce - size: 16MB
4. Download these 2 files for the Stock recovery : Stock_recovery_Tilapia_KTU84P.img - md5: 4d9a7eef1d6039a0e413480c56daedb1 - size: 5.4MB - and undo-perm-recovery-signed.zip - md5: 929125ca99d4c5a09e582a642a9cb2c8 - size: 125KB
5. Rename the bootloader-tilapia-4.23.img by bootloader
5a. Rename the radio-tilapia-1231_0.18.0_0409.img by radio
5b. Rename the Recovery_Stock_Tilapia_4.4.4.img by recovery
5c. Put these 3 files in where your fastboot folder is installed; ex => => disk C: root
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
6. Don't forget to check the USB debugging in your settings before to go to your bootloader.
7. Go to your recovery and flash the zip file : undo-perm-recovery-signed.zip ==> Flash it if you have a PERMANENT CUSTOM RECOVERY, it's really important. If you don't flash this zip file, the process do not run well 8. Reboot to your bootloader on your N7 / 3G - Nakasig-Tilapia (Power off power button and volume down until you see bootloader screen)
9. Connect your nexus 7/3g to your computer
10. Open up your Command line prompt
11. CD to where your fastboot tools were installed
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>[/B]
12. Then type:
(to see if its connected correctly)
Code:
[B]fastboot devices[/B]
[I]- should return a serial number to confirm your FASTBOOT connection -[/I]
Code:
[B]fastboot flash bootloader bootloader.img[/B]
(for the stock recovery)
Code:
[B]fastboot flash recovery recovery.img[/B]
Code:
[B]fastboot reboot[/B]
13. Then the first part is finished, reboot to your bootloader and see if all is installed correctly; You can see the new bootloader version 4.23 and you are in the stock recovery and not custom.
14. Now, we are going to flash the radio. You're still in your bootloader, still connect via the usb.
15. Come back to the command lines "platform-tools" and type
Code:
[B]fastboot flash radio radio.img[/B]
for the new baseband version 1231_0.18.0_0409 for 4.4.4.
Code:
[B]fastboot reboot[/B]
16. Reboot to your recovery for confirm the install - You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode[, if your Nexus doesn't reboot itself, reboot yourself!
17. Delete the 3 files that you flashed "recovery" - "radio" - "bootloader"
18. And now when all it's ok, you are to Android KK 4.4.4 with the new baseband but still on Stock recovery, just come back to your custom recovery now (TWRP or CWM) via the classic way
Well done now you are in KK 4.4.4, with the new bootloader 4.23 and the new radio _0409 :good: :laugh:
Don't forget to click "THANKS" and enjoy a good time with your N7-3G :victory:
If you need you can download one of these files : drivers.zip or - USB DRIVERS r_06 for Windows 7 & 8
If you need more help, you just can see these Instructions =>
[GUIDE] If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
Thanks to @phonic and @azoller1

Factory image & All Binaries files KK 4.4.4
If you need, I've uploaded factory image KK 4.4.4 and all binaries files and one All In One All Binaries files (all binaries files zipped)
FACTORY Images KK 4.4.4
Click to expand...
Click to collapse
- Android 4.4.4 - Factory Image KTU84P - Tilapia
BINARIES FILES
Click to expand...
Click to collapse
:
- All In One Binaries 4.4.4. KTU84P for N7 Tilapia.zip
- Camera, Sensors, DRM, GSM from ASUS
- Wi-Fi, Bluetooth from Broadcom
- Touch Panel from ELAN
- Orientation Sensor from Invensense
- Graphics from Nvidia
- NFC from NXP
- DRM from Widevine/Google

When I try to unzip the platform-tools.zip, it says that the archive is corrupted

ragnarok12 said:
When I try to unzip the platform-tools.zip, it says that the archive is corrupted
Click to expand...
Click to collapse
+1

ragnarok12 said:
When I try to unzip the platform-tools.zip, it says that the archive is corrupted
Click to expand...
Click to collapse
dfirefly said:
+1
Click to expand...
Click to collapse
Done, It's corrected now

Do I need to do this if I flash the JDQ4.2.2 factory img using the Wugfresh toolkit? I'm quite confused here. I thought it would update the radio and bootloader as well?

Neo3369 said:
Do I need to do this if I flash the JDQ4.2.2 factory img using the Wugfresh toolkit? I'm quite confused here. I thought it would update the radio and bootloader as well?
Click to expand...
Click to collapse
It's better to use this guide.
I've tried to update with Wugfresh toolkit, but I had some problem with, that's why I have write this guide whom I applied without problem.

When will there be a zip to cwm this? I also got the donate version of the nexus 7 toolkit can that do it? I've been googling for days, I didn't imagine this tablets updating process being this complicated, I've had several phones since the g1 and I don't think I had to do all this for any of them.

Anybody running this new 4.18 bootloader and the new radio with CM 10.1? Everything fine?

tedr108 said:
Anybody running this new 4.18 bootloader and the new radio with CM 10.1? Everything fine?
Click to expand...
Click to collapse
I'm on and I have any problems.
And all the new stock updates running in this bootloader and this new radio, and it seems that no problems has been reported

My baseband shows 1205 is bootloader but 1021 from Android About Tablet, anyone else?

Worked great here, thanks for the files and guide!
My Bootloader & Radio shows the same as the screenshot on the first page.

Re: [GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions
magecca said:
My baseband shows 1205 is bootloader but 1021 from Android About Tablet, anyone else?
Click to expand...
Click to collapse
That's depends of your rom. If you stay on Stock, you will see the good radio, but if you use a custom rom which is not use the latest radio, you will see the old radio. It's not really important.
Sent from my N7 3G with DroiDevs premium between sky and earth.

Hello! Is the flashing of undo-perm-recovery zip file necessary..? I read from another thread which didn't state this step.
http://forum.xda-developers.com/showthread.php?p=39235937#post39235937
I thought flashing the stock recovery by itself should remove the custom recovery previously installed..? I'm just trying to clarify here and learn more.

kEvinErd said:
Hello! Is the flashing of undo-perm-recovery zip file necessary..? I read from another thread which didn't state this step.
I thought flashing the stock recovery by itself should remove the custom recovery previously installed..? I'm just trying to clarify here and learn more.
Click to expand...
Click to collapse
You can use it if your recovery is permanent.

Re: [GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions
philos64 said:
You can use it if your recovery is permanent.
Click to expand...
Click to collapse
What happens if I missed out on that step..? Wouldn't the flashing of the stock recovery over write the custom recovery?
Sent from my Nexus 7 using Tapatalk HD

kEvinErd said:
What happens if I missed out on that step..? Wouldn't the flashing of the stock recovery over write the custom recovery?
Click to expand...
Click to collapse
If your recovery isn't permanent, don't use it.
Yes, the stock recovery overwrite the custom recovery.
That's why after all flash, you can overwrite the stock by the custom recovery.
Is it good for you ?

Please help I am not able to go back to stock I get this checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
Update: Fix the issue, was in CM 10.1 and for some reason the baseband is N/A but by flashing recovery_stock-tilapia.img in this thread was able to fix it.

Perfect. Super easy, no hiccups. Thanks

buzmay said:
Please help I am not able to go back to stock I get this checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
Update: Fix the issue, was in CM 10.1 and for some reason the baseband is N/A but by flashing recovery_stock-tilapia.img in this thread was able to fix it.
Click to expand...
Click to collapse
ssick92 said:
Perfect. Super easy, no hiccups. Thanks
Click to expand...
Click to collapse
Good, thanks for your feedbacks
Don't forget to rate for the thread and click thanks

Related

[Tutorial][S4/S3] How to use OTA zip to get back to Stock OS

Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!

I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.

I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..

mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.

khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.

mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.

khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.

mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.

khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.

mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!

khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s

mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta

Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.

booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++

khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol

Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!

Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app

asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.

[Q] Flashing Stock from CMB

I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I

xnosajx said:
I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I
Click to expand...
Click to collapse
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Edit: http://droidbasement.com/db-blog/?p=3210
Sent from my DROID4 using Tapatalk

berndblb said:
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.

xnosajx said:
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.
Click to expand...
Click to collapse
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason

berndblb said:
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason
Click to expand...
Click to collapse
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.

xnosajx said:
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.
Click to expand...
Click to collapse
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....

Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.

berndblb said:
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....
Click to expand...
Click to collapse
I should have been more specific. Before I attempt the install of the recovery, I get this when I do fast boot devices:
Code:
C:\>fastboot devices
###d2bbce61c### fastboot
The #'s are actual numbers.
After I try to install the recovery image here is the output:
Code:
C:\>fastboot flash recovey recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 3.588s]
writing 'recovery'...
OKAY [ 3.182s]
finished. total time: 6.770s
C:\>fastboot devices
???????????? fastboot
c:\>
And the green flashing (around the icons) stops and hangs.
I have to hold down power to reboot after that.

sbdags said:
Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.
Click to expand...
Click to collapse
I'm an idiot...thanks. I'll try the CROMi-X 5.3

[Q] T300 install CM 10.1 and up to TWRP 2.7

I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.

RBraverman said:
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
Click to expand...
Click to collapse
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.

cmendonc2 said:
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
Click to expand...
Click to collapse
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?

RBraverman said:
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
Click to expand...
Click to collapse
Hope you get getter
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093

cmendonc2 said:
Hope you get getter
Click to expand...
Click to collapse
Thank you, slowly on the mend.
cmendonc2 said:
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
Click to expand...
Click to collapse
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
So I need 3 things: newest F/W (have), Latest TWRP(don't have - yet but looking, 2.7 I believe), latest way to root(don't know) - Correct?
Again where is that thanks button!!!!!

RBraverman said:
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
Again where is that thanks button!!!!!
Click to expand...
Click to collapse
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.

cmendonc2 said:
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
Click to expand...
Click to collapse
NOW it's there!
Okay upping to stock F/W, looking for TWRP (openrecovery-twrp-2.6.3.0-tf300tg-JB.img) then how do I root this

RBraverman said:
NOW it's there!
Okay upping to stock F/W, looking for TWRP - how do I root this
Click to expand...
Click to collapse
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.

cmendonc2 said:
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
Click to expand...
Click to collapse
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?

RBraverman said:
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much mroe optimized for older devices, and you should see a performance upgrade.

cmendonc2 said:
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Click to expand...
Click to collapse
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much more optimized for older devices, and you should see a performance upgrade.
Click to expand...
Click to collapse
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.

RBraverman said:
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
Click to expand...
Click to collapse
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob

cmendonc2 said:
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
Click to expand...
Click to collapse
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Just rebooted, and it's 4.2.1, but everything I had - most of what I had, is still there!?! And the run?

RBraverman said:
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Click to expand...
Click to collapse
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.

cmendonc2 said:
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
Click to expand...
Click to collapse
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!

RBraverman said:
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
Click to expand...
Click to collapse
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.

cmendonc2 said:
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
Click to expand...
Click to collapse
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.

RBraverman said:
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
Click to expand...
Click to collapse
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.

cmendonc2 said:
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
Click to expand...
Click to collapse
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.

RBraverman said:
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
Click to expand...
Click to collapse
I'm not sure what you are talking about with "fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img". As long as TWRP is working you shouldn't have to use fastboot anymore.
The new bootloader that you upgraded to only has 3 icons when you press vol-down and power. Fastboot now connects automatically if you turn on your tablet with the USB plugged in and pressing the key combo. To access TWRP, selecting RCK is the correct choice. As always, never select the Wipe Data in the bootloader menu or you will brick.
Before flashing new ROMs, you should only have to do the "swipe to factory reset" option in the TWRP recovery. If you update your ROM with a newer version of that specific ROM, you only have to Wipe Cache and Dalvik Cache.

Marshmallow Rom that will update all??

I'm currently on Verizon Version :5.0.1 Software :4.17.605.5. Is there a Marshmallow Rom that I can flash that will update firmware and give me the security/stagefrieght patches that verizon put out months ago? I'm rooted and S-off.

beeper10 said:
I'm currently on Verizon Version :5.0.1 Software :4.17.605.5. Is there a Marshmallow Rom that I can flash that will update firmware and give me the security/stagefrieght patches that verizon put out months ago? I'm rooted and S-off.
Click to expand...
Click to collapse
You can run MM ROMs, yes. There is one from Santod040 that is based off HTC Sense, and one by enewman17 that is based off GPe (Google Play edition)
There is no MM firmware however, until HTC releases it to us.
You can flash the latest 4.17.605.9 LP firmware, and run those above said MM ROMs

Where would I find and how would I flash the firmware..... Through twrp?

beeper10 said:
Where would I find and how would I flash the firmware..... Through twrp?
Click to expand...
Click to collapse
Verizon m8 Development forum: LINK
Latest Verizon firmware and instructions: LINK
Marshmallow Google Play Edition for Vzw m8: LINK
Marshmallow Sense 7 for Vzw m8: LINK

I tried updating the firmware with installing the above zip and it fails.

I've tried to flash the all in one update a bunch of times and it continuously fails.

beeper10 said:
I've tried to flash the all in one update a bunch of times and it continuously fails.
Click to expand...
Click to collapse
Need more info then "it fails".
Exact error or issue you encounter.
Pasting the terminal input and output here would be most useful.
Hard to instruct you any further from what little info you gave.

I'm doing it from the phone and there's no way I can copy and paste the results..... I tried to take a screen shot but that wouldn't work either. It doesn't give a reason it just goes to install and fails. Not sure how to give more info?

Here's a couple pictures of the issue.

beeper10 said:
Here's a couple pictures of the issue.
Click to expand...
Click to collapse
You don't flash it in recovery...
It fails because you aren't following the instructions given...
Copied from Santods thread:
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)

I left my computer at work... Is there anyway to do it from the phone?

beeper10 said:
I left my computer at work... Is there anyway to do it from the phone?
Click to expand...
Click to collapse
Yes... By using an sdcard...
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once furmware is detected by phone.

That I have! That's were I was trying to flash it from.

beeper10 said:
That I have! That's were I was trying to flash it from.
Click to expand...
Click to collapse
Again.... You do NOT flash in recovery.
And I'll post again...
Please follow the instructions.
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once firmware is detected by phone.

Unrooting Mi A1 [Android Oreo ] completely

complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) ‎then power off your device
4) ‎go to fastboot mode
‎ ( by pressing vol- + power buttons simultaneously)
5) ‎then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
‎
‎Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
‎fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :

#reserved

Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".

Thank you very much!!!! Was looking for this in a pretty long time!!!

Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".

nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.

Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.

nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..

_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.

nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.

_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:

nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update

Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again

_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?

rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.

_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota

rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.

camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro

_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess

AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool

Database Info

welcome