Related
Well, I have to ask for help right here because Goole/Yahoo/Wiki DIDN'T help. Although it's a bit long but please read it
Here's my problem:
At the last time that my phone is still being functional, I was playing the game "Contract Killer" and "Facebook", "Internet" were running in the background.
Suddenly, it shut off with showing "power off...(Sth like that). This is obviously a normal situation when the battery is out of power. I took it to charge as usual and went to sleep.
Next day, I waked up and tried to boot up my HTC EVO 3D...
First time: Stuck in the startup screen without playing the HTC opening sound track( The phone used to be in Silent Mode)
Second time: I pulled out the battery and put it back and boot again. Still stuck in the startup screen but this time it play the HTC opening sound track...
I've got a lot data in the internal memory and I've never BACKUP before.....
Is there anyway that can boot up my phone without losing the data???
Oh...my phone has never been rooted.
Anyone know the problem??? (
I dunno, kinda sounds like a Hard Reset/Factory Reset is in order. Did you take the battery out for a while and then try to reboot?
There's no way unless u can take to service provider an have them extract it
Sent from my PG86100 using XDA App
i had that kind of a problem once but i was on a CUSTOM ROM so i'm not sure it will work for you and I'M NOT SAYING this method is THE SAFEST.
so 1st thing i did was.. i panic'd... 2nd, i started googling and when all the signs pointed me to a boot up problem i opened the zipped rom, i extracted the boot.img, connected the phone to the pc in fastboot mode and flashed the boot image. after that it started with no problems, all my data was there. what do anyone else suggest? would it be okay to flash boot.img (stock one) on a stock rom?
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Now if absolutely none of this has worked at all, you have malfunctioning hardware. Your only option at this point is to go to a Sprint store to have your data transferred over to a new replacement phone.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
megabiteg said:
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
Click to expand...
Click to collapse
First of all, thanks for helping~ I would like to know that will my data lose if install the custom recovery? Seems like a huge risk...
Besides, I am a little confused about using the .img to boot my phone.......
MikeyCriggz said:
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
Click to expand...
Click to collapse
I was once using Nokia N900, and it is very easy to flash the rom meanwhile i can keep everything in the emmc remain unchanged! Since ANDROID is based on Linux, I am sure your way will be damn work! Any software or environment would i need to do these stuffs? Thx at all!!
:
All in all, I do care the messages in the phone only. That is what i really want.
Nokiawithandroid said:
All in all, I do care the messages in the phone only. That is what i really want.
Click to expand...
Click to collapse
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
HELLO?
megabiteg said:
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
Click to expand...
Click to collapse
How can i get to access my phone by ADB?
I am totally new for all these...
Nokiawithandroid said:
How can i get to access my phone by ADB?
I am totally new for all these...
Click to expand...
Click to collapse
This can get you acquainted with ADB
http://forum.xda-developers.com/showthread.php?t=1241935
Props to Droidzone for putting it all together.
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Nokiawithandroid said:
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Click to expand...
Click to collapse
If you remove the battery off your phone and then you reinsert it back, press PWR+Vol UP to access the bootloader.
While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else.
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Nokiawithandroid said:
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Click to expand...
Click to collapse
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Oh..damn.....the voyage is lengthy
What equipment/environment do i need?
My target: 1)Back up the Message Database 2) Run this bloody phone.
Difficulties: 1)S-ON 2)command 3) environment 4) Flashing a new (boot?image?)
megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Any thread for that?
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,
I do have a Ace 2 (I8160) but I can't get the mobile on the Wifi and he keeps saying: trying to get the IP-adress
Does somebody know how to solve this problem?
Try to connect to another wifi. If the wifi you're trying is yours, go to the router's settings & remove wireless security, then try again.
For the moment \I'm in another house and again I can't get acces to the Wifi and there is also a Wifi signal that isn't protected and there I have the same problem .......... trying to get the IP-adress
You running stock or custom ROM? Have you flashed anything recently? Did the wifi ever work before?
I do have stock and yesterday I rooted the phone and I "think: it has something to do with that ?!
Is it an option to install the stock back there this is a new phone so I do have another phone for the moment.
Simply having root permissions shouldn't affect your ability to connect to wifi. Have you installed a custom recovery? If yes, try clearing cache & dalvik cache.
No I didn't.
Is it possible to install now or doesn't it make that any sence ..... I don't think so
Pfffff, how can we solve this ??
Some ideas:
Unroot, see if it reverts your problem
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it)
If you have a data connection, install ROM Manager & flash custom recovery that way
post-mortem said:
Some ideas:
Unroot, see if it reverts your problem
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it)
If you have a data connection, install ROM Manager & flash custom recovery that way
Click to expand...
Click to collapse
I'm from Holland and my English is not soooooo good
Do you mean that I can install the original software from this phone with the ROM Manager ( http://www.samfirmware.com/ ) ?
And as far I know it's not possible to unroot this phone ??!!
The ROM Manager app has an option to download & install CWM recovery, if your phone is in their database. sammobile/samfirmware will let you download the stock software for your phone, and you need to plug your phone to a computer to flash it. It will return your phone to stock, and you will lose all data.
I thought it was easyer with the second option:
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it) but I thin it works the same?
If ROM Manager has a custom recovery in their database, then that's easier & less steps, but I avoid ROM Manager because it bricked my phone. If you download a custom recovery .img file which you know is compatible with your exact model #, then Android Flash Recovery is probably safer. Android Flash Recovery requires the use of a computer, and a Windows one, at that. However, you can flash any custom recovery (i.e., AmonRa, TWRM), and not just CWM.
What is the bootloader / fastboot mode ??
Is that the CWM .... but I'm wondering if this is available for my GSM
No, CWM is recovery. When you see that, it means you have done something to force your phone to boot off of the recovery partition, instead of the normal boot procedure. Fastboot is different; it's like an alternative to adb. You can put your phone into fastboot mode (I don't have your device, so I don't know how you would do it), but you can also communicate through fastboot when you're not in fastboot mode.
To test if you're able to communicate with the device properly, connect your phone via USB, then type adb devices to see which devices are visible to your system; same with fastboot devices .
post-mortem said:
No, CWM is recovery. When you see that, it means you have done something to force your phone to boot off of the recovery partition, instead of the normal boot procedure. Fastboot is different; it's like an alternative to adb. You can put your phone into fastboot mode (I don't have your device, so I don't know how you would do it), but you can also communicate through fastboot when you're not in fastboot mode.
To test if you're able to communicate with the device properly, connect your phone via USB, then type adb devices to see which devices are visible to your system; same with fastboot devices .
Click to expand...
Click to collapse
Now I'm lost ...........
I connect my phone to the laptop and it's recognized but where do I have to type this ???
Those commands you type on the laptop, in a cmd window. Remember step 2? You need to be in that folder (which you said was c:\ ).
post-mortem said:
Those commands you type on the laptop, in a cmd window. Remember step 2? You need to be in that folder (which you said was c:\ ).
Click to expand...
Click to collapse
SORRY I don't really know what you are talking about
I know the old ms-dos command prompt ...... do you mean that and where did we talk about it ??
bruce the boss said:
SORRY I don't really know what you are talking about
I know the old ms-dos command prompt ...... do you mean that and where did we talk about it ??
Click to expand...
Click to collapse
LOL, sorry! I got this thread confused with another one! Never mind about the step 2 thing.
Uh, yeah, so those commands are typed into a DOS prompt. You need to be in the same folder as where your adb and fastboot binaries are located (unless you added them to the PATH, of course).
go to samsung service center. claim warranty.
it's easier to fix it
Hi all, my problem is: I have this tablet (I still don't know what's the model, but I don't think it would change much), and I should recover everything from it, but there's a lockscreen and the owner doesn't remember the password/pattern.
An easy way to do this is using adb, but I don't know if the usb debugging setting is turned on or not, so I must have a plan b.
I thought that I could boot it into a custom recovery like twrp with
Code:
fastboot boot recovery twrp.img
but I'm pretty sure it still has a locked bootloader. Is it still possible or it won't do anything?
Any suggestion is apprieciated, but remember that I can't erase all data, so no factory reset, bootloader unlocking and things like these.
Hello everyone!
I have unlocked my bootloader a few years ago and installed lineageOS since.
Now i came across a thread about another OS i wanted to install, instructions saying that i should update my firmware, i did that and it seems this has locked my bootlaoder again.
I think this also has caused trouble in my banking app, because it keeps saying my device is rooted even though its not. I have uninstalled magisk. Before that i never had any problems with the app on customROM.
Is there any way i can make this undone or unlock it again without data loss? I am currently using customfox Recovery if this is any relevant.
Thanks ahead
https://forum.xda-developers.com/t/dkb-tan2go-app-on-rooted-device.3835355/page-27
you have custom recovery on phone? for sure your bootloader is unlocked then.
alecxs said:
https://forum.xda-developers.com/t/dkb-tan2go-app-on-rooted-device.3835355/page-27
you have custom recovery on phone? for sure your bootloader is unlocked then.
Click to expand...
Click to collapse
No, it's not anymore! The unlocked sign is gone, i can't enter bootloader fastboot* but fortunatelly i still can boot my phone and enter recovery mode.
sure about that? bootloader locked phones would go in RED state on custom binaries (such as custom recovery) not able to enter TWRP.
https://source.android.com/docs/security/features/verifiedboot/boot-flow
alecxs said:
sure about that? bootloader locked phones would go in RED state on custom binaries (such as custom recovery) not able to enter TWRP.
https://source.android.com/docs/security/features/verifiedboot/boot-flow
Click to expand...
Click to collapse
Absolutely! Whenever i used to boot my phone before it would say unlocked right under the xiaomi logo. I am lucky it didn't completly bricked.
what recovery you mean is able to boot on locked bootloader (link)?
alecxs said:
what recovery you mean is able to boot on locked bootloader (link)?
Click to expand...
Click to collapse
Customfox
never heard about Customfox, do you have a link?
alecxs said:
never heard about Customfox, do you have a link?
Click to expand...
Click to collapse
sorry meant OrangeFox
OrangeFox Recovery is not signed and can therefore not boot on locked bootloader.
please double check from fastboot
Code:
fastboot getvar unlocked
alecxs said:
OrangeFox Recovery is not signed and can therefore not boot on locked bootloader.
please double check from fastboot
Code:
fastboot getvar unlocked
Click to expand...
Click to collapse
I don't understand what i am supposed to do! I can't enter fastboot!
OrangeFox has option to reboot into bootloader? still you can do it from adb
Code:
adb reboot bootloader
alecxs said:
OrangeFox has option to reboot into bootloader? still you can do it from adb
Code:
adb reboot bootloader
Click to expand...
Click to collapse
black screen like when i tried with buttons!
looks like you didn't update firmware right. fastboot comes before recovery, it is in abl partition. without abl it can't boot into recovery, so most likely fastboot works but you can't just see the logo.
regardless of that you have OrangeFox Recovery, it provides full access to all partitions. you can flash anything you want.
as for the backup, depends if OrangeFox Recovery ask you for lockscreen credentials, then you can backup your data.
alecxs said:
looks like you didn't update firmware right. fastboot comes before recovery, it is in abl partition. without abl it can't boot into recovery, so most likely fastboot works but you can't just see the logo.
regardless of that you have OrangeFox Recovery, it provides full access to all partitions. you can flash anything you want.
as for the backup, depends if OrangeFox Recovery ask you for lockscreen credentials, then you can backup your data.
Click to expand...
Click to collapse
I don't think i can flash anything.
Why would the boot screen not show the "unlocked" sign anymore?
Can i make this undone maybe by flashing a previous firmware?
I can backup and did that already but i am still scared that i might screw up my device even more.
If bootloader were locked this would require user-settable root of trust stored in tamper-evident storage.
The unlock logo is just another picture, like the fastboot bunny. You probably messed up logo partition, that's why you can't see it.
you can flash any zip from OrangeFox. you can even dump or flash partitions not listed in menu. here is a list of partitions you can adb pull or flash with dd (or simg2img)
Code:
adb devices
adb shell ls -d /dev/block/bootdevice/by-name/*
of course you should know what you're doing, flashing the wrong partitions can brick.
alecxs said:
If bootloader were locked this would require user-settable root of trust stored in tamper-evident storage.
The unlock logo is just another picture, like the fastboot bunny. You probably messed up logo partition, that's why you can't see it.
you can flash any zip from OrangeFox. you can even dump or flash partitions not listed in menu. here is a list of partitions you can adb pull or flash with dd (or simg2img)
Code:
adb devices
adb shell ls -d /dev/block/bootdevice/by-name/*
of course you should know what you're doing, flashing the wrong partitions can brick.
Click to expand...
Click to collapse
So if you say my device isn't locked after updating the fw i trust you.
But how do i get my banking app to work again? It keeps saying that my device is rooted. I tried hiding it through magisk, i uninstalled magisk but nothing helps. Any idea?
if hardware-level key attestation is enforced, there is nothing you can do to hide the unlock state.
Magisk may no longer be able to hide bootloader unlocking from apps
The developer of Magisk has discovered that Google may have started using hardware checks to determine if a device has been bootloader unlocked.
www.xda-developers.com
you could however try older methods. just make sure you wipe app data and do not start the app before hiding.
Hide My Applist - A Brief Guide
Hide My Applist Guide Hide My Applist is a LSPosed module by Dr-TSNG (nullptr). Often referred to as HMA. In the simplest terms HMA aims to stop one app detecting a list of other installed apps. - It can often help stop your banking app(s) from...
forum.xda-developers.com
alecxs said:
if hardware-level key attestation is enforced, there is nothing you can do to hide the unlock state.
Magisk may no longer be able to hide bootloader unlocking from apps
The developer of Magisk has discovered that Google may have started using hardware checks to determine if a device has been bootloader unlocked.
www.xda-developers.com
you could however try older methods. just make sure you wipe app data and do not start the app before hiding.
Hide My Applist - A Brief Guide
Hide My Applist Guide Hide My Applist is a LSPosed module by Dr-TSNG (nullptr). Often referred to as HMA. In the simplest terms HMA aims to stop one app detecting a list of other installed apps. - It can often help stop your banking app(s) from...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't get it! It used to run perfectly fine on LOS with unlocked bootloader!
you're running another ROM with another security patch level. and you have updated firmware.