Database Develop

[ALPHA][ROM] Ideapad K1 ICS CM9 Port

Greetings,
Me and krook1 have been working on a CM9 port for the Lenovo Ideapad K1. This is an Alpha release as there is still a lot of work to be done. I have included instructions to either flash as an update.zip with CWM recovery, or if your still on stock you can use the nvflash package.
I have very limited time to invest to this project so if anyone would like to help please join us at freenode IRC room #ideapad-k1. The source code download link is posted below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Working
-Touchscreen
-Wifi
-Bluetooth
-Accelerometer
-Rotation Lock
-Internal and External Storage
-Audio (thx Koshu and digetx)
-HW Acceleration (thx digetx for green overlay fix)
-CWM Backup/Restore - Fixed by using updated CWM below
Not Working
-GPS? appears to work but doesn't connect?
-HD Video Streaming
-Microphone
-Camera
Haven't tested HDMI out
Changelog
Alpha 1.6
- Fixed storage issue
Alpha 1.5
- Bluetooth fix (Audio doesn't work?)
- Full market compatibility
- Hardware buttons
- Rotation Lock Switch (Functions, but doesn't notify the SW layer)
- External SD mounted at /sdcard/external_sd and linked to /mnt/sdcard2
- goo.im app OTA update compatibility
- Synced with CM9
- New CM9 Bootanimation
- nvflash package includes updated CWM with working backup/restore
Alpha 1.0
- Initial Release
Downloads
As usual flash at your own risk
Gapps
http://goo-inside.me/gapps
CWM Package
update-cm-9.0.0-ALPHA1.6-k1-KANG-signed.zip
md5sum: 239091872daae568d7e9f1680ce49176
1. Place the update.zip on your external sdcard
2. Reboot into recovery.
3. Wipe data/Factory reset
4. Install .zip from sdcard
5. Choose the update.zip and say Yes
6. Flash gapps (optional)
Nvflash Package
K1_CM9_Alpha_1-5_nvflash.zip
md5sum: 7c34ec9242ab6ad4659b3bf310627ff4
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode:
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode.
How to flash:
1. Extract the K1_CM9_nvflash.zip contents to a directory
2a. If using Windows, double click the "flash-windows.bat" file
2b. If using Linux, cd into the extracted directory and run either "sudo ./flash-linux.sh" or "./flash-linux.sh" from a root prompt
Source Code
http://github.com/khanning/android_device_ideapad_k1
-or-
git clone git://github.com/khanning/android_device_ideapad_k1.git
Special Thanks
The entire Cyanogenmod team and everyone that has contributed to CM
digetx
Koshu
Jon2555
All the developers that have made the source code for their device tree public. Thank you for helping to move the Android development community forward.

Thank you khanning88 and krook1 for releasing the first ICS rom for the K1!! Of course you had to upload this right before I leave for work, but thats okay! Now I have something to try out over break next week. Woohoo!!

thanks for another great rom ...even being alpha fast and smooth

Been running ice for around an hour now and no issues in performance
Glitches I've noticed
External SD shows being mounted but shows empty in total commander and es file explorer
and will not allow access
But other then the posted issues its running great
Sent from my K1 using xda premium

Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.

After going through the Rom and I've noticed I can get to the external sd card if I go through. /mnt/sdcard2
But not through the regular way
I'm also going to make an update.zip for full screen nexus prime boot anim
Sent from my HTC Sensation 4G with Beats Audio using xda premium

This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.

djsat03 said:
Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.
Click to expand...
Click to collapse
DISREGARD THE POST BELOW. BROWSER STILL CRASHES. BUT THIS ONE INSTALLS IF ANYOE WANTS TO PLAY AROUND WITH IT.
Chrome browser works. The problem is the same that all other unofficial ICS builds on other devices have. It has to do with the Device Id Check in the apk from the market. Download chrome from the link below and you are smooth sailing.
http://forum.xda-developers.com/showthread.php?t=1515900
Sent from my K1 using XDA

arjunprabhu said:
This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.
Click to expand...
Click to collapse
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !

Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.

quyTam said:
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !
Click to expand...
Click to collapse
djsat03 said:
Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.
Click to expand...
Click to collapse
I am not a NOOB, as I flash roms to my Droid Incredible all the time, but I have found the detail of instructions on flashing/root in the Idea K1 to be a bit confusing.
So any chance someone could add to the detail above, " if not rooted do install process #2 and follow these step by step"
Reads as if we can use the nvflash method, but no mention of rooting before, if that is the case great. I am looking forward to getting a new rom installed on my K1 as the stock is very buggy!

sorry, didn't see the nvFlash method. Not sur it need root or not (but think it's also needed)

quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)

ok, thanks for your reply.
didn't know the nvflahs method; it works on all Android device ?
ps: I don't have K1 but Thinkpad. Is it because Thinkpad doesn't have his bootloader unlocked, so it's not possible to use nvflash ?

khanning88 said:
quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)
Click to expand...
Click to collapse
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.

dc52317 said:
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.
Click to expand...
Click to collapse
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?

arjunprabhu said:
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?
Click to expand...
Click to collapse
That is exactly what I am trying to find out. I am planning on installing this when I get home in a few hours, but I am hoping that someone can add that detail to the post. I was looking a bit earlier, and found references to making sure you have these apx drivers installed for rooting etc, but no instructions.

Updated the nvflash section with the APX drivers and instructions.
Updated CWM recovery to 5.5.0.4 and fixed Backup/Restore. This will be incorporated into the next nvflash package. For now download the updated CWM recovery .zip in the 'Mods' section of the first post, and flash from recovery.

thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?

arjunprabhu said:
thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?
Click to expand...
Click to collapse
if you are not rooted and don't cwm on it already. Then just do the nvflash package instructions posted in the op.

Nexus 4 Guide-Unlock Bootloader, Root, Install Custom Recoveries & Custom ROMs/Kernel

Nexus 4 Guide-Unlock Bootloader, Root, Install Custom Recoveries & Custom ROMs/Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings XDA Members and Guests
We are honored to have an addition of a bunch of new members every day, of which a decent lot is new to our Android custom world. So, if you're viewing this thread, it is because you need guidance in context to Root, Install Custom ROM/Kernels & Custom Recoveries on your LG branded Google Nexus 4. I may have spent tons of hours at this N4 section but I also have my history with Android, going way back when I was also a noob (new comer). Though, I was lucky enough because my fellow community members imparted me with sufficient knowledge to bring on to the basics of the Android custom world i.e Rooting the device, Installing Custom ROMs and Mods. Here I am to give out an helping hand and I want our new entries to feel the way I felt in the beginning; never ignored and forever helped.
So if you’re a noob and you’re reading this, don’t you worry at all, I will take care and hit all the basics inside your head, step by step. I have already done this at the Nexus S section (look here).
I’m sure you’re more curious to get into the Android Development section and flash your desired ROM, I have felt that curiosity but I would advise you to stay calm and give these things some time and little bit of importance too, as then this knowledge will defend you from messing up your devices in the future. Please do not be in a haste, understand the steps or information carefully and then only care to process it. Remember, haste makes waste (someone told me the very same and trust me, I could be the most experienced in making a practical example of this).
Terminology
What is Bootloader and Why do we need to Unlock?
A bootloader is a boot initializing component which is generally locked by the device manufacturer to avoid any messing around with the OS. We need to unlock it for the same reason. Once unlocked it will allow us to change the boot sequence and modify the OS in accordance of our needs.
What is Rooting?
It is a process of gaining root privileges over an Android subsystem. Rooting an Android device is easy in most cases. If you will to Install custom ROMs, kernels, other patches or addons to your Android device, rooting is what you will need. It can be achieved in two ways; either by manual method (using Recoveries) or by automatic method (using toolkit or software) . Here, I am going to follow the manual method.
ClockworkMod & TWRP, what are these?
These are secondary recovery systems created by Koush (Koushik Dutta) & TeamWin, respectively. These add enormous features like wiping partitions, flashing flash-able .zip files like ROMs, kernels, patches etc to the stock AOSP recovery. Visit ClockworkMod website & TeamWin website for more detailed information.
What is a Custom ROM?
These are the aftermarket Android firmware which are not official supported by the OEM (Original Equipment Manufacturer). They are made available to the Android public by Android developers and contributors all around the world. Custom ROMs are either built from Google’s source code i.e AOSP (Android Open Source Project) or are modified versions of the device manufacturer’s ROM (Stock ROMs or Factory ROMs) with additional tweaks and extend functions which are not delivered with the Stock ROMs. Some of the popular Custom ROMs include CyanogenMod (CM), Android Open Kang Project (AOKP), MIUI, Codename Android (CNA), Oxygen, ParanoidAndroid and many more.
What is Custom Kernel?
A Kernel is a bridge between the applications and the actual data processing done at the hardware level, In simple words, it is the communication between the hardware and software of an Operating System. In Android world, Custom Kernels play a vital role since they provide the users with several features including changing CPU frequencies, modifying the boot sequence and boot scripts and other features too.
What are Google Apps (GApps)?
The name speaks for itself. Gapps are Google apps for Android available in flash-able zip format. Most of these applications can now be found and updated via the Google Play Store.Some of the apps include the Google Play Store itself, Google Talk, Google Sync (for adding and synchronizing Google accounts), Google Backup Transport, Car Home, Gmail, Google Maps, YouTube, Google Search, Google Voice Search, Google Music, and Google Docs. In some Custom ROMs, the Google Apps are included. These are usually stock ROMs, smaller or less-common ROMs, or those from areas where intellectual property laws are less commonly obeyed. But many AOSP ROMs, most famously CyanogenMod and AOKP, do not include the Google Apps due to licensing issues. They are after all proprietary code owned by Google and not included in the Android Open Source Project.
Now, lets begin. The first thing we’ll be doing here, is to unlock the bootloader of your Nexus 4, followed by Installing a Custom Recovery, so that later on you can root and Install Custom ROMs/Kernels/Mods easily.
Prerequisites
USB drivers configured properly. You may either use these amazing toolkits [WugFresh?s tookit | mskip’s toolkit] or do it manually using the Google USB drivers delivered with Android SDK (Do it the way you find it easy). Remember, USB drivers in this case doesn’t mean only the drivers to mount the device storage but rather the fastboot and adb drivers too.
Compatible USB data cable.
Android SDK configured (Follow this guide to setup Android SDK and thus it itself configures ADB and all other SDK components)
USB Debugging enabled (Don’t know how? Take a look here)
Backup Device Storage, Messages, Contacts, Calendars etc.
60% or above battery life (This is a recommendation to avoid any uncertain shutdowns during the mentioned process, it might cause issues)
Fastboot binary (Put the file in <sdk_directory>/platform-tools)
Once you have filled in all the requirements, you shall follow further. If you have problem with setting up the prerequisites, please comment and get your issue resolved. Always remember, the more you ask, the more put up to your knowledge and the more you learn.
Unlock Bootloader
Don't want to lose your data after unlocking? Read this.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Connect the device to your PC using USB data cable.
Open CMD/Terminal and confirm that the drivers are properly installed and the device is detected by entering the following command
Code:
fastboot devices
The device ID shall be displayed as the output in your shell. If it is so then the response is positive but in case it shows something else, please make sure to properly install the drivers using a different method than that you used earlier.
Type in the following in CMD/Terminal to initiate the unlocking process
Code:
fastboot oem unlock
You will now be prompted with a warning message, use the volume keys to highlight Yes and select it using the power button. Then within a matter of seconds, your device shall be unlocked.
To confirm that it is unlocked, look over to the text in front of Lock State and it should be unlocked.
You’ve successfully unlocked.
What? Too easy? Yes, indeed. The following is as easy too.
Install Custom Recovery
We’ve 2 custom recoveries available yet for our Nexus 4 viz ClockworkMod and TWRP. ClockworkMod or CWM (in short) comes in 2 variants (Touch UI based & Non-Touch UI based). Below I have mentioned on how to flash each one of them using fastboot. For more info about these two recoveries, visit ClockworkMod and TeamWin websites.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Download the latest build of your desired recovery [CWM | TWRP]
Place the downloaded recovery image (.img) file on your desktop.
If in Windows, open CMD and cd it to the desktop using the following command
Code:
cd Desktop
If in OS X or Linux, open terminal and cd it to the desktop using the following command
Code:
cd ~/Desktop
To flash ClockworkMod Non-Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash ClockworkMod Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-touch-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash TWRP, type in the following command:
Code:
fastboot flash recovery openrecovery-twrp-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
Once flashed, you will prompted on the CMD/Terminal itself.
Now, either reboot your device by using volume keys to highlight Reboot and select using Power button or reboot into the recovery by selecting Recovery mode.
Voila! The next to follow is to root or directly flash a Custom ROM, which is already rooted.
Rooting
Not everyone and each one of us like Custom ROMs. Some users might prefer high stock stability over the features offered by Custom ROMs. and that’s completely normal. But, what if you have an App that requires Root privileges or may be, you need to access the System partition of your device to make certain modifications of your own? This is where the process of Rooting enters. Now when you already know what Rooting is, we shall head further and follow another set of very-simple instructions to root your Nexus 4.
Download the latest SuperSU flash-able root package. [Chainfire's SuperSU Thread]
Connect your device to the PC via USB cable.
Transfer the downloaded file to a suitable location in the device.
Do not disconnect the device.
Open CMD/Terminal and type in the following command:
Code:
adb reboot recovery
This will boot your device directly into recovery mode.
You may now disconnect the device.
If you are using CWM, tap on install zip from sdcard > choose zip from sdcard and select the CWM-SuperSU-v0.93.zip. When prompted select Yes to start the flashing process.
If you are using TWRP, tap on Install and select the CWM-SuperSU-v0.93.zip. Slide the circular button to start the flashing process.
When the flashing process has finished, select reboot system now (In CWM) or Reboot > System (In TWRP) to reboot your device.
Congrats! You have successfully rooted your device. Go ahead and use any App that requires Root permissions.
Installing Custom ROM
Its simple, very much simple. All you got to do, is to choose a Custom ROM and simply flash it via your custom recovery.
The very first step is to choose a Custom ROM that fits all your needs and serves you with your desires. When chosen, download the ROM file (flashable zip).
NOTE: Every ROM here at this section is worth and is a result of hardwork of developers/team. Please do not criticize any ROM for any reason. Maintain the forum spirit by encouraging people.
Download the suitable GApps package corresponding to the Android version of your ROM [Link]
In case, the developer has provided specific modified GApps package, download that. Then there is no need to download the GApps package from step #2
Connect your device to the PC via USB data cable.
Transfer the ROM & GApps zip to the device. Its is recommended to put the files in the root of your device storage for convenience.
Disconnect the device,
Power off. Press the Volume Down and Power keys together to boot into the Bootloader mode.
Use the volume keys to highlight Recovery mode and select it using the Power button. Your device will then boot itself into Recovery mode.
Flash using CWM
wipe data/factory reset
wipe cache partition
Go to "mounts and storage" > "format /system" "format /boot"
Go to "install zip from sdcard" > "choose zip from sdcard" > select your ROM .zip file that you placed in step #6. Flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and GApps successfully.
Once everything has flashed successfully, select "reboot system now".
Flash using TWRP
Go to "Wipe" > "Advanced" and "Factory Reset".
Go to "Install" > choose the ROM .zip file and flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
When flashed, go to "Reboot" > "System".
Your phone will now boot into the custom ROM.
Install Custom Kernel
People often prefer using a Custom Kernel rather than that already delivered with the ROM. For the available kernels, head over to Nexus 4 Original Development section. Every kernel is unique in its own terms, so make a choice. If you’re not satisfied with the combination, move on and try some other kernel.
Choose a custom Kernel and download its flashable zip.
Connect your device to the PC via USB data cable.
Transfer the Kernel flashable zip to the device. Its is recommended to put the file in the root of your device storage for convenience.
Disconnect the device.
Power off. Press the Volume Down and Power keys together to boot into the Bootloader mode.
While on the Bootloader screen, use the volume keys to highlight Recovery mode and select it using the Power button. Your device will then boot itself into Recovery mode.
Flash using CWM
- Select "wipe cache partition"
- Tap on "advanced" and select "Wipe Dalvik Cache"
- Tap on "install zip from sdcard" > "choose zip from sdcard". Now browse and select the kernel zip package that you placed in your storage root during step #3.
- Select "Yes" when prompted to start the flashing process.
- Your Kernel will now flash to your OS and replace your current kernel.
- When it has successfully flashed, select "reboot system now".
Flash using TWRP
- Tap "Wipe" > "Advanced Wipe" and tick "Dalvik Cache" & "Cache".
- Slide the button at the end of the screen to start the wiping process.
- Tap on "Install" > now browse and select the kernel zip package that you placed in your storage root during step #3.
- Slide the button at the end of the screen to start the flashing process.
- Your Kernel will now flash to your OS and replace your current kernel.
- When it has successfully flashed, tap to "Reboot" and select "System".
You now have Custom Kernel installed on your Nexus 4.
NOTE: Before choosing and flashing any Custom Kernel, make sure its compatible with your present Android version.
I hope this guide has helped you. I would be proud, if anyone has received any kind of fruitful knowledge/guidance from this thread.
In case you get stuck anywhere, feel free to comment and ask. Or if I've missed something or may if I am wrong somewhere, please do let me know.
:good:Good Luck with going custom on your Nexus 4:good:

Hey awesome tutorial....nice and detailed.....plz can u make a tutorial using the automatic method(toolkit)
Thanks

dsjd said:
Hey awesome tutorial....nice and detailed.....plz can u make a tutorial using the automatic method(toolkit)
Thanks
Click to expand...
Click to collapse
You won't learn anything using a toolkit and if something goes wrong you won't know how to fix it. XDA is a place to learn
Sent from my Nexus 4

spaceman860 said:
You won't learn anything using a toolkit and if something goes wrong you won't know how to fix it. XDA is a place to learn
Sent from my Nexus 4
Click to expand...
Click to collapse
So its safer to do it manually ?

dsjd said:
So its safer to do it manually ?
Click to expand...
Click to collapse
Everything is safe for a Nexus. But, this guide will provide you with suitable knowledge. :good:

dsjd said:
So its safer to do it manually ?
Click to expand...
Click to collapse
Yes and if you need help just ask
http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4

Nice guide. I have one question.
In this guide: http://forum.xda-developers.com/showthread.php?t=2018179 it mentions that after flashing the custom recovery, the stock recovery may restore itself and overwrite the custom one. Is it necessary to do anything to stop this from happening ?
Sent from my HTC Desire using xda app-developers app

Can u plz giv little more detailed steps on installing drivers?

chromium96 said:
Nice guide. I have one question.
In this guide: http://forum.xda-developers.com/showthread.php?t=2018179 it mentions that after flashing the custom recovery, the stock recovery may restore itself and overwrite the custom one. Is it necessary to do anything to stop this from happening ?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
The newest versions of custom recovery prevents that from happening
Sent from my Nexus 4

Hey ...i just wanted to know if there are any safety-nets that i can use ...like backups or something?

dsjd said:
Hey ...i just wanted to know if there are any safety-nets that i can use ...like backups or something?
Click to expand...
Click to collapse
The first thing to backup is your contacts, messages and storage. Up after flashing a Custom Recovery, it is highly advised to take a nandroid backup using the recovery.

DJBhardwaj said:
The first thing to backup is your contacts, messages and storage. Up after flashing a Custom Recovery, it is highly advised to take a nandroid backup using the recovery.
Click to expand...
Click to collapse
Thanks for the reply....do u think this is a safe tool to use http://www.nexus4forum.com/forum/ne...ck-up-your-entire-device-without-rooting.html ? or plz can u suggest sum good ones ...

dsjd said:
Thanks for the reply....do u think this is a safe tool to use http://www.nexus4forum.com/forum/ne...ck-up-your-entire-device-without-rooting.html ? or plz can u suggest sum good ones ...
Click to expand...
Click to collapse
Its good to go.
Here are other two of the very famous toolkits; mskip's toolkit & Wug's toolkit.

DJBhardwaj said:
Its good to go.
Here are other two of the very famous toolkits; mskip's toolkit & Wug's toolkit.
Click to expand...
Click to collapse
and how can u make out if the drivers are installed properly ?Do i enable usb thenthering mode before or after i install the drivers ?

Thanks for your very good job!
Sent from my Nexus 4 using xda premium

Does bootloader version, or android version matter? Or will everything work regardless of any versions?
Sent from my HTC Desire using xda app-developers app

chromium96 said:
Does bootloader version, or android version matter? Or will everything work regardless of any versions?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Doesn't matter it will work
Sent from my Nexus 4

dsjd said:
and how can u make out if the drivers are installed properly ?Do i enable usb thenthering mode before or after i install the drivers ?
Click to expand...
Click to collapse
Connect your device to the PC. Make sure USB Debugging is switched on.
Open CMD/Terminal window and type the following command:
Code:
adb devices
If it shows a device ID, then you've your drivers properly setup.

I have another question. Will unlocking the bootloader and flashing twrp wipe the phone?
Sent from my HTC Desire using xda app-developers app

chromium96 said:
I have another question. Will unlocking the bootloader and flashing twrp wipe the phone?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Yes unlocking the bootloader will wipe the phone completely.
Sent from my Nexus 4

[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.41.6)
https://docs.google.com/uc?id=0B5c3gpyMBJusWi1XN09fZjkzUWM&export=download
aromafm_tass.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusLTk5ZENsNWpudms&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ-Touch Recovery for Galaxy Mini, Tool/Utility for the Samsung Galaxy Mini
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-26

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
GALAXY MINI GOES OFFICIAL NOW!!!!!!
You'll now find Galaxy Mini in the officially supported devices list at the Main thread.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.

alexanderq said:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
Click to expand...
Click to collapse
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery

Faiyaz5yaz said:
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Click to expand...
Click to collapse
You mean, you are always rebooting to recovery and not to your rom?
If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.
Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.

But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.

Can someone else confirm that it always reboot to recovery even after re-installing a rom?

Good work bro.:thumbup:
Sent from my GT-S5570 using xda premium

no
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I didn't restore back up..
I reflashed my previous cwm..
it booted normally

Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.
Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?

Thanks everyone for reporting....
I'll try to fix this when I get time...
ast00,
Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.

Good news:
My friend @chraso gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.

First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.

Bhargav97 said:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Click to expand...
Click to collapse
flashed the latest zip
still not booting into the same rom..
didn't test new rom

Faiyaz5yaz said:
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Click to expand...
Click to collapse
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?

Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .

not that
Bhargav97 said:
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Click to expand...
Click to collapse
I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery

Bro,
please read FAQs, this is a problem of your device sources. For solution, see FAQs.
After that, please give me broader report.

You di not ask the right question:
Does this work for someone , anyone please confirm.

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
Original version created in the summer of 2011. Thanks to birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch!
Thanks to SDX
Requires:
Unlocked bootloader and root access!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directory, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Nexus 6, HTC One M8 (GSM), Moto G, Sprint Galaxy S4, International HTC One (M7), T-Mobile HTC One (M7), Sprint HTC One (M7), HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 5, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:downloadsFlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
Users Guide for flashing ONLY a Kernel (zip file):
1) Ensure the bootloader is unlocked and root access is properly setup
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate that the kernel zip file contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:downloadscwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
XDA:DevDB Information
Flash Image GUI, Device Specific App for the Nexus 6
Contributors
joeykrim
Version Information
Status: Stable
Current Stable Version: 1.6.7
Stable Release Date: 2015-06-29
Created 2015-06-30
Last Updated 2015-06-29

[GUIDE][Unlocked] Flashing T-Mobile OnePlus 6T to International OOS ROM

Note: Firmware flashing procedure is exactly the same for all firmware versions for conversions.
Local Updating using: 9.0.11 is safe
This is a basic write up to convert your bootloader unlocked T-Moilbe OnePlus 6T to the International Version firmware via fastboot flashable firmware files.
Contents:
-Disclaimer
-Full Device Backup - Precautionary - Optional, but Recommended.
-Firmware Conversion Process
-Update after conversion
-Rom Sources
-MSMDownloadTool
-FAQ's
-Additional/Optional Tools
-Credits
Disclaimer:
Like any other form of modding, there are risk involved, we have a near flawless option to recovery by use of the MSMDownload linked at the end of this post, but like with any form of modification, you are solely responsible for what is done to your device and you accept all risk involved, should something go wrong, for the most part, recovery is fairly simply, no matter how bad we screw up, thanks to OP.
Instructions to a full device backup:
1. Download the zip below and extract it to it's own folder
2. Run the backup.bat script
3. It will backup all partitions on your device, including your efs.
4. zip all of the image files and store it somewhere safe.
Backup: https://androidfilehost.com/?fid=11410963190603855581
Steps to convert from stock T-Mobile firmware to Global firmware:
FLASHING STEPS
Requirements:
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file, Not the TMOUS branded ROM. (Get the fastboot flashable full rom here: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516)
3. PC/MAC/LINUX
Flashing Process
1.. Whichever full rom zip you choose, extract its contents. (In my case I used the 9.0.5 full zip)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. In each zip file you'll find images.zip as well as others_flashall.zip, extract both of them into the same folder/directory as the rest of the original zip file.
(Optional, download the modded flash-all-partitions-fastboot.bat file at the end of the thread, it includes the reboot command to auto reboot when done flashing)
Attached Below is also a flash-all-partitions-fastboot.sh script for Mac OS users (Note this script will not wipe your device, so if you need to wipe, run the ./fastboot -w command in fastboot manually)
All bat files, images and adb files should all be in the exact same folder, no subfolder(s)
3. Now boot into fastboot using either the vol+/vol- and power key combo or via adb using the following adb command
Code:
adb reboot bootloader
.
4. Once in fastboot run the bat file called flash-all-partitions-fastboot.bat
9
5. When asked, I would advise typing 'Y' for yes to format the device. (wipe only if you're converting for the first time)
The sparse header error is completely normal.
6. Upon completion, the script should pause and say press enter to continue, it will not reboot your device...
WAIT UNTIL NOTHING ELSE IS HAPPENING AND ITS NO LONGER FLASHING ANY FILES
At this point, hit power and reboot.
Note: Modded fastboot flashing script attached at the end with the reboot command included, also attached is a script for MAC users, mac script will not wipe your device, wipe manually if you need to using
Code:
./fastboot -w
B]
All done!
Update After Conversion (You can also update using the conversion process with the new fastboot files)
Use this if you'd like to convert and relock your bootloader or you've locked your bootloader or simply prefer this method.
1. Download the Full Official Rom from here, not the incremental update, the Full ROM only and copy it to the root of your device: HERE
2. Go to settings > system > system updates > tap settings in top right and choose local upgrade or you can use twrp
3. a) if using local upgrade, choose the ROM zip from the list and install, it will install and give you the option to reboot when complete.
b) if using twrp, boot into recovery, choose install zip and select the full rom file and flash, then follow the steps below
The following steps are for users who have/want root or a modified device or used twrp to install the ROM, device will not boot without the following steps if you installed using twrp:
4. Flash twrp installer HERE
5. Reboot back to TWRP
6. Flash Magisk (if you don't won't boot, you only need this step if your system was rooted/modified in any way) Magisk Here
Or you can skip the additional steps and simply do a factory reset.
NOTE: After using the local upgrade option, you can relock your bootloader if you choose to remain stock, enabling widevine L1 for HD videos, as well as a certified play store device.
You can continue with a locked bootloader using the local upgrade option, but be wary that you should confirm we can local upgrade prior to attempting an update. OTA updates will not show, but future local full ROM updates are working as of: current 9.0.11.
relock using fastboot oem lock command, this will wipe your device.
ROM Sources
Mauronofrio's Thread
T-Mobile 9.0 FULL Fastboot ROM
Saythis' International Firmware 9.0.6​
Full ROMs directly from OnePlus for Updating Purposes ONLY
Recovery - MSMDownloadTool
If for some WEIRD reason you brick, have a HW mismatch, etc, or you just can't boot go to this thread -> MSMDownloadTool - T-Mobile 9.0
OPTIONAL Steps
Root is available via two Options below:
- OnePlus Rooter
- Manual Root Using a Patched Boot Image
Automated Process
Luckily There are devs looking to make things simpler:
For @Dameon87's automated tool to carry out this process, go to the thread below:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-oxygen-os-9-0-6-fastboot-windows-t3870170
WARNINGS!
-Advisable you disable automatic updates in developer options upon boot if it is enabled.
-Do not attempt to update using the OTA files, so far we've had one softbrick due to it and said user was unable to boot into fastboot to attempt any kind of recovery.
-ALSO DO NOT FLASH WITHOUT THE FILES IN THE FOLDER, IF YOU DO YOU WILL END UP WITH A SOFTBRICK
-If you get either dump mode or fastboot bootloop check your downloaded rom file to make sure its complete, unzip again and flash again
FAQ
Q. Will this enable dual sim functionality?
A. Dual sim functionality works, volte, Wifi calling and vvm.
Q. Can I take OTA's like a regular device?
A. No, sadly.
Q. What about when a new update comes out?
A. Update procedure is written above.
Q. What if I brick or have a HW/SW mismatch?
A. Use the MSMDownloadTool to recover.
Q. Do all the features work?
A. For the most part, there are minor bugs, but they aren't consistent, so can't really say.
Q. Is this a full conversion?
A. Somewhat.
Q. Do I have to wipe everytime I update?
A. No, wiping may only be necessary for conversions, no wipe needed to update.
Q. Do I have to root everytime I update?
A. Yup, sadly.
Q. Do I have to convert to a specific version?
A. Nope, you can convert to any version.
if any edits are suggested, I'll include them.
Credits:
@mackentosh for testing and unfortunately bricking using the OTA File
@Velrix for being the second successful tester, among others.
All the other users who've been testing/contributing to testing
I'll add names when I get to comb through the threads.
@Dameon87 for the correct ROM source link of the unpacked ROM with batch files.
@Krunk_Kracker for the disable auto updates image
Thanks to @Addiso for the Stock T-Mobile Backup images
@mauronofrio for the scripts and for hosting the Rom zip @hartleyshc for testing and confirming full dual sim functionality.
@Saythis - for the 9.0.6 FULL ROM Zip
@Taebom for first testing/confirming 9.0.7 local upgrade

Thanks for the write up! It was getting confusing trying to follow multiple threads and conversations. I'm gonna wait a while before I try this but I know it'll only get better and better.

This will only work with the 9.0.4/5 ROM that has already been converted for use with Fastboot.
The full roms in the post you link do not have the required .bat files for flashing and also must be extracted from the Payload.bin file.
Did you perhaps mean to link to this thread instead? : https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

Dameon87 said:
This will only work with the 9.0.4/5 ROM that has already been converted for use with Fastboot.
The full roms in the post you link do not have the required .bat files for flashing and also must be extracted from the Payload.bin file.
Did you perhaps mean to link to this thread instead? : https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Correct, thank you.

Dark Nightmare said:
Correct, thank you.
Click to expand...
Click to collapse
No worries!

nice doing this tomorrow night when my .bin is 7 days old

What's up with persist? No output or not getting flashed? Has anyone run it manually?

Doesn't seem like anything that needs TWRP is flashing to the partitions whether that's a good or bad thing remains to be seen since we have no clue what could brick our devices when flashing those partitions.
LLStarks said:
What's up with persist? No output or not getting flashed? Has anyone run it manually?
Click to expand...
Click to collapse
Sent from my ONEPLUS A6013 using Tapatalk

Edit. I misread. Thanks for the guide..

Does this actually give us 2 IMEIS?

ahrion said:
Does this actually give us 2 IMEIS?
Click to expand...
Click to collapse
No. It's the same imei on both slots.

Will this work with 9.0.5?

Krunk_Kracker said:
Will this work with 9.0.5?
Click to expand...
Click to collapse
Yes. He state's in the OP that he used 9.0.5.
It currently works with 9.0.4 and 9.0.5.

Is there any commands we can use to do flash-all-partitions.bat? My Mac doesn't recognize terminal as a program that can open the .bat file

dchurch85 said:
Is there any commands we can use to do flash-all-partitions.bat? My Mac doesn't recognize terminal as a program that can open the .bat file
Click to expand...
Click to collapse
Open the bat, it references 3 other bats, open those bat files in order (as text files, or just rename them .txt).
Just copy paste each line into terminal and run them that way.

hartleyshc said:
Open the bat, it references 3 other bats, open those bat files in order (as text files, or just rename them .txt).
Just copy paste each line into terminal and run them that way.
Click to expand...
Click to collapse
Thank you!

May be able to make a sh script for terminal.

Can we flash h2os?

Thank you so much to everyone involved. I should be receiving my unlock.bin file today and am anxious to get flashing. I have a few questions if anyone knows the answer:
Is the radio/modem working correctly?
If I understand correctly, after following this guide and flashing to 9.0.5 we CANNOT do future OTAs (say to 9.0.6 for example) as they are released. Is this correct?

Wow, received my token this morning, fired this up and updated. Didn't think it was possible but the update actually made the phone even better.thanks to everyone's pre work in figuring a lot of this out...