Develop Bugs

[Q] HELP - Wiped the OS off of my Galaxy S3 I747

Alright, well I've come to a problem and I'm not quite sure how to fix it.
The title pretty much says it all, I've completely wiped the operating system off of my phone. There is nothing left, absolutely no data or anything. I was much too hasty and irresponsible, and I fear for the worst. I had previously attempted installing multiple ROMs multiple times using CWM to no avail so I re-rooted and switched over to Team Win. I know before installing a ROM you have to wipe your phone, well... I hit advanced wipe and within that I hit "system", went ahead and wiped. There's nothing left on my phone my phone and there are no ROMs on my SD card. I had backed up my phone before wiping but when I wiped that was also deleted. Before restarting it always warns me "No OS installed on your phone, are you sure you want to reboot?" Of course it's bricked and stays at the "Samsung Galaxy SIII" screen. I attempted putting a stock ROM back on my phone through ODIN, but a'las it didn't work (always stops at "SetupConnection"). I have nothing and there is no way for me to get a new ROM on the phone, I obviously cannot connect to my computer unless through download mode because the phone is bricked. So, what do I do? Is there any hope left for me or am I just completely screwed? The phone is less than a month old.

another option is to purchase a micro sd card and place a ROM and gapps (if required) on it, install the card and boot into recovery.
so when you connect your device to your pc, you're getting a yellow com connection in odin? what link did you follow for a stock ROM?
as long as you can still access recovery and download mode, there is hope, buddy.

xBeerdroiDx said:
another option is to purchase a micro sd card and place a ROM and gapps (if required) on it, install the card and boot into recovery.
so when you connect your device to your pc, you're getting a yellow com connection in odin? what link did you follow for a stock ROM?
as long as you can still access recovery and download mode, there is hope, buddy.
Click to expand...
Click to collapse
Yeah, when I connect to the PC I get a yellow com connection in ODIN. I followed what is, perhaps, a sketchy looking link for the stock ROM... It's not letting me post a link because I'm a new member to the board, though I've looked over this place plenty of times in the past. Should I look for something a bit more official and retry? I don't think it's going to work. Will a ROM work, without an OS? I know that may sound silly but everything I've tried so far has failed.

here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/showthread.php?t=1739426
flash the tar in odin like you have been. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
lemme know if that worked, otherwise throw a ROM on a micro sd card as stated and go that route
btw, a ROM is the OS.

And also, my phone has to be rooted for a ROM to be installed, right? Well there's no guarantee my phone is still rooted since I've wiped literally everything on the phone. I like the idea of a placing it all on an SD card but that could be wasted money and I don't have very much money to spend, especially if a ROM isn't going to replace all of the needed system files which have been deleted.

NovoAevum said:
And also, my phone has to be rooted for a ROM to be installed, right? Well there's no guarantee my phone is still rooted since I've wiped literally everything on the phone. I like the idea of a placing it all on an SD card but that could be wasted money and I don't have very much money to spend, especially if a ROM isn't going to replace all of the needed system files which have been deleted.
Click to expand...
Click to collapse
follow my directions above to flash rooted stock firmware

xBeerdroiDx said:
follow my directions above to flash rooted stock firmware
Click to expand...
Click to collapse
Alright, thanks a lot. My internet is super slow so it'll probably be a while before the file is completely downloaded. Let's hope this works. I'll get back to you when it's all said and done.

xBeerdroiDx said:
follow my directions above to flash rooted stock firmware
Click to expand...
Click to collapse
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.

NovoAevum said:
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.
Click to expand...
Click to collapse
booyah.
:good: thats why we're called a community. cheers!

NovoAevum said:
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.
Click to expand...
Click to collapse
One small thing you can do is to hit the "Thanks" button on xBeerdroiDx's posts.
:good:

im having the same promblem
post-mortem said:
One small thing you can do is to hit the "Thanks" button on xBeerdroiDx's posts.
:good:
Click to expand...
Click to collapse
how did u get your phone to connect to odin

dorvilkervins said:
how did u get your phone to connect to odin
Click to expand...
Click to collapse
Have you installed the Samsung drivers?
---------- Post added at 06:03 PM ---------- Previous post was at 05:27 PM ----------
Can you explain what happened with your phone? How did you "lose everything?" Is it able to boot up into Android? Can you get into recovery (TWRP)? Did you accidentally wipe something you shouldn't have?

I accidentally wiped my OS on my Galaxy S3 AT&T - Please Help!!!
Hello all,
I am a rookie user of smartphones and I have a Samsung Galaxy S3 AT&T. I accidentally wiped my OS leaving me with no OS. The good news is that I can still use Team Win and boot into recovery. How can I download and install a new OS? I live in a rural area with no place to go to get this fixed; so I would really appreciate any and all help on this matter. Thanks for reading
Tyler
---------- Post added at 01:10 AM ---------- Previous post was at 12:24 AM ----------
Hello all,
I am a rookie user of smartphones and I have a Samsung Galaxy S3 AT&T. I accidentally wiped my OS leaving me with no OS. The good news is that I can still use Team Win Development. Using Team Win, how can I download and install a new OS? I live in a rural area with no place to go to get this fixed; so I would really appreciate any and all help on this matter. Thanks for reading
Tyler

Check this:
http://forum.xda-developers.com/showthread.php?t=2363882

Hey Bro, xBeerdroiDx, Indeed this is a great community, but, it is the fellas' and ladies, like you,that have the knowledge and experience ,that do not have to assist anyone ,but do anyway. I am just another member here, but as a brother, you get a pat on the back from the gallery. Your willingness to help is very much appreciated.

me too
so twrp and dl mode are cool...but odin fails and zip in recovery kicks a status 7 error...what to do?
sgh-i747 .....i think my build.prop or bootloader is jacked?

hewhoisnotasothers said:
so twrp and dl mode are cool...but odin fails and zip in recovery kicks a status 7 error...what to do?
sgh-i747 .....i think my build.prop or bootloader is jacked?
Click to expand...
Click to collapse
Did you try \the latest CWM or TWRP? Maybe the ROM needs a more recent bootloader?

gottam
audit13 said:
Did you try \the latest CWM or TWRP? Maybe the ROM needs a more recent bootloader?
Click to expand...
Click to collapse
the bootloader may have been corrupted by a 4.x downgraded flash....i'm not sure how to proceed...

hewhoisnotasothers said:
the bootloader may have been corrupted by a 4.x downgraded flash....i'm not sure how to proceed...
Click to expand...
Click to collapse
Were you on stock 4.3 ROM?

audit13 said:
Were you on stock 4.3 ROM?
Click to expand...
Click to collapse
yes...I have tryed everything i can think of....i can flash recoverys just fine, but i havent found a rom that will boot past the splash screen...most just fail in odin...i don't want to jtag if i dont have to...in theory there should be hope since i can get into DL and twrp....

[RECOVERY] TWRP-2.7.0.0-moto_msm8960-hdpi.img YOUR, pre Nov 8, TWRP IS BAD!

Update twrp 2.7, see Dhackers link for the img. Use Recovery Tools from Play to flash from home.
Seems that only Dhackers latest TWRP is the one to use.
Thanks to cyanidium for making it evident to me anyway.
Dhackers msm8960 goodies: http://androidhosting.org/Devs/Dhacker29/msm8960/
BTW Does anyone know what "twrp263-M44.img" is?
Attachments: the ...M44 is 1 day newer & works.
Just extract these to get the fastboot img.
More details
http://forum.xda-developers.com/showthread.php?t=2612883
More conformation http://forum.xda-developers.com/showpost.php?p=49978993&postcount=79
This one is not Dhacker latest anyway :
http://forum.xda-developers.com/showpost.php?p=45688558&postcount=1
Md5 starts with 791.
Want to try Philz.
http://forum.xda-developers.com/showthread.php?t=2545120
Want The latest 2631? w/ SDext usb mount. What is the rub?
This Photon Q TWRP, with full SD mount & more, works on the M! See attachments for the flash-able ver. Now for the rub: screen input requires the mirror of the buttons. I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL.... It is really not that hard to use. Think of it as a game also.
Md5 : 7630baf88ec9d6c2a144a2ee86ec9bb7

I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
No settings, just bad! Thanks for the conformation Watson! We on a train with a new engine!!!

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
How long have you known about it?

aviwdoowks said:
How long have you known about it?
Click to expand...
Click to collapse
I came across this issues first time trying to flash Paranoid and Pacman.
Which left me soft Bricked or in Bootloops. At the time i was just too fed up and went back to stock
second time i encountered that, was with the first stable KitKat by Dhacker.
That's when i decided to start clean and deleted all my Pre downloaded files and I was forced to download the new E33 from Dhacker.
And along with that all my other Roms and Files. I kind of figured something was bad with my TWRP file. But never thought of it since 791 wasnt found by my search engine.
And this December when I was flashing my GFs phone that's when I confirmed that the 791 didn't work for any of my roms.
Because I couldn't find Dhackers E33 through Google.De search (Some odd way searches come up differently if you search from different country)
And it did the same issues I had the First time around. That's when i dug around more and found Dhackers TWRP.
After using that I was able to flash Roms like a mad man until I found a Rom that my GF was comfortable using and liked.

Germanese said:
I came across this ....GF was comfortable using and liked.
Click to expand...
Click to collapse
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Ohh well now we all know!
Thanks again for the history.
This screwed up my data partition & I could not determine if it was philz or this. Then I decided the stop one, as I would go to the other & then data restore failure, so I used just philz & the problem went away!

aviwdoowks said:
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Click to expand...
Click to collapse
Nah i didn't post about it back then and recent we were side tracked ahahaha.
And I actually just got back couple days ago ... work ugh hate it already ...
There maybe a post few months back, me asking somewhere about which TWRP people are using,
because I had my doubt on which one to use; but no one really bothered to respond.
Then i just decided to flash away with what ever, since most errors resulted in an Harmless SoftBrick.
Since i figured a way around to that soft-brick, my thought was, what worse could happen, I did worse before LOL
I won't take credit, just stumbled upon it... That's all you. Just here to Confirm that i did have issues with that version.
Since then I been trying to see CWM for KitKat LOL

Hmm...
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?

Twilla said:
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Click to expand...
Click to collapse
Yes or the e33.
Not sure which is better. Philz is newest & I have an ini file to help you set it up see #2 post.

Update.
Haha. But not a joke. PHOTON Q twrp 2631 up.

twrp 2631 maybe provided by arrrghhh!
http://forum.xda-developers.com/showpost.php?p=49857073&postcount=176
If you want to be synched to his Q versions, go thank him!
That means a good screen version for our m.

Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!

Coronado is dead said:
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Click to expand...
Click to collapse
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.

aviwdoowks said:
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
Click to expand...
Click to collapse
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.

Coronado is dead said:
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Click to expand...
Click to collapse
May I suggest philz new version just out.
Allows you to format many /'s now.
I use only it now.
Not pocket proof like twrp. Beware

New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907

aviwdoowks said:
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
Click to expand...
Click to collapse
It works fine (I have flashed Dhackers *img) but if we want to flash any ROM we must change updater.script and add moto_msm8960 to device list on it.
I have success flashed BeanStalk after I add moto_msm8960 to updater.script
P.S. Also unified ROMs flashed great!
P.P.S. Gummy is most stable for me from unified ones

Flash TWRP-2.7.0.0-moto_msm8960-hdpi.img with Recovery Tools. See OP.

Would anyone know if Dhacker's TWRP works on the XT905 model as well?

Yes. But that is just good advice. I do not have one.

Unlocked Bootloader Message

Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.

http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69

Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !

I also don´t like the screen... the opportunity to hide would be great.

here's the same, maybe someone can make a xposed module?

kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.

uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...

kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:

any luck on the nag screen yet? maybe gone in the july update? =D lol

I get this message Everytime, any ideas? Help would be great

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!

makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.

I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!

Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.

How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it

..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."

I am posting hoping some progress may or may not have been made on this. Its atrocious.

ROM issues

I'm pretty sure this has been asked a lot, but I'm trying to install the "TeamSPR Rom" and i'm following the steps exactly. I still get stuck on the bootscreen with the logo with the blue LED glowing. What am I doing wrong, and this happens with TeamSPR and Renegade.
Software Version: G920PVPU3CPF4
Hardware: G920P.02
Model: SM-G920P
Android: 6.0.1

Saafir said:
Wait 20 minutes.
Click to expand...
Click to collapse
My versions are correct for this right? and do I need anything else besides twrp?

steezoe said:
My versions are correct for this right? and do I need anything else besides twrp?
Click to expand...
Click to collapse
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862

Saafir said:
From the information in your post, you seem to be on the right track. That ROM has taken upwards of 25 minutes to boot for some folks. As long as the blue light is slightly pulsing, it's doing it's thing. As long as you have TWRP installed and working, you should be good to go.
Click to expand...
Click to collapse
So pulsing plus the samsung logo, is a good thing?
koop1955 said:
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
And I'm using the latest TWRP.
p.s. Thank you guys so much, I'm skepticle when it somes to asking for help on forums, cuz usually people are short tempered and or a-holes. I really appreciate it though.

1 last thing, do i install/flash the OTA part after it optimizes all the apps?

finished everything, it's booted up now, but my screen is spamming "unfortunately, "APPNAME" has stopped" is that normal?
EDIT: Can't get into my text messages either.

Saafir said:
You shouldnt receive any errors. I would reboot to TWRP, do a wipe and reinstall the ROM. Let the device boot and set it up. Once all is good with the initial install, reboot to TWRP and install the update.zip. This should ensure a nice clean start.
Click to expand...
Click to collapse
1. Flashed ROM, waited 20 is mins.
2. Phone loaded up, restarted into TWRP and Flashed the OTA zip.
3. Phone loaded up. This is when I start getting a popup saying "Unfortunately the process android.process.acore has stopped working." and my message app still won't open after i cleared cache and data.
Thanks in advance

Saafir said:
Set the device up before flashing the OTA.
Click to expand...
Click to collapse
Meaning I was supposed to wipe everything on my phone?

Saafir said:
Setup the device as go through the Setup Wizard..
Click to expand...
Click to collapse
I did exactly that. Im currently reflashing the Full ROM taking longer at the samsung screen. But I'll wait. If all else fails I'll probably go back to stock.

I'm now back to stock 6.0.1, going to give this one more go.
Would anyone mind giving me specific step-by-step directions. please?
I feel like im forgetting something crucial.

everthing finally worked out. just having an issue with xposed literally taking hours at the boot screen

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs