Related
Hello,
I've encountered one stop point in my way to Jelly Bean. I'm playing with Desire HD, Android 2.3.5, HBOOT-2.00.0027. I've managed to get root by SuperOneClick, but I'm not able to flash the recovery. While I have root privs, I've downloaded "recovery-clockwork-touch-5.8.1.5-ace.img" and put it do sdcard as "recovery.img". Then I've tried to boot to hboot and through the fastboot run the following command:
fastboot flash recovery recovery.img
sending 'recovery' (3554 KB)...
OKAY [ 0.610s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.220s
As you can see without success. Second try was updating the recovery partition with shell root privs through adb shell:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
7108+0 records in
7108+0 records out
3639296 bytes transferred in 2.905 secs (1252769 bytes/sec)
I've got no error, but partition wasn't updated. It still contains the same data as I wouldn't run dd command at all. Is the partition in some kind of read only mode or ? I don't understand how it it possible. I thought that with the root I can do everything.
Is there any other way how I can move image data to recovery partition with the dd?
Are you S-Off or is your bootloader unlocked? If you don't know, paste the contents of hboot here.
The bootloader is locked with security on. Doesn't it matter actually? I thought that if you havethe root privileges, you can flash custom recovery with no problems. Apparently not.
I prefer not to use the htcdev unlocker. So what to do?
Root is software; it has nothing to do with flashing to hardware partitions. You flashed root somehow; did you unlock and then relock your bootloader? How did you root? At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
bananagranola said:
Root is software; it has nothing to do with flashing to hardware partitions. You flashed root somehow; did you unlock and then relock your bootloader? How did you root? At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
Click to expand...
Click to collapse
I know linux a little bit. Simply as I have written already I've got the root by running SuperOneClick application. Not sure what exploit it uses (perhaps ZergRush).
>did you unlock and then relock your bootloader?
No. As I said, I thought that I can simply move data to eMMC partition while I'm root by dd command. I dunno why I need to unlock and lock the bootloader again.
>How did you root?
Run the SuperOneClick application and clicked the "Shell root" button, then connect to phone through the adb connection, wrote "adb shell" and voila got "#".
>At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
Mmm, could tell me how the bootloader blocks the "dd" command from rewriting data on the eMMC partitions?
Can I download the S-Off tool somewhere, or unlock bootloader somehow else, why the root privileges are not enough here?
I'd like to know more about that.
I don't know anything about SuperOneClick. If it S-Offs your phone you should be fine just fastboot flashing a recovery. Can I see what your hboot says? If your phone in fastboot mode?
It helps that you know Linux. The closest Linux analogy is UEFI v. su rights. Root gives the ROM partition su rights in software. However, the bootloader won't let you flash other stuff to the partitions in hardware. They're separate issues.
EDIT: I just reread your OP. You need to have the recovery.img on your computer, not your phone. Then run fastboot from the folder where that recovery.img is saved.
SuperOneClick is here: http://forum.xda-developers.com/showthread.php?t=803682
Bootloader:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
etc...
Er, you are S-On and your bootloader is locked. Are you sure you have root?
SuperOneClick does nothing for HTC devices, AFAIK its simply designed for root and go Motorola and LG phones... same applies for Gingerbreak v1.20 or 1.5...i cant remember if its 1.2 or 1.5.... S-off is hard to obtain now that AAHK is retired, but there are advanced instructions on the developer of AAHK on his/her webpage
Sent from my Inspire 4G using xda premium
> Er, you are S-On and your bootloader is locked. Are you sure you have root?
Well, I have written already that I have security on and my bootloader is locked.
> SuperOneClick does nothing for HTC devices
why I got shell root with it then?
As I understand the issues:
Root - 'root' is linux super user that has all the privileges, if you are the root you are not limited by OS to do everything you want.
Bootloader lock - you can't flash custom ROMs in the fastboot mode, probably because of the fact that the custom ROM or the custom recovery are not signed
- what does it mean actually that the bootloader is unlocked? That it is rewrited by hacked version of bootloader where sign check is jumped? or I am wrong...
S-ON - hardware lock, probably you can't write to partitions ???
- probably that eMMC is set to be in read only mode by registry settings directly in eMMC chip? Am I right? And it is done in every boot when hw is initialized
As I said, I've got root privileges, so I am root in the Android and I can read from and write to everything in the Android. I've got it by some exploit (ZergRush / Gingerbreak). I'm not sure because it was set to "Auto" in the SuperOneclick app.
My situation:
Ok, I am able to obtain root privileges and I can rewrite eMMC partitions, but it has no effect probably because of S-ON (not sure here, nobody wants to tell me ).
I can't flash recovery through fastboot, probably because clockworkmod recovery is not signed by HTC.
As I understand, I can only follow the AAHK. It means downgrade to lower Android version where it is to possible get S-OFF and then it is possible to get root and rewrite eMMC.
I thought that obtaining the root is enough to rewrite the eMMC without S-OFF and/or unlocked bootloader, simply by rewriting block device in Linux.
AAHK is retired, but you can unlock your bootloader.
Ok.
I used AAHK to downgrade, S-OFF and root. Currently I'm running JellyTime 4.2...
I'm reading for few days now and I'm confused in two things:
1) unlocking bootloader
When using Hasoon2000 All-in-one toolkit I get different token, also fastboot oem get_identifier_token gives every time different token :/
Am I doing something wrong or it is normal?
2) making stock backup
Please correct me if I'm wrong
First I have to unlock bootloader, then I have to run custom recovery with: fastboot boot [TWRP or Philz touch recovery.img it will allow me to backup stock recovery and stock ROM (ROM will be cleaned after unlocking bootloader)
Then flash custom recovery fastboot flash recovery xxx.img
and if I want to have stock rooted flash only supersu or flash custom rom.
Am I right?
Globus.gd said:
I'm reading for few days now and I'm confused in two things:
1) unlocking bootloader
When using Hasoon2000 All-in-one toolkit I get different token, also fastboot oem get_identifier_token gives every time different token :/
Am I doing something wrong or it is normal?
2) making stock backup
Please correct me if I'm wrong
First I have to unlock bootloader, then I have to run custom recovery with: fastboot boot [TWRP or Philz touch recovery.img it will allow me to backup stock recovery and stock ROM (ROM will be cleaned after unlocking bootloader)
Then flash custom recovery fastboot flash recovery xxx.img
and if I want to have stock rooted flash only supersu or flash custom rom.
Am I right?
Click to expand...
Click to collapse
I'm not sure about the identifier token, didn't notice if it gives different tokens or not. Have you actually managed to unlock the bootloader though? You should try and do all these things without using all-in-one toolkits, you'll learn a whole lot more that way, especially when it comes to troubleshooting and fixing your device. It's not as difficult as you think it is. :good:
Yes unlock bootloader. Only Philz/CWM makes backup of stock recovery, TWRP doesn't make a backup of it. Rather use adb to make a backup of stock recovery. Boot the custom recovery of your choice and then flash the SuperSU app to get root or you can use towelroot if it works for your device.
Restart your phone(can go into OS) connect to PC, open command prompt and cd to adb folder.
Code:
adb shell cat /proc/emmc - [B]this will give out a list of all patitions on your device.[/B]
On my device it's in mmcblk0p43 , I'm sure it'll be the same for you as well, can just use above command to make sure. You can also type the command in a terminal emulator on your device if you have one installed cat /proc/emmc
So for my recovery block(Yours probably too) continue in command prompt on PC:
Code:
adb shell
su - [B]to gain super user status, just accept on device when prompted.[/B]
dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img - [B]or[/B]
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img - [B]if you want it on external sd card[/B]
There you made a backup of your recovery partition, you can immediately transfer it to the PC(adb folder) if you want by typing:
Code:
exit - [B]to exit shell prompt and go back into normal adb prompt[/B]
adb pull /sdcard/recovery.img [B](Or of course /sdcard2/ if you used external sd.)[/B]
To pull it to another directory just press spacebar after recovery.img and type in path directory to where you want to pull it.
BerndM14 said:
Have you actually managed to unlock the bootloader though?
Click to expand...
Click to collapse
No, I asked on htcdev why generated token is different every time I use fastboot command,
Hi,
I want to install TWRP so I can Install nAOSP ROM 8.1 for Xperia S on my phone.
The phone's bootloader is unlocked and the phone is rooted. I downloaded the correct version of TWRP from here (nozomi).
I tried installing via ADB (I followed the instructions here), but the command:
Code:
fastboot flash recovery twrp-3.2.3-nozomi.img
Fails with:
Code:
Sending 'recovery' (12964 KB)
(bootloader) USB download speed was 33272kB/s
OKAY [ 0.415s]
Writing 'recovery'
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: 'Partition not found')
Finished. Total time: 0.437s
I understand that this is because Sony phones don't have separate recovery partition, and that their recovery is incorporated to the boot.img (see here).
I then tried using the dd install method as described on the project's homepage.
Code:
$ ./adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
25929+1 records in
25929+1 records out
13275872 bytes transferred in 3.747 secs (3543066 bytes/sec)
Although this seems to work (i.e. I don't get an error message), I cannot, try what I might, make the phone boot into recovery.
Can anyone tell me what I'm missing?
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
_jack said:
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
Click to expand...
Click to collapse
How exactly did u do that...i have spent over a week trying to do it.
sweetbanana said:
How exactly did u do that...i have spent over a week trying to do it.
Click to expand...
Click to collapse
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
_jack said:
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
Click to expand...
Click to collapse
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
ZebastianJV said:
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
Click to expand...
Click to collapse
Try flashtool to install twrp. twrp link: https://androidfilehost.com/?fid=1322778262904003720
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
No, it won't be a problem.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
i had the same issue i just flashed the firmware boot.img with flashtools 0.9.8.0
Extract with 7zip/winrar/winzip. Use this kernel via flashtool. has recovery. note for unlocked bootloaders only
If you try to flash the file misc.bin your device can be in bootloop forever, please follow this guide to fix it.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
VD171 said:
If you boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Communos said:
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Click to expand...
Click to collapse
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase misc partition for stops with bootloop in recovery.
Thanks! If I knew this a few weeks ago it would have been helpful, But I fixed it with MiTool V2
VD171 said:
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase or format misc partition for stops with bootloop in recovery.
Click to expand...
Click to collapse
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Communos said:
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Click to expand...
Click to collapse
As I've said, if you've flashed misc.bin from the outdated TWRP, just flashing stock recovery or stock boot will not fix the problem.
For fixing it, you have to erase misc partition. If it doesn't help you, please, go away and let it help who wants help.
Nice job and see you later.
VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to format misc partition:
Code:
fastboot format misc
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
thanks sooo much
imranbinlatif said:
thanks sooo much
Click to expand...
Click to collapse
Good job, my friend.
You are welcome
VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
Click to expand...
Click to collapse
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
If you have access to fastboot and erasing misc did not work, simply flash the entire stock rom you were on through MiFlash.
TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
Erasing misc only works if you are frozen in a black screen after flashing misc partition.
Recovery partition can't break boot.
Probably your problem is vbmeta.
Vbmeta can break the boot.
Did you flash it too?
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
TheMagnificent_Y said:
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
Click to expand...
Click to collapse
Misc partition is not present in original stock rom.
It contains a variable data/parameter for boot.
Did you solve the bootloop after flash full rom?
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
TheMagnificent_Y said:
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
Click to expand...
Click to collapse
You need to avoid the misc partition.
If you've flashed it, you REALLY need to erase it.
Or, it will make your device to enter in recovery forever.
Vbmeta needs to be flashed with disababled verification.
Here you can find safe and secure vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
Or, it will detect modification on partitions and will reboot the device forever.
I think Opt doesn't change anything.
I'm not sure, but I think it only matter for devices without vbmeta partition. (I'M NOT SURE.)
Because it modifies the system, and obviously you will get in a bootloop.
If you want to modify the system, you need to debloat your system before.
Try to flash the whole system again.
Or just try to flash the whole rom again.
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
PS: I tried flashing the un-official and official versions, both leave a brick, and nothing really changes, i haven't tried your "Patched" version tho.
TheMagnificent_Y said:
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
Click to expand...
Click to collapse
I'm not sure.
Just flashing the system should solve it.
Or just flashing the whole rom using the flashing scripts inside the original stock rom.
Vbmeta checks if boot, recovery and dtbo partitions keeps untouched and unmodified.
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
TheMagnificent_Y said:
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
Click to expand...
Click to collapse
Flashing the whole stock rom, certainly solves everything.
And then, if you want TWRP again, try this first: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
Good luck
hello , i upgraded my device from android 10 to android 11 from smart switsh after update is done the imei is 00000000 and model number is none tried to downgrade back to android 10 didnt work downloaded official firmware from samobile still imei 000000000
rooted the phone tried to fix imei in chimera tool not work
and model none plz help
solyvski961 said:
hello , i upgraded my device from android 10 to android 11 from smart switsh after update is done the imei is 00000000 and model number is none tried to downgrade back to android 10 didnt work downloaded official firmware from samobile still imei 000000000
rooted the phone tried to fix imei in chimera tool not work
and model none plz help
Click to expand...
Click to collapse
First of all, do you have efs backup? If so try to restore it with latest twrp.. If not.. then.. I am not responsible for unsuccessful commands.. yet, how worse can it be?
Boot into TWRP recovery.
From TWRP’s main screen, select Advanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Or you can use bootloader and adb
Setup adb and fastboot to your pc.. (google or xda it)
Enable usb debugging in developer options (google again if u dont know)
Then with command prompt using adb and fastboot.
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Good luck..
myaslioglu said:
First of all, do you have efs backup? If so try to restore it with latest twrp.. If not.. then.. I am not responsible for unsuccessful commands.. yet, how worse can it be?
Boot into TWRP recovery.
From TWRP’s main screen, select Advanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Or you can use bootloader and adb
Setup adb and fastboot to your pc.. (google or xda it)
Enable usb debugging in developer options (google again if u dont know)
Then with command prompt using adb and fastboot.
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Good luck..
Click to expand...
Click to collapse
thanks for your reply
step1 not working
step 2 after
fastboot erase modemst1 it stuck on erasing modemst1...
my samsung must be rooted?
You need to tag a moderator and or report your post. And please post in the correct forums
Flash latest stock firmware with Odin
GeeAyeZee said:
Flash latest stock firmware with Odin
Click to expand...
Click to collapse
not work
myaslioglu said:
First of all, do you have efs backup? If so try to restore it with latest twrp.. If not.. then.. I am not responsible for unsuccessful commands.. yet, how worse can it be?
Boot into TWRP recovery.
From TWRP’s main screen, select Advanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Or you can use bootloader and adb
Setup adb and fastboot to your pc.. (google or xda it)
Enable usb debugging in developer options (google again if u dont know)
Then with command prompt using adb and fastboot.
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Good luck..
Click to expand...
Click to collapse
erasing 'modemst1'...
FAILED (status read failed (Too many links))
finished. total time: 221.570s
solyvski961 said:
not work
Click to expand...
Click to collapse
chimeratool can do it, but its a paid service. Ive got a license for it, its well worth paying for.
GeeAyeZee said:
chimeratool can do it, but its a paid service. Ive got a license for it, its well worth paying for.
Click to expand...
Click to collapse
i tried chimera tool i paid 95$ for 1 year license didnt work repair imei and patch certificate
solyvski961 said:
i tried chimera tool i paid 95$ for 1 year license didnt work repair imei and patch certificate
Click to expand...
Click to collapse
Then you should be contacting them for help