Related
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Hamal said:
Dear gurus of Android,
If possible I would like some help with my Galaxy Nexus since I think it is software bricked. When started it states the the phone is encrypted and wait for the key. I have read all I could get my hands on about this problem. No success so far, so I was hoping someone knowledgeable is willing to sacrifice some of his/her time to help me out.
Thanks in advance.
Click to expand...
Click to collapse
did you read this http://forum.xda-developers.com/showthread.php?t=1730463
Thanks for the quick response. Yes I did read the thread. It was one of the first things I tried. I lock/unlock the boot loader successfully. However when I start the phone in normal mode I get the same message, seems like nothing changed.
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Hamal said:
So no ideas ei. Seems Will be throwing away a perfectly functioning (hardware wise) Galaxy Nexus away. Shame since my other phone just died.
Anyway thanks for the effort.
Click to expand...
Click to collapse
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
razi914 said:
Did you flashed factory image?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did, tried several, can't remember which Android version was that finally worked, however upon flashing after I started in normal mode the same **** - encrypted again like nothing happened.
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
sui785 said:
What about CM or another rom?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well I only tried stock Android since this is what I really wanted. But does it make sense to try CM if stock does not work. IS there a chance CM works. IF you say I should try than I should I guess. Never thought about it. Thanks for the advice.
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Hamal said:
Well I might be confusing the terms, but I think I did use fastboot. I got the command lines from the XDA Forum actually and entered them manually through the sdk console the way I remember it. I think I also used some-kind of automated tool that basically does the same. The result being the same naturally. But should it even matter. I mean the problem is that whatever I do once I start the phone in normal operation mode I get the encrypted storage message. I have no idea how to get around this. Should I not be able to completely wipe it somehow so there is nothing when I start it ?
Click to expand...
Click to collapse
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
jaizero said:
Did you flash the factory images with fastboot?
Returning to stock using this method http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1 may fix your problem.
Click to expand...
Click to collapse
Jaizero I just did what you suggested. Followed the link you provided and did everything according to he procedure. There were no errors. However when I restarted the phone with the last command line and it booted up in normal mode there was the same message.
The screen looks like the one on the link below (not actually my phones, have no other one to make a picture with).
http://bensullins.com/wp-content/uploads/2011/12/Nexus-S-Decrypt-On-Reboot-Android-4-600x800.png
Also I do not know if it is relevant or not but when it boots the initial screen with the Google logo in the very beginning there is a closed lock icon below the Google logo, probably because of the encryption ?
Thanks for the help in advance again guys/girls.
jaizero said:
Can you get into the bootloader by pressing the volume up/down keys and power button? Does it give you the encrypted message there?
Were these the commands you used?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader
7) Optional (NOT optional for n00bs) -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img (or whatever the name is of the radio image that you downloaded).
8) Reboot (not required if you did not do step 7): fastboot reboot-bootloader
8a) Verizon and Sprint devices only -- flash the LTE radio: fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (or whatever the name is of the radio image that you downloaded).
8b) Verizon and Sprint devices only -- reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 5 below for optional items.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
Sorry saw your reply a bit too late. Yes these are the exact commands I used. Followed them exactly as stated every step worked out perfectly.
And no there is no encryption messaging while I am in the bootloader mode.
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Hamal said:
Hum... no replies. Seems like I am doing everything right yet results are bad. Means I am not doing everything right ofcourse. I am just not knowledgeable enough I guess to figure it out on my own.
Shame I really like the phone.
Click to expand...
Click to collapse
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
Locking/Unlocking the bootloader does not work tried it a couple of times already. Will try the rest of what you suggested and let you know how it goes.
Thank you for the advice.
beekay201 said:
Unlock the bootloader again, either through fastboot or omapflash. Did you try formatting partitions before flashing? Fastboot allows you to do that. Idk if you tried or have reserves towards ODIN, be extra careful both with omapflash and Odin. There's a link on unlocking the bootloader with omapflash on efrant's android 101 - links section, which is stickied on general.
a manta wrote this.
Click to expand...
Click to collapse
I looked around the forums, could not find this Android 101 link tough. Any chance you might help me find it. I know I sound lazy but I really can't find the thread. Also I was thinking could an USB Jig solve this problem ?
If all else fails you could try this...
http://www.extremetech.com/computin...encryption-and-security-put-it-in-the-freezer
https://www1.informatik.uni-erlangen.de/frost
I don't see why fastboot erase userdata wouldn't work...
Sdobron said:
I don't see why fastboot erase userdata wouldn't work...
Click to expand...
Click to collapse
Well I did try it. What I did might be wrong, but here it is:
I followed the guide by jaizero for flashing via fastboot, but instead inserted " fastboot erase userdata" before the "fastboot flash userdata userdata.img" line. Than there was an error message on the phone, not on the pc command line screen, but it was so quick that I could not read it. However the process continued and was okay according to the command window and everyting went on as normal. Alas to no vail since the result was the same.
Any ideas ?
Ah I also noticed than in fastboot mode it said HW Version: 9. Any idea what it means ?
Thanks in advance for taking the time to bother with my bull
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Which modes can you get into?
TWRP allows you to mount USB OTG. Try flashing something from there.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
Yes, like aniket0317 wrote: if all else has failed, put a ROM on a flash drive, connect it with a USB OTG adapter, and use TWRP.
I've lately had trouble getting my N7 recognized while in recovery mode, though everything's fine while in the bootloader and Android. But with TWRP it's easy to mount external flash storage and install from that.
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
are you able to go into fastboot mode? if so you still have hope
kmaq said:
are you able to go into fastboot mode? if so you still have hope
Click to expand...
Click to collapse
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
RecklessBrandon said:
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
Click to expand...
Click to collapse
download the 4.4.4 image
go to fastboot mode, connect the usb cable to laptop/pc
open command prompt and go to the folder where you have extracted the 4.4.4 image
fastboot oem unlock
type flash-all.bat
if all goes well device should reboot (initally will take some time) if it took more time, reboot again into fastboot mode
this time you can try manually commands one by one
in the folder where you have extracted the 4.4.4 image you will fine "image-razor-ktu84p.zip", extract this zip file as well
execute the following commands one by one:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
device should reboot and if it displays language screen then cool complete the wizard, reboot in to fastboot mode again to lock the bootloader
fastboot oem lock
fastboot reboot
and enjoy!!! do report back what happens.
fastboot -w update stockrom.zip
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
How does it appear in Device Manager? Have you downloaded and installed the drivers?
http://developer.android.com/sdk/win-usb.html
RecklessBrandon said:
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
Click to expand...
Click to collapse
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
I am having the exact same problem, it was installing got stuck on "erasing userdata" for over 2 hours and now nothing will work except for fastboot, and some how the device locked itself again. Only thing i can get to is fastboot mode, the computer recognizes the device. When I try to unlock it, it gets stuck in "erasing userdata" I let it run over night last night hoping it would some how work with no luck. I am unsure of what to do. Is there anyway to install a factory OS without unlocking? Every guide I've searched for has me doing an fastboot oem unlock and then the tablet freezes on erasing userdata. Any help would be greatly appreciated. Thanks!
kmaq said:
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
Click to expand...
Click to collapse
Reread your initial instructions, and it worked! Thank you so much!!!
Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev
After a couple weeks of on and off searching the internet, I finally got a couple GSI ROMs from the treble forum to boot up; so I'm posting this guide in hopes it saves somebody else all the searching
A couple things to note:
You and only yourself are doing this at your own risk. Unlocking your bootloader voids warranty
Have your stock images ready to flash in case of a brick
You must have an unmodified boot.img installed, the Moto REALLY doesn't like clean booting with a modified boot.img. I've tried every combination in magisk when patching a boot.img (keep & remove DM-Verity/Encryption) with no success on Stock and a GSI
Most things should work fine, text are reported to not work unless you change your network mode to 3G
Android 10 brought two fastboot modes to the game. Bootloader and Fastbootd. Since the Moto uses dynamic partitions we have to use fastbootd for this.
The Moto is 64-bit and uses A/B partitions so use arm64 A/B images
Lastly, BACK UP YOUR DATA, you will lose your data
Requirements
Install ADB & Fastboot from here
https://developer.android.com/studio/releases/platform-tools
You must have an unlocked bootloader. You can follow these instructions here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Download this vbmeta.img from here
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
A GSI ROM you want to flash
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Instructions:
Boot into fastbootd
Code:
adb reboot fastboot
Install the vbmeta.img
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Erase the system partition
Code:
fastboot erase system
Install the GSI of your choice
Code:
fastboot -w flash system GSI.img
If you get an error about resizing the partition run this command and try again
Code:
fastboot delete-logical-partition product_#
Replace # with a or b depending on what slot you're flashing toReboot and finish
Code:
fastboot reboot
You might boot into a screen that says to factory reset, do it and it should boot fine. It might happen another time or two (if it keeps happening, you've bootlooped, flash your stock images)
Recover/Back to Stock:
If your device bricked or you just want to go back to 100% stock, you can download the smart recover tool from here:
https://support.lenovo.com/us/en/downloads/ds101291
Recover Tool not working?
You can download the firmware from here:
Retail:
https://forum.xda-developers.com/mo...t/stock-rom-motorola-g-stylus-retail-t4104451
Metro:
https://forum.xda-developers.com/mo...30-80-64-3-t4138681/post83146807#post83146807
- Bricked devices are usually recoverable if they can still get into fastboot
Advanced Tips:
(Anytime you see # in a code box, replace with a or b depending on what slot you want)
- Since the Moto uses a A/B layout it's possible to have two different ROMs installed, but with no decryption it's not possible to share data between them, you have to factory reset every time you want to switch
- I personally like to have slot_a as a stock backup and slot_b set as active for flashing, make sure you flashed the bootloader to slot_b before switching slots
- You can flash or erase a specific slot if desired
Just put the slot after the partition name
Code:
fastboot erase system_#
Code:
fastboot --disable-verification flash vbmeta_# vbmeta.img
- You can change your current active slot with
Code:
fastboot --set-active=#
- Its helpful to use adb to dd some partitions on stock ROM like system and vendor, to make it easier going back to stock/fixing bricks:
Full Instructions here: https://forum.xda-developers.com/pr...si-porting-tools-android-auto-script-t4089193
- Requires Root
System:
Code:
dd if=/dev/block/mapper/system_# of=/storage/emulated/0/Download/system.img
Vendor:
Code:
dd if=/dev/block/mapper/vendor_# of=/storage/emulated/0/Download/vendor.img
Product:
Code:
dd if=/dev/block/mapper/product_# of=/storage/emulated/0/Download/product.img
VBmeta:
Code:
dd if=/dev/block/by-name/vbmeta_# of=/storage/emulated/0/Download/vbmeta.img
Boot:
Code:
dd if=/dev/block/by-name/boot_# of=/storage/emulated/0/Download/boot.img
Thank you for this guide. I was just able to install Phh's latest AOSP FLOSS (v221) GSI using your guide. Also, my data, SMS, and phone calls all worked. My device is on t-mobile.
The only issue I see so far is that the overlay for the punch hole camera is not correct. The time is currently behind the punch hole camera.
SnowStruk said:
Thank you for this guide. I was just able to install Phh's latest AOSP FLOSS (v221) GSI using your guide. Also, my data, SMS, and phone calls all worked. My device is on t-mobile.
The only issue I see so far is that the overlay for the punch hole camera is not correct. The time is currently behind the punch hole camera.
Click to expand...
Click to collapse
Hmm I'm on T-Mobile/Metro too. Maybe I was just doing something wrong, glad you found it helpful though! ?
DMedina559 said:
Hmm I'm on T-Mobile/Metro too. Maybe I was just doing something wrong, glad you found it helpful though!
Click to expand...
Click to collapse
Upon further testing, receiving text messages is not working correctly. I am not receiving new text messages, until a reboot of the device then they all come in at once. Then to receive more text messages I need to do another reboot.
Inbound and outbound calling works. LTE data works as well.
SnowStruk said:
Upon further testing, receiving text messages is not working correctly. I am not receiving new text messages, until a reboot of the device then they all come in at once. Then to receive more text messages I need to do another reboot.
Inbound and outbound calling works. LTE data works as well.
Click to expand...
Click to collapse
Did you capture logs of your SMS app/rcs service?
mrbubs3 said:
Did you capture logs of your SMS app/rcs service?
Click to expand...
Click to collapse
So the issue appears to be more intermittent. It seems if I wait long enough the text messages may come in on their own. I usually have to wait 2-4 hours, however I just did another test this morning where I sent two test text messages, and I received one after about 5 minutes, and it has now been 30+ minutes and I still have not received my second text message.
Here are the logs from the Silence app.
https://1drv.ms/t/s!AjI_xrwAxdGkqOla3nr6b7WvVDqzcg?e=RTSIvw
Right around 9:45 I received one of the two text messages that I sent around 9:40.
Also, here are the adb logs in case they help.
https://1drv.ms/t/s!AjI_xrwAxdGkqOlb6CkRMzgSucZAvg?e=n8Bf5j
Every time I try to flash a system omg it fails at the 3rd portion. Am I doing something wrong?
JimmyJurner said:
Every time I try to flash a system omg it fails at the 3rd portion. Am I doing something wrong?
Click to expand...
Click to collapse
Gapps and Floss version flashed fine for me, try this:
Code:
fastboot flash system GSI.img
fastboot -w
DMedina559 said:
Gapps and Floss version flashed fine for me, try this:
Click to expand...
Click to collapse
I'm getting the same thing. It won't pass the 3rd portion of the flash. I'm supposed to be in fastbootd right?
JimmyJurner said:
I'm getting the same thing. It won't pass the 3rd portion of the flash. I'm supposed to be in fastbootd right?
Click to expand...
Click to collapse
Yess you want to use fastbootd
You're using an Android 10 image right? I can't think of anything else unless it's a driver or a fastboot install issue, but I doubt it is
DMedina559 said:
Yess you want to use fastbootd
You're using an Android 10 image right? I can't think of anything else unless it's a driver or a fastboot install issue, but I doubt it is
Click to expand...
Click to collapse
Yes. I've tried almost every one of these. They all work on my other phones but this one keeps getting the same error. I'll try a different computer and let ya know the results.
JimmyJurner said:
I'm getting the same thing. It won't pass the 3rd portion of the flash. I'm supposed to be in fastbootd right?
Click to expand...
Click to collapse
Yes in fastbootd.
Did you try running the command to delete the partition? I had to do that step for it to work for me.
Code:
fastboot delete-logical-partition product_#
SnowStruk said:
Yes in fastbootd.
Did you try running the command to delete the partition? I had to do that step for it to work for me.
Code:
fastboot delete-logical-partition product_#
Click to expand...
Click to collapse
so run that 1st?
fastboot delete-logical-partition product_a
fastboot: usage: unknown command delete-logical-partition
Thats whats coming up.
JimmyJurner said:
Yes in fastbootd.
Did you try running the command to delete the partition? I had to do that step for it to work for me.
so run that 1st?
fastboot delete-logical-partition product_a
fastboot: usage: unknown command delete-logical-partition
Thats whats coming up.
Click to expand...
Click to collapse
Update your ADB. I just realized minimal adb hasn't been updated since 2018. Use the one I linked in the first post. It's a minimal adb & fastboot directly from google
DMedina559 said:
Update your ADB. I just realized minimal adb hasn't been updated since 2018. Use the one I linked in the first post. It's a minimal adb & fastboot directly from google
Click to expand...
Click to collapse
You sir are a gentleman and a scholar! I haven't updated my adb in awhile lol!
Worked like a charm.
Thank you all for the help!
So far I've gotten lineage os and havoc os to boot. Havocs face unlock crashes on setup. Keep ya guys posted...
SnowStruk said:
So the issue appears to be more intermittent. It seems if I wait long enough the text messages may come in on their own. I usually have to wait 2-4 hours, however I just did another test this morning where I sent two test text messages, and I received one after about 5 minutes, and it has now been 30+ minutes and I still have not received my second text message.
Here are the logs from the Silence app.
https://1drv.ms/t/s!AjI_xrwAxdGkqOla3nr6b7WvVDqzcg?e=RTSIvw
Right around 9:45 I received one of the two text messages that I sent around 9:40.
Also, here are the adb logs in case they help.
https://1drv.ms/t/s!AjI_xrwAxdGkqOlb6CkRMzgSucZAvg?e=n8Bf5j
Click to expand...
Click to collapse
I was able to find a reliable workaround to the SMS issue for now. I went into Settings -> Network & Internet -> Mobile Network and changed my Preferred network type from LTE to 3G and now all my text messages come in right away.
Is anyone else with a GSI having SMS issues? I am wondering if I can change some APN settings to get it work reliably with LTE being the preferred network.
SnowStruk said:
I was able to find a reliable workaround to the SMS issue for now. I went into Settings -> Network & Internet -> Mobile Network and changed my Preferred network type from LTE to 3G and now all my text messages come in right away.
Is anyone else with a GSI having SMS issues? I am wondering if I can change some APN settings to get it work reliably with LTE being the preferred network.
Click to expand...
Click to collapse
I changed the apn to T-Mobile and was no change. Had to switch to hspa to get it working
Fyi don't change slots and try anything. It super bricks. No response what so ever...