[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4 - Nexus 5 Q&A, Help & Troubleshooting

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

Related

I9505G [GUIDE] Install & use adb, fastboot, unlock, Root & unroot Step by Step

I9505G [GUIDE] Install & use adb, fastboot, unlock, Root & unroot Step by Step
I9505G [GUIDE] INSTALL & USE ADB, FASTBOOT, UNLOCK, ROOT & UNROOT STEP BY STEP
This STEP BY STEP GUIDE is for anyone who would like to install the Android SDK or ADB to Unlock the Bootloader, Fastboot Flash Files, Root, and Unroot back to 100% out of the box Stock for your Google Edition Galaxy S4. If you would like to install and use ADB in the future for other devices this is a great place to start. Most if not all of the files that you need are in the I9505G[STICKY] GUIDE that is HERE but links are provided throughout the tutorial below.
Please Note [ By using this Guide you assume all the RISK associated with Customizing and Modifying your GOOGLE EDITION GALAXY S IV I9505G which Voids the Warranty. If you Brick your phone, lose your job or life as we know it ends I nor anyone on this thread or forum is responsible. If you are having trouble use the search button and review the thread, of you still cannot find the answer THEN ASK, We are here to help!
INSTALLING ADB
[ Windows 7 ] Windows 8 installation is the same however you need to install Fastboot Drivers and Disable Driver Verification so follow this YouTube Tutorial HERE after you install the Android SDK. NOW PROCEED TO STEP 1.
ADB or ( Android Debub Bridge ) allows you to send commands from your computer to your phone simply put. You will need ADB to Unlock the Bootloader, relock it, fastboot flash files to the phone like recovery. This Setup will allow you to communicate with ADB from anywhere on your PC.
STEP 1.
Download the Android SDK HERE [ all that you need is SDK Tools Only scroll to the bottom and select DOWNLOAD FOR OTHER PLATFORMS you will see Windows 32 & 64 bit then select android-sdk_r22.3-windows.zip ( r22 is the latest SDK as of the date of this guide )
STEP 2.
Download 7 ZIP file HERE if you do not have 7ZIP, WINZIP OR WINRAR on your PC if you already do then proceed to STEP 4.
STEP 3.
Now that you have both files downloaded. RUN AND INSTALL 7 ZIP.
STEP 4.
Now that 7 ZIP is installed you need to unzip android-sdk_r22.3-windows.zip to your C: Drive
STEP 5
Once this File is unzipped to your C: Drive you will see android-sdk-windows in your C: Drive go ahead and rename it to make it easier to android-sdk ( delete windows part )
STEP 6
Now Open android-sdk and look inside you will see SDK-MANAGER.exe with a little android guy next to it, CLICK ON IT, Once it opens let it load the packages, You will see a buch of check boxes. ONLY CHECK ( Tools and Android SDK Tools ) ONLY thats all you need to push and pull files or do logcats. After those are checked just CLICK INSTALL 2 PACKAGES AND SELECT ACCEPT ALL and it will take awhile to download and install the packages so be patient. Once it is done downloading OPEN UP your android-sdk folder again now you should see the Tools folder and Platform tools folder.
STEP 7
Now you need to set your path so select RIGHT CLICK COMPUTER on your computer and select PROPERTIES now select ADVANCED SYSTEM SETTINGS now select ENVIRONMENT VARIABLES, now under SYSTEM VARIABLES Scroll to PATH, now CLICK EDIT, you will see a long path scroll to the end with your arrow we are going to add your SDK path now. Copy and paste this to the end of your path ;C:/android-sdk/tools;C:/android-sdk/platform-tools Now select OK and OK again and your done now open up and command prompt and type adb and press enter, You should see a long list of adb commands scroll down the screen fast,
WINDOWS 8 USERS FOLLOW THIShttp://www.youtube.com/watch?v=yRggtyNnxtI YouTube Tutorial to disable Driver Signing HERE
CONGRATULATIONS you have installed ADB.
UNLOCKING THE BOOTLOADER
Unlocking the Bootloader allows you to Root and install Custom Recoveries on your GE S4. When you Unlock the Bootloader it is going to factory reset your phone so make sure you backup any important data or contacts before you do.
STEP 1.
Make sure you have enough Battery ( at least 50% ) and Drivers are installed on your computer, if you had your phone plugged in before and your computer recognized it your drivers are installed, if not DOWNLOAD DRIVERS HERE AND INSTALL THEM. Now power off your GE S IV.
STEP 2.
Once the phone is off Hold VOLUME DOWN & VOLUME UP + THE POWER BUTTON all at the SAME TIME until it boots into a screen the has an ARROW that says POWER OFF with a ANDROID LAYING DOWN, this is FASTBOOT MODE.
STEP 3.
Open up a command prompt now that you have ADB installed and in the command prompt type fastboot oem unlock and press ENTER. You will now see a screen on your GE S IV that asks you to confirm that you want to unlock the bootloader, USE VOLUME UP TO SELECT AND PRESS THE POWER BUTTON TO CONFIRM IT. Your phone will now reset with an unlock symbol below the Google Start screen
CONGRATULATIONS YOUR BOOTLOADER IS UNLOCKED.
ROOTING YOUR GOOGLE EDITION GALAXY S IV
STEP 1.
Now that your Bootloader is Unlocked you can root your phone.
STEP 2.
Download Chainfires CF Auto Root Package HERE
STEP 3.
Create a folder on your desktop Name it ROOT I9505G now unzip the CF AUTO ROOT FILE you just downloaded to that folder. Once you unzip it you will see a Odin3-v1.85.exe CLICK ON IT AND RUN AS ADMINISTRATOR. Now select PDA and select CF-Auto-Root-jgedlte-jgedlteue-gti9505g.tar.md5 FILE inside your ROOT I9505G folder. You do not need to check or uncheck any boxes they are already pre-checked for you in ODIN which should be Auto Reboot ONLY.
STEP 4.
Power off your phone and put it into download mode. Once off hold VOLUME DOWN, HOME BUTTON + POWER Button YOU WILL SEE A WARNING SELECT VOLUME UP to CONFIRM you want to GO to DOWNLOAD MODE.
STEP 5.
Plug in your phone and YOU SHOULD SEE A BOX LIGHT UP in the top left above ID:COM that says your connected. CLICK START.
STEP 6.
Now your phone will auto root you will see it reboot with a red android guy with an eye patch and files loading just wait your phone will reboot ROOTED.
THAT'S IT YOUR ROOTED.
( Don't forget to thank Chainfire who provided our root exploit for the I9505G )
RETURNING YOUR PHONE BACK TO STOCK 100% UNROOTED
STEP 1.
Download the Stock Firmware package of your choice HERE the latest is 4.4 I9505GUEUBMKG
STEP 2.
Download ODIN HERE
STEP 3.
Power off your phone and put it into download mode. Once off hold VOLUME DOWN, HOME BUTTON + POWER Button YOU WILL SEE A WARNING SELECT VOLUME UP to CONFIRM you want to GO to DOWNLOAD MODE.
STEP 4.
Open up ODIN and CLICK PDA now select the .TAR file from the Stock firmware package you downloaded. ( Please Note some .TAR Files are contained in a ZIP File which you will have to unzip to get your .TAR File ) Make Sure Auto Reboot and F Reset Time are checked. ( If you are on an older version of ODIN ( DO NOT CHECK RE-PARTITION ) Now Double Check everything and CONNECT YOUR PHONE THAT IS IN DOWNLOAD MODE.
STEP 5.
Wait for the .TAR File to Load it takes a few minutes to load because of the size of the File. Once the File is loaded you will see your phone connected in ID.COM Port Highlighted. CLICK START. This flash is going to take awhile so be patient. Once you see PASS you will see REMOVED in the dialogue box you can now disconnect your phone and wait for it to fully boot up.
ODIN DOES NOT OVERWRITE EVERYTHING SOMETIMES OR YOU CAN GET STUCK ON THE BOOT SCREEN. DO NOT PANIC. PULL THE BATTERY AND BOOT INTO STOCK RECOVERY WHICH IS VOLUME UP + POWER WHEN YOU SEE THE SAMSUNG LOGO KEEP HOLDING A FEW MORE SECONDS AND LET GO OF BOTH. You will now see the phone boot into stock recovery. At this point you need to use the volume button to go down and highlight WIPE DATA FACTORY RESET. Now select it by pressing POWER. After it reformats you phone Make sure Reboot is highlighted and press POWER Again. LET THE PHONE BOOT BACK UP.
STEP 6.
Unrooting and Relocking the Bootloader it critical if you want to take future OTA's or you need to return the phone to Google. Open up the SUPERSU application on the phone CLICK SETTINGS and Scroll to the bottom. NOW CLICK FULL UNROOT and Reboot the Phone. [ You may have to update the SUPERSU Application in Google Play first to FULLY UNROOT if the phone is asking you to update Root in Google Play. Once you click FULL UNROOT and Reboot you are Unrooted.
STEP 7.
To relock the Bootloader you need to Power off your GE S IV. Once the phone is off Hold VOLUME DOWN & VOLUME UP + THE POWER BUTTON all at the SAME TIME until it boots into a screen the has an ARROW that says POWER OFF with a ANDROID LAYING DOWN, this is FASTBOOT MODE. Plug in your phone to the computer and open up a command prompt and type fastboot oem lock you will see on your command terminal screen that your phone is successfully locked and the phone will reboot. THAT'S IT YOUR BACK TO 100% OUT OF THE BOX STOCK UNROOTED.
FASTBOOT FLASHING RECOVERY THROUGH ADB
STEP 1.
If for any reason you need to flash either custom or stock recovery you can do it through ADB. You need to download your STOCK or CUSTOM Recovery images at the links provided. Once you download the .IMG File you need to PLACE that .IMG File in your PLATFORM TOOLS Folder in C:\android-sdk\platform-tools [ YOU CAN RENAME THE IMAGE TO “recovery” ( without quotes ).
STEP 2.
Once that file is in your PLATFORM TOOLS folder do a SHIFT RIGHT CLICK INSIDE the PLATFORM TOOLS folder and select Open command window here.
STEP 3.
Now Put your phone into Fastboot Mode ( See Step 7 Above ) and connect your phone to the computer now type fastboot flash recovery recovery.img that's it ADB will now push the recovery image to your phone.
CONGRATULATIONS YOU HAVE FASTBOOT FLASHED RECOVERY TO YOUR PHONE.
That's pretty much it you have the basic tools and knowledge to modify your GE S4.
MJ
MJHawaii said:
I9505G [GUIDE] INSTALL & USE ADB, FASTBOOT, UNLOCK, ROOT & UNROOT STEP BY STEP
This STEP BY STEP GUIDE is for anyone who would like to install the Android SDK or ADB to Unlock the Bootloader, Fastboot Flash Files, Root, and Unroot back to 100% out of the box Stock for your Google Edition Galaxy S4. If you would like to install and use ADB in the future for other devices this is a great place to start. Most if not all of the files that you need are in the I9505G[STICKY] GUIDE that is HERE but links are provided throughout the tutorial below.
Please Note [ By using this Guide you assume all the RISK associated with Customizing and Modifying your GOOGLE EDITION GALAXY S IV I9505G which Voids the Warranty. If you Brick your phone, lose your job or life as we know it ends I nor anyone on this thread or forum is responsible. If you are having trouble use the search button and review the thread, of you still cannot find the answer THEN ASK, We are here to help!
INSTALLING ADB
[ Windows 7 ] Windows 8 installation is the same however you need to install Fastboot Drivers and Disable Driver Verification so follow this YouTube Tutorial HERE after you install the Android SDK. NOW PROCEED TO STEP 1.
ADB or ( Android Debub Bridge ) allows you to send commands from your computer to your phone simply put. You will need ADB to Unlock the Bootloader, relock it, fastboot flash files to the phone like recovery. This Setup will allow you to communicate with ADB from anywhere on your PC.
STEP 1.
Download the Android SDK HERE [ all that you need is SDK Tools Only scroll to the bottom and select DOWNLOAD FOR OTHER PLATFORMS you will see Windows 32 & 64 bit then select android-sdk_r22.3-windows.zip ( r22 is the latest SDK as of the date of this guide )
STEP 2.
Download 7 ZIP file HERE if you do not have 7ZIP, WINZIP OR WINRAR on your PC if you already do then proceed to STEP 4.
STEP 3.
Now that you have both files downloaded. RUN AND INSTALL 7 ZIP.
STEP 4.
Now that 7 ZIP is installed you need to unzip android-sdk_r22.3-windows.zip to your C: Drive
STEP 5
Once this File is unzipped to your C: Drive you will see android-sdk-windows in your C: Drive go ahead and rename it to make it easier to android-sdk ( delete windows part )
STEP 6
Now Open android-sdk and look inside you will see SDK-MANAGER.exe with a little android guy next to it, CLICK ON IT, Once it opens let it load the packages, You will see a buch of check boxes. ONLY CHECK ( Tools and Android SDK Tools ) ONLY thats all you need to push and pull files or do logcats. After those are checked just CLICK INSTALL 2 PACKAGES AND SELECT ACCEPT ALL and it will take awhile to download and install the packages so be patient. Once it is done downloading OPEN UP your android-sdk folder again now you should see the Tools folder and Platform tools folder.
STEP 7
Now you need to set your path so select RIGHT CLICK COMPUTER on your computer and select PROPERTIES now select ADVANCED SYSTEM SETTINGS now select ENVIRONMENT VARIABLES, now under SYSTEM VARIABLES Scroll to PATH, now CLICK EDIT, you will see a long path scroll to the end with your arrow we are going to add your SDK path now. Copy and paste this to the end of your path ;C:/android-sdk/tools;C:/android-sdk/platform-tools Now select OK and OK again and your done now open up and command prompt and type adb and press enter, You should see a long list of adb commands scroll down the screen fast,
WINDOWS 8 USERS FOLLOW THIShttp://www.youtube.com/watch?v=yRggtyNnxtI YouTube Tutorial to disable Driver Signing HERE
CONGRATULATIONS you have installed ADB.
UNLOCKING THE BOOTLOADER
Unlocking the Bootloader allows you to Root and install Custom Recoveries on your GE S4. When you Unlock the Bootloader it is going to factory reset your phone so make sure you backup any important data or contacts before you do.
STEP 1.
Make sure you have enough Battery ( at least 50% ) and Drivers are installed on your computer, if you had your phone plugged in before and your computer recognized it your drivers are installed, if not DOWNLOAD DRIVERS HERE AND INSTALL THEM. Now power off your GE S IV.
STEP 2.
Once the phone is off Hold VOLUME DOWN & VOLUME UP + THE POWER BUTTON all at the SAME TIME until it boots into a screen the has an ARROW that says POWER OFF with a ANDROID LAYING DOWN, this is FASTBOOT MODE.
STEP 3.
Open up a command prompt now that you have ADB installed and in the command prompt type fastboot oem unlock and press ENTER. You will now see a screen on your GE S IV that asks you to confirm that you want to unlock the bootloader, USE VOLUME UP TO SELECT AND PRESS THE POWER BUTTON TO CONFIRM IT. Your phone will now reset with an unlock symbol below the Google Start screen
CONGRATULATIONS YOUR BOOTLOADER IS UNLOCKED.
ROOTING YOUR GOOGLE EDITION GALAXY S IV
STEP 1.
Now that your Bootloader is Unlocked you can root your phone.
STEP 2.
Download Chainfires CF Auto Root Package HERE
STEP 3.
Create a folder on your desktop Name it ROOT I9505G now unzip the CF AUTO ROOT FILE you just downloaded to that folder. Once you unzip it you will see a Odin3-v1.85.exe CLICK ON IT AND RUN AS ADMINISTRATOR. Now select PDA and select CF-Auto-Root-jgedlte-jgedlteue-gti9505g.tar.md5 FILE inside your ROOT I9505G folder. You do not need to check or uncheck any boxes they are already pre-checked for you in ODIN which should be Auto Reboot ONLY.
STEP 4.
Power off your phone and put it into download mode. Once off hold VOLUME DOWN, HOME BUTTON + POWER Button YOU WILL SEE A WARNING SELECT VOLUME UP to CONFIRM you want to GO to DOWNLOAD MODE.
STEP 5.
Plug in your phone and YOU SHOULD SEE A BOX LIGHT UP in the top left above ID:COM that says your connected. CLICK START.
STEP 6.
Now your phone will auto root you will see it reboot with a red android guy with an eye patch and files loading just wait your phone will reboot ROOTED.
THAT'S IT YOUR ROOTED.
( Don't forget to thank Chainfire who provided our root exploit for the I9505G )
RETURNING YOUR PHONE BACK TO STOCK 100% UNROOTED
STEP 1.
Download the Stock Firmware package of your choice HERE the latest is 4.4 I9505GUEUBMKG
STEP 2.
Download ODIN HERE
STEP 3.
Power off your phone and put it into download mode. Once off hold VOLUME DOWN, HOME BUTTON + POWER Button YOU WILL SEE A WARNING SELECT VOLUME UP to CONFIRM you want to GO to DOWNLOAD MODE.
STEP 4.
Open up ODIN and CLICK PDA now select the .TAR file from the Stock firmware package you downloaded. ( Please Note some .TAR Files are contained in a ZIP File which you will have to unzip to get your .TAR File ) Make Sure Auto Reboot and F Reset Time are checked. ( If you are on an older version of ODIN ( DO NOT CHECK RE-PARTITION ) Now Double Check everything and CONNECT YOUR PHONE THAT IS IN DOWNLOAD MODE.
STEP 5.
Wait for the .TAR File to Load it takes a few minutes to load because of the size of the File. Once the File is loaded you will see your phone connected in ID.COM Port Highlighted. CLICK START. This flash is going to take awhile so be patient. Once you see PASS you will see REMOVED in the dialogue box you can now disconnect your phone and wait for it to fully boot up.
ODIN DOES NOT OVERWRITE EVERYTHING SOMETIMES OR YOU CAN GET STUCK ON THE BOOT SCREEN. DO NOT PANIC. PULL THE BATTERY AND BOOT INTO STOCK RECOVERY WHICH IS VOLUME UP + POWER WHEN YOU SEE THE SAMSUNG LOGO KEEP HOLDING A FEW MORE SECONDS AND LET GO OF BOTH. You will now see the phone boot into stock recovery. At this point you need to use the volume button to go down and highlight WIPE DATA FACTORY RESET. Now select it by pressing POWER. After it reformats you phone Make sure Reboot is highlighted and press POWER Again. LET THE PHONE BOOT BACK UP.
STEP 6.
Unrooting and Relocking the Bootloader it critical if you want to take future OTA's or you need to return the phone to Google. Open up the SUPERSU application on the phone CLICK SETTINGS and Scroll to the bottom. NOW CLICK FULL UNROOT and Reboot the Phone. [ You may have to update the SUPERSU Application in Google Play first to FULLY UNROOT if the phone is asking you to update Root in Google Play. Once you click FULL UNROOT and Reboot you are Unrooted.
STEP 7.
To relock the Bootloader you need to Power off your GE S IV. Once the phone is off Hold VOLUME DOWN & VOLUME UP + THE POWER BUTTON all at the SAME TIME until it boots into a screen the has an ARROW that says POWER OFF with a ANDROID LAYING DOWN, this is FASTBOOT MODE. Plug in your phone to the computer and open up a command prompt and type fastboot oem lock you will see on your command terminal screen that your phone is successfully locked and the phone will reboot. THAT'S IT YOUR BACK TO 100% OUT OF THE BOX STOCK UNROOTED.
FASTBOOT FLASHING RECOVERY THROUGH ADB
STEP 1.
If for any reason you need to flash either custom or stock recovery you can do it through ADB. You need to download your STOCK or CUSTOM Recovery images at the links provided. Once you download the .IMG File you need to PLACE that .IMG File in your PLATFORM TOOLS Folder in C:\android-sdk\platform-tools [ YOU CAN RENAME THE IMAGE TO “recovery” ( without quotes ).
STEP 2.
Once that file is in your PLATFORM TOOLS folder do a SHIFT RIGHT CLICK INSIDE the PLATFORM TOOLS folder and select Open command window here.
STEP 3.
Now Put your phone into Fastboot Mode ( See Step 7 Above ) and connect your phone to the computer now type fastboot flash recovery recovery.img that's it ADB will now push the recovery image to your phone.
CONGRATULATIONS YOU HAVE FASTBOOT FLASHED RECOVERY TO YOUR PHONE.
That's pretty much it you have the basic tools and knowledge to modify your GE S4.
MJ
Click to expand...
Click to collapse
Isn't the Bootloader already unlocked on the GPE I9505G? I was able to root and install custom recovery without going through the bootloader unlock process.
Please don't quote the whole OP. Last I checked it would be impossible to flash root or custom recovery on a locked boot loader.
Sent from my Nexus 5 using Tapatalk
MJHawaii said:
Please don't quote the whole OP. Last I checked it would be impossible to flash root or custom recovery on a locked boot loader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So my point is why tell people who have the I9505G GPE phone they need to unlock the bootloader to root their phone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dratsablive said:
So my point is why tell people who have the I9505G GPE phone they need to unlock the bootloader to root their phone?
Click to expand...
Click to collapse
You cannot Root a or install Custom Recovery on a Locked Boot loader.
The GE S4 could fall under the Nexus category but I don't know anyone willing to try it except you which you obviously did not do your homework and took a risk. If you did root the I9505G successfully on a locked BL then unroot relock and try it again then I will have all OP updated. You could even film it and upload it to YouTube so we can show it..
Sent from my Nexus 5 using Tapatalk
MJHawaii said:
You cannot Root a or install Custom Recovery on a Locked Boot loader.
The GE S4 could fall under the Nexus category but I don't know anyone willing to try it except you which you obviously did not do your homework and took a risk. If you did root the I9505G successfully on a locked BL then unroot relock and try it again then I will have all OP updated. You could even film it and upload it to YouTube so we can show it..
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My point was I was able to root and install a custom recovery on my GPE I9505G without having to do the bootloader unlock. So my question is the GPE I9505G unlocked? Or was my phone an anomoly?
Not to drag this on and on, but I am 99% sure that I never unlocked bootloader on my GE either. That was one of the draws when these phones were announced while developers were struggling to unlock the ATT bootloader. Looking back in google search, it appears that the phone was to be delivered with unlocked bootloaders. I could be mistaken about this, but it is my recollection.
wilbarger said:
Not to drag this on and on, but I am 99% sure that I never unlocked bootloader on my GE either. That was one of the draws when these phones were announced while developers were struggling to unlock the ATT bootloader. Looking back in google search, it appears that the phone was to be delivered with unlocked bootloaders. I could be mistaken about this, but it is my recollection.
Click to expand...
Click to collapse
The phone shipped with a locked boot loader but falls under the Nexus category so CF Auto Root is able to flash and OEM unlock that's why when you run it on a locked BL and chainfires exploit runs when the phone reboots you see the unlocked symbol.
But to go back to the guy who's initial question. Yes you can Root without fastboot OEM unlock but only for select phones mentioned. It would BEHOOVE YOU to not look for shortcuts and Learn how to install the SDK and use fastboot FOR WHICH the guide was INTENDED. Its a MUST Have in certain situations.
Sent from my Nexus 5 using Tapatalk
MJ, thanks for the clarification. I have used SDK tools and must have unlocked my bootloader as I flash kernals, ROMS and radios without issues.
wilbarger said:
MJ, thanks for the clarification. I have used SDK tools and must have unlocked my bootloader as I flash kernals, ROMS and radios without issues.
Click to expand...
Click to collapse
This guide if used correctly and understood will help anyone when it comes to modding android phones. ADB is an absolute Must if you have an HTC phone, toolkits fail so having the Old School knowledge is a life saver and is quicker once you get used to it. My goal with this guide is bigger than one phone or tablet. It gives you the core skills. Hope it helps
Sent from my Nexus 5 using Tapatalk
In my case I didn't use Chain Fire to root my phone, I used odin to flash a rooted stock rom, and then installed TWRP Manager and installed TWRP.
I
dratsablive said:
In my case I didn't use Chain Fire to root my phone, I used odin to flash a rooted stock rom, and then installed TWRP Manager and installed TWRP.
Click to expand...
Click to collapse
That's not What you said and that's a stock pre-rooted Odin package that does the BL Unlock for you. Do me a favor drat get off my thread or be absolutely clear on what your saying instead of confusing everyone.
SO FINALLY TO BE CLEAR GO BACK AND READ!! YOU CANNOT ROOT A LOCKED BOOTLOADER except in the cases previously mentioned X, Y, Z .
CASE CLOSED
I wrote you an easy guide to use adb but you want to be lazy use Odin firmware packages and then troll this thread when you missed the Guides purposes all together
Sent from my Nexus 5 using Tapatalk
No need to be hostile. My query was that the GE , I9505G, had an unlocked bootloader to begin with, and didn't need unlocking.
dratsablive said:
No need to be hostile. My query was that the GE , I9505G, had an unlocked bootloader to begin with, and didn't need unlocking.
Click to expand...
Click to collapse
Your query was wrong! The I9505G does not have a unlocked bootloader to begin with you flashed a firmware package that does the work for you. What I am trying to do here is get you to understand how it works so you or someone else doesn't brick your phone because you think this is how everything works. The I9505G is different than other Samsung phones. If you tried to run a root exploit without Odin in this case on a locked bootloader you would brick your phone. I hope this clears things up for you. I hope that you go back re read the OP here and XDA forum rules and how important searching and reading is before posting potentially damaging comments. MJ
Sent from my Nexus 5 using Tapatalk
I don't want to throw gas on this discussion but the info is wrong. I installed TWRP and rooted long before I ever unlocked the bootloader. The ONLY reason I unlocked it at all was to help Chainfire test something, and that was about 6 weeks after I got the phone. You CAN flash custom recovery or other unsigned code without unlocking. It's quite possible. I've done it. It's one of the VERY few phones I've ever seen that allows it.
SamuriHL said:
I don't want to throw gas on this discussion but the info is wrong. I installed TWRP and rooted long before I ever unlocked the bootloader. The ONLY reason I unlocked it at all was to help Chainfire test something, and that was about 6 weeks after I got the phone. You CAN flash custom recovery or other unsigned code without unlocking. It's quite possible. I've done it. It's one of the VERY few phones I've ever seen that allows it.
Click to expand...
Click to collapse
Yeah I know I made the point a couple posts back that this phone is like the nexus but I also wanted to get a good adb guide posted here for those who would like to learn and use it.
Our phone is unique in that sense. Hope this guide helps those who want to install and use adb.
Sent from my Nexus 5 using Tapatalk
MJHawaii said:
Yeah I know I made the point a couple posts back that this phone is like the nexus but I also wanted to get a good adb guide posted here for those who would like to learn and use it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Would be incredibly useful! Did you notice that in MKG they removed the ability to load an OTA from external sdcard? I had to sideload it this morning. Not a big deal but if you've never done it before it can be a little confusing. An ADB guide would rock!
SamuriHL said:
Would be incredibly useful! Did you notice that in MKG they removed the ability to load an OTA from external sdcard? I had to sideload it this morning. Not a big deal but if you've never done it before it can be a little confusing. An ADB guide would rock!
Click to expand...
Click to collapse
Hence your adb guide feel free to add to it or I can put in a sideload guide, system dump..etc..etc.
Sent from my Nexus 5 using Tapatalk
A good idea. The trick to sideload isn't so much the adb. It's the damn drivers. I cheat and use Koush's universal ADB driver. I use adb sideload for installing root with touchless CWM, as well. These are very useful things to know how to do.
SamuriHL said:
A good idea. The trick to sideload isn't so much the adb. It's the damn drivers. I cheat and use Koush's universal ADB driver. I use adb sideload for installing root with touchless CWM, as well. These are very useful things to know how to do.
Click to expand...
Click to collapse
Strange I never have any problems using adb to flash or side load anything but the universal driver is an excellent tool
Sent from my Nexus 5 using Tapatalk

[Tutorial | In-Depth] Huawei G750-U10 from Android 4.2 to 4.4.2 (+ personal exp)

Hello Everyone. This is my first post on XDA-Developers, and I want to share my experience on how I transferred my Huawei G750-U10 to Android 4.4.2. For the people not interested in my experience, and are only here for the explanation, scroll down to the tutorial part.
Story part (my experience)
First off, I did some research on how to root the phone, because you will need a rooted phone to install other firmware and custom ROMS. Rooting is essentially unlocking an account on your phone that has access to all the files and programs so that you can have more control over your phone (it is normally disabled for security reasons). Rooting the phone was easy. I used a program called RootGenius, which is just a 1 click-root program. Very handy and easy. After this, the hard part started.
Fyi, the only reason that I started this project is because I wanted to play Pokémon GO w/o buying a new device
From this step I did a full backup of my current ROM and NVRAM and wrote down my IMEI numbers (the G750 has 2 IMEI numbers because it has 2 SIM-Card slots). These numbers are unique for your phone and are used for calling and sending SMS messages. So make sure you write them down (in my phone they were also written down under the battery). The program I used to backup the NVRAM and the IMEI numbers is MTKDroidTools.
After this step, I tried unlocking my bootloader. But it was very stubborn (I was using the latest firmware from Huawei, B119) and I tried doing this with fastboot. Which failed every single time and gave a 0x7000 error when I tried to unlock the bootloader. But I have to say that my bootloader was acting weird from the start anyway. Whenever I used the command:
Code:
fastboot oem device-info
It always showed that the bootloader was unlocked, eventhough after I locked it using the command:
Code:
fastboot oem lock
Which is weird. So I will just include a tutorial on how to unlock the bootloader just in case yours works normal.
So, after realising that my bootloader was not working correctly, and I could not install any recovery mod like CWM or TWRP (or any custom ROM for that matter), I found out that I needed to flash to the chip directly. This was also a huge challange, since i've never done this before and I actually did not know what I was doing. I've changed ROMS on phones a couple of times before, but that always was with a unlocked bootloader and so via the "normal" recovery system way.
For this part, I used XDA user: jacktackles' post a lot. He had some handy information about flashing to the chipset immediately and on what files to use. Since my B119 firmware was locked, I first wanted firmware with an unlocked bootloader. So I flashed some Chinese G750 firmware, that changed my device from a G750-U10 to a G750-T00. The flashing process was not flawless at all, and was the part that took me the most time (10+ hours). This all because I forgot to untick 1 simple box... Oh well, I guess that is how it works (at least I got it to work ). So, after flashing this Chinese firmware, the hardest part was done. And I had access to TWRP Recovery. With this I installed the custom ROM that I wanted, and that is where my adventure ended.
So, to summarize: It is not easy, and not beginner friendly. That is why I wanted to make this post: To make it easier for you guys to do the same and get to catch YOUR Pokémon! (Or just to upgrade to 4.4.2). So let's now go to the tutorial part!
Tutorial part
I did this with a Windows 10 64-bit computer, although I would recommend using Windows 7. You will also need a usb-cable to connect your phone to your computer. Make sure that everytime you install a new ROM that you re-enable USB-debugging. You do this by going to your phone options > About Phone > Click "build number" 7 times > Go back to options > Developers options and tick the USB-Debugging tickbox.
Sorry for not uploading screenshots, but XDA prevents me from using any outside links because I'm a new user (so i'll try to be as precise as possible). This means that also any downloadable files should be retrieved from jacktackles' post (again big thanks to him!). His forum post can be found here: http://forum.xda-developers.com/android/general/huawei-g750-u10-honor-3x-kitkat-4-4-2-t3038166.
So, go to his post and download the VCOM drivers, MKT Droid Tools, B113 4.2.2 base with unlocked bootloader, Root Genius, and this ROM from another XDA-Developer: http://forum.xda-developers.com/showthread.php?p=62356379#post62356379 (Thanks a lot mate! Awesome upload). The Gaaps link is not needed with my method, and the last link is down. So you will need to get a replacement ROM for that. I used one from NeedRom. Just go to their site, and search for G750-U10 and download a ROM that you want (which is Android 4.4.2 of course). Or download another rom from any other site. The one I used is called: G750-U10 KitKat which was listed on the site on: 07/22/2015 11:35 pm. But you can also choose to download another ROM.
So to sum up, we got 3 ROMS:
1. The Chinese Firmware downgrade to B113
(FILENAME: G750-U10 V100R001C00B113CUSTC432D001_Firmware_Slovakia_Austria_Lithuania_Czech Republic_Latvia_Estonia_Greece_05021NHU)
2. The ROM from pavel22 to change the device to G750-T00
(FILENAME: G750-T00_mod8_265_FlashTool)
3. The ROM that we finally are after
(FILENAME: Huawei G750 U10 Kit Kat 4.9.16)
(In my case of course, not if you downloaded another "final" ROM)
Okay, so after all the files are downloaded and extracted (except for the 3rd ROM), we can start!
1. Rooting
This step is very simple and quick. Plug in your phone to your PC and open Root Genius. Click the big button and your phone should be rooted. If it gives an error, just try again and again until it works. After this restart your phone, and a new app "RootKing" should be installed. If not, the phone is not rooted.
2. MTK Droid Tools (backing up NVRam & IMEI)
Extract MTK Droid Tools from it's ZIP file, and place it in a folder. Now extract the VCOM drivers and install them. These drivers make MTK Droid Tools recognize your device. After installing the drivers, open up the .exe file from MTK and make sure it recognizes your device. If it does not, reboot your PC and try again. After your device is recognized, install the "adbd insecure" app on your device, from the playstore (or download it somewhere else if you do not want to pay). But trust me, it is worth the money. Once adbd is installed, tick both boxes on the app, so that we can connect to your phone with MTK. If done correctly, MTK Droid Tools should now be able to get full access to your device, and a green box will appear in the left bottom of the program.
Now, backup your NVRam and IMEI. You do this by clicking on the "IMEI/NVRAM" button, and clicking backup. To be safe and for ease of access, write down your IMEI's on a paper or notepad file. Now the real fun starts!
2.5 Unlocking the bootloader (you might not have to do this)
Only do this step if you get a BROM error with code 6045 when trying to flash any roms. Here is how you unlock the bootloader:
1. Install ADB drivers. I used a tool made by XDA user Snoop05 (http://forum.xda-developers.com/showthread.php?p=48915118)
2. Connect your device to your pc
3. Open up a command promt from windows
4. type "adb" and check if it returns a big list of available commands (that you know for sure that adb is installed)
5. Type "fastboot" and check if it returns a big list, for the same reason
6. Now type "adb devices" and check if it gives your device, if not make sure you have correct usb drivers installed for the G750-U10, if not just install HiSuite from Huawei (It comes with the correct drivers), then disconnect your device and type "adb devices" again.
7. Now type "adb reboot-bootloader" and your phone will restart in fastboot mode.
8. Type "fastboot oem unlock" and follow the instructions on your phone screen (they are very small and hard to read).
3. Flashing the Chinese Firmware
In the Chinese firmware folder, there will be 4 sub-folders: SD_Upgrade, Update Tool, USB_DRV, USB_Upgrade.
0. Delete the SD_Upgrade folder (Not needed).
1. Go to USB_DRV and install the .exe file in the: "Driver For servers 2012-11-27" rar file.
2. After this open the Update Tool folder and extract files.
3. Open the flash_tool.exe file, which is used to flash the device (like the name suggests )
4. Once the program is open, click on the "scatter-loading" button. Search for the USB_Upgrade folder, and select the MT6592_Android_scatter.txt file.
5. Turn off your device, remove the battery, wait a few seconds and reinsert the battery back into the device. Do NOT turn on the device.
6. Make sure SP_Flash_Tool is set to "Download only" (can be set by the dropdown box)
7. Click the "Download" button, and connect your device to your PC.
8. Wait, and the progress bar will fill up. DO NOT DISCONNECT YOUR DEVICE OR YOU COULD BRICK IT!
9. Success? Great! Restart the phone and progress to the next step!
10. Failure? Untick the Preloader partition and repeat from step 5. Still not working? Also untick USRDATA and try again.
4. Flashing the: "G750-U10 to G750-T00" Firmware
This will be almost the same as part 3.
Extract the "G750-T00_mod8_265_FlashTool" rar file, and:
3. Open the flash_tool.exe file, which is used to flash the device (like the name suggests )
4. Once the program is open, click on the "scatter-loading" button. Search for the USB_Upgrade folder, and select the MT6592_Android_scatter.txt file (make sure that you select the scatter file from the new rar file, and that you are not using the same one as before).
5. Turn off your device, remove the battery, wait a few seconds and reinsert the battery back into the device. Do NOT turn on the device.
6. Make sure SP_Flash_Tool is set to "Download only" (can be set by the dropdown box)
7. Click the "Download" button, and connect your device to your PC.
8. Wait, and the progress bar will fill up. DO NOT DISCONNECT YOUR DEVICE OR YOU COULD BRICK IT!
9. Success? Great! Restart the phone and progress to the next step!
10. Failure? Untick the Preloader partition and repeat from step 5. Still not working? Also untick USRDATA and try again.
5. Restoring your NVRam and IMEI
You might need to root your device again, check if need be, by searching for an app called SuperSU or RootKing. If they are not present, root the device again with Root Genius.
You will need to re-install the "adbd" app on your new ROM. If there is no Play Store present, search for a Play Store APK on Google. Once, installed check the 2 tickboxes and re-open MTK Droid Tools.
Click on the "IMEI/NVRAM" button restore your backed-up NVRAM and retype you IMEI codes. Once the restores are done, restart the phone and check if you can call someone. If it works, good job! You can now progress to the very last step! If not, check if you entered the IMEI correct. You probably made a Typo.
6. Installing final ROM
Now that you have installed pavel22's ROM, you have access to a recovery system. So copy the whole 3rd zip file to the root folder of you device. Turn off your device, and turn it on again but this time while holding both volume buttons and the power button until TWRP opens. Click on install, search your zip file and swipe right. When it finishes, do a factory reset from TWRP and then reboot the system normally. You should now have a fully working G750-U10 with Android 4.4.2. Congratulations!
This was my tutorial and personal experience with converting my G750-U10 to Android 4.4.2. It has been a wild ride, and i've reached points that I wanted to throw my device against the wall. I'm now very happy with my (feeling like) new device. I can now finally catch 'em all and become the best PokéMaster ever!
~ NeusAap.
Thank you for the tutorial. I know nothing about flashing.
However, I could follow the instruction until 4. Flashing the: "G750-U10 to G750-T00" Firmware.
The problem is that after I had clicked the "Download" button, and connected my device, the error popped up BROM ERROR : S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND (6045).
Could you please help? Thank you.
NT79 said:
Thank you for the tutorial. I know nothing about flashing.
However, I could follow the instruction until 4. Flashing the: "G750-U10 to G750-T00" Firmware.
The problem is that after I had clicked the "Download" button, and connected my device, the error popped up BROM ERROR : S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND (6045).
Could you please help? Thank you.
Click to expand...
Click to collapse
That error means that your bootloader must be locked. For me, it was acting weird. They way you want to (try) to unlock the bootloader is as follows:
1. Install ADB drivers. I used a tool made by XDA user Snoop05 (http://forum.xda-developers.com/showthread.php?p=48915118)
2. Connect your device to your pc
3. Open up a command promt from windows
4. type "adb" and check if it returns a big list of available commands (that you know for sure that adb is installed)
5. Type "fastboot" and check if it returns a big list, for the same reason
6. Now type "adb devices" and check if it gives your device, if not make sure you have correct usb drivers installed for the G750-U10, if not just install HiSuite from Huawei (It comes with the correct drivers), then disconnect your device and type "adb devices" again.
7. Now type "adb reboot-bootloader" and your phone will restart in fastboot mode.
8. Type "fastboot oem unlock" and follow the instructions on your phone screen (they are very small and hard to read).
If your bootloader is now unlocked, you should try to flash again. My phone gave an error at the step 9, but I still followed these 9 steps. So the error I got could also have been a visual programming error, or bug.
I hope this helps! Keep me up to date
NT79 said:
Thank you for the tutorial. I know nothing about flashing.
However, I could follow the instruction until 4. Flashing the: "G750-U10 to G750-T00" Firmware.
The problem is that after I had clicked the "Download" button, and connected my device, the error popped up BROM ERROR : S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND (6045).
Could you please help? Thank you.
Click to expand...
Click to collapse
Same error. I tried several times with "fastboot oem unlock" but it didn't work: err 0x7000. I could't find anything helpful on the internet.
The odd thing is when i typed "fastboot getinfo-bootloader" I got "(bootloader) unlocked".
I just wanted to be a pokemon trainer too
Iroh96 said:
Same error. I tried several times with "fastboot oem unlock" but it didn't work: err 0x7000. I could't find anything helpful on the internet.
The odd thing is when i typed "fastboot getinfo-bootloader" I got "(bootloader) unlocked".
I just wanted to be a pokemon trainer too
Click to expand...
Click to collapse
That was the excact same error I was getting. Also the same deal with the oem get-bootinfo thingy. Are you sure that while flashing you have unticked the "preloader" and the "usrdata" sectors? That is what did it for me honestly
SeñorNeusAap said:
Are you sure that while flashing you have unticked the "preloader" and the "usrdata" sectors? That is what did it for me honestly
Click to expand...
Click to collapse
I'm very sure, i tried locking ad re-unocking the bootloader but i get the same error
Iroh96 said:
I'm very sure, i tried locking ad re-unocking the bootloader but i get the same error
Click to expand...
Click to collapse
Alright, then skip step 3 and go to step 4. I might have screwed up the step orders (It's hard to remember in what order I did all the steps ) if that works, i'll change the OP. I'm dorry if thats the case.
SeñorNeusAap said:
Alright, then skip step 3 and go to step 4. I might have screwed up the step orders (It's hard to remember in what order I did all the steps ) if that works, i'll change the OP. I'm dorry if thats the case.
Click to expand...
Click to collapse
You mean flashing the G750-T00 fw and then the chinese one? So I have to reinstall the original fw? Cause currently I'm running the chinese
Iroh96 said:
You mean flashing the G750-T00 fw and then the chinese one? So I have to reinstall the original fw? Cause currently I'm running the chinese
Click to expand...
Click to collapse
Yes, flash the g750-t00 one, and then the rom that you want if that worked. I think that I might have skipped that whole firmware downgrage rom
Thank you for answering
I tried what you had told me to do, but when I typed "fastboot oem unlock", the phone told me to use Volume Up/Down button. I used "Volume Up" button to unlock bootloader but it failed - err 0x7000 same as Iroh96, I guess. So I typed "fastboot getinfo-bootloader"; however, I got "waiting for device" instead of "(bootloader) unlocked". Then, I tried step 4 but it was still an error 6045. I don't know what to do next.
Why is it so hard to be a pokemon trainer?
hi, i couldn't download the:
"Rooted with twrp recovery inbuild base rom"
because the link is not available.
is this really necessary?
if yes, can you give me another link to download it?
i wanna start follow the steps but first i need all the downloads
Inquiries
I already read and downloaded all files which included in jacktackles thread.. I even read the whole posts
My point of view is, im kinda a noob to root business and afraid to end up by destroying my device especially when I contacted an Egyptian -who had already converted his phone- and he didn't recommend to do this.. so please bare with me.
*first of all is the deal link for "Rooted with twrp recovery inbuild base rom" is this really necessary?
*2nd point is my phones build, its B116. Can I proceed converting my phone or it won't work?
Thanks in advance
FOR THOSE WHO ARE HAVING TROUBLE UNLOCKING THE BOOTLOADER:
I found this post from Pavel22
http://forum.xda-developers.com/showpost.php?p=55497054&postcount=1768
Good luck! I successfully converted my Huawei G750-U10 to G750-T00. Now, I'm on Kitkat 4.4.2. Thanks for this in-depth tutorial, btw. Was really a great help.
SeñorNeusAap said:
Hello Everyone. This is my first post on XDA-Developers, and I want to share my experience on how I transferred my Huawei G750-U10 to Android 4.4.2. For the people not interested in my experience, and are only here for the explanation, scroll down to the tutorial part.
Story part (my experience)
First off, I did some research on how to root the phone, because you will need a rooted phone to install other firmware and custom ROMS. Rooting is essentially unlocking an account on your phone that has access to all the files and programs so that you can have more control over your phone (it is normally disabled for security reasons). Rooting the phone was easy. I used a program called RootGenius, which is just a 1 click-root program. Very handy and easy. After this, the hard part started.
Fyi, the only reason that I started this project is because I wanted to play Pokémon GO w/o buying a new device
From this step I did a full backup of my current ROM and NVRAM and wrote down my IMEI numbers (the G750 has 2 IMEI numbers because it has 2 SIM-Card slots). These numbers are unique for your phone and are used for calling and sending SMS messages. So make sure you write them down (in my phone they were also written down under the battery). The program I used to backup the NVRAM and the IMEI numbers is MTKDroidTools.
After this step, I tried unlocking my bootloader. But it was very stubborn (I was using the latest firmware from Huawei, B119) and I tried doing this with fastboot. Which failed every single time and gave a 0x7000 error when I tried to unlock the bootloader. But I have to say that my bootloader was acting weird from the start anyway. Whenever I used the command:
Code:
fastboot oem device-info
It always showed that the bootloader was unlocked, eventhough after I locked it using the command:
Code:
fastboot oem lock
Which is weird. So I will just include a tutorial on how to unlock the bootloader just in case yours works normal.
So, after realising that my bootloader was not working correctly, and I could not install any recovery mod like CWM or TWRP (or any custom ROM for that matter), I found out that I needed to flash to the chip directly. This was also a huge challange, since i've never done this before and I actually did not know what I was doing. I've changed ROMS on phones a couple of times before, but that always was with a unlocked bootloader and so via the "normal" recovery system way.
For this part, I used XDA user: jacktackles' post a lot. He had some handy information about flashing to the chipset immediately and on what files to use. Since my B119 firmware was locked, I first wanted firmware with an unlocked bootloader. So I flashed some Chinese G750 firmware, that changed my device from a G750-U10 to a G750-T00. The flashing process was not flawless at all, and was the part that took me the most time (10+ hours). This all because I forgot to untick 1 simple box... Oh well, I guess that is how it works (at least I got it to work ). So, after flashing this Chinese firmware, the hardest part was done. And I had access to TWRP Recovery. With this I installed the custom ROM that I wanted, and that is where my adventure ended.
So, to summarize: It is not easy, and not beginner friendly. That is why I wanted to make this post: To make it easier for you guys to do the same and get to catch YOUR Pokémon! (Or just to upgrade to 4.4.2). So let's now go to the tutorial part!
Tutorial part
I did this with a Windows 10 64-bit computer, although I would recommend using Windows 7. You will also need a usb-cable to connect your phone to your computer. Make sure that everytime you install a new ROM that you re-enable USB-debugging. You do this by going to your phone options > About Phone > Click "build number" 7 times > Go back to options > Developers options and tick the USB-Debugging tickbox.
Sorry for not uploading screenshots, but XDA prevents me from using any outside links because I'm a new user (so i'll try to be as precise as possible). This means that also any downloadable files should be retrieved from jacktackles' post (again big thanks to him!). His forum post can be found here: http://forum.xda-developers.com/android/general/huawei-g750-u10-honor-3x-kitkat-4-4-2-t3038166.
So, go to his post and download the VCOM drivers, MKT Droid Tools, B113 4.2.2 base with unlocked bootloader, Root Genius, and this ROM from another XDA-Developer: http://forum.xda-developers.com/showthread.php?p=62356379#post62356379 (Thanks a lot mate! Awesome upload). The Gaaps link is not needed with my method, and the last link is down. So you will need to get a replacement ROM for that. I used one from NeedRom. Just go to their site, and search for G750-U10 and download a ROM that you want (which is Android 4.4.2 of course). Or download another rom from any other site. The one I used is called: G750-U10 KitKat which was listed on the site on: 07/22/2015 11:35 pm. But you can also choose to download another ROM.
So to sum up, we got 3 ROMS:
1. The Chinese Firmware downgrade to B113
(FILENAME: G750-U10 V100R001C00B113CUSTC432D001_Firmware_Slovakia_Austria_Lithuania_Czech Republic_Latvia_Estonia_Greece_05021NHU)
2. The ROM from pavel22 to change the device to G750-T00
(FILENAME: G750-T00_mod8_265_FlashTool)
3. The ROM that we finally are after
(FILENAME: Huawei G750 U10 Kit Kat 4.9.16)
(In my case of course, not if you downloaded another "final" ROM)
Okay, so after all the files are downloaded and extracted (except for the 3rd ROM), we can start!
1. Rooting
This step is very simple and quick. Plug in your phone to your PC and open Root Genius. Click the big button and your phone should be rooted. If it gives an error, just try again and again until it works. After this restart your phone, and a new app "RootKing" should be installed. If not, the phone is not rooted.
2. MTK Droid Tools (backing up NVRam & IMEI)
Extract MTK Droid Tools from it's ZIP file, and place it in a folder. Now extract the VCOM drivers and install them. These drivers make MTK Droid Tools recognize your device. After installing the drivers, open up the .exe file from MTK and make sure it recognizes your device. If it does not, reboot your PC and try again. After your device is recognized, install the "adbd insecure" app on your device, from the playstore (or download it somewhere else if you do not want to pay). But trust me, it is worth the money. Once adbd is installed, tick both boxes on the app, so that we can connect to your phone with MTK. If done correctly, MTK Droid Tools should now be able to get full access to your device, and a green box will appear in the left bottom of the program.
Now, backup your NVRam and IMEI. You do this by clicking on the "IMEI/NVRAM" button, and clicking backup. To be safe and for ease of access, write down your IMEI's on a paper or notepad file. Now the real fun starts!
2.5 Unlocking the bootloader (you might not have to do this)
Only do this step if you get a BROM error with code 6045 when trying to flash any roms. Here is how you unlock the bootloader:
1. Install ADB drivers. I used a tool made by XDA user Snoop05 (http://forum.xda-developers.com/showthread.php?p=48915118)
2. Connect your device to your pc
3. Open up a command promt from windows
4. type "adb" and check if it returns a big list of available commands (that you know for sure that adb is installed)
5. Type "fastboot" and check if it returns a big list, for the same reason
6. Now type "adb devices" and check if it gives your device, if not make sure you have correct usb drivers installed for the G750-U10, if not just install HiSuite from Huawei (It comes with the correct drivers), then disconnect your device and type "adb devices" again.
7. Now type "adb reboot-bootloader" and your phone will restart in fastboot mode.
8. Type "fastboot oem unlock" and follow the instructions on your phone screen (they are very small and hard to read).
3. Flashing the Chinese Firmware
In the Chinese firmware folder, there will be 4 sub-folders: SD_Upgrade, Update Tool, USB_DRV, USB_Upgrade.
0. Delete the SD_Upgrade folder (Not needed).
1. Go to USB_DRV and install the .exe file in the: "Driver For servers 2012-11-27" rar file.
2. After this open the Update Tool folder and extract files.
3. Open the flash_tool.exe file, which is used to flash the device (like the name suggests )
4. Once the program is open, click on the "scatter-loading" button. Search for the USB_Upgrade folder, and select the MT6592_Android_scatter.txt file.
5. Turn off your device, remove the battery, wait a few seconds and reinsert the battery back into the device. Do NOT turn on the device.
6. Make sure SP_Flash_Tool is set to "Download only" (can be set by the dropdown box)
7. Click the "Download" button, and connect your device to your PC.
8. Wait, and the progress bar will fill up. DO NOT DISCONNECT YOUR DEVICE OR YOU COULD BRICK IT!
9. Success? Great! Restart the phone and progress to the next step!
10. Failure? Untick the Preloader partition and repeat from step 5. Still not working? Also untick USRDATA and try again.
4. Flashing the: "G750-U10 to G750-T00" Firmware
This will be almost the same as part 3.
Extract the "G750-T00_mod8_265_FlashTool" rar file, and:
3. Open the flash_tool.exe file, which is used to flash the device (like the name suggests )
4. Once the program is open, click on the "scatter-loading" button. Search for the USB_Upgrade folder, and select the MT6592_Android_scatter.txt file (make sure that you select the scatter file from the new rar file, and that you are not using the same one as before).
5. Turn off your device, remove the battery, wait a few seconds and reinsert the battery back into the device. Do NOT turn on the device.
6. Make sure SP_Flash_Tool is set to "Download only" (can be set by the dropdown box)
7. Click the "Download" button, and connect your device to your PC.
8. Wait, and the progress bar will fill up. DO NOT DISCONNECT YOUR DEVICE OR YOU COULD BRICK IT!
9. Success? Great! Restart the phone and progress to the next step!
10. Failure? Untick the Preloader partition and repeat from step 5. Still not working? Also untick USRDATA and try again.
5. Restoring your NVRam and IMEI
You might need to root your device again, check if need be, by searching for an app called SuperSU or RootKing. If they are not present, root the device again with Root Genius.
You will need to re-install the "adbd" app on your new ROM. If there is no Play Store present, search for a Play Store APK on Google. Once, installed check the 2 tickboxes and re-open MTK Droid Tools.
Click on the "IMEI/NVRAM" button restore your backed-up NVRAM and retype you IMEI codes. Once the restores are done, restart the phone and check if you can call someone. If it works, good job! You can now progress to the very last step! If not, check if you entered the IMEI correct. You probably made a Typo.
6. Installing final ROM
Now that you have installed pavel22's ROM, you have access to a recovery system. So copy the whole 3rd zip file to the root folder of you device. Turn off your device, and turn it on again but this time while holding both volume buttons and the power button until TWRP opens. Click on install, search your zip file and swipe right. When it finishes, do a factory reset from TWRP and then reboot the system normally. You should now have a fully working G750-U10 with Android 4.4.2. Congratulations!
This was my tutorial and personal experience with converting my G750-U10 to Android 4.4.2. It has been a wild ride, and i've reached points that I wanted to throw my device against the wall. I'm now very happy with my (feeling like) new device. I can now finally catch 'em all and become the best PokéMaster ever!
~ NeusAap.
Click to expand...
Click to collapse
I can't download the KitKat rom from needrom.is there any other link?????
Hi mates! I'm stuck in the bootloader unlock step; it keeps showing the 0x7000 error and it doesn't let me flash anything with the SP Flash Tool (guess it's because of the 0x7000 error). I tried to follow the Pavel22 guide posted up there... i can flash the rework-secro succesfully, but i get the 4008 error when flashing the whole rom. Can someone help me? Thanks!!

[Root] lenovo k4 note running on marshmallow (6.0) official rom

This procedure has been tested on LENOVO K4 NOTE MARSHMALLOW (S219) and it worked perfectly fine.
i posted this thread since the previous procedures only covers rooting prior to S218.
verified working on s219
DISCLAIMER:
I JUST FOLLOWED THE PROCEDURE PROVIDED BY "AYAN CHOUDHURY" ON YOUTUBE CHANNEL SO CREDIT GOES TO HIM.
IF SO HAPPENED THE PROCEDURE WAS MADE BY ANOTHER DEV AND WASN'T QUOTED PROPERLY BY MR. AYAN COUDHURY. MY APOLOGIES AND GIVE CREDIT TO THE ORIGINAL OWNER OF THE PROCEDURE
I WON'T BE RESPONSIBLE FOR ANY DAMAGE, SOFT BRICK, HARD BRICK, AND OTHER INSTANCES FOR YOUR DEVICES AS IT WORKED PERFECTLY FOR ME 3-4X BEFORE POSTING THIS THREAD.
original vid: https://www.youtube.com/watch?v=fPx8QWnYLNo
Before we start:
Here is the details of my handset
Model: Lenovo K4 note (PH) [MTK MT6753 8CORE 1.3GHZ 3.00GB RAM]
Model #: A7010a48
OSv: marshmallow 6.0
Android security patch level: April 1, 2016
Kernel ver: 3.18.19+ [email protected] #1, su jun12 18:27:10 CST 2016
Build number: A7010a48_S218_160612_ROW
Step 1:
download all necessary files.
all files and links are not mine and credit goes to the owner of the files
adb tools : https://drive.google.com/open?id=0B16daNyhWTx1djhqSkJ6QkFKaUk...
recovery(i.e TWRP) : https://drive.google.com/open?id=0B16daNyhWTx1RlB0U01sUkVHMjg...
aroma file manager: https://drive.google.com/open?id=0B16daNyhWTx1TmJqRmxIUUI3YUU...
Super Su : https://drive.google.com/open?id=0B16daNyhWTx1V2ZobTI0RVpKQ1E...
xposed installer : https://drive.google.com/open?id=0B16daNyhWTx1N2RDc2Y4TzlWaWM...
xposed framework : https://drive.google.com/open?id=0B16daNyhWTx1QmlRTHhXOUMydDQ...
step 2:
a. back up any necessary files from your handset.
b. since some computers doesn't show your lenovo k4 note while on recovery mode, it is imperative to put aroma file manager and supersu on your sd card. "do not extract. just copy them as it is"
take note that the next step will definitely hard reset your device.
step 3:
a. enable developer option on your handset. go to system settings/about and click build 7x or as it says "you are now a developer"
b. go to developer option do this two things
enable oem unlock
allow usb debugging
c. once you are done please connect your device to your laptop
step 4:
a. run adb server (go to adb folder, shift+right mouse click and choose open command window here.
b. it will prompt you to allow your pc to connect/control your devices just click YES
c. on your command window, type ADB DEVICES (it will detect your lenovo k4 note)
d. once detected type ADB REBOOT-BOOTLOADER (your device will reboot)
e. once rebooted, type FASTBOOT DEVICES to verify if you are already in fastboot mode
f. if connected proceed to step 5. if not please repeat procedure
step 5:
a. once connected go to adb folder on your computer. you will see a file named unlock recovery.bat
if not, copy this text
call adb.exe devices
call adb.exe reboot bootloader
call fastboot.exe getvar all
call fastboot.exe oem unlock
call fastboot.exe format userdata
call fastboot.exe erase recovery
call fastboot.exe flash recovery recovery/recovery.by.gursewak.img
call fastboot.exe getvar all
call fastboot.exe reboot
echo done successful please press any key to continue
echo disconnect your phone and press power button untill phone reboots
pause
Click to expand...
Click to collapse
to notepad and save as batch file, name it as UNLOCK_RECOVERY.bat
b. click the UNLOCK_RECOVERY.BAT then it will ask you on your device to confirm, (will add screen shot later on) just press volume up button
c. once the process has been done, (will take few seconds) extract recovery.img to adb folder
d. go to your previously opened command window and type
FASTBOOT FLASH RECOVERY RECOVERY.IMG (the one you extracted)
step 6:
a. once flashed, disconnect your device (it will show a tiny text telling you transmission ok)
b. press and hold the power button for few seconds to turn off the device
IT IS IMPERATIVE THAT YOU WON'T TURN ON THE DEVICE UNLESS THE NEXT STEPS ARE DONE. IF YOU ACCIDENTALLY TURNED ON YOUR DEVICE REPEAT TO STEP 1.
c. press and hold vol up+vol down+ powerbutton simultaneously for few seconds, once you felt a vibration, release power button whilst still holding the vol up and down button
it will show the lenovo screen then go black. (don't worry it means you successfully flashed recovery.img)
d. connect the device to your computer
if lenovo shows on your device, now is the time to recopy aroma file manager and supersu. if not just wait for the screen to turn back on.
e. once twrp recovery is on, go to mount and check SYSTEM. (do not touch anything aside what i unstructed)
d. go back to previous menu and go to install
install aroma file manager and wait for it to finish
f. once installed it will go directly to aroma file manager, go to system folder and scroll down. look for recovery-from-boot.p and delet it
g. once deleted exit aroma file manager (button can be found on right corner)
h. go back and install beta supersu which you copied. (browse sd card)
i. once flashed, reboot system,
step 7:
a. if you made it this far, then you are almost done.
b. just finish the lenovo start up.
c. once done, connect your device again on your computer and copy xposed apk and xposed arm to internal or sdcard
d. install xposed apk
e. turn off your device
step8:
a. reboot to recovery (press vol up and down and power button simultaneously, once you felt a vibration release power button whilst holding vol up and down button. lenovo screen will show and it will eventually go to twrp recovery)
b. click install and install xposed arm
c. onced install. reboot system.
THERE YOU GO... YOU ARE DONE. YOU CAN VERIFY ROOT BY DOWNLOADING ROOT CHECKER FROM GOOGLE PLAY STORE.
WELL I WAS FORCED TO ROOT MY K4 NOTE JUST TO PLAY POKEMON GO.
I WILL UPLOAD SCREEN SHOT ONCE I ALREADY COMPILED THEM. THANK YOU
IF YOU LIKE AND HELPED YOU A LOT PLEASE HIT THANKS AND LEAVE A MSG.
IF YOU HAVE QUESTIONS, JUST COMMENT IT HERE.
Thanks it worked. I was about to complain when twrp recovery does not show up. BUT IT WORKED THANKS
xposed isn't necessary to root the phone. Am I right? Maybe you should explain that in the OP. You'll get people confused down the road if they don't already know what they're flashing.
Sent from my f320 using XDA Labs
Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?
infected_162k said:
Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?
Click to expand...
Click to collapse
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:
infected_162k said:
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:
Click to expand...
Click to collapse
hi
will it erase internal phone memory (i mean after flushing ROM can i get my data using any recovery software)
i am also using same s219 Rom model lenovo k4 note phone.
Actually i deleted some files unexpectedly from internal memory but i want them back, so i tried many ways but no software is identifying internal memory as a drive. I tried to root using root apps but marshmallow not allowing.
i found this topic, but i have only doubt is after flushing the rom can i recover my data using any recovery software?
Thanks in advance
thank you so much!
now to answer some queries and give thanks...
@Duffy144: glad you like it.
@Bdwilk: thank you for the input, i will do that.
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
@anvesh.k yes it will delete all files as the procedure requires you to factory reset your handset.
Rooted K4 Marshmallow
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.
Can someone confirm if this works with 2 gb / 32 variant?
RK_D2502 said:
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.
Click to expand...
Click to collapse
Can you recovered old data after rooting the device?
anzei19 said:
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
Click to expand...
Click to collapse
Amm, about that memory leak thing, i basically know what that is cause it was a huge problem in my father's phone(gionee m3). But i exactly don't know how to know if it's still there or not as I use messenger hardly 2-3 times a week. guide me about this so I can tell you exactly.
Another thing that will help other users: I have to factory reset my phone due to a google error ( unable to communicate with Google server). I was not sure about root and xposed will be gone or not. But here is the result : lost both, root and xposed. Just flashed both again, super su and xposed framwork, worked
anvesh.k said:
Can you recovered old data after rooting the device?
Click to expand...
Click to collapse
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Sir Ansei, everything is fine except 1 minor issue, when rebooting to TWRP, I often get the black screen. Power cycling the phone works. Any ideas?
RK_D2502 said:
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Click to expand...
Click to collapse
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...
infected_162k said:
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...
Click to expand...
Click to collapse
Thanks for understanding my problem
call fastboot.exe flash recovery recovery/recovery.by.gursewak.img - needs to be edited? make sure path is correct and image name.
call fastboot.exe flash recovery recovery.img
Just put recovery.img in the same folder
I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!
sujitmohanty2012 said:
I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!
Click to expand...
Click to collapse
you should install fastboot driver
setpam25 said:
you should install fastboot driver
Click to expand...
Click to collapse
@setpam25 Is there a specific driver for that.? If yes, could you please share the link to download that?
My system currently has the lenovo usb driver 1.16, windows 10 mtk vcom preloader & ADB interface driver (by google) properly installed!
Does this work on s230 update marshmallow
Please help me,
I am stuck there until I reboot system

Nexus 5 - Enable Usb debugging mode from Fastboot ?

Hi guys,
Sorry to bother you with that but i have an issue with my Nexus 5 and i wanted to have more information about a " solution " i found on the web.
So First, my phone got a problem with the power button (on the motherboard). I managed to find a repair shop doing that kind of repair.
Now's the real problem !
The phone won't go further than the " Google " logo.
I can access Fastboot mode but not recovery mode.
The phone is not root, official stock rom, bootloader locked, usb debugging mode : OFF.
I find something on the web but it seems the guy who write it down skipped some steps. And i'm a total noob at that so i don't understand how he managed to do what he described.
Here's the link :
(Ok so i can't post link since it's my first post.... so i will C/P his method here)
METHOD :
Things you will need
Download the Stock ROM for your device- Just Google it, I am dam sure you can find it.
Download SuperSU from UPDATE-SuperSU-v1.65.zip
UPDATE-SuperSU-V1.65.zip contains :
Superuser boot permission manager.
Update script (important) etc.
Basic Knowledge of C++ or Java
Notepad++
WinRAR
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock rom.
Within the extracted folder you will find system.img well extract it too using Ext4 Unpacker
Also extract the Update-SuperSU.v1.65.zip file.
Now open the folder where you have extracted the system.img files
Grab any .apk file from this folder and change the extension from .apk to .zip
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist)
Also copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder
Located the update-script file within this folder and edit it using Notepad++
You need to update the build.prop file after adding the following line at the bottom
persist.service.adb.enable=1
Next step is updating SQLite Database
Which can be done by adding following code to update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
Cheers! You have Enabled USB Debugging
Now you can install your custom or stock rom using ADB – USB Debugging.
So basically, i wanted to know if the " solution " was possible to achieve or if the guy is plain dope, so i can backup my personal data before doing a factory reset.
Or if there's another way to backup my data.
Ah ! When i plug my phone on my PC, it isn't recognised as a Nexus 5 but as a Android Interface Bootloader (or something like that).
Sorry for the long post !
Hi, I understand what you're trying to do but I think this is not possible. The tutorial you've find on the web seems pointless to me because it just say you to customize some system files of a stock rom downloaded from google repo without saying to flash anything (or maybe this is what I understood).
Anyway I'm sorry but the only solution to this is to unlock the bootloader and flash a new system image, of course if this is a softbrick.
Have you already repair the power button? And how the phone get stucked on the logo image, bootloop or just freezed?
Hi
Thank you for replying !
The power Burton is repaired.
And to answer your question, it just freeze.
The phone turns on, "Google" logo appears and it stays that way, and after waiting a few minutes it automatically reboot and freeze again when "Google" logo shows again
In my opinion this could be a softbrick caused by something, I don't see any way out exept flashing something new. Fastboot doesn't require usb debugging enabled to work properly but unlock the bootloader means wipe all your data.
Probably your recovery has gone o something is corrupted in the system startup sequence.
You could wait for someone that can help you in another way that I don't know I'm sorry.
Well, i think i will wait and continue to search until this weekend.
Anyway ! Thank you for answering me, that was very kind
Was there anything that could have been the cause if the bootloop? Have you tried wiping /cache & /data from the recovery? If not try booting into stock recovery and preforming a factory reset. Google: "how to open nexus 5 stock recovery" android.gs has good instructions on booting into recovery. After following those instructions navigate to factory reset, press the power button, then hold the up volume button. If this doesn't work then you'll have to unlock your bootloader. But I won't get into that now. Good luck.
FYI: Don't bother with the instructions outlined in your post, they don't pertain to your situation.
Also, I can't post links as this was my first time posting here.
Hi SuBAtomicFlux,
Like i said, i can't access stock recovery, when i'm at the step where the Android robot shows a red warning sign, nothing happens when i do the key combo to enter into the Stock Recovery Mode and after a few seconds, the phone reboots by itself.
But thank you for trying to help me !

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any thoughts please?
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.
strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image
who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition

Categories

Resources