Shouldn't a phone like this have a second screen / secure output with which to verify what firmware is booting?
Related
I'm currently trying to develop a custom ICS Rom for the Thinkpad Tablet.
One of the problems I'm encountering is, that I'm unable to debug the boot process.
Often, the device hangs on the Vendor logo, suggesting that something went wrong during the boot, but without any way to see what exactly is going on, I can't resolve the problem.
The device doesn't register on my USB-Port until very late in the boot process (i.e. when the Interface is already visible), so I can't see the logcat during boot.
Is there a way to disable the boot animation and see the actual kernel messages?
Or is there a setting for the init.rc, so that I can access the kernel messages either via ADB or directly via a serial console?
so what happened, I had a request for hard reset for a spectrum mobile, which is surprisingly difficult because of the lack of any information about this phone online, since there was no recovery (no kidding there isn't any) and the only thing I managed to exploit was a little bug in the software that allowed me to enable debugging, the phone was pin locked, the guy who told me to reset didn't know the pin as he doesn't remember it, but i've made sure that it was his phone, anyways, what happened is that I managed to enable USB debugging, and I wanted to install twrp on that phone in order for a more secure installation, turns out, it has no unlock OEM in its configuration nor the command
Code:
Fastboot unlock oem
works, what I did instead i used fastboot to clear cache and userdata, hopefully resetting the pin, and what happens is that I'm now locked in a boot loop with a recoveryless phone that has literally no other combination than volup+power which now doesn't even work TL, DR:
I'm stuck with a Chinese phone in a boot loop without any possible recovery nor fastboot, combinations don't work and the computer doesn't recognize the phone
here is the data I've got from the box:
CPU: SC 7731 Quadcore 1.2GHz
GPU: Mali 400 MP2
Storage: 8Gb
Android: 4.4.2
Dual Sim
and i don't think that the other info are relevant
G935P failed to root, shows "Custom binary blocked by SECURE BOOT (modem.bin)", help!
I have Samsung S7 Edge (G935P) that I wanted to unlock, is in android version 7.0, so I downloaded root file from https://download.chainfire.eu/1087/...to-Root-hero2qltespr-hero2qltespr-smg935p.zip and flash the phone with it but the root flashing did not complete, then the phone started writing that I flashed the phone with unsupported unlock file, then I download stock rom from https://www.sammobile.com/ and flash the phone complete and it started writing on top of the screen in red color this below;
Custom binary blocked by SECURE BOOT (modem.bin)
And also showing on the screen this on the link below;
https://lionfinger.com/gsmerrors/s7edge_error1.jpg
This are also how the download mode and recovery mode shows;
Download mode => https://lionfinger.com/gsmerrors/s7edge_error2.jpg
Recovery mode => https://lionfinger.com/gsmerrors/s7edge_error3.jpg
Please someone help me on how to revive the phone to boot completely.
Thanks!
Hi , try with this one :
https://updato.com/firmware-archive-select-model?record=E6BB0C3642A611E99F15FA163EE8F90B
or this one :
https://updato.com/firmware-archive-select-model?record=E8FFA23642A611E99F15FA163EE8F90B
Teddy Lo said:
Hi , try with this one :
https://updato.com/firmware-archive-select-model?record=E6BB0C3642A611E99F15FA163EE8F90B
or this one :
https://updato.com/firmware-archive-select-model?record=E8FFA23642A611E99F15FA163EE8F90B
Click to expand...
Click to collapse
Thanks.
Both of them are the same file.
If I flashed this file, will it make it to come on completely?
Thanks
Hi,
I can't use my tablet anymore tried Odin to re-install the origin firmware "SM-T825Y_1_20180122165040_zf84f94qoe_fac.zip" (new android 8 stock ROM) but it fails, Odin shows the transfer has PASSED but I still get this message in the screen:-
"Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. "
I wasn't planning flashing a custom ROM the only thing I did is put OEM Lock on, not sure why I did that.
When I put in Download Mode it shows this in the screen:-
ODIN MODE [High Speed]
PRODUCT NAME: SM-T825Y
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
OEM LOCK: ON
DID: 03EA1E00AE16
WARRANTY VOID: 0x1 (Ox20C)
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B3 (1, 1, 1, 1, 1) K2 S2
SECURE DOWNLOAD: ENABLE
CCIC: S2 MM005 HW: 4
BOOT: 6 MAIN: DS
Regards,
Sal.
1. It's FRP not FAP ya perv.
2. Reflash firmware with odin, do not go into download mode afterwards before 3.
3. The rest watch this video carefully, and next time you want to leave your device stock, leave it stock, if you want to install a custom rom or twrp, do not have auto reboot ticked.
4. here is link ---> https://www.youtube.com/watch?v=o0T-CR-KpfM
I did reflash with odin but I still get this message "Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img)"
Odin tells me its PASSED but the Tablet still says its locked FRP and OEM locked .
In download mode I am getting same info.
I just went to the Samsung Shop and they fixed it for free, they said they just put a new firmware not sure how they did it but I tried it myself with latest firmware but I couldn't get rid of the lock, I am missing something? like software? or just not enough info about about getting rid of locks?
I had the same issue after i installed a Xposed module. Had to reflash Pie Bootloader and Rom via odin. Now it boots, but i can't flash twrp anymore... It always fails.
Hello, due to a swollen and drained battery problem (I replaced it now), my phone is not able to start after being abruptly disabled.
I have some very important stuff in my apps (also not backed-up ) so am trying to fix the phone without doing:
- a factory reset
- erasing app data in the recovery mode (it will erase my app data permanently, right?)
Device: Samsung Galaxy S9+
- not rooted
- USB debugging disabled (the android UI does not load so I am not able to change it there)
- no recovery/backup available (both system and apps) - I know - hard lesson for me.
Situation:
1. Device tries to boot a couple of times.
2. Asks for the unlock pattern.
3. Keeps hanging at the "unlocking padlock" screen. [attached]
4. Reboots itself.
5. After few reboots a recovery screen appears with a message: "Your phone couldn't start normally. Some configuration data may be corrupt."
and 4 options: Try again; Erase app data; Power off; View rescue log. [attached]
Following "View rescue log", the stack trace says an exception happens during boot:
-> (...) java.lang.IllegalStateException: Failed to parse roles.xml: /data/system/0/roles.xml (...)
-> (...) org.xmlpull.v1.XmlPullParserException: unterminated entity ref (position:TEXT @3:319 in [email protected])
I thought I could somehow:
A. pull the roles.xml file
B. see the content,
C. possibly fix it (
D. push it back to the device,
I have some programming background, but it's my first time trying to fix my Android device and I am not sure how to pull and push back the /data/system/0/roles.xml
What are my options? Is any of the following viable?
- The default/standard adb mode is not working due to USB debugging being disabled - is there any workaround to change it?
- The adb sideload is available, but if I understand correctly adb in sideload mode is responsible for installing custom ROMs. Or maybe I am wrong and am able to install any app, even my own?
- If there would be a way to install my custom app I would do the previously mentioned steps. Is there a way?
- I did not follow the init.d script possibilities, because it seems I would need to have my device rooted before, right?
I would appreciate any help.