Related
hi,my htc got stuck logo.i format my desire z with no backups.i unlocked bootloader with htcdev.com........temp root.....S-on..........nothing flashing any Rom...neither custom roms..Nor default roms.....plzzzz help....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
klassikkamii said:
hi,my htc got stuck logo... ....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
Click to expand...
Click to collapse
Hello,
I am not sure If someone can help in this case.
Please provide more information.
* Do you confirm, that you cannot boot in recovery from HBOOT?
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
When only fastboot is working then I only see a little chance for your phone when you have an engineering HBOOT.
Best regards,
Catherall
P.S: Seems like you really tortured you helpless Desire Z
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
More Detail are,
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
emmc-boot
Dec 20,2011,16:21:13
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.i flashed Villision1.0 ,Android_Revolution_HD-4G_7.0.3,C7 succesfully but never start normally just stuck in logo.i use also fastboot flash boot boot.img as well but nothing happened.same stucking.when i use adb commands or adb shell ,getting error device not found.plzz give me back earlier position as company setting it was gingerbread 2.3.3.
i am sorry abount my low english language capabality.
Get your phone back on track with proper unlocking (S-OFF)
klassikkamii said:
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.
Click to expand...
Click to collapse
Two things are not clear to me:
1) How did you "unlock" you phone, did you use http://htcdev.com/bootloader/ method to get "****Unlocked****" in HBOOT? This is important to know for me.
When you indeed unlocked using http://htcdev.com/bootloader/ method, then you have to install an suitable "boot.img" every time you flash a new ROM.
Otherwise the old boot.img tries to boot the old ROM that was overwritten with the new one you flashed.
2) When you can boot ClockworkMod Recovery then you can connect using adb. Just use adb while booted into your custom recovery.
I really recommend to proper unlock your HTC Desire Z as described in
http://goo.gl/aXNr
The advantage of this method is, that you can flash any custom ROM without the need to flash the kernel of the ROM (boot.img) separately!
ATTENTION: Before doing anything like "fastboot oem lock"
you have to use "misc_version 0.1" and "flashgc". Do not continue without that!
When you do not know how to use that then ask (here or in freenode IRC channel #G2ROOT)!
Then you can go on to downgrade your phone:
[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1178912
Please make sure that you follow the steps described under the topic ***If you have used the "official" htcdev.com unlock option***
Then you can gain S-OFF (real unlock) using gfree
If you have questions then come to the awesome freenode IRC channel #G2ROOT.
Best regards,
Catherall
yes i unlocked with htcdev.com,so i will lock it again with "fastboot oem bootlock" command and will try to unlock as your advice.
i am so happy after seeing your advices.and i didn't know that i can use adb shell in recovery.you mean boot in recovery than use adb terminal from pc.ok i check it and try to apply it.and thankyou very much again for your help.
I will tell you results.
Attention
Before using fastboot oem lock make sure that downgrade would work.
Run the commands "misc_version 0.1" and "flashgc" successfully before doing anything like
fastboot oem lock!
Visit freenode IRC channel #G2ROOT
I am not 100% sure what happens on your semi-bricked phone with fastboot oem lock!
Best regards,
Catherall
one more plzz
ok i will make sure but plzzz tell me can i restore officialy stock rom with adb support ( may be with golcard support ) sothat i dont wanna take any risk.no downgrade,no s-off just my previous position.
I went to #G2Root but i didnt understand how talk anybody.i am not familiar on that.again thxx for your attention for me.
P.E : ok i tried adb commands while booted in recovery. adb devices command works and show serial number, but when i command ' adb shell ' got " # " instead " $ " so stuck again need more advice plzzzzzzzzzzzz.how can get " $ "
PLssss Help
i am getting " ~ # " Error in adb shell please helppp....
Options for S-OFF/root or reverting to Stock
Hello klassikkamii,
most custom Recoveries provide root access when you use "adb shell" to connect to them.
So adb shell returns "#" to indicate root access. When you get the prompt "$" then you have access as a user.
I would do the following steps. They allow you to get full S-OFF, Engineering HBOOT and a ROOTed ROM, or if you prefer return to stock ROM.
Returning the latest stock is much easier and safer when you do the following steps to change the internal software version number of the phone an make your SD card a goldcard.
Download misc_version 0.1:
http://forum.xda-developers.com/attachment.php?attachmentid=661216&d=1311237785
Download flashgc:
http://forum.xda-developers.com/attachment.php?attachmentid=819704&d=1324116910
And then use the following procedure to change version number and make a goldcard (as provided by Setherio in his guide [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo:
1) Unzip misc_version_01.zip and flashgc.zip in the platform-tools directory.
2) Run the following commands from you platform-tools directory:
Code:
adb shell mount /data
adb push misc_version /data/local/tmp/misc_version
adb push flashgc /data/local/tmp/flashgc
adb shell chmod 777 /data/local/tmp/*
adb shell
Now you are in the phone shell with root access (indicated by the prompt "#").
Continue with the commands:
Code:
cd /data/local/tmp
./misc_version -s 1.00.000.0
This should return:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Continue to make you SD card a goldcard:
Code:
./flashgc
Note: If you get the following error, please make sure your sdcard is inserted in your phone: Error opening backup file.
Continue with the command
Code:
sync
Double check that you phone's software version number is set to 1.00.000.0 with the command:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
The first line of the command output must be:
1.00.000.010+0 records in
Exit the phone's shell with
Code:
exit
From here you can get an Engineering HBOOT and a custom, rooted ROM, or revert to a stock ROM. Both ways are about the same effort.
Please post how this worked out for you.
Best regards,
Catherall
still stuck
adb push misc_version /data/local/tmp/misc_version
Getting Error
failed to copy 'misc_version' to /data/loca/tmp/misc_version :Not a directory
As i am already with "~ #" i try direct command :cd /data/local/tmp
Got Error This :/sbin/sh: cd:can't cd to /data/local/tmp
if i use command for sd card,
adb push misc_version /Sdcard/misc_version
it show size of file or push succed but not in local/tmp.
i think if i would get "$" instead " ~#" May be i can do all u advice me.
Better do it interactive
Hello,
there might be several reasons why the command did not work.
Not having "$" is none of them.
Please come to freenode IRC and login to channel #G2ROOT. Ask for Catherall, I should be there for the next hours. When I am not there then check back later.
Best regards,
Catherall
ok i solved all Puzzle.solution was only use " GoldCard Method".i use command mmc2 instead mmc1 and voilaaaaaa i got my CID then everything was eassy.....in the End i really thanks to Catherall,You help me well...your information was helpfulln from your instructions i got my way thanksssss...
Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways
Hi There
So, I normally obtain adb root by the following process:
1. Unlock the Bootloader (if required)
2. Use fastboot to OEM unlock the boot loader
3. Get the boot.img and upack it
4. Change ro.secure=0 and ro.debbugable=1 in default.prop
5. repack boot.img
6. flash boot.img to device
7. Boot up device, ensure USB debugging is enable.
8. Then use adb root, adb remount rw and I usually always get adb root this way. So I can "adb shell" and I have a # root prompt.
However I think I have always had the ENG or DEBUG builds of the OS when I did this.
So I now only have a USER build of the OS.
I follow the above procedure but it doesn't matter how many times I change the ro.secure and ro.debggable settings , they are always locked. They must be being set somewhere else?
So I heard that this is normal for USER builds, the build simply does not allow access to ro.secure=0.
My questions are:
1. Is what do I need to change in the USER build of my OS or boot.img to get ro.secure=0 working?
2. Is it even possible?
3. Failing this, can you get generic DEBUG/ENG boot.img's for MTK 6755 devices?
Hello everyone, a year ago a I had installed a custom recovery on my Lenovo S5000-F and it caused a bootloop and I lost the recovery, fastboot is working fine but it only allow me flash boot, system, userdata and cache partitions. I already tried do:
1-Unpack boot.img
2-Edit default.prop to allow adb debugging and then create a custom OTA update to install by adb sideload.
But when I boot the system I get device offline. So looking through system.img I found an interesting thing, a flash recovery script: install-recovery.sh
Bash:
#!/system/bin/sh
echo 1 > /sys/module/sec/parameters/recovery_done #tony
if ! applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:boot:5781504:94079a17dc0e061e417363e4d44d7d8d0e609f16 EMMC:recovery b1d3582729e0f954b16931a7a87d4c09b6854396 6156288 94079a17dc0e061e417363e4d44d7d8d0e609f16:/system/recovery-from-boot.p
if applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then #tony
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image completed"
else
echo 2 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image not completed"
fi
else
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Recovery image already installed"
fi
This script means to replace any recovery installed by the user to the original one, but for some reason its not working.
So I would like to know if there is any way to flash a recovery partition through a script, so I can write this script to init.rc to install the stock recovery and fix bootloop.
EDIT: The install-recovery.sh had installed the stock recovery but I didn't noticed lol, the cause of bootloop is because the recovery and logo partitions its in the same file so when I flashed TWRP with a size bigger than my recovery partition it wrote to logo partition too.
Solved by creating a custom script using the same "applypatch" binary to flash the logo partition and worked fine
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Pachacouti said:
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Click to expand...
Click to collapse
But I can't flash stock booloader, fastboot only flash boot, system, userdata and cache partitions, since I can flash boot I can make a modified init.rc script to flash the stock recovery during boot time, but I don't know how to do this :/
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Pachacouti said:
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Click to expand...
Click to collapse
Oh I got it now, you mean flashing stock bootloader into boot partition so when I turn on the device it will be on bootloader, I can try it but there's another problem, I don't have the stock bootloader lol
GO get it then lol...
Pachacouti said:
GO get it then lol...
Click to expand...
Click to collapse
Unfortunately I didn't found the bootloader, but I tried flash the stock recovery into boot partition, but when I reboot the device boots into grey screen and then shutdown. I have no idea why this not worked :/ I already tried boot the recovery through fastboot but its just transfer the recovery.img and not boot.
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
akram0010 said:
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
Click to expand...
Click to collapse
Assuming that the bootloader is unlocked.
aIecxs said:
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
Click to expand...
Click to collapse
Sorry i forgot to mention, but still unlocking bootloader doesn't root device.
I think the question is still valid
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Is root needed
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Can you please tell me what is this recovery.img, and where would i get it (in Fastboot rom or recovery rom).
As i said earlier i am a newbie in this field and very much confused with these terms.
no root required click on the first link above and download TWRP for your device (TWRP-3.4.2.b_lancelot.zip)
I assume you are running windows?
extract zip file and place recovery.img on your PC in platform-tools directory. connect phone in fastboot mode, install android_winusb.inf "Android Bootloader Interface" drivers and from cmd.exe check fastboot devices
if you can see device serialno you are ready to boot TWRP from fastboot with above first command.
for linux just install android-tools-fastboot
As i am using Ubuntu i installed ADB, FASTBOOT using the APT :
Code:
sudo apt install android-tools-adb android-tools-fastboot
.
Therefore i don't have the platform-tools directory.
Also I am unable to quote reply, its showing error (Oops, we broke the Matrix, someone call Neo)
yes that's right. it doesn't matter which directory files are placed. that way you installed fastboot binary is already in PATH. linux is far more easier and doesn't require additional drivers. it might require additional udev rules to make fastboot work, but you can simply by-pass with sudo fastboot for now...