Update: 2nd post now has a way to update the Moto G7 without erasing user data. Method uses most of this tutorial but now you unzip image and select a file within in the unzipped image. Either way still backup your phone just in case. User MrCamby let me know about the "Lenovo MOTO Smart Assistant" for backup.
Yesterday I updated my US Retail version Moto G7 Power to the newest firmware build# PPO29.114-108 with the May 1st Security update manually. My previous build with the March 1st security update was PPO29.114-63-2. I have the Retail US Model with 3GB of RAM and 32GB of Storage. DO NOT flash the Moto G7 Power international version with 4gb RAM and 64GB storage, it will probably brick it.
This process will delete everything on the phone as it flashes all the phone's partitions. The phone will be as it was when you first bought it having to re-enter your account info and download all your extra apps not included with the stock phone. Please backup everything if you decide to update the phone using this method. On my phone most things were stored on the cloud but I did forget I had some unimportant things on the phones download folder.
Thanks to user MrCamby for letting me know bout the "Lenovo MOTO Smart Assistant" which will backup the phone on your PC (Windows only) before you flash it. I haven't personally used it but from it's .pdf guide it will backup your phone before you flash it preserving images, SMS, Contacts, etc... Link to Lenovo Moto Smart Assistant
https://support.lenovo.com/us/en/downloads/ds101291
The first step is to download Motorola RSDLite6.2.4.zip software used to flash the firmware file.
The software is available at: https://mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
Unzip and Install the RSDLite software and move to step 2.
Step 2 is to download and install the MotorolaDeviceManager_2.5.4.exe Software/Drivers at:
https://mirrors.lolinet.com/software/windows/Motorola/Drivers/
Step 3 is to download the 1.9GB firmware. Be sure the file downloads completely! Flashing an incomplete image could damage the phone. The MD5 checksum is 8bb8f13ec0fe23c977b57c86f2033db9 MD5 Checker attached.
Choose the Firmware dated 2019-06-05 and Named:
XT1955-5_OCEAN_RETUS_9.0_PPO29.114-108_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
With the two pieces of software installed and the firmware downloaded it's time to install the firmware.
Warning this process will completely erase your device and reinstall the new firmware. only attempt this
process if you have a US Retail G7 Power with 3GB RAM and 32GB of storage. Do not interrupt the process
once the flashing has begun or you may have a brick(dead phone). Please continue at your own risk.
1) You'll need a USB C cable and be sure the computer is plugged in to power if a laptop. The phone should have at least a 60% charge.
2) Shut off the phone. Once the phone is completely off, Hold the volume down and press the power button still holding the volume down button.
3) The phone should boot into the boot loader mode, release the power & down volume button. See bootloader.jpg attached to see what screen looks like.
4) Plug the USB C cable into the phone and into a USB 2.0 port(black colored) on your computer. On my computer the phone didn't show up in RSDLite program when plugged into a blue colored USB 3.0 port. Others online reported the same problem.
5) Launch the RSDLite program and click show device. (Figure_1 Picture attached to post)
6) If everything went right you should see your phone listed on line 1. The program doesn't list any specific info just that a device is connected. See Figure_1 Picture attached to post.
7) Click the box on the top and select the firmware image still zipped. (The RSDLite program will unzip the firmware) and then click on the start button. See Figure_2 picture attached to post for box to load firmware and start button.
8) This is your last chance to not ERASE your phone and load the new firmware. After clicking start in last step a menu will pop up with three options. Choose the middle option "Uncompress and Start Flashing" See Figure_3.jpg attched to the post. During the firmware flash DO Not unplug your phone or allow your laptop to sleep. The process took about ten to fifteen minutes. The program will update the files it's flashing i.e. flashing 1 of 32, 2 of 32, etc....
9) When the flashing is done RSDLite will reboot the phone and you'll be prompted to choose your language like a new phone.
Troubleshooting: If line 1 in the RSDLite program is blank after plugging in the phone and doesn't show a device then you'll need to try a different USB port on your computer. For some reason the phone only shows up on my black colored USB 2.0 ports and not my blue colored USB 3.0 ports. Also try a different USB cable if it doesn't show up. These are common issues with the RSDLite program from my research.
Update Moto G7 Power without erasing device.
Follow the steps in the post above but stop at step 6 and start here.
7) Unzip the firmware image you downloaded in a folder you create.
8) Open the RSDLite program and click the box on the top and then select servicefile.xml in the folder you created in step 7.
9) After selecting the servicefile.xml click start and flash your phone. This should not erase your data.
10) Some forums reported it is better to erase the phone per the top posts but no reason was given.
Update Moto G7 Power without using RSDLite.
Since some people have reported trouble getting to RSDLite to work so I decided to do it in a way similar to the way I updated my Pixel using Android Platform Tools.
1) Create a folder where everything will be kept. like a folder called android in C:\ like C:\android
2) Download the Android Platform Tools attached to this post and extract to the folder you created.
3) Download the Phone firmware in top post and UNZIP into the same folder you created with platform tools in it.
4) Download update_batfile.zip attached to this post and unzip into the folder you created with the phone firmware and Android Platform Tools in it.
5) Open a Windows command prompt in Start menu--> windows system or by holding the windows key + R and typing CMD.
6) Plug your phone into the laptop and go to Settings--> System-->Advanced-->Developer Options then toggle "USB debugging" to on. A screen should appear on the phone "Allow USB Debugging" press OK.
7) If you don't have developer options in your System-->advanced go to System--> about and tap the build number 7 times. Now try step 6 again. Developer options should be there.
8) Navigate to the C:\android folder you created or whatever folder you created with all the files in the Command Prompt. Something like cd \android
9) Turn off the phone, Once the phone is off, hold the volume down and then hold the power button. You should boot into the bootloader screen. Release the two buttons.
10) So you should have the phone in bootloader mode, all the files in one folder, have previously selected USB debugging when the phone was booted up, and the command prompt at the folder with all the files in it.
11) now type in the command prompt type either update_no_erase.bat or eraseandupdate.bat Obviously the update_no_erase.bat updates the phone without erasing it and eraseandupdate.bat erases the phone and then updates it. After typing the one of the two .bat filenames press enter and the .bat file will update the phone and then reboot it.
12) Good luck!
Man I was wondering why nobody was updated yet since that firmware has been available for a while.. I flashed it about last week or less all good..
Man I forgot about RDS Lite damn it.. . I flashed it manually and was PITA since it has Patition A and B and a few times I messed up the commands and installed parts of partition B on partition A since everything installs by default to Partition A unless you specify System_b because I forgot to specify the partition..
T
I weird thing about this May 1 lst Firmware and the one before after unlocking bootloader, in system updates it stated that my device is compromised so no more Ota but today out of nowhere that message changed back to normal System Up to date. So weird I did nothing at all.
I knew there had to be a way a way to find that updated firmware. I just been too distracted having fun with a rooted phone finally to research it yet (my last 2 phones were sm-j727t-1's and before that some kyocera pos... I make bad decisions lol). so i take it we will have to reroot our devices after this as well...? we should be able to get all our other stuff back nearly identical using titanium with cloud storage though right? just slightly more of a headache than twrp...
You will definitely have to Re-Root the phone as this flashes all the partitions like it was when new. You may have to Unlock the bootloader again but I'm not sure about that. The bootloader may stay unlocked because that's a deeper setting I believe. With my Pixel 2 I would always have to Re-Root whenever I updated but that wasn't to difficult. If you do update report back on if the bootloader stayed unlock or not. You should be able to still unlock the bootloader again if it did lock, but again I don't think it will lock. You will be able to get everything back that's cloud based as you sign in with your google account. It will take a little time to reinstall some apps and change a few settings depending on how your phone is set up. I couldn't get the May 1st Security / phone fixes from system update so I went this route.
thaessential said:
I knew there had to be a way a way to find that updated firmware. I just been too distracted having fun with a rooted phone finally to research it yet (my last 2 phones were sm-j727t-1's and before that some kyocera pos... I make bad decisions lol). so i take it we will have to reroot our devices after this as well...? we should be able to get all our other stuff back nearly identical using titanium with cloud storage though right? just slightly more of a headache than twrp...
Click to expand...
Click to collapse
My PC ports are all 2.0 and RDSLite do not recognize the device. I belive is the other way around (Need 3.0 Ports) because of that.
nucher said:
You will definitely have to Re-Root the phone as this flashes all the partitions like it was when new. You may have to Unlock the bootloader again but I'm not sure about that. The bootloader may stay unlocked because that's a deeper setting I believe. With my Pixel 2 I would always have to Re-Root whenever I updated but that wasn't to difficult. If you do update report back on if the bootloader stayed unlock or not. You should be able to still unlock the bootloader again if it did lock, but again I don't think it will lock. You will be able to get everything back that's cloud based as you sign in with your google account. It will take a little time to reinstall some apps and change a few settings depending on how your phone is set up. I couldn't get the May 1st Security / phone fixes from system update so I went this route.
Click to expand...
Click to collapse
yeah I'm definitely getting it done soon. these unsuccessful update warnings are super annoying. i keep trying to hide more google and moto apps and some other things but nothing seems to have any effect
I know on my Lenovo Thinkpad the USB 3.0 ports would not recognize the phone in RSDLite. I tried switching between 3.0 and 2.0 and it would only show up in the 2.0 ports. Be sure to install the MotorolaDeviceManager_2.5.4.exe listed in the thread and the phone will only be recognized when it's in the bootloader mode (power on holding volume down button). I had trouble initially getting RSDLite to see the phone and in a few forums people reported trying a different USB C cable and using the 2.0 USB ports. For me it was using the 2.0 ports. Getting RSDLite to see the phone can be the most difficult part of the whole operation. Good Luck!
Omar04 said:
My PC ports are all 2.0 and RDSLite do not recognize the device. I belive is the other way around (Need 3.0 Ports) because of that.
Click to expand...
Click to collapse
nucher said:
I know on my Lenovo Thinkpad the USB 3.0 ports would not recognize the phone in RSDLite. I tried switching between 3.0 and 2.0 and it would only show up in the 2.0 ports. Be sure to install the MotorolaDeviceManager_2.5.4.exe listed in the thread and the phone will only be recognized when it's in the bootloader mode (power on holding volume down button). I had trouble initially getting RSDLite to see the phone and in a few forums people reported trying a different USB C cable and using the 2.0 USB ports. For me it was using the 2.0 ports. Getting RSDLite to see the phone can be the most difficult part of the whole operation. Good Luck!
Click to expand...
Click to collapse
Yes I know that. Thanks anyway I been playing this game since Android 2.2 ? In my case are the ports 95% sure about it.
all my ports are also 2.0 and i couldn't get my phone to show up in RSDlite. probably just wait for TWRP at this point
thaessential said:
all my ports are also 2.0 and i couldn't get my phone to show up in RSDlite. probably just wait for TWRP at this point
Click to expand...
Click to collapse
Yeah man I test it in several laptops only being recognized on 3.0 Ports. Because of "USB Type C"
Manually flash the firmware through terminal and fastboot. That will fix the issue!
Rondeau79 said:
Manually flash the firmware through terminal and fastboot. That will fix the issue!
Click to expand...
Click to collapse
I been doing it for years manually no problems. I just wanted to try RSDlite once again has been years I have not use it. Still same issues as always ?
I was aware of the fastboot method but I figured this would be easier for some people who didn't want to install Android Tools Package and deal with the typing or copying fastboot commands in a terminal. Using RSDLite is a simple and foolproof method of updating our phones. I didn't have much trouble getting RSDLite to work but but it seems like others are. Once you have RSDLite working updating your phone would take less than a minute. I plan on updating my phone each time Motorola issues a System update. My phone doesn't receive them in a timely matter because I'm on Verizon who tends to postpone System updates.
Omar04 said:
I been doing it for years manually no problems. I just wanted to try RSDlite once again has been years I have not use it. Still same issues as always
Click to expand...
Click to collapse
FYI: Before you flash the update, you can use the Lenovo assistant to do a backup of your phone. Then you can restore from backup after the firmware flash.
Sent from my moto g(7) power using Tapatalk
Good to know. I'm new to the Motorola / Lenovo ecosystem. I've had Nexus and Pixels for the last 4 years. I'll add a link to the Lenovo Moto Smart Assistant Software in the main thread. Thanks!
MrCamby said:
FYI: Before you flash the update, you can use the Lenovo assistant to do a backup of your phone. Then you can restore from backup after the firmware flash.
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
nucher said:
I was aware of the fastboot method but I figured this would be easier for some people who didn't want to install Android Tools Package and deal with the typing or copying fastboot commands in a terminal. Using RSDLite is a simple and foolproof method of updating our phones. I didn't have much trouble getting RSDLite to work but but it seems like others are. Once you have RSDLite working updating your phone would take less than a minute. I plan on updating my phone each time Motorola issues a System update. My phone doesn't receive them in a timely matter because I'm on Verizon who tends to postpone System updates.
Click to expand...
Click to collapse
Agree with you 100% RDSLite awesome once you have it up and running but a PITA to the power of 10 when not. I usually don't type any command at all I just open notelad write all commands there save as bat and then open cmd in working folder fastboot devices to make sure device is connected and drag and drop the bat to the cmd window hit enter to star and it does all the job automatically. ?
My 2nd post below the top will be a .bat file to use with ADB tools. Basically put the unzipped firmware, .bat file, and the adb tools all in one folder and run the .bat file. I just finished testing it now to type the post up.....
2nd Post is up now....
Omar04 said:
Agree with you 100% RDSLite awesome once you have it up and running but a PITA to the power of 10 when not. I usually don't type any command at all I just open notelad write all commands there save as bat and then open cmd in working folder fastboot devices to make sure device is connected and drag and drop the bat to the cmd window hit enter to star and it does all the job automatically.
Click to expand...
Click to collapse
so i noticed there are also linux and mac versions of rsdlite. i have a linux pc running debian 10. was gonna try stuff out on that and see if i get different results. personally when it comes to stuff like this i would much prefer to use gui software than term. i only have one phone... well that's not quite true... i only have one new phone lol
Related
It seems on various blogs/sites that there is a pretty big number of LT28at owners hoping for an AT&T rom, which isn't going to happen...I just wanted to make a quick thread of EXACTLY how to simply flash an available stock JB rom onto the LT28AT...without any other information, and i can simply link to it when needed.
This isn't a criticism, but almost every thread i've seen on using flashtool, there is mixed or downright false information on how to get it to work properly. I know its not just for an Ion, but many tutorials tell you to do things that are either incorrect, or otherwise not needed.
So...if you simply want JB on an LT28AT w/ locked boot loader...and want to keep LTE, etc...simply do this: (this is specific to 64bit windows 8, but similar for vista or 7...the only difference is what you need to do for a flashtool driver)
All of this goes with the assumption that you can find the required stuff to do the flash. Searches will quickly link you to the downloads you need. This is more for getting flashtool to work for you the first time...one other note, for all the driver installation stuff...by default, the action center in windows 8 will just give a prompt of a driver installing...that disappears when the action is completed (instead of previous windows versions saying 'your device is now ready to use', etc.)...and no other notifications are given...so in this case, if you're not seeing errors or other problems, you're good to go...just don't unplug anything until the little installation icon disappears...
download the latest version of flashtool (newest version being released in mid June iirc).
use the Ion development page on this site and find one of the multiple stock rom threads, then download the Ion JB version of your choice, as well as the latest .111 AT&T ICS (this may not be needed, but more on that later)
After that is downloaded, make sure your phone is on, go into the settings menu...under connectivity disable the check box for installing pc companion with a usb connection...that is a myth...you DO NOT need to install PC companion, and in fact PC companion will interfere with flashtool depending on autoplay settings in windows. Also, make sure the phone is in MTP mode, and you can also allow USB debugging in developer options...but for simply flashing; the latter isn't completely necessary.
with PC companion set to not install when you plug in the USB cable, plug your phone into your computer with it still ON. Windows will prompt you for 2 different driver installs, depending on your windows Action Center settings. This will install the Ion on your PC as a device with both internal storage and the ext. card accessible...as apposed to just the SD card...
After that installs, unplug the phone, and turn it off. With it completely off, do nothing but plug the phone in again. Another driver will be installed. Allow that to finish, unplug the phone again. I'm not positive as to what this driver does, but i've had better luck getting this out of the way before the next part...
With the phone unplugged and off still, hold the volume key DOWN and plug the phone back into the PC...The LED will turn bright green, and keep holding the volume key until it disappears...this will install the critical 'S1 Boot Driver'. Windows takes a good full minute or so to install this one, but just be patient, it should go fine.
Now install Flashtool from the setup.exe downloaded earlier. Keep track of its install directory, and after it finishes installing, locate the firmware folder and move your firmware ftf files into there...remember that you may need to unzip the firmware before moving it over, depending on the download source.
Now the windows 8 specific stuff. Windows 8 will block unsigned driver installation by default. To get around this, head to the start screen, bring up the charms, click on settings...and at the bottom right; click on Change PC Settings. From this screen, move to 'general' on the left, then scroll to the bottom and enable 'advanced start up'...and hit restart now.
after a reboot, you'll be taken to a screen with 3 options:
Continue
Troubleshoot
Turn-off
choose troubleshoot, then:
Refresh your PC
Reset your PC
Advanced Options
choose advanced options, then:
System Restore
System Image Recovery
Automatic Repair
Command Prompt
Windows Startup settings
choose windows startup settings, and click restart
after the reboot, you'll find a screen of options again, and simply choose 'disable driver signature enforcement'
now you're almost done
back in the flashtool folder, find the drivers folder...open it, and run the driver installer...you'll see a screen with 25 or so different drivers...ONLY ONE is necessary for the flashing an Ion with a stock rom...at the bottom of the driver list, find 'flashmode driver'...install it, wait for the prompt that its an unsigned driver, and click allow.
Now every bit of communication software between your Ion and PC is complete. You do not need to install all those random drivers, despite claims that they are needed.
to flash your JB rom, phone unplugged from PC and OFF. hit the lightning icon in flashtool...then click flashmode...from the next screen select the JB firmware from the list...set flashtool to wipe everything, and exclude nothing, and leave no final verification checked...this is generally regarded as the best way to flash to a totally new firmware version, limiting bugs, etc...then click flash...wait for the files to be prepared by flashtool...
then follow the on screen prompt, but hold volume down while plugging it in...not 'back'; the screen shows some Xperia phone thats 4 years old or something...
Depending on your area, and the JB version you're flashing...you may need to go back through and flash just the baseband from the att ICS you also downloaded...I didn't have to do this, i still have LTE, i just had to set LTE to 'preferred' in the mobile network settings...you also may need to manually enter the APN settings for att, also...I usually had to do this with international ICS firmwares, but it auto-downloaded perfectly with JB...
Sorry for the length, but I'm sure many guys have run into flashtool fighting back pretty hard...and simply not cooperating...if you install everything in the exact order i listed, you should have no problem...it took me installing this on 5 different machines to finally get it to where it works the first time, every time...PC companion seems to be the biggest variable with this...with that running, it'll very often interrupt flashtool and not let the flash kick off properly...
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Dulu93 said:
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Click to expand...
Click to collapse
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
k0rax said:
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
Click to expand...
Click to collapse
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i dont think so.. tried a few different cables
Dulu93 said:
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Click to expand...
Click to collapse
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
k0rax said:
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
Click to expand...
Click to collapse
i can only find die x.15 version but i think it should be enough. the problem is that ze2 is not reacting to pc commands when in bootloader.. so i can not operate in with fastboot commands and asus flash tool requires fastboot mode
maybe my last option is to flash my phone via intel phone flash tool which operates via the soc. but i dont have the necessary files. as i remember i would need some flash.xml and image
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Dulu93 said:
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Click to expand...
Click to collapse
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
k0rax said:
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
Click to expand...
Click to collapse
This did:
Make sure you go to settings-->apps-->default apps and select the dialer as your default application to make calls.
k0rax said:
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Click to expand...
Click to collapse
thank you very much for your help.
the first point chaning it to 4 zeros did the trick. i was able to reinstall the bootloader.
but i still dont have connectivity via fastboot. im sure all drivers are installed and even on linux i cant see my phone. what is that special google driver?
k0rax said:
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Click to expand...
Click to collapse
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Dulu93 said:
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Click to expand...
Click to collapse
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
k0rax said:
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
Click to expand...
Click to collapse
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
k0rax said:
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
Click to expand...
Click to collapse
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
You can leave flash tool and xfstk open same time. I flashed with xfstk, waited some time and moves between the bootloader options. Make sure no residual adb or fastboot exes are running. Then unplug the phone and plug it back in. Then it will show up. Select the option you have and click start. See if the bootloader shows any life or incoming partitioning happening . If that doesn't work reboot to bootloader scroll around in it to make sure it's loaded , it brings in the correct serial intermittently. But I don't think it's necessary.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
So xfstk reboots
Xfstk round two no reboot scroll around
AFT
Unplug USB from phone and reconnect
Should show up .
Then click start. Did it give an error with that X?
Look at processes and see if it's launched adb or fastboot
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
I think you're close - it's flashing what's needed, and recognized the phone, although it did for me also but fastboot didn't work until the drivers with adb and fastboot. The last things I would think is reinstall the Google adb fastboot drivers with the phone connected to the USB port that got you this far, and if there is some serial no verification, look for .14 version of AFT.
As the title says, I am stuck here. I CANNOT get ADB to detect my M9 after I type fastboot reboot bootloader or fastboot reboot download...not sure which one I am even supposed to use though tbh, as I cannot find a even half decent guide for this device...I found the download one on the normal M9 page and the bootloader command on TWRP's page for this device. Not that it matters, as neither works as my device isn't detected and they both hand on 'waiting for device'. I have uninstalled and reinstalled about every damned usb driver I can find, manually installed them, used installers, different cables, different usb ports. rebooted my phone and my PC over and over, etc. I am about to pull my damned hair out here lol.
Anyone have any experience with this or a link to a guide for this specific piece of locked down peice of crap?
Welp...after 7 hours of fiddling...it randomly worked. I did literally nothing. Just tried adb reboot download again. And it rebooted and accepted the flash...I suspect there was a weird driver installation issue with windows 10...but I'll probably never know.
I know this is fixed but this post is simply an FYI for others that may have trouble.
I've had trouble instelling TWRP. It would randomly give: the command is not recognized or some sort error message.
*****Before beginning, find your device's firmware number by booting to Download mode. You can do this by restarting your phone and before it begins to reboot, hold the volume down button. Once in the black screen, look for something that says Firmware or "3.37.305.7" The last 4 digits will be different depending on your country and device carrier. This firmware info specifically will tell you which version of TWRP you need to download and which version of SuperSU you'll need. Example, I run a US Verizon phone so I needed TWRP 3.0 or above and SuperSu 2.64 (not anything higher than that). Using the wrong TWRP and/or SuperSU caused my phone to brick to a white screen with red lettering. To fix it, I had to reflash back to stock and then try again. (unfortunately, which combination of the two you'll need is something you'll have to search for as I don't have an exhaustive list. But I highly recommend you verify before flashing the recovery)***********
For me I fixed it by:
- Ensure USB Debugging is enabled on the phone,
- re-downloading the HTC M9 drivers,
- Downloading Android Studio Bundle 145.3
- Searching my computer for "ADB.exe" and found it in "C:\Users\7\AppData\Local\Android\sdk\platform-tools" Your location may be different as I'm running Win 7. They key is that you have to find the exact folder where adb.exe is located and move your TWRP recovery file there.
That's the only way I was able to get TWRP to flash to my phone.
inorite said:
I know this is fixed but this post is simply an FYI for others that may have trouble.
I've had trouble instelling TWRP. It would randomly give: the command is not recognized or some sort error message.
*****Before beginning, find your device's firmware number by booting to Download mode. You can do this by restarting your phone and before it begins to reboot, hold the volume down button. Once in the black screen, look for something that says Firmware or "3.37.305.7" The last 4 digits will be different depending on your country and device carrier. This firmware info specifically will tell you which version of TWRP you need to download and which version of SuperSU you'll need. Example, I run a US Verizon phone so I needed TWRP 3.0 or above and SuperSu 2.64 (not anything higher than that). Using the wrong TWRP and/or SuperSU caused my phone to brick to a white screen with red lettering. To fix it, I had to reflash back to stock and then try again. (unfortunately, which combination of the two you'll need is something you'll have to search for as I don't have an exhaustive list. But I highly recommend you verify before flashing the recovery)***********
For me I fixed it by:
- Ensure USB Debugging is enabled on the phone,
- re-downloading the HTC M9 drivers,
- Downloading Android Studio Bundle 145.3
- Searching my computer for "ADB.exe" and found it in "C:\Users\7\AppData\Local\Android\sdk\platform-tools" Your location may be different as I'm running Win 7. They key is that you have to find the exact folder where adb.exe is located and move your TWRP recovery file there.
That's the only way I was able to get TWRP to flash to my phone.
Click to expand...
Click to collapse
Hi! I'm looking for ways to unlock the bootloader of my verizon's M9. Have been searching here but yet to find any success. Seeing your comment here, i thought you might be able to direct me to a useful thread. Thanks.
Hi!
Because I wanted more privacy and security online I decided to buy a second hand Pixel 3 XL and want to install graphene OS. I've been trying for days now to make it work but I just cant get it to work and it's very frustrating:crying: so can someone please help me out??
I've been trying to install it on a windows pc and on a linux pc.
I'm not new to computers but I'm new to installing custom roms and new to linux.
This is what i'm following for installing it in windows:
Flashing GrapheneOS in Windows 10
Install or update the Android SDK Platform Tools:
Download and unpack the Standalone Android SDK Platform-Tools package: https://developer.android.com/studio/releases/platform-tools
Add a PATH Environment Variable to the unpacked folder (Windows 10: Control Panel > Advanced System Settings > Environment Variables)
Make sure that there are no other versions of Android SDK Platform Tools in your computer. Old versions will result to failures in image flashing.
Install or update the Google USB Device Driver:
Download the Google USB Device driver: https://developer.android.com/studio/run/win-usb
Open Windows OS Device Manager and find the new device that shows up when you plug in your phone
Update device driver (Windows 10: Device Manager > Universal Serial Bus devices > [Device Name] > Update driver) using the Google USB Device driver
Prepare the system image:
Download the factory system image that is appropriate for the device:
Important: Always use factory system images for installations. OTA system images are intended only for updates: https://grapheneos.org/releases
If possible, verify the system image integrity
Verify checksum
Check signature
Flash the system image into the device:
Notes:
First make sure that the stock system image is updated to the latest release to avoid any problems.
There is no need to turn on USB Debugging in Developer Options to flash a system image (even when sideloading with ADB in Recovery Mode.)
Enable OEM unlocking in Developer Options (Important: This requires internet access on devices with Google Play Services as part of Factory Reset Protection (FRP) for anti-theft protection.)
Unlock the bootloader:
Put the device in Fastboot Mode (Turn off the device then press and hold the Power and Volume Down Buttons at the same time until you see the Fastboot Mode Screen)
Connect to the computer and verify the connection: "fastboot devices"
Unlock the bootloader: "fastboot flashing unlock" (use the Volume then the Power buttons to confirm)
The device performs a factory reset then boots back to Fastboot Mode
Install the system image:
Open a Command window, go to the unpacked system image folder and run the flash-all.bat script
During the update, the device will reboot to fastbootd. Do not do anything and let the update continue
After it is done, choose option 'Reboot to bootloader' from the fastbootd menu to go back to Fastboot Mode
Re-lock the bootloader:
Lock the bootloader: "fastboot flashing lock" (use the Volume then the Power buttons to confirm)
The device performs a factory reset then boots back to Fastboot Mode
Complete the device configuration
Unplug the device from the computer and choose option 'Start' in Fastboot Mode to load the device OS
Perform device configuration
Click to expand...
Click to collapse
So the issues i'm facing are:
When I'm Trying to install using windows I can't get windows to recognize my phone.
I've installed platform tools but when i want to verify the fastboot connection it keeps saying waiting for device.
I've tried updating the driver many different times in many different ways but cant resolve the issue.
on a linux pc i'm following the manual from the website:
https://grapheneos.org/install
I downloaded platformtools but I cant set the PATH to update the version. and use the new version.
is there another way to install it? Or can someone guide me step by step exactly what to do?
thanks in advance!
Not sure if this will help any but perhaps try new a cable or a different USB port. I've read sometimes USB 2.1 works but USB 3.0 doesn't or vice versa.
Sent from my Pixel 3 XL
Eudeferrer said:
Not sure if this will help any but perhaps try new a cable or a different USB port. I've read sometimes USB 2.1 works but USB 3.0 doesn't or vice versa.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Thanks for your reply,
I got it to work! I misread one step, I connected the cable and instead of staying in fastboot mode (on the fastbootmode screen) I pressed start (power button) and proceeded to starting the OS. I thought that this was how it operated but now I understand how it works
i'm not really helping here but what is so good about GrapheneOS vs stock? i have never heard of them
masri1987 said:
i'm not really helping here but what is so good about GrapheneOS vs stock? i have never heard of them
Click to expand...
Click to collapse
Look at the GrapheneOS website and you'll find the answer.
In a nutshell: No Gapps or Play Services and securized kernel plus some other under-the-hood security improvements.
Only thing which i miss per default is the root access so i'm using it without AVB.
JaniceJop5843 said:
Hi!
Because I wanted more privacy and security online I decided to buy a second hand Pixel 3 XL and want to install graphene OS. I've been trying for days now to make it work but I just cant get it to work and it's very frustrating:crying: so can someone please help me out??
I've been trying to install it on a windows pc and on a linux pc.
I'm not new to computers but I'm new to installing custom roms and new to linux.
This is what i'm following for installing it in windows:
So the issues i'm facing are:
When I'm Trying to install using windows I can't get windows to recognize my phone.
I've installed platform tools but when i want to verify the fastboot connection it keeps saying waiting for device.
I've tried updating the driver many different times in many different ways but cant resolve the issue.
on a linux pc i'm following the manual from the website:
https://grapheneos.org/install
I downloaded platformtools but I cant set the PATH to update the version. and use the new version.
is there another way to install it? Or can someone guide me step by step exactly what to do?
thanks in advance!
Click to expand...
Click to collapse
Well... I'm not sure if you got your problem solved; however, now that the Pixel 3 no longer receives security updates, Graphene will no longer support their OS for your phone...
So, you can go with Lineage OS or do what I did and utilize Calyx OS.
I've had no issues thus far ..
does anyone have a graphene os build files for pixel 3xl? I want to return to stock and i must have deleted build. Thank you