Related
So I had an old Nexus 5 running a custom KK rom. I tried getting it back to stock using Wugs Toolkit. I've been playing with it for hours trying to get it to work. I ended up making it worse and it gets stuck on Google Logo now. I tried using the revert to stock option on the toolkit. It looks like everything is working.. Here is the log..
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: hammerhead
finished. total time: 0.001s
Launching flashstock.bat
and then it just stops.. I tried downloaded two seperate .tgz images from Google. They both do the same thing. It doesn't go out of the bootloader screen or anything. It writes the radios and that's about it.
This is a *very* high-level suggestion - there are many tutorials that take you through drivers/ADB, etc. I just want to give you the script I followed for the manual procedure, which turned out to be extremely quick and simple.
After suggesting Wugfresh's NRT to several people in these forums (I'm a very big fan) I decided to refresh my Nexus 6 with the latest image and make it unencrypted - a problem that doesn't exist on the N5. I wasn't sure that NRT would do this for me, since the script automatically restarts the device and I wanted to be sure that it didn't start before I had flashed a modified no-encrypt boot image, since it would just encrypt itself again. So I downloaded the factory image, a no-encrypt boot image (thanks, doitright ) and TWRP - naturally being very careful to get the right ones. I unzipped the TGZ and the image files down to their final *.img components. To make things simple I renamed the various images to one-word names (e.g. radio.img). I put all of them in the same directory as ADB & fastboot.
Since all Nexus devices are updated the same, this should also work for you. Since you've used NRT I'm guessing that you have the PC drivers already installed. You'll also need ADB/Fastboot. Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Some of these may be overkill (I believe the -w wipe command erases userdata anyway), but it worked for me.
I would say take a TWRP image first as well so that you can recover, but it sounds as if you have nothing to recover anyway.
If the more expert member want to suggest amendments to the script, I won't be insulted...
dahawthorne said:
Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
USB debugging means nothing if you're trying to use fastboot.
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
gregs1213, stop using a toolkit, since you don't know what you're doing. read the above link and the following one as well:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
dahawthorne said:
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
Click to expand...
Click to collapse
Hey, sure, I didn't mean to "attack" you. I noticed that you wanted to help. Really. Thanked you for that.
No worries, beekay. Posts don't allways mean what they look like, which is why we have smilies.
And I did read the articles. I tried with my N6 to attach it in bootloader mode with no USB debugging, and you're absolutely right. I suppose I just read "Remember to switch on USB debugging" so often that I assumed it was needed for any sort of work. Thanks for the tip. It's things like this that encourage all of us to try new things - like flashing a ROM manually instead of with NRT...
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
mraramesh said:
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
Click to expand...
Click to collapse
Toolkits don't teach people stuff, they just hide it from them
mraramesh said:
The problem is Wugfresh NRT
Click to expand...
Click to collapse
I edited your post to show you the error of your ways
Sent from my Xperia z5 using Tapatalk
While replying to another thread asking for help in installing a ROM, I linked to this, and I notice that the OP never did tell us if he managed to get his device working. Feedback is not only helpful to the forum, it's also polite.
So bump for gregs1213's attention...
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Do a factory reset
Do NOT use toolkits!
My first advice is: Do NOT flash using toolkits! You never know what's exactly going on if you don't do it manually. There are plenty of reasons why to not use them...
Okay, now my second advice: Don't flash cache partitions. Caches are built during boot/runtime. However, as far as I know, a corrupted cache partition can lead to bootloops - so it's better to just wipe them before boot...
I don't know what the toolkit did and what not - but try to follow these steps:
1. Install fastboot and adb
Preferred method is via Android Studio command line tools from official source: http://developer.android.com/sdk/index.html - Scroll down to "Get just the command line tools". You can decide between an installer or just a zip. It's your choice.
2. Boot your phone in bootloader mode and execute these commands one by one...
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp-recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Use the proper files! Extract bootloader and radio from latest Google factory image and download TWRP from twrp.me!
3. Boot your phone into TWRP and choose wipe -> DO NOT SLIDE TO FACTORY RESET -> advanced wipe -> cache + dalvik ticked, rest unticked -> slide to wipe
4. Try to boot...
Not sure if it works - but that's the only thing I can think of right now
EDIT: @GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!
experience7 said:
@GtrCraft That would definitely solve his bootloop, but he wants to keep his data Hopefully he heeds my advice to keep his hands off of toolkits!
Click to expand...
Click to collapse
Then he should do all the ota's instead of flashing the factory image
Sent from my XT1562 using XDA Labs
Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?
experience7 said:
Don't do full-quotes please.
Seriously? His device is rooted and therefore not receiving OTA (over-the-air!) updates. He'd have to catch all of the zips and flash them manually. So why not just use the system.img?
Click to expand...
Click to collapse
Because you have to factory reset the device. That's the downside of being rooted and wanting to update, especially with M
I'm sorry to say that you're terribly wrong. I hope you didn't factory reset your device every single time you did an update just because you're rooted! Actually you can use the flash-all.bat file that's provided with the factory image. Just remove the "-w" flag from the "fastboot update" command. This will stop fastboot from wiping your /data partition.
That's what the OP could use as well - however, for his better understanding I listed the commands separately.
For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Start to finish - 15 minutes, including the rebuilding of the apps. No data loss (because you haven't touched the data/userdata partition).
I don't say that every step is essential (I note the comment from experience7 about cache) - but this works fine for me.
Please feel free to amend or correct...
dahawthorne said:
For what it's worth, this is the script that I've been using since the monthly updates started (copied from another XDA thread which I've forgotten - apologies to the OP of this script).
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash SuperSU
Click to expand...
Click to collapse
Same problem again. I'm trying all 6.x.x versions but same problem. All commands running without error.
In that case all I can suggest is that you bite the bullet and run the flash-all.bat. Back up all your important stuff (photos, etc.) because you'll lose them.
I've seen it suggested often that you should always do a full wipe when upgrading between major versions (e.g. 5 to 6), so maybe this will fix your problem and give you a working phone even if you lose some data and have to set up from scratch.
P.S. Please "Quick reply" - don't repeat the entire previous post. We've all read it; we don't need to read it again.
marios.v said:
Hello, i'm trying to upgrade my rooted nexus 5 from 5.1.1 LMY48I to 6.0.1 MOB30H without losing my data, but at first boot, stops at android logo. I follow this steps with nexus root toolkit:
- Erasing Boot, Cache, Recovery and System.
- Flashing bootloader, radio, cache, boot and system with official .img files from Google developers webpage
- Flashing recovery with TWRP .img
After all these steps, stops on android logo...
Any ideas?
Click to expand...
Click to collapse
Search for a full guide thread. I'm sure you will come out with something.
Sent from my GT-I9505 using XDA-Developers mobile app
"Search for a full guide thread. I'm sure you will come out with something."
Excellent advice. It's amazing that so many experienced senior members with all their years of combined knowledge missed that blindingly obvious idea...
Problem solved by unfreezing all frozen apps from Titanium Backup before upgrade.
Thank you!
So I tried to return back to stock with the Factory Images and I keep running into a problem. It won't let me and now I am stuck in a bootloop. I tried the flash-all script provided by Google and it failed after flashing the Bootloader and Radio. I also tried the toolkit located in the Development section and I get the same thing!
Any help would be great. I am used to flashing from command line but now there are so many img. I don't know which is what.
Edit:
I downloaded the new ADB and Fastboot drivers from Google and then I was able to restore my phone with Google's flash-all script.
I have not done it yet, but here is my recommendation. Reboot the phone into bootloader. Check the active slot (a or b). Let's assume a is active. These should get your back to stock.
fastboot flash boot_a boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
If you want it back to a brand new phone (not setup) then add the below as well.
fastboot flash userdata userdata.img
Make sure your adb drivers are up to date. You need sdk version 25. 24 and older has issues with the new partitions.
dbrohrer said:
Make sure your adb drivers are up to date. You need sdk version 25. 24 and older has issues with the new partitions.
Click to expand...
Click to collapse
Yeah, that actually worked for me.
#Prerequisites:
Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img
Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for custom roms, when you need to install GApps.
Magisk: https://github.com/topjohnwu/Magisk/releases/download/v19.0/Magisk-v19.0.zip
Magisk Manager: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.1/MagiskManager-v7.1.1.apk
DM Verity Disabler: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
Unlocked Bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal ADB/Fastboot (Windows only): https://androidfilehost.com/?fid=962187416754459552
Moto USB Drivers (drivers only, no manager): https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
Windows hint:
For all what you want to do with your Motorola phone, you need the above provided Minimal ADB/Fastboot environment.
Download and extract it,
Move the files you want to flash into the folder
Open CMD (Windows Key and R - then type cmd) and navigate into the extracted folder.
//It's easier when you type cd into the cmd and drag the folder from your adb/fastboot environment into the cmd window and hit enter.
And that's it. The patched boot image is no longer needed.
Rooting the Moto G6
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
5. Repeat the wiping and reboot another time into recovery.
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
7. Go to Install and flash dm-verity disabler first, then magisk.
Thats it. You're rooted.
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Wait until it finished, disconnect your phone, wait and set it up.
That's it.
Simple and easy.
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
madbat99 said:
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
Click to expand...
Click to collapse
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
And for root not need boot.img file?
cecogor said:
And for root not need boot.img file?
Click to expand...
Click to collapse
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
ThisIsRussia said:
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
Click to expand...
Click to collapse
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
cecogor said:
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
Click to expand...
Click to collapse
Due to OS changes and it's a feature bundle.
It edits DM-Verity, ForceEncrypt and Disk Quota.
Can't get root
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
mward7221 said:
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
Click to expand...
Click to collapse
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
ThisIsRussia said:
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
Click to expand...
Click to collapse
I tried all that and couldn't get it to work, I downloaded everything from your links above but no go. Someone posted a no-verity boot image in another thread. post 598 I believe and I flashed that file, flashed Magisk 18.1 in twrp and now I have root so I'm set, Thanks for your reply
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
Of course on Linux no drivers are needed. But most running Linux don't need instructions. It's usually windows users needing such instructions.
That's the only reason I chimed in.
Carry on.
Nice guide.
ThisIsRussia said:
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Click to expand...
Click to collapse
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
kmssd said:
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Click to expand...
Click to collapse
If you Change major OS Version, you always need a clean Flash and rerooting.
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
I would change official TWRP to Dejello's unofficial TWRP as official one won't install Gapps
https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
Click to expand...
Click to collapse
>> Here is ok,
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
Click to expand...
Click to collapse
>> Here is ok too
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
Click to expand...
Click to collapse
>> Here is ok too, similar to flash my Sony
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
Click to expand...
Click to collapse
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
5. Repeat the wiping and reboot another time into recovery.
Click to expand...
Click to collapse
>> The phone will be need a wipe two wipes? or only one?
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
Click to expand...
Click to collapse
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
7. Go to Install and flash dm-verity disabler first, then magisk.
Click to expand...
Click to collapse
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
brunogroa said:
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
>> Here is ok,
>> Here is ok too
>> Here is ok too, similar to flash my Sony
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
>> The phone will be need a wipe two wipes? or only one?
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
Click to expand...
Click to collapse
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Stuck on Booting screen
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
theseeker2654 said:
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Click to expand...
Click to collapse
Ohh sure... So need twrp to do, I Will trie this, thx a lots, here is the same with pie
Tom Swift said:
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
Click to expand...
Click to collapse
On top of using the disabler download and flash the no verity boot.img from the link below. Works great on my xt1925-6 with pie.
Also, use Magisk 19.0
https://drive.google.com/file/d/1JLMVRBCsMnr7RYxdRFjFLOwVSy8r8hSQ/view
The DM Verity Disabler link not working:
https://zackptg5.com/downloads/Disab...02.04.2019.zip
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.