I've been trying to help my friend get her phone at up with a custom ROM but boy did things change since when I was doing this.
I managed to unlock the bootloader, boot into twrp (without actually installing it, only the temporary version) sand then I accidentally deleted her stock rom and now I can't seem to flash a new one.
Not 100% sure if I managed to root it. Also I'm confused by these slots. On slot b it complaints that there is no OS and slot a I'm not even sure the bootloader is unlocked on.
Can someone please give me some tips on how to troubleshoot and see if I can save this phone?
Thank you!
On A/B devices slot A by default is where device's Android OS is housed, slot B by default is where Android OS updates ( temporarily ) get stored.
If you can access device by means of Fastboot then you can try to flash device's Stock ROM applying the flash-all.bat what typically is to be found in the Stock ROM's ZIP-file.
Finally had time to look at this.
I managed to download a RUU exe (which I hope is the right version, I really am not sure, the only clue I have is SDM UFS) and am working on extracting the rom.zip from it.
What worries me is that I'm sort of stuck in Fastboot and can't seem to reboot to download. It also says
SECURE BOOT - PRODUCTION
DEVICE STATE UNLOCKED
and in the bottom it says:
*** Software status: Modified ***
This device is corrupt. It can't be trusted and will not boot.
THANK YOU SO MUCH FOR TAKING THE TIME TO TRY AND HELP ME UNDERSTAND!
Ok, I got it back into download mode, found the right RUU. Couldn't find the flash-all but am writing boot and system now.
Hoping it works!
Did flash boot and system and can start into something that looks like android but nothing works, I can't enter settings and there seem to be no apps installed. What do you think I have missed?
Hey, how'd you get your phone into Download mode? I'm having the same issues and seem to not be able to do anything with no real answers in sight. Thanks!
Related
Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag
You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington
When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.
shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.
Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
xxTECRAxx said:
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
Click to expand...
Click to collapse
adb commands don't run on fastboot.
You must flash stock boot.img or magisk patched boot.img using fastboot flash boot "the_boot.img_file_you_want_to_flash"
should i flash this image "root.boot.sunfish-qd4a.200805.003.img"? or do you know where i get a patched magisk boot image? i've looked through magisk github as well as here but i may not be looking for the right stuff. i get the idea of what needs to be done. how i do it exactly is a little stretch, outside the obvious command "fastboot flash boot.img"
little more push in the right direction, please?
EDIT:
reviewing this https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
and this https://forum.xda-developers.com/t/help-access-internal-storage-from-fastboot.4221223/#post-84332187
the fastboot mode screen displays the following for the bootloader version: s5-0.2-6281315 and i do have a bootloader that matches that. going to give that a whirl
making headway but not booting still
xxTECRAxx said:
making headway but not booting still
Click to expand...
Click to collapse
Judging by the screens you've shared, you've just tried to flash bootloader into boot partition. DON'T DO THAT.
If I were you I would just download the complete fastboot ROM and would run flash-all.bat.
In order to retain your data, before running the bat, open it and remove the "-w" you'll see on the update command line.
This will flash the hole ROM and firmware, thus making your device to achieve boot.
Afterwards you may try to root it again.
THANK YOU!
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
xxTECRAxx said:
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
Click to expand...
Click to collapse
That storage space values are just... weird. Can't quite find another word for it.
If I ran into that kind of problem I would completely clean flash the stock ROM again, this time keeping the "-w" flag. You see, that flag completely cleans the user data partition and creates it again as soon as the flashing procedure ends. Most likely, and by doing so, your storage space values will be correct again. Obviously this will wipe everything so, if you decide to do so, please backup manually all your important stuff.
As for SafetyNet fix, you may use kdrag0n module (he made and shared one universal mod that fixes it) or you may flash my addon features module (link on my signature) that, not only, fixes SafetyNet, but also, adds several cool mods.
Cheers!
flashed from graphene os and back to stock during stock flashing something failed and gives me a black screen and goesinto the screenshot provided
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
JohnC said:
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
Click to expand...
Click to collapse
it wont work , that is what caused the issue, there is no adb or fasboot commands as the phone has nothing to load or read, it was flashing the official latest stock firmware using the flash-all.bat, then after the first rebbot and waiting for devices it goes to a black screen and shows what i put in the screen shot,(i believe the battery died during flashing) there is two modes it goes into the qusb which is the qualcomm download mode and some other mode i cant tell neither can the pc device find drivers to read the phone, techinically this phone is not fixable using normal methods , but i believe there is a way to flash to firmware back on,i have looked into using edl and qspt flashing but it still doesnt read the phone, any help would be greatful i have device protection but they are sending me a refurbished phone i would rather try to fix this before i do get the replacement, as it was a new and working device
i have been able to find a working qualcomm driver is there anyway to edl or msm file for the pixel 4a to fix this, now that the phone is being read properly it should be able to take commands as it is reconized as a modem driver or port
Any Ideas Why Its Failing , says sahari protocal failed
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
miko12312 said:
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
Click to expand...
Click to collapse
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
vabeachboy0 said:
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
Click to expand...
Click to collapse
I believe Qualcomm is the ones that obtain these files not Google , only other way is to dump the files from download mode on a working device
I'd like to help by dumping the required files, I didn't know anything about EDL before doing research for this thread, but as I understand using EDL mode require a device-specific non-free "loader".
I'm trying to use B. Kerler's EDL tool (https://github.com/bkerler/edl) but fail because it doesn't have the proper loader file in its database.
If anyone come across the loader for the Pixel 4a (000e60e10066000a_3ef72a02fb931be1_fhprg.bin), I'd be happy to share boot and memory dump from my phone.
I encountered the same situation as you, did you solve it?
Older thread I know, but I've used EDL mode (on LG phones) to save partitions and write partitions.
But you have to have a 'programmer file' for the specific device for it to work. Aka a 'firehose' file for the specific device / chip.
Some mfg's make this available, some don't. Google does not. So, even having the file(s) you want to flash won't help, not if you don't have the firehose file.
sorry, cheers
Has anyone figured this out? Could really use some help. Thank you
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
mizzunet said:
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
Click to expand...
Click to collapse
Only suggestions are the go to software of choice,, pixel flasher or android flash tool, both need bootloader unlocked
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
mizzunet said:
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
Click to expand...
Click to collapse
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
hammered58 said:
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
Click to expand...
Click to collapse
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
mizzunet said:
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
Click to expand...
Click to collapse
I will second that, unfortunately I don't think it's possible, at least not that IAM aware of
Hey all. I am currently trying to get my Galaxy Tab 8.0 2019 (sm-t290) unlocked. I have the bootloader unlocked. But since I did this, I cant get download mode in the usual fashion. I can still technicallly get there, but via a different route. When I try booting to DL mode, I get the screen that warns you not to save data on your device because it is "unsafe." If I do nothing here, I get booted into the OS. If I hit 'volume up' within the first few seconds, I get recovery mode, but not the usual one. The warning screen stays, but a few recovery options are displayed at the top of the screen. One let's me go to the regular recovery mode. From there, I can get the other download mode. Is this normal on Android 10, or have I f***ed something up? BTW, I haven't flashed anything yet. Haven't even plugged into Odin or ADB. As I said, I can get download mode, I am just a bit nervous to flash anything until I figure out what is going on. Thanks
edit: nvm i got it. I tried i for like the 10th time and it worked...
This all has NOTHING to do with Android OS itself, but with device's bootloader: Don't confuse things.
Hint: Add SOLVED to this thread's title.
nvm I got i
jwoegerbauer said:
This all has NOTHING to do with Android OS itself, but with device's bootloader: Don't confuse things.
Hint: Add SOLVED to this thread's title.
Click to expand...
Click to collapse
thanx. Although now I am confused. If the bootloader isn't getting swapped out with new os versions, then why are people having to patch their files before flashing on version 10? I thought it was to include the version 9 bootloader. Wouldn't this suggest that the bootloader is getting replaced with, at the very least, each major update?
lifeModder19135 said:
nvm I got i
thanx. Although now I am confused. If the bootloader isn't getting swapped out with new os versions, then why are people having to patch their files before flashing on version 10? I thought it was to include the version 9 bootloader. Wouldn't this suggest that the bootloader is getting replaced with, at the very least, each major update?
Click to expand...
Click to collapse
or is it the actual boot partition that is getting swapped out?
lifeModder19135 said:
or is it the actual boot partition that is getting swapped out?
Click to expand...
Click to collapse
The bootloader starts up the Android OS when you turn on the phone. This is a pretty important job, so it’s very important that nothing goes wrong with it. That’s why phones keep their bootloaders stored in special stable memory.
Some ( if not even almost all ) bootloaders, however, contain an extra layer of security that checks to make sure that it only loads an OS that passes its approval process - what is intended by OEM. That's the main reason why people try to hack the bootloader.
I personally can't see any reasonable reason to modify the bootloader.
Bootloader is comparable to UEFI/BIOS.