Database Info

BEST downgrade HBOOT 2.00.0002 to 0.98.XXXX this way removes the ***re_locked***

Mod Edit.

Thank for giude but i can find RUU for my HTC Ds

hoanglamtong said:
thank for giude but i can find ruu for my htc ds
Click to expand...
Click to collapse
RUU's on 1st post now mate loads 2 pick from

anyone sucessfully used my guide?
Can anyone who has successfuly used my guide to downgrade please post why u think if my guide an how u think it could be made better. And say if u think its better than the other guides and why thanks very much. Have a good evening all.

ok, here is a success story with a minor modification...
i unlocked my device via htcdev, and rooted it also so i just did:
downloaded http://rapidshare.com/files/6806934...0805U_38.03.02.11_M_release_177977_signed.rar
- adb push misc_version /data/local/tmp
- adb shell chmod 777 /data/local/tmp/misc_version
- adb shell /data/local/tmp/misc_version -s 1.27.405.6
then rebooted to bootloader (power off, power+vol down) and
- fastboot oem lock
this reported error, but device was relocked
right click / run as administrator ruu (still in bootloader)
ruu installation went smoothly and now device is:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Just to save my fellow noobs trouble:
-bootloader must be locked before installing ruu!
-i have read somewhere that if you use custom rom when re-locked your device WILL NOT BOOT, so do this only if you know what you are doing
-when using Win7 you can start CMD in specific folder (avoid 5-10 cd's or long/path/to/folder) by holding shift+right click/open command window here)
paul.robo, thanks again, especially for trouble of gathering all those ruus!

No problem mate good to see my guides helping people can u confirm that the **re locked** at the top of the screen has gone ?

yes! no "re-locked", "locked" or "unlocked", i copied text in bootloader "as is" from top of the screen to time and date.

Htcdev.com guide aded now guys :d
The guides up now and for htcdev.com unlocked bootloaders please use the attatchment in the 1st post. If u unlocked with htcdev.ciom i assumed u got root access there for u dont need to use the zergrush method you can just push the misc_version to your saga and change it. If u need anymore help jjust pm me .

Thanks Paul, your guide worked perfect where the others failed

Dear paul.robo,
HBOOT-0.98.0000 is not supported by htcdev unlocker and therefore we can not see re-locked or whatever in bootloader but even after you get back to stock your phone is officialy out off warranty.
I can add one think for those who get in to a trouble with RUU installer.
You can use rom.zip en flash it like described below:
Start your phone after all the steps with misc_version and hboot in bootloader "Fastboot USB" mode.
Step 1: On you computer in "cmd" run fastboot oem rebootRUU you will be presented with black screen on your phone.
Step 2: On your computer in cmd run fastboot flash zip rom.zip.
It is possible that after first reboot it will not go further then bootloader and stay in "Fastboot USB" mode then follow Step 1 and 2 again then it will install the whole rom and reboot your phone into normaal mode.

Help,hboot 2.00.0002
I am on mac , can u help me please ? I am new to all these

I downgraded my Phone successfully using this. My Phone if from FET TW region.
While the downgrade works & you return to S-ON & Locked as default settings, the moment you upgrade to 2.3.5 FOTA Update Your bootloader becomes Relocked..
Just some thing to note before you use this..
Great Guide and restored my phone to stock back..

Giorgio89 said:
I am on mac , can u help me please ? I am new to all these
Click to expand...
Click to collapse
its the exact same use all the same commands as you would on a windows pc. i have done this on my hackintosh and my windows 8 pc both works, also on ubuntu is same

Huh
Thanks man , I guess I gotta try harder ...

Giorgio89 said:
Thanks man , I guess I gotta try harder ...
Click to expand...
Click to collapse
how are you stuck mate ?

paul.robo said:
how are you stuck mate ?
Click to expand...
Click to collapse
I don't really know to tell the truth ...
Consider me as a small child learning the alphabet right now
I open the terminal , then I drag the folder with the name "downgrade".
after that I type the commands you write and I get this :
Last login: Sun May 6 01:32:21 on ttys000
G.H.-iMac:~ goneis$ /Users/goneis/Desktop/DOWNGRADE.SAGA.AND.GUIDE adb push misc_version /data/local/tmp
-bash: /Users/goneis/Desktop/DOWNGRADE.SAGA.AND.GUIDE: is a directory
G.H.-iMac:~ goneis$ adb shell chmod 777 /data/local/tmp/misc_version
-bash: adb: command not found
G.H.-iMac:~ goneis$ adb shell /data/local/tmp/misc_version -s 1.27.405.6
-bash: adb: command not found
G.H.-iMac:~ goneis$
thanks again for your time ...
Also would you mind making a more analytical guide for osx ?
Baby steps -guy here

Giorgio89 said:
I don't really know to tell the truth ...
Consider me as a small child learning the alphabet right now
I open the terminal , then I drag the folder with the name "downgrade".
after that I type the commands you write and I get this :
Last login: Sun May 6 01:32:21 on ttys000
G.H.-iMac:~ goneis$ /Users/goneis/Desktop/DOWNGRADE.SAGA.AND.GUIDE adb push misc_version /data/local/tmp
-bash: /Users/goneis/Desktop/DOWNGRADE.SAGA.AND.GUIDE: is a directory
G.H.-iMac:~ goneis$ adb shell chmod 777 /data/local/tmp/misc_version
-bash: adb: command not found
G.H.-iMac:~ goneis$ adb shell /data/local/tmp/misc_version -s 1.27.405.6
-bash: adb: command not found
G.H.-iMac:~ goneis$
thanks again for your time ...
Also would you mind making a more analytical guide for osx ?
Baby steps -guy here
Click to expand...
Click to collapse
lol right open terminal ( go into applications then at the bottom there will be app called terminal open it and type cd then make sure u put a space after u type cd then after you type that drag my folder into the terminal then press ENTER once you done that type all commands 1 by 1 okay
my other downgrade threads here http://forum.xda-developers.com/showthread.php?p=25717156#post25717156

paul.robo said:
lol right open terminal ( go into applications then at the bottom there will be app called terminal open it and type cd then make sure u put a space after u type cd then after you type that drag my folder into the terminal then press ENTER once you done that type all commands 1 by 1 okay
my other downgrade threads here http://forum.xda-developers.com/showthread.php?p=25717156#post25717156
Click to expand...
Click to collapse
this time I get this :
Last login: Sun May 6 01:13:35 on ttys000
G.H.-iMac:~ G.H.$ cd
G.H.-iMac:~ G.H.$ cd /Users/G.H./DOWNGRADE.SAGA.AND.GUIDE
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$ adb push misc_version /data/local/tmp
-bash: adb: command not found
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$ adb shell chmod 777 /data/local/tmp/misc_version
-bash: adb: command not found
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$ adb shell /data/local/tmp/misc_version -s 1.27.405.6
-bash: adb: command not found
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$
:/

Giorgio89 said:
this time I get this :
Last login: Sun May 6 01:13:35 on ttys000
G.H.-iMac:~ G.H.$ cd
G.H.-iMac:~ G.H.$ cd /Users/G.H./DOWNGRADE.SAGA.AND.GUIDE
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$ adb push misc_version /data/local/tmp
-bash: adb: command not found
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$ adb shell chmod 777 /data/local/tmp/misc_version
-bash: adb: command not found
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$ adb shell /data/local/tmp/misc_version -s 1.27.405.6
-bash: adb: command not found
G.H.-iMacOWNGRADE.SAGA.AND.GUIDE G.H.$
:/
Click to expand...
Click to collapse
right im going to go onto my mac and ill make a file that will do it for you. ill PM u when ive done it mate okay did u try my other guide ???? its here http://forum.xda-developers.com/showthread.php?p=25717945#post25717945
when u download it unzip it drag the folder onto your desktop open up terminal and drag the Desire Downgrade Kit.bat file into your terminal and press enter

paul.robo said:
right im going to go onto my mac and ill make a file that will do it for you. ill PM u when ive done it mate okay did u try my other guide ???? its here http://forum.xda-developers.com/showthread.php?p=25717945#post25717945
when u download it unzip it drag the folder onto your desktop open up terminal and drag the Desire Downgrade Kit.bat file into your terminal and press enter
Click to expand...
Click to collapse
I connected the phone with the mac , entered it on debug mode . Used your other guide , entered the .bat file on the terminal and all I got was command not found ... ( I guess I have to wait for the file )

[Q] Cant get kindle fire into fastboot

Ive been trying out pokey'9000 [fastboot] stock 6.2.1 fastboot mode without rooting or cables to get my kindle fire into fastboot, I typed in the"adb shell " command and get:
"[email protected]: $" so i guess adb is working I then follow the next step,
"adb push fbmode /data/local/tmp"
and get:
"942 KB/s (510876 bytes in 0.529s)" then:
"adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode"
but just after this final line I get:
"fail opening shift: No such file or directory"
My kindle is rooted and has superuser access already but I cant get it into fastboot mode, also tried:
" adb shell su -c 'idme bootmode 4002' "
and get :
" Reading idme data...
Setting bootmode to 4002
writing new vars to temp area
you must reboot before new values will take efect "
I reboot my kindle bust still cant get into fastboot. What could I possibly be doing wrong?

[resolved] Help for thread [6039y] **GUIDE** Repartitioning of the internal memory

Problem solved, by using an other usb adb driver, instead of universal adb driver ; thx petrov.0
Hi, sorry for my bad english,
I've trouble to understand what's wrong or I miss : want to run the 1st command umount /cache at the 4th step (unmount all partitions of the internal memory )
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ umount /cache
umount /cache
failed: Operation not permitted
1|[email protected]:/ $​
Actually the phone are root, TWRP v2.8.6.0 by decker. I've also swap with twrp-2.8.7.0-idol3-6039y-with-gdisk instead of just run it one time : same trouble, Operation not permitted
Any idea ?
Just to be sure, when it writing go to device, we are under the TWRP -> Reboot -> System ... and we go to android ? And at this point I run adb shell, that ok ?
I would also say, that my first smartphone / 1st root / 1st trying

Ok I've discover what's wrong
Need writing on the commande line : adb shell su
SuperSu on the phone ask me an authorization about "adb shell", of course I say yes
Now i can see :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su
[email protected]:/ #​
Symbol and "user" have change
shell --> root
$ --> #​
Hope now all clear for the next step.
Unfortunaly, it's not to seem that, now I can't writing any caractere in command line
Have try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # gdisk
gdisk
tmp-mksh: gdisk: not found
127|[email protected]:/ #​
umount /and-sec directory not found
gdisk not works
...help !

You shouldn't reboot the device. Everything must be done while the phone is in the recovery.

Not sure to understand you
When i'm under TWRP, writing in command line adb shell --> error: device not found
I really need you can detail step by step until there.

bykarat said:
Not sure to understand you
When i'm under TWRP, writing in command line adb shell --> error: device not found
I really need you can detail step by step until there.
Click to expand...
Click to collapse
You do this from Windows, so you need drivers which recognize your device when is in the recovery. I'm not sure which drivers work with the phone. The vendor and the product IDs for the recovery are
Code:
idVendor=18d1, idProduct=4ee2

Yes the problem come from the usb driver, you have good see., despite the id vendor & product number are good
img15.hostingpics.net/pics/282113Sanstitre2.png​When I follow an tutorial for rooting, it mention to install "Universal adb driver", enought for that, but not for your Guide "Repartitioning of the internal memory"
Have use those ones of : (can't add link in this forum at this time) 54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_%20Driver%20Qualcomm_ADB.rar
I want to say lots of thank you for all that :victory:

bykarat said:
Yes the problem come from the usb driver, you have good see., despite the id vendor & product number are good
img15.hostingpics.net/pics/282113Sanstitre2.png​When I follow an tutorial for rooting, it mention to install "Universal adb driver", enought for that, but not for your Guide "Repartitioning of the internal memory"
Have use those ones of : (can't add link in this forum at this time) 54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_%20Driver%20Qualcomm_ADB.rar
I want to say lots of thank you for all that :victory:
Click to expand...
Click to collapse
Glad to see that you made it. There is a thanks button by the way . I will include the link to the drivers in the guide.

[HELP] Need help running command 'fastboot erase modemst1' on Pixel 5

After the March security update my Pixel 5 is not receiving any mobile network and i am not able to turn on radio power via the *#*#4636#*# command.
After googling for a solution i found similar posts which suggested resetting the modemst1 and 2 partitions
Tried running the following commands in adb but was unable to
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
For fastboot I used the following commands
Code:
fastboot erase modemst1
fastboot erase modemst2
which gave me an error
Code:
FAILED (remote: Not allowed to erase (modemst1))
I'm also not able to boot into adb root but i am able to run adb shell su
I tried installing adbd insecure which was unable to patch adbd and also installed an adb_root module in magisk which still failed to initialize adb root
Currently I'm running ProtonOS on my Pixel 5. I thought running a custom rom might help but the problem still persists
Please help

Hi.
I would suggest making a back up before you erase a partition in case you need to restore it.
Make sure to name the backup clearly so you know what it is.
Since you do not have adb root, you need to run the command as root using su -c "NameOfCommand".
If you boot into a custom recovery, you generally have adbd and do not need to use the su -c option.
Also double check your path, you should be able to call it from /dev/block/by-name.
or list by-name, ls -la /dev/block/by-name/ and call it from the true partition number.
Example of making a backup.
Dump the partition(s) into an image.
Code:
adb shell su -c "dd if=/dev/block/by-name/modemst1 of=/sdcard/redfin-modemst1.img"
adb shell su -c "dd if=/dev/block/by-name/modemst2 of=/sdcard/redfin-modemst2.img"
Copy the image(s) to computer.
Code:
adb pull /sdcard/redfin-modemst1.img
adb pull /sdcard/redfin-modemst2.img
Delete the image(s) from the device.
Code:
adb shell rm /sdcard/redfin-modemst1.img
adb shell rm /sdcard/redfin-modemst2.img
You need to be in fastbootd to modify critical partitions.
adb reboot bootloader will reboot into fastboot.
adb reboot fastboot will reboot into fastbootd.
You can do the same in fastboot/fastbootd
fastboot reboot bootloader will reboot into fastboot.
fastboot reboot fastboot will reboot into fastbootd.
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Good luck.
Cheers.

ipdev said:
Hi.
I would suggest making a back up before you erase a partition in case you need to restore it.
Make sure to name the backup clearly so you know what it is.
Since you do not have adb root, you need to run the command as root using su -c "NameOfCommand".
If you boot into a custom recovery, you generally have adbd and do not need to use the su -c option.
Also double check your path, you should be able to call it from /dev/block/by-name.
or list by-name, ls -la /dev/block/by-name/ and call it from the true partition number.
Example of making a backup.
Dump the partition(s) into an image.
Code:
adb shell su -c "dd if=/dev/block/by-name/modemst1 of=/sdcard/redfin-modemst1.img"
adb shell su -c "dd if=/dev/block/by-name/modemst2 of=/sdcard/redfin-modemst2.img"
Copy the image(s) to computer.
Code:
adb pull /sdcard/redfin-modemst1.img
adb pull /sdcard/redfin-modemst2.img
Delete the image(s) from the device.
Code:
adb shell rm /sdcard/redfin-modemst1.img
adb shell rm /sdcard/redfin-modemst2.img
You need to be in fastbootd to modify critical partitions.
adb reboot bootloader will reboot into fastboot.
adb reboot fastboot will reboot into fastbootd.
You can do the same in fastboot/fastbootd
fastboot reboot bootloader will reboot into fastboot.
fastboot reboot fastboot will reboot into fastbootd.
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Good luck.
Cheers.
Click to expand...
Click to collapse
Hello, I hope you will see this text. As you have mentioned, I have rebooted my Pixel 5 to fastbootd but I cannot erase any critical partition. for example, when i run fastboot erase cache OR fastboot erase modemst1, i get the same error message saying FAILED (remote: 'Partition doesn't exist'). Would you mind helping me? I would appreciate it a lot. Thank you.

Adb and fastboot list

ADB Commands​
Adb Install app remotely
adb install appname.apk
Adb pull file
adb pull <path-of-the-file> (on device e.g. /system/app/Settings.apk)
Adb push file
adb push <source-path> <target-path> (/local/path/Reddit.apk /sdcard/apps/)
Adb Check devices
adb devices
Adb boot into bootloader
adb reboot-bootloader
Adb boot into recovery
ADB reboot recovery
Adb Sideload
adb sideload filename.zip
Adb start server
adb start-server
Adb kill server
adb kill-server
Adb shell command
adb shell "<command>"
Adb install apk
adb install filename.apk
Adb re install apk
adb install -r filename.apk
Fastboot Commands​
Fastboot check devices
Fastboot devices
Fastboot flash image file
fastboot flash recovery filename.img
Fastboot flashing boot.img
fastboot flash boot
Fastboot flash radio file
fastboot flash radio radio.img
Fastboot reboot device
fastboot reboot
Fastboot enter recovery
fastboot reboot recovery / fastboot boot twrp.img (a/b partition devices)
style='mso-bidi-font-weight:normal'>
Fastboot bootloader
fastboot reboot bootloader

Noticed that among others the most important ADB command
adb shell "<command>"
what opens a terminal shell and let you e.g. run Linux-commands / scripts is missing.
See also here:
Adb useful commands list
Adb useful commands list. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

jwoegerbauer said:
Noticed that among others the most important ADB command
adb shell "<command>"
what opens a terminal shell and let you e.g. run Linux-commands / scripts is missing.
See also here:
Adb useful commands list
Adb useful commands list. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
Thanks added