Related
Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without apk
!!!!!!THIS IS NOW ALL FIXED AND PROPERLY WORKING BY THESE INSTRUCTIONS HOPE THIS HELPS YOU ALL!!!!!!
Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without
Q apk.
this is a guide I compiled from the following devs that are credited and thanked
below.
Apparently Google did not like that we are using our Q's again and have killed
the servers that host our Nexus Q apk, if you are currently logged into your Q
you will not notice it. If you try logging into another Q or relog into your Q for
the first time. It will not work any more.
I have 3 of these and want to keep the Q community alive, I needed to figure out
as many of you how to access your Q through adb if the app is dead to enable usb
debugging so you can load cheap cast and continue to use your Q.
This will get adb debugging back so you can load a custom recovery and get
cheapcast back running through CyanogenMod.
!!!!You will need a otg cable powered is a good idea these are $10.00 here ->
-------------------------------------------------------------------------------
To fastboot unlock your device / Credit and thanks to -> fiveipads
-------------------------------------------------------------------------------
1. cmd to platform-tools
2. Reboot to the bootloader -> cover your Q with your hand -> power on nexus Q as
soon as you see red remove your hand -> (will go solid red and you are in
bootloader)
3. Unlock your device* (with fastboot tool) (type) -> fastboot oem unlock
(immediately copy and paste this into tool and hit enter you have only 5 secs) ->
fastboot oem unlock_accept
4.Q will reboot and turn purple etc.
5.Unplug Q and restart in bootloader see #2. (type) -> fastboot getvar unlocked
(this verifies you unlocked your Q->should reply->unlocked:yes)IF NOT DO NOT
PROCEED TILL IT DOES.
-------------------------------------------------------------------------------
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/attachment.php?attachmentid=1563302&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.Flash the image -> (type in fastboot) -> fastboot flash boot boot-root.img
(image will write should say ok and writing boot etc.)
5.Pull the power on your q and restart the Q
-------------------------------------------------------------------------------
Load Clockwork Mod Recovery / Credit and thanks to -> Koush
-------------------------------------------------------------------------------
1.Download koush's ClockworkMod Recovery.
koush's ClockworkMod Recovery ->
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.1-steelhead.img
md5: dec2a809a20e8cb236ae092e71d8d5fe
2.Connect the Nexus Q to the computer via USB.
3.Make sure the fastboot binary is in your PATH or that you place the downloaded
image in the same directory as fastboot. (rename the downloaded recovery file
recovery-clockwork-6.0.3.1-steelhead.img to -> recoveryq.img to make it easy to
type)
4.Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader or by using the hardward -> cover your Q with your hand ->
power on nexus Q as soon as you see red remove your hand -> (will go solid red
and you are in bootloader)
5.Once the device is in fastboot mode, verify your PC sees the device by typing
-> fastboot devices
***If you don't see your device serial number, and instead see "<waiting for
device>", fastboot is not configured properly on your machine. See fastboot
documentation for more info.
6.FLASH ClockworkMod Recovery onto your device (type) -> fastboot flash recovery
recoveryq.img
(should confirm by okay if not do it again till it does)
7.(type) -> fastboot reboot (this will reboot your device to the factory startup
screen) -> (type) adb devices (make sure your device shows up) -> (type) -> adb
reboot recovery (you should be in clockworkMod recovery)
--------------------------------------------------------------------------------
Install Cyanogenmod to your Q through adb on Clockwork Mod / Credit and thanks to Cyanogen mod crew and hharte for amplifier support and Anthony Hopf for updated working zip file.
--------------------------------------------------------------------------------
1.Download the prebuilt release of CyanogenMod you wish to install.
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited. *****IF YOU CAN MIRROR THESE LINKS CONTACT ME WITH THE LINK*****
TAS5713 (Audio Amplifier):
Download: https://www.dropbox.com/s/vk77uq7dmpazzpz/cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: http://www.magicandroidapps.com/download/cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build. found here ->http://get.cm/?device=steelhead
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
2.Rename your cm10 file to -> cm10.zip (this will make it easier to type later)
3.Move your cm10.zip to your platform-tools folder again like you did the recoveryq.img file
4.To install boot into recovery mode (type) -> fastboot boot recovery.img (or if you are still at recovery ignore this)
5.When Q has reached recovery mode, push the cm10.zip to /sdcard using adb, (type) -> adb push cm10.zip /sdcard/
6.To push gapps (if desired download here -> http://goo.im/gapps/gapps-jb-20130301-signed.zip md5SUM: b7e53e96e1c8b1a1c4865bf29418c8e0 and rename to gapps.zip and move to platform-tools folder)(type) -> adb push gapps.zip /sdcard/
7.From within recovery, "install zip from sdcard" and browse to cm10.zip file After this has installed, it is a good idea to wipe data and cache.
8.Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps.zip file.
9.If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
10.Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu
OR YOU CAN INSTALL THIS ICS BASED ROM BASED ON THE STOCK IMAGE HERE->
http://api.viglink.com/api/click?fo...=Download it&jsonp=vglnk_jsonp_13777850981938
YOU MUST USE ICS BASED GAPPS.
--------------------------------------------------------------------------------
Install Cheapcast to q with auto boot option / credit and thanks to -> Sebastian Mauer and other devs involved (YOU NOW NEED THE OTG CABLE AND A MOUSE)
--------------------------------------------------------------------------------
1.Start your q get the otg cable plug it in wait for the Q to boot all the way the plug the mouse into the otg cable it should work.
2.+Sebastian Mauer's CheapCast allows an Android device to act as a target for #chromecast enabled applications. Android device == Nexus Q; chromecast enabled application == +Google Play Music.
3.Go to the asop brower on the Q and go to this link -> http://www.androidfilehost.com/?fid=23060877489999380
4.Download the apk do not use the store version at this time it is broken.
5.Using a file explorer find and open the apk it will be in the downloads folder. (you may need to authorize installing 3rd party apps in the security menu) once installed open cheapcast tick enable on startup and start sevices button. Now reboot your Q using a reboot button apk from the store.
6.Now your Q will be recognized as a target for any Chromecast enabled app upon startup, like Google Play Music it will also work on youtube as I have verified this, however if using the steelhead internal amp zip it will not output sound except to the internal amp. Use your device (I'm using my S4 GPE) to start and enjoy!
7.If for some reason the apk stops working on boot you may need to reinstall it and restart it for on boot starting. Your Q will now be on all day long so unplug it when not using it. until someoen makes a remote turn off apk or something.
Edit: All the XDA folks who put up a bounty? Please donate to Sebastian - grab the CheapCast app and hit the donate button!
______________________________________________________________________________
(If your Q boots up and the resolution looks wrong you will need to use a different tv or monitor ot happened to me)
I hope this help anyone like me who thought everything on this forums was way to hard to find and put together, this is all tested and is done how I typed it in.
If you mess it up DO NOT COME TO ME CRYING!
If I helped you, click my thanks button and send your donations to all the devs mentioned above, also donate to cheap cast to make it stay around.
Obviously Google does not want us to keep using our Q balls so make sure we keep devs working for us here by posting and showing interest.
Thanks- Ian
OTG cable
At what point did you need an OTG cable? Looks like you did all this via PC? Thanks so much!!!! I have two of them, both had USB debugging enabled until I did factory resets on them this morning. <sigh> The folks at Google were very nice and excruciatingly unhelpful when I called them about it this afternoon. But... apparently a "Nexus Q expert" will get back to me very soon, and I'm sure the response will be the standard Google canned response regarding the Q.
Still trying to figure out how to authorize adb debugging with only 1 usb port please someone explain
Figured it out
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
unknownkwita said:
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
Click to expand...
Click to collapse
I will try that later and report back if it works for me
This is now all fixed and working correctly!
im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing
Could someone please post a video on youtube of how to do this?
dts924s said:
Could someone please post a video on youtube of how to do this?
Click to expand...
Click to collapse
Seriously....read man....... its laid out exactly how to do it.
If you need a video you do not need to be hacking your Q
ianandamy said:
This is now all fixed and working correctly!
Click to expand...
Click to collapse
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
kario said:
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
Click to expand...
Click to collapse
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
Should be: fastboot flash boot boot-root.img
ianandamy said:
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
Click to expand...
Click to collapse
Once this rom is installed how does one get past the nexus q welcome screen?
I still can't believe that CM didn't integrate the amp functionally in their ROM..
watso4183 said:
Once this rom is installed how does one get past the nexus q welcome screen?
Click to expand...
Click to collapse
Hit the "home" key on your KB.
Lokifish Marz said:
Hit the "home" key on your KB.
Click to expand...
Click to collapse
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
ianandamy said:
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
Click to expand...
Click to collapse
Remove or rename AtHomeThemeService.apk, HubBroker.apk and Visualizer.apk from v1.0.2 and flash it. This will remove the stock Q services/frontend without breaking the audio output.
Thanks for the great guide, I just bought my Q a few days ago. I will definitely try this out. It is good to know, that the community is still alive.
Sent from my Nexus S using Tapatalk 4
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/atta...2&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.This is to test it first before you permanatly install it -> (type in fastboot)
-> fastboot boot boot-root.img (If the device reboots and the mute light goes
from red to off then you've successfully booted! Run `adb devices` to ensure it's
showing up and that you can connect to it. If all goes well (which it should)
then you can flash the boot image)
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
(image will write should say ok and writing boot etc.)
6.Pull the power on your q and restart the Q
-------------------------------
you have fastboot flash boot-root.img
its supposed to be-- fastboot "flash boot" boot-root.img
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Finally Managed to get a hand on this after a late night session with OnePlus. Great that we now have the MM Stock Reset which should theoretically help to get back to stock regardless of the ROM, customizations etc.
I believe this is the best option to use to return to stock from CM.
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
Thank you for mentioning me, Great Work
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
mantiyeah said:
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
Click to expand...
Click to collapse
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Hello , after b3 command of the tools I FAILED appears . Tips ?
---------- Post added at 02:43 PM ---------- Previous post was at 02:14 PM ----------
Thank you. Solved !!
fareed_xtreme said:
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Click to expand...
Click to collapse
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
mantiyeah said:
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
Click to expand...
Click to collapse
My Friend, you need to do any one of the above 3 mentioned methods. You could:
1. Follow this guide, the first post which has all the details. This is the method used by OnePlus to restore your phone when you have issues.
3. You could alternatively flash via Fastboot using the images from the mentioned thread.
You chose either one of the above mentioned procedures. Not both. If you run into issues do let is know. The procedure is detailed and if you follow my guide to the dot, you should be all set in the first attempt itself (for Flashing method 1)
Thanks fareed_xtreme, everything went well. Good job !
Sim and wifi not detected!!
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Thx!! My OnePlus 2 is almost dead. Fastboot recovery only works for CM recovery, and there is no ROM inside sdcard. I flash TWRP, but no working. ADB sideload, TZ version problem - no luck. Thank you for sharing this thread.
Now is back and alive again
muthukumarc said:
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Click to expand...
Click to collapse
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
fareed_xtreme said:
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
Click to expand...
Click to collapse
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
muthukumarc said:
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Click to expand...
Click to collapse
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
C.H.T.J. said:
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
Click to expand...
Click to collapse
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
fareed_xtreme said:
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
Click to expand...
Click to collapse
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
muthukumarc said:
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
Click to expand...
Click to collapse
I don't have much information on this. If your IMEI doesn't show, it means that one of your device specific partition is corrupted (I guess it's EFS, not sure). If you have a nandroid backup of all your partitions, then you could use them to recover. Else, your options are limited and your only friend is Google search. This doesn't usually happen.
When everything is ok. Press the start button. and let the progress finish.
Click to expand...
Click to collapse
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Chhatrapal said:
When everything is ok. Press the start button. and let the progress finish.
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Click to expand...
Click to collapse
This could mean that it is still waiting for your device to connect. Have you double checked your drivers and have you found the different line in the flashing app? You will need to restart the process and follow it step by step again.
It will usually take between 8 - 12 minutes max to finish flashing in the app. Also once it's done, in the app all lines will turn green (if I recall correctly).
So i've tried this and various other methods along similar lines. The flashing tool finishes and goes green but then also goes red.
On the reboot, recovery is still missing and i have fastboot.
If i use 'fastboot continue', I boot into the rom for setup and everything starts to work. However, I don't have any recovery, so the phone does not boot. Bootloader is now locked too so I can't try to flash recovery.
Hello all,
I have a Z2 on MM with 23.5.A.1.291 firmware. I want to root and install a custom recovery and have looked at the threads on here about it but I'm pretty confused! None of the various options seem to be up to date, or stable, or understandable.
This thread seems to be the most up-to-date, but the instructions are pretty vague, files seem to be missing, and quite a few people seem to have had problems with it.
Can anyone explain the simplest, safest way to root the Z2 on the latest firware? Or at least help me make head-nor-tail of the existing instructions...
Many thanks
tooplanx said:
Hello all,
I have a Z2 on MM with 23.5.A.1.291 firmware. I want to root and install a custom recovery and have looked at the threads on here about it but I'm pretty confused! None of the various options seem to be up to date, or stable, or understandable.
This thread seems to be the most up-to-date, but the instructions are pretty vague, files seem to be missing, and quite a few people seem to have had problems with it.
Can anyone explain the simplest, safest way to root the Z2 on the latest firware? Or at least help me make head-nor-tail of the existing instructions...
Many thanks
Click to expand...
Click to collapse
Download .314 ftf (or any rootable ftf for z2)
Then search for dual recovery for Xperia z2 and download the last version
And download Xperia root kit
1. Flash the ftf file that you have downloaded
2. Root it using Xperia rootkit(usb debugging must be on)
3. Install dual recovery using your pc
Thats it now you have root and recovery
I followed the guide you linked to and everything worked perfectly! As long as all files are available, I would do this again. Be sure to follow the directions exactly and you'll be fine.
Whatever you do, DON'T try to flash Nut's Dual Recovery on MM, because you'll then be in a continuous bootloop at the Sony logo; don't ask me how I know this! ;>)
wicozani said:
I followed the guide you linked to and everything worked perfectly! As long as all files are available, I would do this again. Be sure to follow the directions exactly and you'll be fine.
Whatever you do, DON'T try to flash Nut's Dual Recovery on MM, because you'll then be in a continuous bootloop at the Sony logo; don't ask me how I know this! ;>)
Click to expand...
Click to collapse
I've read through that entire thread pretty much and still haven't found clear step by step instructions :/
I've downloaded the flashtool but don't know what to do now: there is no option to 'flash' or select a file..
Surely someone out there is able to write a clear, full, step-by-step guide to root this very popular phone..?
I've rooted many different phones and installed plenty of ROMs but never found so much confusing information before!
IDIOTS GUIDE Root and TWRP
Okay, may as well do it my self...
IDIOT'S GUIDE: (for Z2 Marshmallow .291)
1. Firstly go to https://drive.google.com/file/d/0B6aEcBP7FwsWUGpQdHdvaVRCQlk/view and download the .291 kernel.
2. Then download SuperSU from here.
3. Put both these files on your phone's SD card.
4. Next download the .575 kernel here.
5. Before this can be used, you need to change it from a .zip file to a .ftf file.
- Go to the file location in the file browser.
- Click on the 'View' section in the top ribbon (Win 10).
- Check 'file name extensions' in the 'show/hide' section.
- Rename the kernel file, deleting the .zip and replacing it with .ftf instead at the end.
6. Download the Recovery for MM from here.
Extract the zip file.
7. Download the correct drivers for your phone: simplest way seems to be by installing Sony PC Companion and connecting your device.
8. Download and install 'Flashtool' from here. (The 0.9.18.6 version seems to have better compatibility).
9. Install the drivers for the flash- if you are on windows 10 or 8 you will need to turn off driver signing first:
A) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
- This will take you to the advanced boot menu.
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers.
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machineTo install the drivers you need to go to the Flashtool install folder (e.g. C:\Flashtool) and go in to the 'drivers' folder and run the 'flashtool-drivers.exe'.
- From the menu select Flashmode drivers, Fastboot drivers, and then scroll down and select Xperia Z2 device drivers (not sure if this last one is necessary if you've done step 7 previously, but I did it and everything worked.)
- Click install, and click okay on the warning messages.
10. Enable developer options on your phone (repeatedly tap on build number in 'About phone' in settings.)
Then make sure that USB Debugging is enabled, and in 'Security' that 'Allow Unknown Sources' is enabled.
11. Back up vital data (though you shouldn't loose anything), then power your phone off with it not connected to the computer.
12. Startup Flashtool and let it update etc.
13. While holding the volume down button on your phone, connect it to your PC.
Flashtool should respond and spew out a few lines of text ending with something like 'Phone ready for flashmode operations'.
14. Click on the lightning bolt, select 'Flashmode', and then in the next window browse to the location of the .575 .ftf kernel file you made. Select it, then click 'flash' at the bottom right. There should be more lines of text hopefully showing that this is completed successfully.
15. Close Flashtool, disconnect your phone, then turn on your phone.
16. Flash the recovery: Reconnect your phone to the PC and select MSC mode.
Go to the unzipped recovery and run 'install.bat' as administrator (if that doesn't work try not as administrator).
If the window that opens up stays on 'starting daemon...' for a while check on your phone as you may need to authorize the 'unknown source' connection from the PC.
The installation should complete with a 'press any key to continue'. Your phone should then automatically reboot in to TWRP recovery.
17. Install SuperSU: Once in TWRP go to 'Install' and select the SuperSU zip (you may need to select 'storage' and choose your SD card first). Swipe to install!
18. Reinstall the .291 kernel: still in TWRP do basically the same as for SuperSU but this time with the MM .291 zip.
19. Cross your fingers and reboot!
20. All being well you are now rooted, you can check root by installing 'Root Checker' form the play store.
21. Open a beer and relax!
(22. Install Cyberian camera!)
Please give me some thanks if I have helped you!
I will post this as a new thread as well so it's easier to find.
Credits:
Rocker00
Xperia Blog
Dr. Death
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Jonsonrocky said:
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Click to expand...
Click to collapse
any here? ...
Jonsonrocky said:
any here? ...
Click to expand...
Click to collapse
Hi there, I have THE VERY SAME PROBLEM. Done the same, with same lame results... BOOTLOADER STILL UNLOCKED!!
It is really frustrating... been through many posts and guides but can't finish them... fastboot OEM unlock with the user data eraser switch didn't work out well in any case.
IS THERE ANYBODY OUT THERE WITH A COMPLETE WORKING GUIDE WILLING TO SHARE IT?
Thanks in advance.
J.
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
pvkid said:
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
Click to expand...
Click to collapse
I guess no one knows the answer to this problem. This phone used to be rootable but I guess Blu changed something in their latest release of the Life One X2
How to root a Blu life one X2
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Thank you for this. I just left on vacation and will not be able to try this till next week, hope you are around then as I am sure I will have questions.
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Any luck?
We have ROOT in BLU Life One X2
dougo007 said:
Any luck?
Click to expand...
Click to collapse
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Links aren't working
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: Link works
TWRP: Link does not work
MAGISK: Link works
STOCK: Link does not work
DRIVER: Link does not work
DOWNLOAD: Link does not work
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Hello dougo007,
Some of the links are dead and I am stuck and cannot figure out how to get passed the failed error on OEM unlock. It just keeps saying try unlock go.
Could you please provide new links or point me to someplace that I can use to oem unlock my BLU Life ONE X2. I searched and can't seem to find anything.
Having the same issue as you were and the links don't work
pvkid said:
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Click to expand...
Click to collapse
Hi pvkid, do you happen to have the files from the link? or new places I can find them I am stuck in the same place you were and can't for the life of me find anything anywhere else that helps.
DISCLAMER!Follow the instructions shown in this thread at your own risks, I will not be held responsible for bricking your device, you did this yourself.
That said, the information will be kept up to date relatively frequently, and should you follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded content.
Note: This is a GSI (generic system imaging) ROM and the credits go to @eremitein and the link to his thread is below:
[OFFICIAL CAOS GSI]-----------------------------------------------------------------------------------
The download link to the rom is below:
Click here to download the ROM
----------------------------------------------------------
Here are some requirements to install this ROM on your device.
1. You must have a PC
2. The bootloader of your device must be unlocked. (if you don't know how to unlock the bootloader of your device then the instructions are below.)
3. Your phone's battery must be above 50%
4. You must install this ROM with a clean boot.img. (it is recommended to install this ROM with a clean boot.img, installing this ROM with a patched boot.img can often result in bootlooping/bricking the device.)
-----------------------------------------------
Here's how you can unlock the bootloader of your device.
1.Create a Mi account if you already don't have one.
2. Open up your phone and go into the settings and go into "About phone" then tap on the MIUI version 7 times. (you will unlock the developer options)
3. Now go back from about phone to the settings app and scroll down to "Additional settings" scroll down and you will see "developer options"
4. Open the developer options and turn on "OEM unlocking" and then click on "Mi unlock status" and now turn off the WiFi and turn on your mobile data. Now click on "Add account and device"
5. Go back to the developer options and scroll down and enable "USB debugging"
6. Now go onto your PC and head over to this link (https://en.miui.com/unlock/download_en.html) and download and extract the file that has been downloaded.
7. Go to the exctracted folder, locate and open the .exe file named "miflash_unlock"
8. Login with your Mi account.
9. Connect your device to the PC via a USB cable. (the one that comes in the box is recommended)
10. If the drivers are installed and the device is connected properly then you must see a "Unlock now" option click on it and you will get a 7 days waiting time.
11. After 7 days, try again and if nothing goes wrong your device will be unlocked.
---------------------------------------------------------------------------------------------------------------------------
Now onto installing the ROM:
1. First download and extract this file on your computer SDK Platform tools
2. Download this file and extract it on your computer MIUI 12 ROM download the fastboot file and extract it on your computer.
3. Download the custom ROM and extract it. (the download link is above)
4. Copy and paste the file to the SDK Plaltform tools folder rename the custom ROM file to "system"
5. Copy the vbmeta.img from the MIUI 12 RO folder and paste it in the SDK platform tools folder.
6. Head to your device and power it off, once it is powered off, Hold the volume down button and the power button till the fastboot screen shows up.
7. Now connect the device to your computer and on your computer open the SDK Platform tools folder and make sure that those 2 files are there, "system.img" and "vbmeta.img"
8. Right click and press the shift key at the same time and click on "Open powershell window here"
9. Now in the powershell window, type in the following codes:
Code:
.\fastboot.exe reboot fastboot
.\fastboot.exe --disable-verification flash vbmeta .\vbmeta.img
.\fastboot.exe flash system .\system.img
.\fastboot.exe -w
.\fastboot.exe reboot
-------------------------------------------------------------
If you followed the all steps then your device will be booted up with Android 11.
Hello
will it work with Redmi 9 Galahad or in general with all Redmi 9s?Thanx.
-CALIBAN666- said:
Hello
will it work with Redmi 9 Galahad or in general with all Redmi 9s?Thanx.
Click to expand...
Click to collapse
Hello, this thread is made for Redmi Note 9. I don't know why XDA moved it here... but yeah since this is a GSI it will work for Redmi 9 as well. But once again, try at your own risk.
I know what i do,thanx.Another question.
Is all running for you without bugs or something?
What about battery time and performance in general,can we use it as daily driver,thanx and nice evening,Cheers!!!
-CALIBAN666- said:
I know what i do,thanx.Another question.
Is all running for you without bugs or something?
What about battery time and performance in general,can we use it as daily driver,thanx and nice evening,Cheers!!!
Click to expand...
Click to collapse
Its a very good rom, more stable than MIUI