Related
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
reaper24 said:
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
Click to expand...
Click to collapse
Sorry, update the status apologize for the mistakes
Any expertise?
Helpppppppppppppppp pleaseeeeeeeee!!!!!!!!!!!!!!!!!!!!! (((
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
I am having something close to that issue. i have Hboot 1.49.0008 it is Unlocked but with s-On
now i can boot farther then the htc white. mine goes to the htc + quietly brilliant screen. then hits a boot loop.
what are my options and how do i do it?
thanks
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
ok...then what can I do to fetch the data out or save my phone?
Nokiawithandroid said:
ok...then what can I do to fetch the data out or save my phone?
Click to expand...
Click to collapse
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
megabiteg said:
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
Click to expand...
Click to collapse
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Nokiawithandroid said:
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Click to expand...
Click to collapse
You posted this same question in a separate thread: http://forum.xda-developers.com/showthread.php?t=1525176
In an effort to keep the threads organized, I answered in that thread as follows:
Background on system.img: The system partition is generally only distributed in the system.img format for stock system images. Most aftermarket ROMs perfer to distribute their system content in the form of an update .zip file.
Background on bootloader: The system.img can't be flashed until you unlock the device. This is a standard security feature on any device with a "locked" bootloader, as yours shows from the information you posted.
One option: Once the bootloader is unlocked, the command should be as simple as: fastboot flash system c:\system.img
Hope that helps. Good luck!
Click to expand...
Click to collapse
Not sure how many times this can be repeated or how many different ways the same thing can be repeated. Without unlocking the device, HTC will not allow you to selectively modify any of the partitions from the bootloader or fastboot.
With these three conditions:
1) Without unlocking the device
2) Having the device freeze on the HTC splash screen
3) Never having previously loaded a custom recovery
The only option HTC provides is to run the RUU which will return the device to 100% stock erasing all information currently on the device.
If you're able to unlock the device (condition #1), you would be able to either flash a custom recovery (condition #3), or a stock/new system.img which would allow you access to the device where you can retrieving the stored SMS and MMS.
Using the stock RUU should resolve condition #2, if it didn't, there could be a more serious hardware issue with the device.
I might have missed some aspect. I'm sure somebody will post up if I did.
Hope that helps make more sense!
Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Good to see you here!
I am not sure if memory is locked to bootloader
I dont think so because ics changed the system partition size
We cant edit the .sin files in a .ftf
Sony included a file which contains a long key (like a long md5) which is unique
We cant fastboot boot. ..:... It is not included in the bootloader
If you need any info pm me
Sent from my LT22i using xda app-developers app
Hey Nicholtus!
Thanks for the reply!
So ICS upgrade changed partition layout ? On which model ? And upgrade preserved data or is it a global format ?
You're sure about fastboot boot ? Because it's doing something on Xperia S. Kernel doesn't boot, but something starts as device get stuck, so I was thinking that maybe I was not doing it the right way.
And system ext4, any idea ?
Regarding sin, I know about signature and that we have no way to bypass it.
Hi,
Layout is changed on the xperia s
I thought it was the system partition
If we find a way to bypass the sin header we can re partition the phone
I heard from DooMLoRD that the fastboot boot option is not included
Sent from my LT22i using xda app-developers app
letama said:
Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Click to expand...
Click to collapse
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
munjeni said:
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
Click to expand...
Click to collapse
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
I should ask that someday on sony forum I guess.
Regarding the extract of ics, I solved the issue since then, the issue was an incomplete understanding of sin format. Since that time, I wrote a tool that can directly extract sin properly and Androxyde introduced similar changes in recent releases of FlashTool, so now it can be all done on PC without having to flash and dump.
I saw also your investigation regarding boot partitions, isn't the second one the one used for fotakernel ?
Just in case you want to look into this, don't bother if your bootloader is similar to Xperia S . I wanted to use it to have a second kernel for recovery, but after looking at bootloader, booting from this partition is blocked by bootloader as soon as you unlock your bootloader.
This is why I came to this, three different kernels boot with one dedicated to recovery .
letama said:
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
Click to expand...
Click to collapse
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
munjeni said:
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
Click to expand...
Click to collapse
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
Click to expand...
Click to collapse
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
munjeni said:
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
Click to expand...
Click to collapse
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
letama said:
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
Click to expand...
Click to collapse
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
K900 said:
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Click to expand...
Click to collapse
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
munjeni said:
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
Click to expand...
Click to collapse
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
letama said:
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
Click to expand...
Click to collapse
Fastboot is actually open source in AOSP.
K900 said:
Fastboot is actually open source in AOSP.
Click to expand...
Click to collapse
Yes, but I was looking for hidden/unknown oem commands, found known
Is bootloader partition locked? We can write to him by dd?
munjeni said:
Is bootloader partition locked? We can write to him by dd?
Click to expand...
Click to collapse
The bootloader is not stored on the eMMC.
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Wow. We've got an expert here.
K900 said:
The bootloader is not stored on the eMMC.
Click to expand...
Click to collapse
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
---------- Post added at 06:26 PM ---------- Previous post was at 06:26 PM ----------
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
munjeni said:
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
Click to expand...
Click to collapse
The lowest level thing is not there, and I'm pretty sure that's what blocks fotakernel.
munjeni said:
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
Click to expand...
Click to collapse
It should work now with a recent flashtool. Androxyde implemented my sin extraction method that properly extract ext4.
Sent from my LT26i using xda app-developers app
Hi guys,
I’m currently using a custom MM ROM and after learning how easy it is to get around the lockscreen, I would like to encrypt my device. Really, what’s the point of using PINs and having a fingerprint reader when anyone can just delete a few files and access your data?
So my question is does Kenzo support decrypt from TWRP? I succeeded in encrypting my data, but I can’t get TWRP to accept any PIN or password. I’m afraid to stay encrypted in case I need to access my data in TWRP. I don’t even know if its possible to make backups if you encrypt your data.
So, is there any way to access encrypted data in TWRP?
Good news for everyone interested in protecting their data! (I see there are no such people here.) I solved the problem where anyone could remove my lockscreen with the following method.
First, I flashed stock recovery. You can find it in any official fastboot ROM and flash it either in TWRP or Flashify and similar. Then, I disabled USB debugging (so that no one could use adb to remove the files). And finally I relocked my bootloader (with the command “fastboot oem lock”), which means that no one can flash TWRP in fastboot (you can still flash it in Flashify).
I will congratulate myself. Also, I no longer need to bother @vibhu0009 to implement decryption (I would still feel safer if he did it though )
Filip013 said:
Good news for everyone interested in protecting their data! (I see there are no such people here.) I solved the problem where anyone could remove my lockscreen with the following method.
First, I flashed stock recovery. You can find it in any official fastboot ROM and flash it either in TWRP or Flashify and similar. Then, I disabled USB debugging (so that no one could use adb to remove the files). And finally I relocked my bootloader (with the command “fastboot oem lock”), which means that no one can flash TWRP in fastboot (you can still flash it in Flashify).
I will congratulate myself. Also, I no longer need to bother @vibhu0009 to implement decryption (I would still feel safer if he did it though )
Click to expand...
Click to collapse
Hey! I am interested in unlocking bootloader ONLY and at the same time protect my data and you seem to be having experience in this situations. It would be great if u help.
Note: I am asking everything regarding xiaomi devices.
Q1. Do fastboot commands work if usb debugging is disabled?
Q2. When bootloader is locked, can we flash anything (unsigned roms or images) through fastboot or only signed packages or nothing?
Q3. If i have an unlocked bootloader, is it possible that anyone would flash a custom recovery (TWRP) through fastboot and use its file manager to copy my data to external otg or something even worse, delete my lock screen settings (password files) and have direct access to the device.
What would be the case If i have secure boot (password before bootup) turned on? Will he be able to access the files (encrypted) via recovery's file manager?
Q4. Suppose secure boot is turned on and anyone flashes custom recovery through fastboot, will it boot directly into the recovery or will it ask for password when booting first time into the newly flashed recovery. If it would boot directly into recovery, what will happen if one tries to access files through file manager of recovery. Will he be able to gain access to the files (copy, move, delete)?
Q5. Can a device be factory reset or completely erased including passwords and all by any fastboot commands. Can it be prevented if usb debugging is disabled?
Thanks in advance.
Hi everyone,
I just replaced my home security panel into my old sgp311.
It is on stock 5.1.1, just rooted, with locked bootloader.
all things are just going fine and I'm finishing few very end steps, I made a wrong decision, which is install xposed without flashing zip file, I tried to copy/overwrite all the files from the ZIP to system and I thought if I simply make every files with right permission, I won't be messed up, yes I know it is not that easy.
Now I got a bootloop sgp311, I can put it into fastboot or download mode, I tried
Code:
fastboot boot twrp_various_versions.img,
hope it could boot into TWRP recovery and I can flash xposed ZIP and make it come back to earth again but, no.
Is there still a way?
Thanks.
Hak.
etann said:
Hi everyone,
I just replaced my home security panel into my old sgp311.
It is on stock 5.1.1, just rooted, with locked bootloader.
all things are just going fine and I'm finishing few very end steps, I made a wrong decision, which is install xposed without flashing zip file, I tried to copy/overwrite all the files from the ZIP to system and I thought if I simply make every files with right permission, I won't be messed up, yes I know it is not that easy.
Now I got a bootloop sgp311, I can put it into fastboot or download mode, I tried
Code:
fastboot boot twrp_various_versions.img,
hope it could boot into TWRP recovery and I can flash xposed ZIP and make it come back to earth again but, no.
Is there still a way?
Thanks.
Hak.
Click to expand...
Click to collapse
I think you have to reinstall everything from Flashtool (0.9.18.6) or restore with xperia-companion.
fastboot won't flash anything on a locked bootloader. It won't boot afterwards.
Rootk1t said:
I think you have to reinstall everything from Flashtool (0.9.18.6) or restore with xperia-companion.
fastboot won't flash anything on a locked bootloader. It won't boot afterwards.
Click to expand...
Click to collapse
Thank you.
I flashed with flashtool and leave checkbox "wipe userdata" blank, now seems everything but root is untouched.
Hak.
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205