[WIP] Reset Binary Counter - Galaxy S III Mini Original Android Development

Please note that if you perform this procedure, you do it at your own risk. I am not responsible for any damage!
For resetting binary counter :
In terminal emulator/adb shell, do this :
Code:
$ su
# dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732
Exclude $ & #.
Make sure that you issue the correct command as this is extremely risky and if done incorrectly, might result in a HARDBRICK.!!
I need someone to test if this method works on the s3 mini. This has been tested on GT-I9070. Please do this at your own risk.
If you feel my work worthwhile, please consider donating!

No takers? Seriously?
You guys can gain your warranty back using this! This works with tee!
I do not respond to tech support via PM

Yes but we also risk a hard brick I wanted to try but changed my mind when saw about hard brick. Sorry I hope someone else will test it.
Sent from my GT-I8190 using xda premium

Shaaan said:
Please note that if you perform this procedure, you do it at your own risk. I am not responsible for any damage!
For resetting binary counter :
In terminal emulator/adb shell, do this :
Code:
$ su
# dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732
Exclude $ & #.
Make sure that you issue the correct command as this is extremely risky and if done incorrectly, might result in a HARDBRICK.!!
I need someone to test if this method works on the s3 mini. This has been tested on GT-I9070. Please do this at your own risk.
If you feel my work worthwhile, please consider donating!
Click to expand...
Click to collapse
hi all
i tryed this but dont work on s3 mini

Lazarosh said:
hi all
i tryed this but dont work on s3 mini
Click to expand...
Click to collapse
Can you please post a detailed result?
I do not respond to tech support via PM

Shaaan said:
Can you please post a detailed result?
I do not respond to tech support via PM
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i have costum recovery

Is it not working?

Lazarosh said:
i have costum recovery
Click to expand...
Click to collapse
You need to be on stock kernel
I do not respond to tech support via PM

wouldn't it be more safe to examine multiple mmcblk0 contents first before blindly trying to overwrite a byte in flash…
sry it just feels a bit blindheaded to do it that way… lazarosh has hopefully first made a backup of the partition before erasing the byte to recover the previous state as the flash counter was clearly not in that place on his device and he may have overwritten different data…

Shaaan said:
You need to be on stock kernel
I do not respond to tech support via PM
Click to expand...
Click to collapse
tryed with stock but same

Really?

I'm testing but not working.

Nope doesn't work, it's probably in a different column/block not in 3145732.
But I'm sure you'll figure it out eventually, keep up the good work.

When do you think this problem solved?

Please post the result of this :
hexdump -s 3145732 -n 1 /dev/block/mmcblk0
I do not respond to tech support via PM

Shaaan said:
Please post the result of this :
hexdump -s 3145732 -n 1 /dev/block/mmcblk0
Along also post your binary count.
I do not respond to tech support via PM
Click to expand...
Click to collapse
I do not respond to tech support via PM

Shaaan said:
I do not respond to tech support via PM
Click to expand...
Click to collapse
" hexdump not found " via Terminal emoulator

Sorry for OT, but nice to see you around s3mini dev-section Shaaan.
Hope you'll figure it out, and thanks for taking your time on this!

tys0n said:
Sorry for OT, but nice to see you around s3mini dev-section Shaaan.
Hope you'll figure it out, and thanks for taking your time on this!
Click to expand...
Click to collapse
Well. I cannot continue anymore! I don't have the device. Also, the method used here is pretty dangerous!
To get this to work, i will have to study the hex dumps of mmcblk0, by changing the binary counter 3-4 times.
So sorry. But this cannot be continued without a device!
I do not respond to tech support via PM

Find a solution is still not known for the moment, right?

Related

[GUIDE] Perma-root and S-OFF!! (Both manually or if you used VISONary r12)

FINALLY!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: THIS COULD PERMENANTLY BRICK YOUR PHONE, INSTEAD OF ROOT IT IF YOU DO THE EVER-SO-SLIGHTEST THING WRONG. YOU'VE BEEN WARNED. I AM NOT LIABLE FOR YOUR STUPIDITY. ALSO, THE HBOOT FILE LOCATED HERE SHOULD ONLY BE USED ON THE G2. IF YOU SO CHOOSE TO USE THIS ON YOUR DESIRE Z, DESIRE HD, MOTOROLA RAZR, WHATEVER, IT WILL PROBABLY SCREW THINGS UP. YOU HAVE BEEN WARNED, ONCE AGAIN!
The next person to spam or hijack the thread with immature pics or comments will get a perm Ban!!!!​
Whoa, where did that comment above come from?? =P Thanks mods, I appreciate it!
On that note, I would not recommend this on any phone other than the G2, as I have not personally tested it.
NOTES: This thread is not working in Tapatalk for some reason. Click here to open it in your browser. Also, this will not fix your phone's hinges, your nagging girlfriend, or world hunger. It is what it is.
If you perma-rooted with VISIONary r12, you only need to follow steps 5, and 7. All other steps can be omitted. If you would like to do this all manually, you can still use VISIONary r12, however, instead of using the "PERMANENT" option, use the "TEMPORARY" option, where applicable.
VISIONary r12 has been temporarily pulled.
Expect an update to work with VISIONary r14 soon!
Credit goes out to scotty2, and all of the wonderful folks at #G2ROOT! WE LOVE YOU! <3
Donate to scotty2 (for root): [email protected] (PayPal)
Donate to me (for this guide): [email protected] (PayPal)
You need these files:
hboot-eng.img
wpthis-OTA.ko
wpthis-pre-OTA.ko
MIRRORS:
http://bt.microcozm.net/vision-perm-root.zip
MD5s:
Code:
4ed6ac813dbea0ee263ba0f6dc288693 wpthis-OTA.ko
8ac8e7a331a199a48001c691e59b1b33 wpthis-pre-OTA.ko
7669ae12dc2faa10ae555a164980efd0 hboot-eng.img
Step 1
Firstly, run VISIONary to gain temp root
Step 2
Push the .ko file appropriate for your phone, and hboot-eng.img to /data/local/
Step 3
Open a terminal on your phone, or open an adb shell from your computer.
Step 4
Code:
$ su
# insmod /data/local/wpthis-[YOUR_VER].ko
It should return:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That is good.
Step 5
FINAL WARNING: THIS STEP COULD SEVERELY DAMAGE YOUR PHONE. USING THE INCORRECT FILE COULD CAUSE IRREPARABLE DAMAGE, MAKING YOUR PHONE NOTHING MORE THAN A BRICK.
That noted, if you would like S-OFF, go ahead and run this command in your terminal.
Code:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Step 6
Note: This step is not required if you have used VISIONary r12 to perma-root.
If VISIONary gives you issues about already being rooted here, go ahead and skip this step. After you complete the guide and reboot, go ahead and run VISIONary, and hit "ROOT NOW", wait a minute or two, and reboot again. At this point, you will be fully rooted.
Close your terminal. If you are in adb shell, disregard
Run VISIONary again, this will lock in root. But wait, you're not done yet.
Step 7
This step will lock in your perma-root and S-OFF. If you are using adb shell, you should still have your shell open. If you have used VISIONary r12 to perma-root, and are just wanting to apply S-OFF, your terminal should still be open. If you have just completed step 6, go ahead and reopen your terminal, and type su and press enter to regain root access.
Code:
# sync
Wait a minute or two, and reboot. Congratulations, you are S-OFF!! Go ahead and power off your phone, and hold down VOL DOWN and press POWER to boot up into your bootloader. Check the top line to confirm you have S-OFF. Enjoy!!
Thanks again, everybody!
This is most excellent. 3 cheers to all behind this
Edit: Sent $5 to Scotty2's beer fund
<3 #g2root
win.
Just a WARNING - screwing up this command:
Code:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
can turn your new phone into a very pretty paperweight.
Caution!
It should be noted in the post that this was a collaborative #g2root effort, primarily involving scotty2, tmzt, IntuitiveNipple but also many others!
skyjumper said:
Just a WARNING - screwing up this command:
Code:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
can turn your new phone into a very pretty paperweight.
Caution!
Click to expand...
Click to collapse
Maybe this should be edited with 20-font, underlined and bolded in the OP You know someone will screw it up, ***** about it and blame unforgiven512 for their mistake.
edit: though I see that he already put a warning up on the post...LOL.
good work folks in #g2root!
has anyone done this?
Nevermind - Got it.
Here's what the error should look like.
Thanks!
ramainli said:
Where should I push the .ko files to and where? Using ADB to push it?
Click to expand...
Click to collapse
No offense man, but if you have to ask, you didn't take the time to read the post, you shouldn't be doing this.
i can mirror them on my 4shared account. let me download them now and put them up
Mediafire links to the same files.
hboot-eng.img
wpthis-OTA.ko
wpthis-pre-OTA.ko
EDIT: I was blind, the md5sums were already in the post. Verified to be the same in the above links.
unforgiven512 said:
EDIT: Can someone mirror these files for me? I forgot to pay my hosting bill, and I know I only have so much bandwidth on Dropbox. Thanks in advance!
Click to expand...
Click to collapse
Mirror for all 3 files
Wait...
REALLY?
Sent from my T-Mobile G2 using Tapatalk
mirrors
HF
Code:
http://hotfile.com/dl/81463991/019567e/hboot-eng.img.html
http://hotfile.com/dl/81464095/afc52d4/wpthis-OTA.ko.html
http://hotfile.com/dl/81464138/d441072/wpthis-pre-OTA.ko.html
RS
Code:
http://rapidshare.com/files/429789096/hboot-eng.img
http://rapidshare.com/files/429789097/wpthis-OTA.ko
http://rapidshare.com/files/429789098/wpthis-pre-OTA.ko
Mirror -
http://hotfile.com/dl/81465009/05845ea/wpthis-pre-OTA.ko.html wpthis-pre-TOA.ko
http://hotfile.com/dl/81465176/726aa62/hboot-eng.img.html hboot-eng.img
http://hotfile.com/dl/81465326/207607c/wpthis-OTA.ko.html wpthis-OTA.ko
here you guys go:
MIRROR
hboot-eng.img
wpthis-OTA.ko
wpthis-pre-OTA.ko
lol, guess we have plenty of mirror for this now, lol
Will this also work with folks with the European Desire Z?
HBOOT: VISION PVT SHIP S-ON 0.85.0005
Baseband: 12.28b.60.140eU_26.03.02.26_M
Build: 1.34.405.5 CL273326

[Q] Clockworkmod Touch?

Hey guys,
Great job all the dev's are doing, just wondered if there is/will be Clockworkmod Touch for our phone?
Thanks
Jamie
right now...no. there is only one developer who made cwm availible for out device and that person is busy making a well known rom; cyanogenmod9. there might be in the future but...probably not. depends. who knows. unless the devs of cwm make an official version of cwm for our device then we might get a better cwm touch then a replica from a random dev.
Sent From The Phone Of Gamers
Okay thanks
download at http://www.mirrorcreator.com/files/1XJJFPOR/
Extract .zip file to SDCARD
open terminal emulator/ shell then type this:
adb remount
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
reboot recovery
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
gmaster1 said:
right now...no. there is only one developer who made cwm availible for out device and that person is busy making a well known rom; cyanogenmod9. there might be in the future but...probably not. depends. who knows. unless the devs of cwm make an official version of cwm for our device then we might get a better cwm touch then a replica from a random dev.
Sent From The Phone Of Gamers
Click to expand...
Click to collapse
Actually, yes.
willypt said:
download at http://www.mirrorcreator.com/files/1XJJFPOR/
Extract .zip file to SDCARD
open terminal emulator/ shell then type this:
adb remount
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
reboot recovery
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
Actually, yes.
Click to expand...
Click to collapse
No modding needed? O.O
mkcy said:
No modding needed? O.O
Click to expand...
Click to collapse
Just do as I stated above
http://www.kaskus.us/showpost.php?p=655248189&postcount=4181
Here, lemme translate it
scmsystm @ kaskus said:
Hello,
Anyone here interested on trying CWM Recovery with Touch enabled feature?
Download Here
Code:
Extract .zip file to SDCARD
open cmd/terminal then type:
adb remount
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
reboot recovery
Here's a video showing you how to operate it.
http://youtu.be/kAKcv4uJ1xQ
-swipeup, down to choose menu
-swipe right to go to the next menu
-swipe left to go to previous menu
-Or you can use virtual button below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source: sk8erwitskil github based on CWM Recovery v5.5.0.4.
Kernel and device settings by arco.
Click to expand...
Click to collapse
I can say that this successfully works
just follow willypt's instructions
how can this work on our device???
Sent From The Phone Of Gamers
gmaster1 said:
how can this work on our device???
Sent From The Phone Of Gamers
Click to expand...
Click to collapse
Err, I don't get what you mean?
I believe it's called porting.
AFAIK, CWM 5 touch and CWM 5 shares the same setting and kernel.
Anyway... You can fully use it
willypt said:
Err, I don't get what you mean?
I believe it's called porting.
AFAIK, CWM 5 touch and CWM 5 shares the same setting and kernel.
Anyway... You can fully use it
Click to expand...
Click to collapse
i guess so...
Sent From The Phone Of Gamers
and how do we remove this CWM from our phone?
nezt94 said:
and how do we remove this CWM from our phone?
Click to expand...
Click to collapse
Why you wanna do that ?
Sent from my GT-I8150 using xda premium
works fine for me
thank you very much
nezt94 said:
and how do we remove this CWM from our phone?
Click to expand...
Click to collapse
Just install another one using the same command. It will be overwritten.
1haumann1 said:
works fine for me
thank you very much
Click to expand...
Click to collapse
You're most welcomed
Should I put this in the Development section Anyway?
willypt said:
You're most welcomed
Should I put this in the Development section Anyway?
Click to expand...
Click to collapse
I think you should It's not going to get the attention it deserves here in General.
And make it a visually-nice post, with colors and everythign - I noticed people get attracted by those stupid little things
Anyone who tried this cwm touch to flash CM9 for our phone?
acelim23 said:
Anyone who tried this cwm touch to flash CM9 for our phone?
Click to expand...
Click to collapse
If it helps you: I have 2 backups on my SD card (CM9 and Rio's Black Notes) and switch back and forth more times. It works perfectly every time. I think to flash CM9 should not be a problem.
acelim23 said:
Anyone who tried this cwm touch to flash CM9 for our phone?
Click to expand...
Click to collapse
I have cm9 and f.a.w back up in my sd card too, using this cwmtouch to restore for 2 times on both roms without any problem...
Sent from my GT-P1000 using XDA
Arco told us to flash cm9 through clockworkmod 5, or we may brick our phone. but if we flash clockworkmod touch, would we brick it with the touch version?

[Q] Debuggerd.bin asking for root permission?

I've Googled this and not found anything I could understand. debuggerd.bin is asking for root permissions. What is it? Ive never seen it ask on any of my other devices, apparently it's something to do with the Android OS. Why is it asking for root? Should I allow it? I am running MOAR v 1.1.
Any insight is greatly appreciated!
Sent from my SIII
I can't say for sure but I've never seen it before. Definitely suspicious. I'm going to take a shot in the dark and say you don't have supersu pro. Noww is Def a time when full logging would come in handy
I set it to log the debuggerd.bin and rebooted. Now its not using the access. I had JUST rebooted from a permissions fix when it asked for the permission and I posted this. I am at a total loss here.....
Sent from my SIII
If you dont know what it is, dont give permissions. If you find that any app is acting wonky, still dont give permissions and see if uninstalling that app removes that file asking for permissions
Sent from my PG06100
I have since denied it permission. Think I'll post about it in the ROM thread. Maybe someone there can shed some light on what the heck it is or why it would be asking for root.
Sent from my SIII
Hi.
I have a SGS2 with the same issue.
Here post the sequence of the petitions (not all, sorry)
- lsof
- sqlite3 .....(sorry i couldn't write it down)
- netcfg
- iptables -L -nvx
- ip6tables -L -nvx
- iptables -t nat -L -nvx
- ip6tables -t nat -L -nvx
- wpa_cli list_networks
- ping -c 2 -i.5 192.168.69.1 (using Connectify)
- cat /data/system/packages.xml
- cat /proc/28115/maps (the 28115 changes to 17859 in the next sequence)
I know that isn't the sgs2 forum but for information: I used NeatROM Lite LS8 4.1.2 rom, with Dorimanx 7.46 kernel.
More information: Yesterday I installed CrossBreeder (http://forum.xda-developers.com/showthread.php?t=2113150). Inside the zip I see the script "install_debuggerd.sh", but i don't know if this could be the problem.
Thanks and sorry about my english
Hmm. Those lines are exactly what it's logging on my S3. I also am running CrossBreeder. Now we know what's up. Time to visit that thread.
Sent from my SIII
My S3 also using latest crossbreeder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mw86 said:
My S3 also using latest crossbreeder.
Click to expand...
Click to collapse
I am not using crossbreeder at all I am seeing this as something link2sd is doing?
curioct said:
I am not using crossbreeder at all I am seeing this as something link2sd is doing?
Click to expand...
Click to collapse
Yes. They are link2sd commands. Do you have any other lag apps or mods? Seeder? I can confirm it was Crossbreeder for me. I denied and forgot debuggerd.bin and installed the new version of Crossbreeder with the fix and debuggerd.bin has not asked for permissions again. But you are correct that link2sd uses the same command line for what it does. I also use link2sd and have not had this problem with it. Try going to that thread.
http://forum.xda-developers.com/showthread.php?t=919326
[App] Link2SD
Sent from my SIII
hi guys , i've installed link2sd and it still same and i don't use Crossbreeder so is there any ideas ?

Help Mounting Remote Samba/CIFS Shares (persistent)

So basically I'm rooted and Busybox installed trying to use XBMCTORRENT and getting the unmounted shares error
So trying to mount my remote shares using this command while adb shell and su:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
I get this error ermission denied
Also tried a lot of apps like CifsManager and Mount Manager but none of those worked either.
Any help would be greatly appreciated.
username, not user name
/mnt/obb/nas exist? with which permission?
Kramar111 said:
username, not user name
/mnt/obb/nas exist? with which permission?
Click to expand...
Click to collapse
Oh yeah sorry about user_name that was just me posting the thread
/mnt/obb/nas was created previously for this purpose with 777
thanks for the quick reply btw
Just checked
Code:
adb shell su -c mount -o noperm,unc=\\\\192.168.1.1\\Media,username=123,password=12345 -t cifs none /mnt/obb/nas
All Ok
Kramar111 said:
Just checked
Code:
adb shell su -c mount -o noperm,unc=\\\\192.168.1.1\\Media,username=123,password=12345 -t cifs none /mnt/obb/nas
All Ok
Click to expand...
Click to collapse
OK so stupid question under username is my NAS user and password right???
THat username has access and rights for my nas folder so idk what's going on here really
I still get permission denied error
I double checked the folder inside the firetv for the permissions dont know what else to do damn
LastDeuS said:
OK so stupid question under username is my NAS user and password right???
Click to expand...
Click to collapse
Yes.
Can you make screenshot?
Kramar111 said:
Yes.
Can you make screenshot?
Click to expand...
Click to collapse
Suere here it goes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you change (for testing purposes) username and password to something like 123?
Kramar111 said:
Can you change (for testing purposes) username and password to something like 123?
Click to expand...
Click to collapse
Man I was away for vacations so I couldn't test anymore but thanks that did the trick
I must be honest I'm so lazy I was waiting for someone to tell me to test a simpler user and pass so I would go ahead and create another user on my NAS
I like to think all systems now are beyond those simple problems but hey it's working now thanks again man!!!
Kramar111 said:
Can you change (for testing purposes) username and password to something like 123?
Click to expand...
Click to collapse
Now that we got that working
How can I make this script run each time I reboot the device
LastDeuS said:
Now that we got that working
How can I make this script run each time I reboot the device
Click to expand...
Click to collapse
Don't know
For now my device is bricked (hope temporary) (bueller-51.1.4.1_514013920-rooted + reinstall Xposed framework)
Kramar111 said:
Don't know
For now my device is bricked (hope temporary) (bueller-51.1.4.1_514013920-rooted + reinstall Xposed framework)
Click to expand...
Click to collapse
Oh man sorry to hear that I'm thinking I can use some sort of script app to run this command each time I turn on the FireTV
LastDeuS said:
Oh man sorry to hear that I'm thinking I can use some sort of script app to run this command each time I turn on the FireTV
Click to expand...
Click to collapse
My Fire TV is restored now!
Thanks to rbox
But no time to try with script

How to get rid of the "Your device is corrupt message"?

This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.
Yes please that would cut down a lot
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!
randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days
Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character

Categories

Resources