Related
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
PasserbyPassingBy said:
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
Click to expand...
Click to collapse
I do the same! Now my phone stuck on boot screen.
Does anybody can help us?
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
mr_gourav2000 said:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
PasserbyPassingBy said:
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
Click to expand...
Click to collapse
All necessary to read.
Hope you fix the problem.
Fixed
I managed to fix my phone, but not with the method Mr Gourav so kindly posted. I chose not to use mr_gourav2000's IntelSoC fix because the guide was written in a way that made it very hard to follow, and I was unsure if MOOREFIELD was supposed to flash briefly or stay on the Device Manager. Regardless, I wasn't going to risk bricking my phone beyond help by pushing on without knowing what i was doing.
The key was bypassing Status 7 (or 1), which prevents you from downgrading firmware. If your phone says something like "Installation failed with Status 1" or "Status 7," or you get the "Can't install this package over newer build" error when you attempt to flash a previous firmware, this fix can help you. Funny enough, the fix was posted by the very same person earlier this year:
http://forum.xda-developers.com/showpost.php?p=65995574&postcount=116
First, download the latest full firmware from Asus' support site: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Then, open or extract the .zip file, and go to into UL-Z00A-WW-(Firmware.Version.Number)-user.zip\META-INF\com\google\android\ . Select updater-script (no file extension), and open it in a plain text editor like Notepad++.
Remove lines 1-6, beginning with "(!less_than_int" and ending with "getprop("ro.product.device") + "\".");". The result should look like this.
Then, insert the edited updater-script into the .zip file, overwriting the old updater-script. At this point, I should mention that one of the removed lines probably checked your phone's model number to see if it was compatible with the firmware. I sure hope you downloaded the right file for your phone. If not, brick city here you come.
Finally, put the edited .zip into a microSD card, and insert that into your phone. If you want to use the stock recovery to install the firmware, rename the .zip to MOFD-UPDATE.zip and put it in the root of the SD, then restart the phone and let it update. Presumably. I didn't use the stock recovery. I used the temporary ClockworkMod recovery to fix my phone, so I'm not sure if it's that simple. If you're using that temporary CWM, just go to the zip installation menu and apply the zip from external_sd.
If you were going through the same problems I was, your phone should boot into stock, unrooted firmware again. Pat yourself on the back and never do whatever dumb thing you did to get to this point in the first place (like absentmindedly apply an OTA update in the middle of a lecture)!
Once again, thanks to mr_gourav2000 for posting this fix earlier. I may not have understood the IntelSoC fix, but I did understand this one!
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Redtexan said:
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Click to expand...
Click to collapse
If it's the 1st boot it generally will as it is recreating cache, dalvik-cache or ART...
It seems to take forever to clear cache too when using recovery but about a heartbeat when using fastboot.... Just another quirk of the phone...
Thank you much
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
mastet68 said:
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
Click to expand...
Click to collapse
You need to flash boot, droidboot and recovery for the build you are using.
I use fastboot to do this but make sure developer settings are enabled and USB debugging is ticked before trying to flash.
To find the img files for the above mentioned, go to Shakalaka's pre-rooted rom thread in Android Developement, you don't need to download the rom if you don't want to but it sure makes rooting easy.
Find the version of Android you need and download boot,droidboot and recovery img files. Flash with fastboot using these commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
***Make sure the right commands are used or it may result in a brick...***
So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....
I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183
joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)
https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!
well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.
Its not rocket science
timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.
i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!
Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8
Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.
steadfasterX said:
Well first of all your issue is not an UsU issue .
This thread is only about UsU so this is going more and more off topic .
I would suggest you open an own thread for your specific issue and we continue there.
You wrote you flashed all partitions of that kdz. Write down (in that new thread ) which partition names exactly.
Click to expand...
Click to collapse
Lets start from the beginning then, shall we;
I have a LG G4 H815 TWN variant. It was on LP for the longest time because it had root, and there was no chance for an official unlock.
My phone WAS on LL/LP because the phone suffers ILAPO but was recommended I upgrade, so I use a KDZ i found [H81520e_00_0818.kdz][9C861EA87A0E07C873A7835ABF21A5CE]. flashed through LGUP. (unsure where I originally found this file)
fine and removed the battery when it attempted to reboot the phone (still saw the LG logo)
I presumed all was fine then followed the guide to install UsU, which went fine (used option 3, files from PC)
Flashed a '4 core fix' version of TWRP
Formatted Data, after the phone showed 0 bytes free. After formatting, everything seemed fine.
Installed LOS 15.1 UsU version from SFXs website
Now here is where it went pear shaped.
Booting would always result in TWRP being launched, no matter what.
I was told it may have been ILAPO catching the boot of the new OS, so i should patch my boot.img.
I patched the boot.img, but accidentally flashed aboot due to unclear instructions and an incorrect guess on my behalf.
I was then told to use some specific QFIL guide to recover from my brick. The process succeeds.
But I am back to square one. Booting only to TWRP
Follow FAQ #20
-Downloaded this KDZ this time, instead of using my original KDZ from before
-Downloaded newest current version of FWUL (v3)
-Ran KDZ extract via SALT
-FASTBOOT flashed extracted files. (All finished OK)
Code:
fastboot flash factory factory.image
fastboot flash hyp hyp.image
fastboot flash modem modem.image
fastboot flash pmic pmic.image
fastboot flash rpm rpm.image
fastboot flash sbl1 sbl1.image
fastboot flash sdi sdi.image
fastboot flash sec sec.image
fastboot flash tz tz.image
-Rebooted. (boots only into TWRP)
- - - - - - - - - - -
SALT says the firmware is still: LGH815AT-00-V10f-TWN-XX-JAN-13-2016+0 - which to me looks like its still LP firmware.
- - - - - - - - - - -
I tried flashing a different OS (after formatting of course), for the sake of it, maybe it'd be different somehow, i tried; RR-O-v6.0.0-20180622-h815-Unofficial.zip
then flashed H815_UsU_baseband_flash-in-twrp.zip too.
still only boots to TWRP.
steadfasterX said:
Also let it bootloop and when back to TWRP :
adb shell
strings /dev/block/bootdevice/by-name/misc | head -n 6
Write the output in your new thread as well
Click to expand...
Click to collapse
Code:
BSP Forever
SM03s151212002753
0,1111111111111111
LGH815AT-00-V10f-TWN-XX-JAN-13-2016+0
LGH815AT
LGH815AT-00-V10f-OPT1-YT-JAN-13-2016+0
QFPROMalreadyblown
1,12,0212,21,2011,201,1,111,1,331122,10,0,1200,2,1,1,1,213,10222,0,2,2,0,2,2,2,2
"1","fff,fff,ffffffff,ffffffff,55"
not sure if this is the sort of stuff you wanted. I couldnt get adb shell to work from within TWRP so i just used the terminal from within TWRP and wrote out the output here instead.
I hope this is enough information for @steadfasterX
I thank him for all his time and effort on the unlock and also the time on the forums helping dummies like me.
tim455 said:
I hope this is enough information for @steadfasterX
I thank him for all his time and effort on the unlock and also the time on the forums helping dummies like me.
Click to expand...
Click to collapse
Flash this one in TWRP:
http://leech.binbash.it:8008/stock/LG/h815/
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
Wipe -> advanced -> select system and wipe it
Reboot -> recovery
Download & flash:
http://leech.binbash.it:8008/lineage/nougat/h815-UsU/
--> lineage-14.1-20190120-UNOFFICIAL-h815_usu.zip
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Flash this one in TWRP:
http://leech.binbash.it:8008/stock/LG/h815/
--> h815_20p_bootloader_29a_modem_TWRP-flashable.zip
Wipe -> advanced -> select system and wipe it
Reboot -> recovery
Click to expand...
Click to collapse
Thanks for the simple instructions. Turns out I couldn't follow them through to the end.
I wiped my system so it was clean prior to this, so I didnt mess anything else up. (I've done this before with no issue)
Flashed the bootloader/modem zip, then restarted (to recovery).
black screen, and a hard brick.
- - - - -
after that. I "played around" to see if i could maybe fix the issue myself and try again. using that same qfil guide as before. but this time, ran into an error..
Code:
COM Port number:4
Sahara Connecting ...
Download Fail:Could not connect to the COMPORT
Download Fail:Sahara FailValue cannot be null.
Parameter name: key
Finish Download
Device manager shows the little orange warning sign, but the drivers appear to be correctly installed.
EDIT: needed to be in unsigned driver mode. phone booting in TWRP again.
EDIT2: tried installing the LOS zip and get an error
E3004: This package is for device: g4,p1,h815,h815_usu; this device is []ro.product.name ----(a square box with a character it couldnt read)
I can try restoring an old backup I have if you think that would be wise, but I dont think I will play with it any more before hearing from you again. It's definitely the bootloader/modem zip thats causing the brick btw.
tim455 said:
Thanks for the simple instructions. Turns out I couldn't follow them through to the end.
I wiped my system so it was clean prior to this, so I didnt mess anything else up. (I've done this before with no issue)
Flashed the bootloader/modem zip, then restarted (to recovery).
black screen, and a hard brick.
- - - - -
after that. I "played around" to see if i could maybe fix the issue myself and try again. using that same qfil guide as before. but this time, ran into an error..
Code:
COM Port number:4
Sahara Connecting ...
Download Fail:Could not connect to the COMPORT
Download Fail:Sahara FailValue cannot be null.
Parameter name: key
Finish Download
Device manager shows the little orange warning sign, but the drivers appear to be correctly installed.
EDIT: needed to be in unsigned driver mode. phone booting in TWRP again.
EDIT2: tried installing the LOS zip and get an error
E3004: This package is for device: g4,p1,h815,h815_usu; this device is []ro.product.name ----(a square box with a character it couldnt read)
I can try restoring an old backup I have if you think that would be wise, but I dont think I will play with it any more before hearing from you again. It's definitely the bootloader/modem zip thats causing the brick btw.
Click to expand...
Click to collapse
I am soooo sorry dude.. I wrote the wrong file name. You have to flash ofc an UsU zip not the other.. I have corrected it above but here again:
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
That one does not cause a brick!
Your current state means you have to use SALT to flash UsU again. Afterwards you should be able to install the LOS zip without an issue
sorry again.. I am doing all this in parallel of my work and private life which both are continuously stressful since years and well yea I haven't thought before writing, that can even happen to me..
,.-
steadfasterX said:
I am soooo sorry dude.. I wrote the wrong file name.
sorry again.. I am doing all this in parallel of my work and private life which both are continuously stressful since years and well yea I haven't thought before writing, that can even happen to me..
Click to expand...
Click to collapse
It's okay dude. I can understand your mis-concentration due to stress. Don't worry about it. :good:
You're always helping others.
steadfasterX said:
You have to flash ofc an UsU zip not the other.. I have corrected it above but here again:
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
That one does not cause a brick!
Your current state means you have to use SALT to flash UsU again. Afterwards you should be able to install the LOS zip without an issue
Click to expand...
Click to collapse
I flashed UsU again via SALT (although it still said UsU was installed correctly) and got a weird message saying that something didnt work (attached)
tried to install LOS after, but was hit with teh same error message. had to reflash TWRP in order to get it to continue.
Installed LOS and.................. always boots to TWRP :\
I've attached logs again.
tim455 said:
I flashed UsU again via SALT (although it still said UsU was installed correctly) and got a weird message saying that something didnt work (attached)
tried to install LOS after, but was hit with teh same error message. had to reflash TWRP in order to get it to continue.
Installed LOS and.................. always boots to TWRP :\
I've attached logs again.
Click to expand...
Click to collapse
Yes that message is normal in your case . No need to worry.
So it let you flash LOS now without an error?
Well if you can come to IRC from Monday to Friday , 9am-5pm UTC+1 ..
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Yes that message is normal in your case . No need to worry.
Click to expand...
Click to collapse
great.
steadfasterX said:
So it let you flash LOS now without an error?
Click to expand...
Click to collapse
Yes. It now installs fine and finishes without any errors.
steadfasterX said:
Well if you can come to IRC from Monday to Friday , 9am-5pm UTC+1
Click to expand...
Click to collapse
Sure. Not really used to IRC. I'm taking a look now (even though its after those times) and just asking which channel should I join to talk to you about this? (what should I say or ask?)
tim455 said:
great.
Yes. It now installs fine and finishes without any errors.
Sure. Not really used to IRC. I'm taking a look now (even though its after those times) and just asking which channel should I join to talk to you about this? (what should I say or ask?)
Click to expand...
Click to collapse
All my main threads have a topic for
"support/irc "
like the SALT one:
https://forum.xda-developers.com/android/software-hacking/tool-salt-lg-revolution-t3717864
Sent from my OnePlus 6T using XDA Labs
I just got a Sprint LS991, i have a VS986 that i Was used to where all the way up to 2BA Firm ware i could go all the down to 13B firmware and root. Now with this LS991 i am at ARB4 right off the bat on ZVI firmware. I cannot even do the USU method to unlock the bootloader. I really want to Sim Unlock this device and gain root.
Is there any possibility of wiping out the partition that contains the ARB somehow so a downgrade can be preformed? Or any method of any way shape or form. I also have a H810 main board G4 with H811 stickers and firmware (Bootloader Unlocked) but it is stuck in a bootloop and i only got it to turn on once since that happened with the oven method and now its stuck at the boot screen only and freezes.
robles4242 said:
I just got a Sprint LS991, i have a VS986 that i Was used to where all the way up to 2BA Firm ware i could go all the down to 13B firmware and root. Now with this LS991 i am at ARB4 right off the bat on ZVI firmware. I cannot even do the USU method to unlock the bootloader. I really want to Sim Unlock this device and gain root.
Is there any possibility of wiping out the partition that contains the ARB somehow so a downgrade can be preformed? Or any method of any way shape or form. I also have a H810 main board G4 with H811 stickers and firmware (Bootloader Unlocked) but it is stuck in a bootloop and i only got it to turn on once since that happened with the oven method and now its stuck at the boot screen only and freezes.
Click to expand...
Click to collapse
you are out of luck dude. ARB is no partition - consider to read the technical details if interested ( https://bit.do/antirollg4 ).
It is a physical fuse and so irreversible (means it requires to replace parts on the mainboard to make it work again - nobody knows which/what though).
No root as you are on MM as well and you cannot downgrade due to ARB.
.-
This only works on the v7 and v8 bootloader(for now)
I am proud to present a new rom pre-installed with supersu!
Make sure to follow instructions. You will also be able to downgrade to 7.0 if you have 9.0
This tutorial is easy and will take a max time of 30 minutes to complete.
The samsung s8+ snapdragon has been hard to root to only have temp root, to bricking, but now, I have found and modified some files that you can use to permanently root your s8+ G955U and..You...can...install...TWRP!!!
TWRP will be installed as you go threw the process. Safetrap will be disabled and like all of the other rooting methods, your phone will only charge to 80%. YOUR WARRANTY WILL VOID DUE TO ROOTING AND INSTALLING A CUSTOM ROM. I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE(some idiot will accidentally brick there device. Like bruh, this method is easy. I don't see any way how you could accidentally brick your phone. If your reading this after bricking your phone...read the damn title next time. This method is only for the u.s versions of the s8+ aka Snapdragon.)
Let's get started!
You will first need to download this custom rom. It will disable safetrap and install twrp!
While the files are downloading, take that time to factory reset the phone and clear the cache.
Mod edit: Link removed.
This file package includes a modified version of odin.
There will be two firmware files. DO NOT FLASH BL AS IF YOU HAVE A BOOTLOADER 8 IT WILL NOT WORK. If you have bootloader 7 then it might work.
Next, put the phone into download mode. Hold Power + Volume Down + Bixby Button until the blue screen shows up. Press the volume button to continue after the blue screen shows up.
After that, open up odin and connect your phone with your cable to your computer using a USB 2.0 port. You can try USB 3.0 but might suffer a failure like a Auth error.
Once your phone is connected to your computer., odin should be showing (added!) and also will show a bar saying com. It doesn't matter what the number is.
After that, download the bootloader file for v8. You might be able to tell if your bootloader is 8 or seven(if you try flashing, it might say 8 > 7 or it just might say error. If you have v7 flash the file that came with the first download.
IF YOU FLASH SOMETHING AND IT FAILS, YOU HAVE TO RESTART THE PHONE INTO DOWNLOAD MODE AGAIN TO CLEAR THE ERRORS. IF NOT THE PHONE WILL NOT ALLOW YOU TO DOWNLOAD OTHER THINGS.
V8 BL download
Link removed.
If v8 fails then you might have to flash v7( located in folder from first download) if v7 fails flash v8(second download)
Flash the BL by clicking the BL button and navigating to the file location of the BL file.
In odin, go to the options table and unchecked f reset time and auto reboot. After that click flash! It will be quick when flashing the BL. After that once it says pass! Reboot the phone into download mode again. After that, click the reset button next to start and click on the AP button. Go to the folder where the AP file is located and load it into odin. It will freeze odin for a few seconds as it checks the MD5. Once your phone is in download mode and odin is responding again, click start and wait for the system to flash over! Depending on the speed of your pc it might go slow or fast.
Once it is done, it will said Failed! but that's ok. It has successfully completed installing and now you can reboot the phone normally. After it loads, safetrap should be disabled if a screen pops up saying continue or recovery. If none of that pops up that's fine, we still have some more files to flash.
Give the phone time to boot. The phone is not usable yet as android is still locked down. Wifi will not work but you will have temporary root access to the phone. You will see a app called flash fire. Open it but before you do, download the system file below!
Link removed.
Give it time to download. Extract the file from the 7z(have a file extractor that supports 7z). There should be a img file. Right click on it and press Send to the click on the phone. It will send it to the internal folder not downloads. Once it's on the phone, open flashfire then on the plus button. Then press the flash system(not Ota button) look for the img file and then press flash once you loaded in the .img Give it a few minutes to flash. After it's done flashing it will auto reboot. It might say that you flashed unauthorized files onto the phone and to contact your carrier. If not then skip this step. Go into odin. Select a BL file(remember if you think you have v8 flash the second download you downloaded. If you have the v7 bootloader, flash the BL that came with odin aka the first download. Uncheck f reset time and auto reboot. Flash the BL then wait. Once its done reboot the phone normally(hold Power button + down button) The error should be gone. The phone should reboot itself with a new boot logo animation. If that does happen, congrats you finished step one successfully . Now on to step two!
Shut down the phone and wipe the data and cache(factory reset)
Download the pre-installed supersu rom below:
Link removed.
Extract the files and only keep the AP file.
Go. Ack into odin and click on the AP button. Load in the AP file you just downloaded. Odin will freeze while checking the MD5. Once unfrozen, select the BL file you have. Remember, if you have v8 use the second download. If you have v7 use the first download or the one that came with odin. After that flash the two selected files and wait for the system to install.
Once the system is done it will say failed! Which is still good! Then reboot the phone and wait for it to load again. It will load into safe mode on first startup. Setup phone without Google until you want to login. Keep wifi off until your done setup. Once setup is done reboot phone by pressing power off. Once phone powers off, hold Power button until boot. Congrats if you made it this far! You have successfully rooted the samsung s8+ 955U snapdragon!
Will be making a video soon for people who had trouble installing.
@Flinnyd Please check your PM inbox. Thank you.
-Regards: Badger50 FSM
THANK YOU HAVE ...i made It as a NOOB !!! best user noob level guidance ever !!! I am trying to get to pixel simulation rom ...any pointers
jeetjeet said:
THANK YOU HAVE ...i made It as a NOOB !!! best user noob level guidance ever !!! I am trying to get to pixel simulation rom ...any pointers
Click to expand...
Click to collapse
So you were able to get your s8+ rooted?Look for any rom that might support your phone or cpu. As you learn, you might be able to edit rom files to work with your phone. The only problem is that phone companies are making it harder to make custom roms and also there's increasing security. I would say go for it!
Yes i fully rooted the SM 955u Snapdragon using the instructions above word by word and step by step ! Thanks a lot !
jeetjeet said:
Yes i fully rooted the SM 955u Snapdragon using the instructions above word by word and step by step ! Thanks a lot !
Click to expand...
Click to collapse
Yay!!!! Glad it helped
I am trying to flash other ROMS like Pixelexperience using the safestrap4.06v>Install>the zip file of the ROM ...i keep getting errors that "This package is for device greatlte etc" and the process stops , could you help with any ROMS suggested for snapdragon 955u
Sure. I'll try to find some roms then I'll pm you
jeetjeet said:
I am trying to flash other ROMS like Pixelexperience using the safestrap4.06v>Install>the zip file of the ROM ...i keep getting errors that "This package is for device greatlte etc" and the process stops , could you help with any ROMS suggested for snapdragon 955u
Click to expand...
Click to collapse
Forgot to mention installing other roms like pixel experience will remove your root.
I was able to root my S8+ with your method, thank you!
Now, I tried to use a module through Xposed but it doesn't work. I activated the module, rebooted and Xposed will detect it but it will not work even when it says that the module is active. Any suggestions?
Xpose probably broken pre installed. Try to reinstall xpose if you can
HEllo,
thank you for your work.
I am after all the stuff for SM-G955F
any idea?
thanks for the help
chandler132 said:
HEllo,
thank you for your work.
I am after all the stuff for SM-G955F
any idea?
thanks for the help
Click to expand...
Click to collapse
Will post for 955F but might not work and will need testers since i don't have the 955F
Flinnyd said:
Will post for 955F but might not work and will need testers since i don't have the 955F
Click to expand...
Click to collapse
thanks, I will test for you. Quick question, is it possible to bypass the FRP, if I flash the phone?
chandler132 said:
thanks, I will test for you. Quick question, is it possible to bypass the FRP, if I flash the phone?
Click to expand...
Click to collapse
From what I know, I believe it has to be bypassed to install a custom rom.
Flinnyd said:
From what I know, I believe it has to be bypassed to install a custom rom.
Click to expand...
Click to collapse
ok, so it means, that the installation will erase everything as well as the FRP?
Installing a custom rom will disable it
Does this work with the SM-G599U1? My BL is V8 and I had trouble installing this, and another root. It soft bricked my device and I had to flash stock BL I think? Anyways I'm a bit rusty and haven't done this since the Galaxy S3 was the biggest thing lol, so that may have contributed. Would love to hear some feedback on a link if this isn't the place to be rooting my device. Thanks!
AntyGuy77 said:
Does this work with the SM-G599U1? My BL is V8 and I had trouble installing this, and another root. It soft bricked my device and I had to flash stock BL I think? Anyways I'm a bit rusty and haven't done this since the Galaxy S3 was the biggest thing lol, so that may have contributed. Would love to hear some feedback on a link if this isn't the place to be rooting my device. Thanks!
Click to expand...
Click to collapse
I believe you can flash the 955U1 with this firmware but maybe I'm wrong. If you have bootloader v8 then flash the BL V8 file with odin with the AP file(second AP file download saying SAMFAILED) try that again and tell me if it works. If it doesn't then I'll release another method for the 955U1.
Thanks!
Flinnyd said:
I believe you can flash the 955U1 with this firmware but maybe I'm wrong. If you have bootloader v8 then flash the BL V8 file with odin with the AP file(second AP file download saying SAMFAILED) try that again and tell me if it works. If it doesn't then I'll release another method for the 955U1.
Thanks!
Click to expand...
Click to collapse
I tried again and I was successful. It was definitely confusing with all of the failed messages. but I got it. You can add that the 955U/1 works if you haven't tested yourself. Thanks again as a lot of the other methods seemed outdated and didn't work, or maybe I did it wrong lol.
Anyways, cheers!