I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.
Same here, except I have no issues with it saying its rooted
just the boot message
If you want a normal stock phone then don't buy Chinese oem devices. They have to add tons of tracking and spying software that is required by the Chinese government. You can research it. Many are even banned in many countries due to their back ally tactics
Darth_revan_returns said:
Same here, except I have no issues with it saying its rooted
just the boot message
Click to expand...
Click to collapse
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.
vostok_amphibia said:
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.
Click to expand...
Click to collapse
Thanks man, now that the 6.1 plus is coming soon I think we'll be able to put it on using this guide!
vostok_amphibia said:
I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.
Click to expand...
Click to collapse
Same here, so anyone help us to solve this problem?
Related
***********Don't follow this method**************
THIS is what you want to do. This thread is an older method.
Do this at your own risk!!!....I'm by no means an expert on this. In fact it's the first time I have done this. There are probably tons of guide to doing this on the T-Mobile version but I made this to help people with the Canadian Rogers G1. So it only applies to that specific phone. This is also expecting you be using Windows (I use XP but Vista will work but I don't know where the command prompt is found....google it if it isn't in the usual spot). Also the commands would be the same using a Mac but yet again I don't know what or where the equivalent of windows command prompt would be found on a Mac.
First off you need the Android SDK which you can get from here (http://developer.android.com/sdk/1.5_r2/index.html).
Unzip the folder inside the .zip file to C:\Android so the final resulting file structure will look like C:\Android\android-sdk-windows-1.5_r2\
Now do the steps 2 and 3 found here http://developer.android.com/guide/developing/device.html
I have cut and pasted these steps here but if you are using a mac you may need to refer to the link. Actually refer to it anyways in case I missed something.
**************** Steps 2 and 3 *********************
Turn on "USB Debugging" on your device.
On the device, go to the home screen, press MENU, select Applications > Development, then enable USB debugging.
Setup your system to detect your device.
If you're developing on 32-bit Windows, you need to install the 32-bit USB driver for adb. The USB driver is included in the SDK package. To install it, follow these steps:
1.Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software. Select No, not this time and click Next.
2.Select Install from a list or specified location and click Next.
3.Select Search for the best driver in these locations. Browse to the usb_driver/x86 in the SDK package (<sdk>\usb_driver\x86).
4.Click Finish. The system should install the driver files as necessary. Your machine may require a reboot.
********************************************
Plug your USB cord into your phone and plug the USB cord into your computer.
Open a command prompt in windows by going to Start/Run and then type cmd. You should a dos like window open up. Now navigate to the directory C:\Android\android-sdk-windows-1.5_r2\tools
Type “adb devices” to confirm USB Debugging is turned on
Keep the command prompt open for later use
Get fastboot from here (http://www.htc.com/www/support/android/adp.html) and put it in the tools section of the SDK
Get these files http://drop.io/ii4t2ax and put them in the tools section of the SDK. Mount your sd card so you can copy update.zip to the root of your sd card.
Turn off your phone and then press the camera button and the power on button so it loads up to fastboot mode (or whatever it is called..lol). Once it gets to the screen with 3 androids on skateboards on the bottom you should press the “call” button to the farthest left. It should go to another screen that says “FASTBOOT USB”. If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
Now in the command prompt you need to type “fastboot boot recovery.img” don't touch your phone tile it gets to a new choice of menus in recovery mode. Once it gets there you should make a nandroid backup. I really urge you to make the backup. Make sure there is space left on your SD card.
So follow the menus and press the button combination to make the back up and once that is done press the other button combination to apply the update.zip file....Do not touch your phone at all....I'll cut and paste what Haykuro's directions were on this part to emphasize the importance of not touching anything....
(LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
Mine didn't take very long but if it does still do not touch anything. Please....just don't!
Once it is done press HOME+BACK to reboot the phone out of recovery mode.
Power off your phone and then press the camera button while pressing the power on button to go back to the fastboot menu. Press the “call” button (to the farthest left remember!) so you see it say “FASTBOOT USB”. Once again...If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
In the command prompt which you should have left open for convenience you have to type “fastboot flash boot boot.img”
Then type “fastboot flash recovery recovery.img”
Then type “fastboot reboot”
At this point you basically have root but you need to change permissions on a file that need to be on the phone so everything works as your would expect with root
Turn the phone on to be on the operating system.
Type “adb root” in the command prompt to confirm you have root access
Download this file http://www.magicandroidapps.com/su.zip
Unzip the file to the tools folder of the SDK
In the command prompt type “adb remount”
Then type “adb push su /system/bin/su”
Then type “adb shell” and you should get prompted with a # symbol
Type “chown root.shell /system/bin/su” right after the # symbol
Then type “chmod 6755 /system/bin/su”
That should be it...try running the market enabler or SetCPU which you can get here http://forum.xda-developers.com/showthread.php?t=505419
If they work then you have root....currently you CANNOT use any of the custom roms because they were made for T-Mobile versions of the G1. I'm waiting for conversions of these roms myself so have fun waiting just like me. This is the first time I have ever hacked/rooted any phone so be sure to research stuff yourself...I might have things wrong. Who knows....it's all a risk just like I took when I decided to try it without having a step by step guide to read from.
Remember guys...I JUST wrote this so be sure to read it the whole way through before jumping into things. Post problems you run into here so I can fine tune it.
so you managed to root the rogers G1?? great job!! did you figure this out yourself???
no...Haykuro did this. I just took all the available information and put it in order to help others do it. It was all in this thread here http://forum.xda-developers.com/showthread.php?t=522127
Can we get a tutorial of how to flash a new rom now I really want to try out the new hero rom.
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
XwXDv8XwX said:
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
Click to expand...
Click to collapse
Is Haykuro working with Cyanogen? Man I just want to play with the Rogers Rom. Oh well I guess I'll settle for getting rid of the Rogers crap and being able to buy stuff on the Market finally.
Yep, I made a 3.6 for the Rogers Dream. I haven't actually tested it because I don't have one, but I used Haykuro's tools to build the boot image. Let me know if it works for you guys!
Holy...where is that at? lol
My wife has gotta get her ass home with my phone damnit! lol
http://forum.xda-developers.com/showthread.php?t=518851
lol, I just finished restoring my phone too. Oh well I am downloading your files now cyanogen, here's to hoping I don't brick my phone on my first flash attempt.
Can someone point me to a guide to flash this rom to my phone?
XwXDv8XwX said:
Can someone point me to a guide to flash this rom to my phone?
Click to expand...
Click to collapse
After you have rooted, copy the file to your sdcard as "update.zip", boot into the new recovery mode, wipe your data if you are coming from the stock build, then flash the update! The first boot will take a bit longer than usual. Check my thread for a FAQ.
Just wanted to say "Thank You" I have been following the threads in the background for the better part of a week, and was hesitant to give it a shot as I am not too sharp on dealing with dos boxes. However followed it along and everything went off perfect, grabbed set CPU and installed it and works. So I guess I have root. Not really sure what I can do with root, but will look forward to browsing around and seeing what is cool.
The big thing is I want to be able to flash new roms. So I guess this is the first step in doing that. (already actively flash PPC roms on the Hermes)
Again thanks for everyones work on this.
well here it goes....it'll be the first time I ever flashed a new rom to my phone...at least I know some other people have tested this version of cyan's rom so I feel pretty safe doing this. I would just send it back and pretend I don't know what's wrong with my phone if I did brick it but things seem to be going pretty smooth so far.
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
XwXDv8XwX said:
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
Click to expand...
Click to collapse
No, you wipe before the update. Wiping doesn't erase your SD card, only the internal data partition.
Also, my ROM is a "Google" based ROM. You'll have to sacrifice the spiffy HTC dialer and Exchange support, but I include all the other HTC apps.
How's your flash going XwXDv8XwX? I tried, but was stuck on the Rogers screen for more than 10 minutes. I rebooted the phone and tried again using the "adb logcat" command to try and see what my phone is doing but as soon as it restarted I stopped getting stats. Is this like a 20-30 minute setup process perhaps?
This is taking ALOT longer than usual. It's staying at the rogers logo right now....how bad is this?
I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped
The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.
Preamble
Hello, all.
Soooo I've never posted on this forum before. I've mainly leeched the invaluable info for my personal gain. I'm sure many a googler has come here trying to figure out how to root their phone. And I'm sure many a "swimmer" in Schitz Creek has come here via Google to figure out how to save their device from what had been perceived as an upgrade. I'm speaking, of course, of trying to root/unlock a phone and finding said phone "bricked".
Well, it’s time to give back.
Because yesterday, I was neck deep in Schitz Creek. After a series of dumb decisions and a lack of knowledge, I bricked the phone I’d bought for my wife’s birthday. I was just trying to be able to delete the Asus bloatware and install titanium backup and greenify. By the way, since when did Facebook become a system app? How is this a thing? Anyways, my wife deserves better battery life. And it’s fun to feel like Cyber MacGuyver by rooting a phone. But the situation went awry. My wife kept telling me that everything was going to be alright, but I know the limitations of my knowledge.
Brief aside: I'm decently computer/phone savvy, but I would, in no way, consider myself an advanced user. Sure, to my family, I'm a computer wizard. But that doesn't mean a whole lot. To them, opening up a command prompt in Windows is seen as an act of magic. And I haven't had my planeswalker spark yet. However, I have successfully rooted, and in most cases unlocked the bootloader, for several phones (HTC desire, Galaxy S3 [three different models over three years], Asus Zenfone 5, LG G4 [once pre-motherboard-death and once post (after a downgrade)], and now the ZE552KL). So I know how to at least fumble my way around adb, fastboot, odin, and various recoveries. As long as you’re at this level, or willing to learn, then you should be able to follow these instructions. End aside.
Mistakes not to make
Let’s get down to brass tacks. I made two big mistakes that you shouldn’t make. Both mistakes stemmed from the basic mistake of using a root method other than this one: https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
The problem with not using this EXACT method is that some of the files/programs which you need to use have specific versions which will ensure an easypeasy root. Honestly, if you properly follow the instructions in the above post, you will most likely not run into any problems. The only addition I can make is that instead of steps 6 and 7, you might find it easier to install SuperSU.zip through TWRP instead of pushing and sideloading.
Mistake 1: Not using the proper TWRP file and SuperSU file
For some reason, there are multiple versions of these files. Your SuperSU file should be 4.8MB. Using the wrong SuperSU will break the dm-verity. Your TWRP should NOT be the latest experimental version. It should be the one from November or earlier of 2016. Using the wrong TWRP will leave you unable to use the touchscreen. Trust me. I know from experience.
Mistake 2: KEEP TWRP READ ONLY
Disabling read only has no current benefits. It will just break the dm-verity. Your device will still be able to be written to if you keep TWRP read only. I have no idea why it’s called “read only”.
How to unbrick the phone
I’m sure some of you skipped straight to here. While I can’t blame you, please at least read the above paragraph. It will help you.
First I will describe the situation the phone was in, and then I will explain how I saved it. Before I continue, I want to give a big shout out to Niemer. Without their helpful post, I would’ve had no idea what to do. Thanks!
Situation the phone was in
--TWRP could not be used because the touchscreen wasn’t working.
--The dm-verity was messed up (i.e. “not started in enforcing mode").
Before you look at the solutions, make sure that your phone shows up in the windows device manager as an ADB device/ASUS ADB device/ADB composite device/etc. no matter which step you’re in. Google it to figure out how if you don’t already know.
The solution
Part 1 - Create and flash a system image which will restore your dm-verity
step 1. download the latest system “update” from the asus drivers website. I have a WW version of the phone, so I downloaded “WW_V13.20.10.152”. It’s a 1.76GB file, so be patient. I haven’t tested this method with other versions of the phone, but they should work in theory.
step 2. go into the updater script file (META_INF → com → google → android → updater-script). Open it with notepad ++.
step 3. delete from the beginning of the file up until the line “ui_print("Target: asus/WW_Phone/ASUS_Z012D:6.0.1/MMB29P/13.20.10.152-20161222:user/release-keys");”
The code that you are deleting checks to make sure that your phone is the proper model. But there is a good chance that it will mistakenly identify your phone as a phony. So we need to get rid of this code.
step 4. save the updater-script file
step 5. create a copy of the modified system update zip file. You should now have two 1.76GB files (or maybe slightly different if your phone is a CN, JP, or other model. Once again, I have a WW version of the phone). Name one of the files “realupdate.zip” and name the other “dmsaver.zip”. The names aren’t actually important.
step 6. enter dmsaver.zip. delete these four files: file_contexts, system.new.dat, system.patch.dat, and system.transfer.list. Exit out of the file. It should now be about 60MB.
step 7. turn on your ZE552KL and enter fastboot mode
step 8. in a cmd screen from your main folder (i.e. the one with adb, fastboot, and all the other files, including the ones you just created), type in the command “fastboot flash system dmsaver.zip”
step 9. if successful, you have just restored the dm-verity. You should now no longer get that sinister red text which has been ruining all your fun.
Part 2 - Install a proper version of TWRP
(This is only important if your version of TWRP won’t let you do anything because you can’t use your touch screen)
Download the version of TWRP that is included in the how-to-root post I linked to above. Also, you can download the oldest version (NOT the newest) from a sharing website which is linked to in a post on the ASUS website. It’s not in english though. Flash it to your phone in fastboot mode using the “fastboot flash recovery” command. Make sure you turn your phone off before turning it back on, or your recovery might not activate correctly.
Part 3 - Install a new version of your system.
Go into TWRP and install the zip file “realupdate.zip” that you created in Part 1 - step 5.
Part 4 - Root your phone
Follow the instructions in the link I posted earlier. It comes from this website, so you know it’s good. This time, though, you probably don’t need to unlock the bootloader
Part 5 - Breathe a sigh of relief
Parting words
I really hope this guide can be of assistance to you. The full procedure for fixing “my” phone wasn’t really recorded anywhere (although once again, big shout out to Niemer for their post). I went through hundreds of iterations of seemingly random fastboot, recovery, and adb actions before everything worked out. Because of this, I feel quite fortunate to have saved the phone, and I really wanted to give back. This community has been super helpful to me over the last seven years, and this is my chance to reciprocate. I sincerely hope that this post will help you.
I hope I didn’t forget anything. I have a sneaking suspicion that I did. In any event, if you have any questions, please post them, and I’ll try to be of assistance. Happy rooting!
thank you man but i start Part1 step8 "fastboot flash system dmsaver.zip" it's successful then i go into TWRP and install the zip file “realupdate.zip” dm-verity show again.
Thank again.
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
thank you, you helped me, now im on N
I guess the version matters then. So be careful with which firmware you download/install. If anyone has success with other versions, please share how you did it
I am stuck on Step 8. i put the 2 zips in where my adb and fastboot is located, and then proceed to type 'fastboot flash system...' and then it wont let me flash, any help?
Device Locked
When I flash the dmsaver.zip, receive the error "FAILED (remote: not allowed in locked state)". Apparently this with the bootloader locked, but I already unlocked before. Someone can help me unlock the bootloader again?
Further hyperlinks & solution ideas
Check out my solution and Ideas in those in links I posted in this thread at 4th of septembre 2017:
https://forum.xda-developers.com/ze...-zenfone-3-zoom-ze553kl-t3657239#post73661437
The hyperlinks in my post might also be useful, I hope.
Would be glad about your feedback, if it helped! :good:
how do you update the script file ..can u just post the file that u made somehow or email it or attach it to a message?
cant get it to work followed the instructions still getinf error code 7 trying to install lineage os
If you have lineage OS version not is a zip file but all the images (boot.img, system.img, ...) then you could try to flash the images through ADB...
if someone have the no verity issue, can you try a method for me please?
it consists on:
re-flash the rom kernel via fastboot
and run:
Code:
fastboot oem reset-dm-verity
Followed all the steps and twrp still has no touch function.
Tried all different twrp versions.
OS Version is a key
Hi everybody that has the same issue, I hope you read that so you can fix your problem.
So what I did was downloading old version of OS that autor mentioned "WW-13.20.10.152". It is necessary to download this version even if there are more newer versions. Then follow tutorial and you should be fine.
So again, thanks OP for posting this. You helped me a lot!
WOW!!!!
One 1 person stepped up to help!! Guess I am not in a Linux forum.!! For those that run into the same problem I had below, here is the solution I came up with:
This guide got me rooted with TWRP installed.
https://forums.oneplus.com/threads/...r-flash-twrp-root-nandroid-efs-backup.931719/
If you are running Linux instead of windows be sure to run " adb start-server " before you start, nothing works well or at all if you don't. Depending on your set up you may need to prefix the commands with sudo, I had to to get the fastboot commands to work.
Here is the guide that got lineage installed for me, HOWEVER, it leaves out 1 very important step.......before you reboot, reinstall the twrp. zip file a 2nd time. If you don't lineage will install it's own recovery environment. Be sure you do this AFTER you install Lineage.
If you get an error70: not enough room in system file when installing Gapps don't panic. Here are the instructions to fix that:
https://forum.xda-developers.com/android/help/fix-error-70-install-gapps-t3311779
I will mark this solved if I can figure it out. Hope this helps someone.
My original post is below.
Howdy!
So here is where I am....... I was a long time IOS diehard until I decided no more $1200 phones for me. Got my 6t in Jan and absolutely love it! I have been watching and waiting for an official Lineage + micro g to be announced and decided I would go ahead and unlock the bootloader. This is only my 2nd time to play around with an android unlock. I knew to make a backup. I use MX Linux and Mint so I did an adb back up.
As I was unlocking the bootloader I clicked ok, then read the next line of the instructions that said "this will wipe your phone".......would have been nice to see that FIRST as I would have made multiple backups.
I did have and adb backup but, it turns out my backup will not install. Everything is fine until it gets to the audio driver file then it locks up then fails. I have tried android backup extractor with the plan of deleting the problem folder, installing, then dealing with the driver issue........but I can't get extractor to work. This may be a separate post, but a link to detailed instructions for this would be nice as well.
So, what the hell, now is a good time to install lineage, right?!?!?!
Here is my problem......I know enough to do this, however, all of the guides I can find, including the ones on this site, are either written for windows or leave out MAJOR steps that a newbie just doesn't know. For example, the guide from this site I followed to do an adb backup NEVER mentioned "adb start-server" which turned out to be the command that made the difference between a 457mb backup file and a 12.5 G back up file!!!
Unfortunately, searches on the forums turn up instructions that have not been helpful for me.
Can someone point me to an installation guide for dummies?? I would rather have a guide that tells me each and every mundane detail( even if I know it already ) than have to google solutions like I did with my back up and unlocking.
From my understanding I can install micro G instead of GAPPS, but I can't seem to find a package to install. I only find individual files with very little instructions. I would like to use Micro G to see if I can kick google out of bed like I have done Microsoft. If this is unreasonable for my skill set, I will have to settle for GAPPS.
I use Linux, not windows. I have a oneplus 6T( with a fresh, blank install LOL)., and enough knowledge to know I don't wanna brick my phone, but not enough to follow the techie guides I have found.
**UPDATE** I found some detailed instructions and finally got twrp installed and rooted with magicz....
Thank you in advance!!
Glockdoc
Somehow its true that in custom rooms threads the install guides do not exist for this phone. I see this situation for the first time on xda. Every other phone i had had a very good installation guide on xda.
See this thread
https://forum.xda-developers.com/oneplus-6t/help/question-encryption-t3940261
Thanks G, but that seems to be a thread about encryption, not a lineage install.
I did however, catch I need to disable my passcode and fingerprint BEFORE I start this adventure. Glad I read it!
I tried searching for "us997", but the search came back with an error, even though I know there are threads with "us997" in the thread title. So, forgive me for posting this new thread.
Now that the warranty has expired for my LG-US997 phone, I'd like to unlock it so that I can install Android 10 in it. It currently has 8.0.0.
I'm assuming that there is a thread specific to this phone. I'd appreciate said link.
Thanks.
Try this thread : https://forum.xda-developers.com/lg-g6/help/us997-cellular-brightpoint-bootloader-t4102267
challenger07 said:
Try this thread : https://forum.xda-developers.com/lg-g6/help/us997-cellular-brightpoint-bootloader-t4102267
Click to expand...
Click to collapse
I saw that, but dismissed it because it is about brightpoint. I have no clue as to if I have a brightpoint device. I tried using the IMEI info website, but my number is only 14 digits and they wanted 15. I filled out their contact form about it, but I've not received a response.
Even if I can unlock the phone, is Android 10 even available as a custom ROM for the phone?
I think I found custom Android 10 for the US997: https://forum.xda-developers.com/lg-g6/development/rom-havocos-v2-1-t3893668
I've downloaded the zip file.
Next step was to unlock the phone. That did not go well at all. Followed the steps from here: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
When I did this step: adb reboot bootloader
I got: no devices/emulators found
The Win7 box sees the phone, because "G6" shows up in explorer so that I can get at the SD data, internal and external.
Sigh! No fun, no fun at all.
I assume you have read the guide I wrote when I moved mine to Havos? https://forum.xda-developers.com/lg-g6/how-to/guide-step-step-install-android-10-t4141901
I would check your cable I've had issues in the past where I didn't have a quality cable, the normal reason your PC doesn't respond is that you have not turned on ADB in developer settings.
challenger07 said:
I assume you have read the guide I wrote when I moved mine to Havos? https://forum.xda-developers.com/lg-g6/how-to/guide-step-step-install-android-10-t4141901
Click to expand...
Click to collapse
Sorry, no. I had not seen that.
I would check your cable I've had issues in the past where I didn't have a quality cable, the normal reason your PC doesn't respond is that you have not turned on ADB in developer settings.
Click to expand...
Click to collapse
The cables are fine. As noted, Win7 mounts the phone and it shows up in explorer as "G6". ADB Developer settings were indeed turned on. Phone even welcomed me.
I'll be going thru your steps and will report back.
Well, looks like I am stuck until LG gets back to me as to why I am getting the error message. The LG instructions didn't have the user download the device driver, which your instructions did. I downloaded and installed and re-entered debugging mode. I re-ran the adb command, but it still comes back no devices found.
The device driver poped up a message that it did not successfully install. Of the five items in the list, it failed to install the MTP device. Looking in the device manager, I can see the MTP device, but is marked that it cannot start. Code 10. Device driver is up-to-date.
I don't know about the device driver but I searched Google and there was a useful article on unlockunit website under blog / 14-digit-imei/
In another thread, I wrote that I found the 15 digit IMEI number on the box. Unfortunately, because the adb program can't find the device, I can't get the device ID in order to get the unlock.bin file from LG. LG still has not responded to my query via their website. It looks like my attempt to unlock this phone is for naught.
Doing a little more reading, I've discovered that U.S.Cellular phones, sold after Feb 2016, are unlocked. Meaning that I can take the LG G6, in theory, to another carrier. But, that doesn't appear to mean that I can put a different Android release on it. Is the term "unlocked" being used to define more than one thing?
Since LG has not called me back, I've placed an order for the Pixel 4a.