yashsingh1/xdaforums huggingface dataset:
[Android General] incitenoob:
Help! My phone is hard bricked!

I ordered from joybuy, and downloaded the ROM they mentioned "SAT....". I put that on the phone, renamed it as per their instructions, and the ROM was not recognized. Then I renamed it as "SS2...", as per another website that I saw. The ROM installed, and went to reboot. After that, the phone will not register anything. Power button has no effect. Power plus volume buttons have no effect. Volume buttons have no effect. Connection to a computer only loads the USB driver, but the phone is not listed under My computer in Windows.

Is the device ruined or is there some way to unbrick this? I really appreciate any help!
[Android General] seryioo:
Nothing works, same problem, SIM did not recognized. I will keep S3v2.

Thank you!

---------- Post added at 12:19 PM ---------- Previous post was at 12:16 PM ----------

Maybe test point would works.
[Android General] incitenoob:
---------- Post added at 12:19 PM ---------- Previous post was at 12:16 PM ----------

[/COLOR]

Maybe test point would works.[/QUOTE]

Any way to do that without tearing the whole phone apart?

The phone is not recognized with any drivers in Windows 10 and the device just shows up as QUSB_BULK. ADB universal drivers and samsung drivers posted in this thread don't work either. Can somebody post the SS2 USB drivers, in case that has any chance? Thanks!
[Android General] AndroPlus:
I added some screenshot link and how-to:

https://xdaforums.com/showpost.php?p=76594420&postcount=524

When you reboot 6 or 7 times, bootloader mistakenly counts up "retry count" which means "this boot image failed x times to boot", then bootloader thinks you failed to boot 7 times and enter into bootloader recovery mode.

(Look at "Error Enter bootloader recovery mode" in the chart of this page:

https://source.android.com/devices/tech/ota/ab/ab_implement

You can check retry count by running

fastboot getvar all

and reset it to 7 (max?) by

fastboot --set-active=_a

or

fastboot --set-active=_b

There is no such report on non-treble custom roms for A/B devices, so maybe Phh-treble has problem with A/B devices.

I'll try to find root cause...

For the mobile network, please dial *#*#4636#*#* and set "Cell Info Refresh Rate" to "Immediate".

There will be some info in "All Cell Measurement Info" if the baseband is working.

If there is no info, tap menu (right-top) and tap "Select Radio Band" to see if you can select band for your country.

In my case, I also had to set MVNO type to SPN and set MVNO value in APN.
[Android General] incitenoob:
Any way to do that without tearing the whole phone apart?

The phone is not recognized with any drivers in Windows 10 and the device just shows up as QUSB_BULK. ADB universal drivers and samsung drivers posted in this thread don't work either. Can somebody post the SS2 USB drivers, in case that has any chance? Thanks![/QUOTE]

After getting the OST bat file to run properly, the phone is now seen as a Qualcomm HS-USB QDLoader 9008. But OST does not recognize it as a phone still... Is there any solution?

---------- Post added at 03:02 PM ---------- Previous post was at 02:37 PM ----------

Tried this with my bricked SS2, but nothing happens after "flash firehose image". Any advice?
[Android General] seryioo:
[MENTION=5169444]AndroPlus[/MENTION] I follow your steps and I get SIM not recognized issue.

IMEI in my slot is unknown, I tried change SIM to slot2 but same issue.

I have S3v1 ROM, enter TWRP, wipe all partitions, flash your files (boot, vendor and system), wipe userdata and set partition=a...
[Android General] incitenoob:
Please tell me exactly how you were able to fix the phone. Each and every step. Please, that will help so much.
[Android General] bozicko:
Need help..

Does anybody knows how to remove name of the country in dialer app, and callui apk?

Its very frustrating...
[Android General] incitenoob:
After getting the OST bat file to run properly, the phone is now seen as a Qualcomm HS-USB QDLoader 9008. But OST does not recognize it as a phone still... Is there any solution?

---------- Post added at 03:02 PM ---------- Previous post was at 02:37 PM ----------

Tried this with my bricked SS2, but nothing happens after "flash firehose image". Any advice?[/QUOTE]

OK, problem solved! One needs to hold power plus volume up as OST runs to unbrick, and then let up at just the right time! :good:
[Android General] tminus3:
Damn, the is driving my crazy. Still can't get OST running to flash the WW rom.

I've tried every tip provided, but getting nowhere. I've tried to run the batch file, tried installing all items manually, as Admin, in compatibility mode, different orders of doing things, uninstalling stuff and retrying, different computer.

The best I can manage for three evenings of trying is an MS .NET framework error popup after launching the cracked OST 6.0.4 FIH:

"Object reference not set to an instant of an object"

Continuing despite this error I'm getting the OST windows with just placeholder tags instead of actual buttons.

Can someone please point me in the right direction on this? I've flashed at least a dozen different brands/models of phones over the last 7-8 years just by following instructions, so I'm feeling rather stupid right now.

I'm running a half year old up-to-date Win10 Home installation (albeit on some rather ancient hardware) fwiw.

Regards,

Tminus3
[Android General] AndroPlus:
S3v1 ROM has "Sharp Aquos S3 SIUI ver 121L WW MODEM", so maybe it causes the problem.

I'm using original S2 2070CN modem without problem.
[Android General] seryioo:
Ok, so, you flash this ROM over 2070CN firmware with S2 bootloader or over some Heineken firmware ported from S3?
[Android General] amiali:
https://www.mediafire.com/file/44m6a59lp0dtzxc/android[1].theme

Place it in the directory "SD Card\zookingsoft\ThemeStore\themes" and reboot phone

I changed my theme to my icons
[Android General] AndroPlus:
I flashed over 2070CN.
[Android General] amiali:
Why is not there any way to unlock bootloader and recovery for SAT? I'm tired so much

If there's no way I'll sell this phone
[Android General] seryioo:
Would it works over latest 2120CN?
[Android General] heineken78:
yes we have all files. later
[Android General] amiali:
I'm waiting for this to happen, and unlock bootloader
[Android General] AndroPlus:
UPDATE for this problem:

https://xdaforums.com/showpost.php?p=76598801&postcount=543

I uploaded 180524 build which adds workaround.

https://drive.google.com/open?id=1tVmMItEBK78u7hrZ7ayeNazvAXzOzs_n

I added "bootctl" command to force mark slot status:

https://github.com/AndroPlus-org/device_phh_treble/commit/b9627a6bc9945451f3ea6c7dffbe594a370e2f40

After the system boots, please run once (each time you flashed image):

bootctl mark-boot-successful

bootctl command doesn't need root, so you can use Tasker or something to run the command on boot.

After you run above command, current slot is marked as bootable and won't enter into bootloader recovery mode after several reboots!

I reported the problem to phhusson.

Maybe...
[Android General] amg_brabus:
Guys, pls help. I have noticed battery drain , about 6 percent per 8-9 hours. Wifi, gps, mobile internet and other stuff turned off. Firmware - ww 135E. Is that ok or something wrong with phone?
[Android General] KOCTA:
Come on, less than 1% per hour?! Is it a real drain?
[Android General] amg_brabus:
Well, dude, i had a lot of phones and didnt notice something like this. Sharp's battery is acting like it 4 years old. I think this should not be.
[Android General] nyco:
Hi,

Where the files?

I can try to do somethong, but i don't find the source code.

Thks :)
[Android General] heineken78:
some app is making errors, you dont see it visual. for 100% result make hardreset.

you dont need sourcecodes. I need the device to make apropriate vendor partition, then all system/twrp from s2/treble can be used on both devices.
[Android General] nyco:
Ok :) But how can you make it without unlocked bootloader ? ??

Have you got a "*.bin extractor " to extract the payload.bin from the update rom ?
[Android General] mihnthien0711:
[MENTION=5169444]AndroPlus[/MENTION] AICP ROM

this rom use google camera or Camera same nokia 7 plus ?
[Android General] AndroPlus:
Preinstalled camera is AOSP camera. I'll try Google camera tomorrow.

[EDT]

This one works!

https://xdaforums.com/moto-g4-plus/themes/app-google-camera-t3754816
[Android General] HeyM8:
Hello.

Thank you for the guide. Successfully flashed my phone with 135E WW Official ROM.

Couple questions:

(Firstly I'm new here so I can't embed pictures, please go to my imgur album link at the bottom)

I noticed that Google Search/Assistant doesn't have any audio output? If you use voice to ask it something, the answer is shown but no audio. No other app has a problem. I think it's related to this: https://www.xda-developers.com/google-assistant-voice-output-fix/ and a more in depth discussion can be seen here en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=1465017&pid=21050310

Opening build.props and going to the property mm.enable.qcom_parser, my current value is 13631487 and the correct value for this should be 13615103 (15th bit turned off as per miui post). Can anyone else confirm and if so can they try this value if they have root?

In addition, I've noticed that the Notification LED seems to stop after ~20 minutes. Using matlog I can confirm this. I reckon this could be fixed with an app that sends a 'dummy' notification to refresh the timeout, but is there anything that could be done with root?

I've taken several screencaps to illustrate, please go to imgur.com/a/p2zWwoD

Thanks!
[Android General] heineken78:
more nb0 roms

if you want to unpack repack nb0 files, here you ho with this tool
[Android General] heineken78:
SAT

SAT support is added.

First of all thx to [MENTION=9135345]Argoin[/MENTION] for files for SAT that he bought.

Here I made OST nb0 unbricking rom for SAT based on 127N CN initial service firmware.

For OST SAT-127N-0-00CN-B01.nb0 https://drive.google.com/open?id=1t0lRlTlTNNIMvbT1Y0bp33HfMp7UV_u3

Check first page for bootloader unlocking instructions added!

Later, I will meet guy in Kiev to borrow his SAT to make universal rom such treble v1 project for SS2.

SAT are you happy now?
[Android General] nyco:
Yeah!! Very good news, thanks a lot both !
[Android General] babaorum1973:
What about p preview test ??
[Android General] fegsfgg1:
Great work, appreciated!

But the weird thing is, that by VOLUME UP + POWER, my SAT enters the "fallen android" interface, while reboot -bootloader in adb leads to the "DOWNLOAD MODE" as per instruction?

Fastboot also doesn't recognize the device in both cases; adb only recognizes before rebooting into bootloader mode.

Double checked the Windows device manager too, their respective drivers seem to be working well, no exclamation or question marks.

Or it's because I'm currently on CN ROM, and have to switch to WW ROM first?
[Android General] heineken78:
In Download mode manually change driver in device manager from "adb" to "fastboot" device.
[Android General] amiali:
wow tnx

Someone has already tested , I want to do but I need help
[Android General] bukely:
I want to know where is the deviceinfo and how to send it to u.
[Android General] fegsfgg1:
Rechecked this, upon rebooting into Download mode, Windows would auto-change from "adb" to "fastboot". I tried manually switching to adb then back into fastboot, but to no avail. Still stucks on <waiting for device>.:confused:

----

EDIT: Nevermind. After some random updating, it seems that fastboot begins to work.

Now I have the productid and thus the md5, but it returns "FAILED (remote: unknown command)" when I attempt "fastboot oem cert_timecount get"?

Googled around a bit but did't find any resolution for this. My suspicion is that the CN ROM doesn't support these DIY issues well, just like their customer services.

----

EDIT#2: Flashed unlock.elf successfully without even bothering with cert_count. Despite there's not any unlock: "fastboot oem cert_timecount get" now fails no more, and says cert_count = 0. Figuring how to get rid of it. 9008 diagnostics are not working either. Not a lucky day perhaps.
[Android General] AndroPlus:
AICP 180527 build now supports NFC;)

https://drive.google.com/open?id=1LtPNR6R4dxJslXFIjpF9FhyfEfhBTCOa
[Android General] szmir:
Thanks, but where is the place to change the "Region Code"? Is that the hardware ID or firmware version?

Actually, I bought my S2 from JD.com and flashed its firmware to ww135E directly. And I did nothing on the firmware after that. But, I unlocked the bootloader successfully by following the instructions. But it failed on my Friend S2 device (I think he also bought from JD.com belongs to China region code)... That's weird. :confused:

Thanks,

Charles
[Android General] heineken78:
I found reason why you are not able to unlock.

Also there is NO dependency on region..

There is counter in "deviceinfo" partition, its counting downwards from FF till 00 each time you use fastboot (or fastboot commands).

When it reaches zero, you will be not able to use some fastboot commands such oem unlock or skuid set.

That's why taobao selling many cheap week-two used Sharps with zero in partition-> those devices will be blacked out by service :)

May be your friend has wasted 100's of devices in looking of unlock with brutal force?:)

Too late, china unlock mafia should now pick another device.
[Android General] heineken78:
How to make backup and restore of phone partitions

WORKS ON SAT AND SS2 models

Pay attention to model names:SS2 (4gb/64) SAT (6gb/128)

backups:

modemst1

modemst2

rf_nv

securefs

deviceinfo

fsg

fsc

SS2/SAT private partitions backup:

1. Switch to EDL mode:

For model SS2 flash service loader before (Visit first page -bootloader unlock till Step 6):

Enter: fastboot oem reboot-edl

For model SAT: use Methode1 or 2

2. Install Qualcomm HS-USB 9008 driver (comes together with OST if you don't have installed)

3. Change com port number of Qualcomm HS-USB 9008 driver in file

params.cmd.

Open file in text editor.

set SaharaComPort=com...[number of com port]

change path of prog_..file in

set FirehoseFile=[full path to programmer] (programmer is SS2-prog_emmc_ufs_firehose_Sdm660_ddr.elf for SS2 and SAT-prog_emmc_ufs_firehose_Sdm660_ddr.elf for SAt)

Save changes.

4. Start

readselparts.bat

Write back?

Start writeselparts.bat

Note: script is written by someone
[Android General] meetness1:
After unlocking Bootloader，can we flash twrp？And how？

I have tried the command "fastboot flash recovery xxx.img" but it returns an error "recovery no such partition".

The official recovery can't be used to flash zip file. When I choose "Apply update from SD card" it returns "Couldn't mount /sdcard".

I also tried adb sideload but failed too. So I began tring flashing 3rd party recovery but failed.

Without 3rd party recovery can, I flash zip file？I want to flash certain modules of Magisk in order to pass SafetyNet checking.

Any help or hint is appreciated.
[Android General] heineken78:
do you have twrp?

There is no recovery partition.

boot - is kernel + recovery ramdisk

system - has boot ramdisk in root and system as subfolder!
[Android General] heineken78:
TWRP Recovery. Ver Gamma.0.00001

Recovery https://drive.google.com/open?id=1L-wT1t_TK7FCFc-ecGQC7WTKF8AGmjPP

fastboot flash boot new-image.img

Note:

In order to access encrypted userdata, you have to agree with full decryption of it. To do it:

1. in TWRP format data.

2. Intsall this https://drive.google.com/open?id=1ORdkUL8UhDevksawnCBVk4XpI56i9_j3 to disable rom encryption.
[Android General] Jun_Ming:
ADB mode

Now my S2 still cannot start up. It is show logo, after connect to computer it is ADB mode. any body know please help me!!:rolleyes:
[Android General] heineken78:
Ming read how flash with OST with normal mode. Choose options 1,3,4
[Android General] pcgg:
Did you try to make factory reset via recovery? Mine worked after that way.
[Android General] meetness1:
Thank you very much. The TWRP works normally and file names are successfully decrypted. By flashing Magisk.zip, device got rooted successfully.
[Android General] szmir:
Yes... That's probably issue caused. My friend check the counts of the fastboot command usage with "fastboot oem cert_timecount get", it shows "CERT_count=0". But mine shows "CERT_count=74".

Ok, now I think he wanna fxxk up the JD.com and seeking the solution to reset the counters? Any idea to reset it?

BTW, he tried "fastboot oem cert_timecount set 100", but shows invalid command.

Thanks a lot.

Charles
[Android General] heineken78:
if its 0 you cant use set :)))

if its > 0 you can use set

Solution is in deviceinfo partition =p
[Android General] szmir:
Thanks my friend. I tried to backup my deviceinfo follows this guide (Thanks):

https://xdaforums.com/showpost.php?p=75946587&postcount=43

And asked my friend restored them all, the process goes successful. It showed his fastboot counter has been reset to 97, but it still not able to use "set" command to set the bootloader counter, also, failed to unlock its bootloader.

:confused: Hmmm... If anyone else was able to share the backup deviceinfo data and he might get another try?

Thanks,

Charles
[Android General] heineken78:
May be he erased service abl? Service abl need to be flashed
[Android General] Jun_Ming:
hi friend heineken78. OST cannot run on my computer. My computer is Window 10pro
[Android General] Seavovk:
C:\adb>fastboot flash abl unlock.elf

target reported max download size of 536870912 bytes

sending 'abl' (204 KB)...

OKAY [ 0.006s]

writing 'abl'...

OKAY [ 0.004s]

finished. total time: 0.013s

C:\adb>fastboot oem cert_timecount set 100

...

FAILED (remote: unknown command.)

finished. total time: 0.003s
[Android General] heineken78:
deviceinfo

editing of device info:

0) Check here how to get personal partitions and writeback https://xdaforums.com/showpost.php?p=75946587&postcount=43

1) Open deviceinfo in hex editor

2) Search for offset 5101 and set it to "60". Save file

3) Writeback to device

4) try unlock again

Note: If offsets 5000-5100 are empty - key is wiped- unlock is not possible!
[Android General] heineken78:
I have Windows10 too. It works.
[Android General] Jun_Ming:
Thanks brother. My phone working now ??
[Android General] heineken78:
One month left..
[Android General] AndrewMcE:
Is there a way to upgrade to s3v2 from s3v1 without loosing data?

My TWRP seems to be gone because I can't find it. Also can't get into it. Which nb0 I should flash?
[Android General] babaorum1973:
thanks, is there a way to try it with locked state bootloader?
[Android General] AndroPlus:
Maybe you can install system image in TWRP, but I don't know what will happen on locked bootloader...
[Android General] babaorum1973:
Thanks, i tried via fastboot with half success i will try
[Android General] seryioo:
Any one have the SIM card does not recognized on Treble ROMs?

I did all of this:

When I flashed AICP Treble I tried:

Over S3v1 doing all wipes.

Over S3v1 doing data wipe only.

Over S3v1 without flashing AndroPlus vendor and boot.

Over S3v2 doing all wipes.

Over S3v2 doing data wipe only.

Over 135H from S2 doing data wipe only.

Over 2120CN from S2 doing data wipe only.

I tried also flashing in B partition... but the same issue.

SIM is not recognized, if I put SIM card in slot1, IMEI1 is unknown and IMEI2 is a number. SIM card in slot2 has also IMEI2 unknown and IMEI1 is a number.

Sometimes baseband is unknown but I reboot and field show information again.

I tried also flashing pico gapps for Android 8.1... also removing system/lib64/android.system.net.netd@1.0.so.

I flashed also Phh-Treble but...... ****ING SIM IS NOT RECOGNIZED. I think there is some problem with spanish SIMs because this is not normal.

One more thing. When I tap on Developer options Settings.apk freeze (On Phh-Treble and AICP)
[Android General] babaorum1973:
Thanks it works with locked bootloader but i have no modem because i erase old s3V2 internal data..baseband is unkwnown i will try to flash modem img from s3v2
[Android General] aingerunn:
You could clearly explain. How to install it in our phone? and since rom is recommended.
[Android General] AndroPlus:
Instruction is here:

https://xdaforums.com/showpost.php?p=76594420&postcount=524

If you can't understand the commands, please don't install AICP.
[Android General] amiali:
For me, cert_count 0 should I do
[Android General] babaorum1973:
i managed to have the sim functionning one time only with asking for pins with the *#*#4636#*#* tips given by Androplus but u should:

tick the 3 dots and select europe bands and only after modifing search immediate but its not stable i will wait for a fix.

Sim is not often recognized

Developper option crashed

Works with locked bootloader over s3v2 by flashing trough twrp the 3 files :

-TWRP in boot,

-System image ab in system

-Vendor partition in vendor

and after erase data;)

AICP customization and omniswitch is cool

The screen calibration needs accurate for more white but the rom is promising thanks to AndroPlus
[Android General] AndroPlus:
[MENTION=9046323]babaorum1973[/MENTION]

For screen calibration, set LiveDisplay to off in Settings -> Display.

LiveDisplay is turned on by default and it changes display color based on time to save your eyes.
[Android General] homjen:
Thanks very much How should I compress my deviceinfo partition？

How should I compress my deviceinfo partition？
[Android General] Lovetz:
Hi. Is your build pass SafetyNet test? Is Google Play work?
[Android General] heineken78:
editing of deviceinfo

till I write whole manual

For guys who have try to unlock and have cert 0

-open deviceinfo (dump it via 9008 mode)

-Backup original file

-open in HEX editor, naviagate to offset 5101.

Change value from 0 to 70 in hex.

-flash deviceinfo back, then you will be able to unlock!

Note if you have empty offsets 5000-5100 - means you don't have unlock key inside- unlock is not possible!
[Android General] heineken78:
Google pay doesn't require safety net checks now!
[Android General] fegsfgg1:
Thanks again for all this dedication, but here are still mysteries unsolved...

All the drivers are installed, after "fastboot oem reboot-edl", the Windows system could identify my SAT in 9008 mode perfectly (or at least the "Qualcomm HS-USB QDLoader 9008" device

appears)

params.cmd was edited as per instructed;

Then I executed readselparts.cmd, it says:

----

Version 2.15

Downloading flash programmer: F:\S2kit\qpst_personal\prog_emmc_ufs_firehose_Sdm660_ddr.elf

Successfully open flash programmer to write: F:\S2kit\qpst_personal\prog_emmc_ufs_firehose_Sdm660_ddr.elf

Expecting SAHARA_END_TRANSFER but found: 0

!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!

Dumping data to file F:\S2kit\qpst_personal\modemst1.img

Dumping at start sector: 0 for sectors: 0 to file: F:\S2kit\qpst_personal\modemst1.img

Programming device using SECTOR_SIZE=512

<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>



----

Then it jams. After a few minutes, it adds:

"ERROR: No response to configure packet

Status: 21 The device is not ready."

----

Sometimes it directly jams upon "Version 2.15", and no further.

====

Any idea on fixing this? My guess is that a replacement 9008-USB cable might work, or should I just revert to ordinary USB cable?:confused:
[Android General] heineken78:
manually swap driver from Qualcomm HS-USB QDLoader 9008 to another in list .. also reboot device again in edl mode, once its failed you have to reenter mode on phone, cos it hangs.
[Android General] fegsfgg1:
Tried all 5 drivers I can found.

4 Qualcomms, ver.2.0.9.6, ver.2.1.0.5, ver.2.1.1.2, ver.2.1.2.2;

1 Windows provided generic driver (HS-USB Diagnostics 9008)

Rebooted PC and SAT after every try, none worked, all gets "Expecting SAHARA_END_TRANSFER but found: 0

!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!" :mad:

Can you provide a source of your version of driver that works?

Or is there some other possible cause?