Related
Ok, as many of you know, the only thing between custom ROMs and your phone is the fact that we can not get the ROMs that we make to flash correctly in our current CWM recovery. We either get status 0, status 1, status 6, or status 7 errors when flashing. Most of these errors directly correlate with the boot.img command line(s) in the updater script.
uoY_redruM and I have spent over ten hours a piece trying to figure this out and have made progress but are still stuck.
We soon found out that the kitchens we were using to cook our ROMs did not have the latest directory for our phones partitions and their addressess (mmcblk0p1, etc.) This directed us to where we need to look to fix this.
The critical partitions we need to make ROMs flash are
1. Data
2. System
3. Boot
4. Cache
5. (optional) SDCard
It was easy enough to find 1,2, & 4, however the boot was a little bit trickier.
There are drives on our phone that had the following IDs:
1. mmcblk0p5 aboot
2. mmcblk0p7 boot
3. mmcblk0boot1 disk
4. mmcblk0boot0 disk
We believe that the real boot partition is 7, however we have yet to get a fully functional ROM up and running, despite writing the boot.img to p7.
With certain modifications to the boot.img lines in the updater script, I have been able to flash a ROM, but upon boot I lose SU permissions and the radio is borked (does not detect SIM card). Clearly this is still not functional and is caused by the boot.img (kernel) not being included in the ROM.
Attached is a scanned copy of a list of all of the partitions in our phone, along with their ID.
This is a thread where we can easily bounce ideas off of each other and hopefully get to the root of this problem ASAP.
Let's please keep this on topic. Thanks.
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Reviewers said:
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Click to expand...
Click to collapse
Yeah, we're starting to think it's recovery related.
We've (well most he) got the ROM to boot up now....but......and that's a big but.....it reads as if we have no SIM card. So, that's where we're currently stuck.
Same place boots loads kernel but no root or radio same sim card error
Wildchld said:
Same place boots loads kernel but no root or radio same sim card error
Click to expand...
Click to collapse
Are you using an insecure boot.img?
FiveOhFox said:
Are you using an insecure boot.img?
Click to expand...
Click to collapse
yep
Built in the kitchen
---------- Post added at 06:46 PM ---------- Previous post was at 06:41 PM ----------
I think it maybe the recovery too because I have lost root on restores
Wildchld said:
yep
Built in the kitchen
Click to expand...
Click to collapse
Ok. I'm trying it with secure boot.img files to see if that has any bearing on our results but so far nothing.
Ok well I'm going to shelf working on the script for a while and instead start working on my ROM and possibly learning how to make a recovery lol.
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Reviewers said:
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Click to expand...
Click to collapse
Why are you so adamant that it's the recovery?? You don't even own the phone!
I owned the amaze before and it didn't flash with 1 recovery but it worked on another.
I know this is Samsung but another user is agreeing with me as well.
Read the thread I made in General.
Flashing something from another phone will never work 100% as made for that phone.
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
Plus when I get the phone I'll look into it as well.
I might not be much help in this area but I'll do what I can.
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
uoY_redruM said:
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
Click to expand...
Click to collapse
If you use the update-binary from the EU rom the status 6 error goes away but same results but the kernel will load. Status 6 error is a syntex error not because of the script but the binary is looking for different parameters.
Also I see no Sprint roms being dev maybe they have the same problem
One last shot before work... Attached is a working script and binary
Rom boots fine and about shows baseline unknown so maybe we need to load the radio in the rom also.
Also when I restore a nandroid radio comes back but won't connect till I turn off wifi then service returns.
Here's the thing I found odd....
If you use CWM to pull a backup, the boot.img/recovery.img are both 10MB in size.
If you use the Toolkit to pull a backup, the boot.img/recovery.img are 2MB/512KB.
Why is that? That doesn't make any sense to me. They should be duplicate but they're not.
....the only thing that comes to mind is maybe the Toolkit (since it was designed for the international phone) points to different partition points and aren't pulling the correct files? Then again, why would they be named properly?
That's where I'm at for today.
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
uoY_redruM said:
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
Click to expand...
Click to collapse
You used the recovery.img from what, again? And the script posted above writes to p18 which is recovery so that's not a problem.
So it boots but is missing radio? Do you have root?
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
uoY_redruM said:
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Click to expand...
Click to collapse
Lol your right but i have loaded this nandroid like 30 times i know its good
Sent from my SGH-T999 using Tapatalk 2
FiveOhFox said:
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
Click to expand...
Click to collapse
Found a few more files that could be of use. Five is writing up some commands to try flashing them.
I'm starting to feel really good about today!
I have the newest philz and some how it can't wipe every time I tell it to wipe it can't do it? I even did another recovery but that one won't install roms this is twrp? Then after when I got a rom to sort of work with twrp recovery I switched thinking that was the problem. After resetting instead that one some how broke adaway and adfree there stuck in a loop and I can't call out that is what happens when I use twrp and I can't flash roms I even checked if the files were broken and they weren't. what recovery works or what is my phone doing with this rom or recovery ?
JinxTheCat said:
I have the newest philz and some how it can't wipe every time I tell it to wipe it can't do it? I even did another recovery but that one won't install roms this is twrp? Then after when I got a rom to sort of work with twrp recovery I switched thinking that was the problem. After resetting instead that one some how broke adaway and adfree there stuck in a loop and I can't call out that is what happens when I use twrp and I can't flash roms I even checked if the files were broken and they weren't. what recovery works or what is my phone doing with this rom or recovery ?
Click to expand...
Click to collapse
You didn't give us nearly enough details to know why you are having problems. Lots of people use TWRP without problems and TWRP can certainly install custom ROMs. To have any idea why you are having difficulties, you'd have to give us a detailed, step by step description of what you did with your phone and the error messages that you received.
.
Ok I'm not sure what details to give you I got my phone on I used a rooting process off the unlocker.com for my phone and it worked but my recover doesn't work no mater witch one I use i have s5 g900f for t mobile I'm not sure if I should just try re-rooting my phone maybe? Also the error I'm getting for installing anything is just abort and it can't install because it can't open? and I know the files are not broken tried downloading from computer and phone and saving to my card and the phone. What else do you need me to provide? I'm using the alliance rom that isn't working right because of what is going on with my phone. I can't go back cuz my backups don't work because my recovery isn't working no matter what I use because it will always not complete the restore in either.
I went to get a error message now and now I just get a blank screen in recovery so it's frozen and I can't bring up anything just the name of any rom I try to flash.
fffft said:
To have any idea why you are having difficulties, you'd have to give us a detailed, step by step description of what you did with your phone and the error messages that you received.
Click to expand...
Click to collapse
JinxTheCat said:
Ok I'm not sure what details to give you
Click to expand...
Click to collapse
Well we can't see your phone. And obviously there is no way to know what is going on if we can see it and you don't describe what you see in detail. For instance you say that you had an error message. But you don't paste the verbatim message here. Don't you think that message might be useful, if not critical.
For effective troubleshooting, you should post a detailed description of what you did, step by step and what was on screen. But I already said that in my last post and you disregarded the suggestion. I'm sure that others will guess at solutions for you. But efficient troubleshooting isn't possible without information.
.
1 If I told you I couldn't post the error message which I did because the recovery screen is blank what do you want me to post? I mean there is nothing on the screen to post there is nothing there because it froze it does not say open or anything there is nothing there unless you want to see a blank background. 2 If you mean what I used to root it would be CF root. Other then that I tried philz and twrp both have the same blank screen when you try to open a zip to install. would you like a black screen for twrp or a or blank purple and pink screen for philz with no text ? I posted that I went for an error message but the screen is blank and I can't make anything happen now. I can't give something when nothing is currently there. I'm just going to flash stock and unroot then root and see if that fixes my problem.
Hi everyone, I've searched and tried some solutions for this but the problem is the display is permanently black, not even samsung logo is displayed on bootup.
My GT-i9505 has a CWM recovery installed and a custom ROM, and today it notified me that SU Binary needs to be updated, so I updated it and it said Success, recommend to reboot, which I did.
It seemed to boot up but the display was constantly black. Manually turned it off by holding down power button, then restarted but still nothing.
I have Odin and samsung drivers etc, just not sure if I should try and flash a stock/new Custom ROM from Odin or if theres an easier way to do it (maybe someone can guide me thru the CWM recovery and be my eyes since my screen is Black?)
Please and thank you.
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
GDReaper said:
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
Click to expand...
Click to collapse
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
...err...wow...
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
_neutron_ said:
...err...wow...
Click to expand...
Click to collapse
Starting to think XDA is not the right place to ask for help...
3mel said:
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
Click to expand...
Click to collapse
Good idea, I do have chromecast but will need mini HDMI cable/adaptor to check. Although it would be massive odds against random screen death, since it was immediately after reboot from SU binary.
Thanks for the intelligent reply, glad to see there are still some helpful people here.
if you can borrow a lead and your screen is being mirrored you can download an image file of TWRP and flash it with flashify from the store. I doubt screen mirroring works from the recovery
http://play.google.com/store/apps/details?id=com.cgollner.flashify
unzip the attached file and copy it to your SDcard then find it within the flashify app...
Awesome OK that gives me a starting point TY. When I connect the MHL adapter will it mirror automatically or will I have to try to blindly press the mirror symbol? I haven't used an MHL adapter/cable before. If it works then I'll use Flashify and hope it restores the phone screen.
if it's going to work it will work without any selecting of options, it's automatic...
If the you run out of solutions, you could flash a stock ROM back to your phone as this will bring the phone back to the factory settings; however, you will lose your data and installed apps.
If you decide to flash back to stock using Odin, I suggest launching Odin, uncheck everything except f.reset time, connect the phone in download mode, flash the rom, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 5 seconds and replace the battery, boot into recovery, perform a factory reset, and reboot. Be sure to use the stock firmware from sammobile.com for your phone.
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
Since you said you have CWM recovery and a rom installed I assumed you would knew how to flash stuff. Unless they were flashed by somebody else?
Anyway, flashing SuperSU.zip is as easy as googling for the zip then boot into recovery and flash the zip file.
Unless the recovery is dark too. Then that's a problem.
And flashing the rom again is done the same way. No need for TVs and chromecasts.
Theoretically, flashing the SuperSU.zip should work, as it replaces the binaries.
Flashing the rom should work too. Unless you have a dead screen. Then no software can fix it.
When you're using apps that modify system files things like this can happen. Something may have went wrong during the update.
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
1) to see if the phone is running normal minus the screen
2) to replace CWM as you suggested without using recovery (which he won't be able to do even with MHL).
3mel said:
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
Click to expand...
Click to collapse
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
GDReaper said:
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
Click to expand...
Click to collapse
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Pandemic_ said:
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Click to expand...
Click to collapse
Ok. Then it is definitely a screen problem. Changing software won't fix it.
You have to get a new screen.
I've tried the cable, no output to HDMI though. Phone is operating but in complete black screen from power on. Have tried to tap the screen mirroring button blindly (by touching all the top system buttons one by one) but no change. This leads me to think it is a software/firmware issue, somehow the SU binary has affected graphics output???
So my only chance now is try to flash using Odin? I have downloaded a new Custom ROM, ResurrectionRemix-M-v5.6.4-20160223-jfltexx but I think I can only flash that one using recovery which will be difficult blind, unless someone can give me precise button sequence. Unfortunately I can't remember exactly what recovery I have on there, but I think it may be the touch version...
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Pandemic_ said:
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Click to expand...
Click to collapse
SamFirm should speed things up.
---------- Post added at 07:37 AM ---------- Previous post was at 07:34 AM ----------
leNoobe said:
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Click to expand...
Click to collapse
There isn't much you can do. Backup user data and factory reset.
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.
Thexmastermind said:
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.
Click to expand...
Click to collapse
Your not going to get a signal with Boost or any other CDMA carrier with custom ROMs right now. They work for GSM models but need to be fixed for CDMA.
Sent from my Moto E (4) using XDA Labs
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Thexmastermind said:
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Click to expand...
Click to collapse
If you don't already have it, the Boost stock firmware is here: https://firmware.center/firmware/Motorola/Moto E4/Stock/
Download this one:
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
If you can't get RSDlite to recognize your device, you'll have to use adb/fastboot to flash the firmware manually piece by piece.
Sent from my Moto E (4) using XDA Labs
RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Thexmastermind said:
RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Click to expand...
Click to collapse
I'm not sure what your problem could be other than not having the correct firmware. I haven't used RSD with this device (maybe someone who has will chime in) because it wouldn't recognize it so I've just been flashing it with fastboot on Windows with a script to flash everything automatically, so it's just as easy. It's the only time I really ever use Windows. You shouldn't need to erase anything before flashing. I've never had to. Be careful using the erase command, I've seen users screw up partitions using it and ending up with a brick. I only use it erase modem st1 and st2 and to wipe data.
Sent from my Moto E (4) using XDA Labs
I only have Linux ATM. My machine had XP on it till it crashed setting up eclipse lol rsd communicates with the device fine, so I'm assuming it's the firmware. Like I said I'm at family's for the holiday, but I'll keep you posted when I get home.
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Thexmastermind said:
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Click to expand...
Click to collapse
Pretty sure no verity zip or magisk takes care of that (though you get n/a in the corner)
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Quick question: when I flash twrp, leave it as read only, correct? Then flash verity, then su?
Thexmastermind said:
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Click to expand...
Click to collapse
No, don't leave it read only.
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
Thexmastermind said:
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
Click to expand...
Click to collapse
Yes
Alright, so I got an error message about a bad key when I tried flashing twrp. I booted into twrp from fastboot via command line, flashed verity, flashed su "successfully" just waiting on partition details to be updated....
But it feels like it's been a good ten minutes of nothing happening. I ran the following from desktop:
adb shell whoami
Return was:
root
But I'm still waiting for it to update the partition details...
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Thexmastermind said:
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Click to expand...
Click to collapse
You don't delete it. Be careful debloating.
Yeah I noticed there were a handful of apps that don't want be uninstalled. I saw a thread about it so I'll probably do a little more research.
how recovery?
pretty much same deal... how did you recovery to work
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
convolution said:
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
Click to expand...
Click to collapse
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
convolution said:
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
Click to expand...
Click to collapse
It has been awhile since I rooted any phone, but yes, pressing power to continue was what I remember. And, yes annoying, but not fatal !
Sent from my PH-1 using Tapatalk
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
GryphKid44 said:
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
Click to expand...
Click to collapse
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
I would think that would do the trick. In my case I knew the system was issue so I just flashed system. I find fastboot extra finicky on this phone. Did you happen to notice if something errored in the script?
convolution said:
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
Click to expand...
Click to collapse
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
wolfu11 said:
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
Click to expand...
Click to collapse
I do... but my wifi doesn't work as well, so I think I did something wrong.
convolution said:
I do... but my wifi doesn't work as well, so I think I did something wrong.
Click to expand...
Click to collapse
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
wolfu11 said:
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
Click to expand...
Click to collapse
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
convolution said:
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
Click to expand...
Click to collapse
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
wolfu11 said:
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
Click to expand...
Click to collapse
no need for twrp?
you follow this one?
convolution said:
no need for twrp?
you follow this one?
Click to expand...
Click to collapse
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
wolfu11 said:
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
Click to expand...
Click to collapse
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
convolution said:
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
Click to expand...
Click to collapse
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
spotmark said:
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
Click to expand...
Click to collapse
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
delete
If it works, you should worry about that message at all.
convolution said:
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
Click to expand...
Click to collapse
The slot thing is pretty new in general. This doc has some explanation for the architecture of our phones: http://mata.readthedocs.io/en/latest/
Once you get the hang of it, it's pretty simple to deal with.
BTW, awesome signature. PTL, SDG. :victory: