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
Related
Hi,
My android device CPU is MT6592 (8xARM Cortex –[email protected] MHz) with instruction set 32-bit ARMv7. Board and product is ht1_107a_iball_mjk. Apart from this, Codename is REL, Internal Memory is 16GB and RAM is 2GB.
I did root and un-root my device multiple times.
I see connected device through adb devices command. After adb reboot bootloader and fastboot oem unlock, I confirmed on android device by pressing Volume Up key but there is no change on device screen and computer screen even after 30 min. I changed USB cable and USB port. However, there is no change.
Therefore, I am not able to unlock its boot-loader.
After adb reboot bootloader and fastboot flash recovery twrp.img, I found No TWRP or other Custom Recovery images are compatible for my device.
Therefore, I am not able to install Custom ROM as well.
I tried all above procedures multiple times and with multiple ways. However, at the end I am with Stock ROM (Android 4.4.4). And only two processes I can do successfully; rooting and un-rooting.
In such scenario, may my device be hard bricked, if I continue above processes multiple times forcefully?
Ugn10
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !
I'm looking for help in gaining root access to my phone. I have searched the forums and while this device already has it's own thread, it seems as though the info provided is relevant only to those with Mediatek processors (?) and mine has a Qualcomm Snapdragon chipset. I've tried pretty much every root application available (both for pc and .apk) and none have successfully rooted my device or even achieved temp root. I am open to installing custom recovery +SuperSu and have done so on previous devices, however I'm completely lost on this one as Fastboot and anything resembling a bootloader menu are apparently hidden.
adb reboot bootloader reboots the phone normally, shows Alcatel splash screen then home screen
fastboot hangs at <waiting for any device>
Powering up the device while holding Vol up/down boots into a screen with various options (factory data reset, apply update from ADB, etc) but no fastboot mode.
Is there a way for me to root this device? Why do all the root applications fail?
+2
Has anyone managed to root this phone? I've tried many rooting apps and it has always ended in a fail. I checked to see if the bootloader was unlocked but it seemed to be unknown with no indication of whether its unlocked or not
The specifications of the phone (not sure if needed since I'm a newbie at this kind of stuff):
Name: LGE LG Phoenix 4
Carrier: ATT
Board: msm8937_32
Android Version: 7.1.2 (Nougat)
Processor: Qualcomm Snapdragon 425 (Cortex-A53)
Graphics: Adreno 308
OpenGL: ES 3.0
Architecture: armv7l (32-bit)
This is all I can provide. If this isn't helpful, then I may do a bit more research on this phone. I am really edged about rooting this phone. It could be an easy process unknowingly, or it could be teeth gritting difficult. Hopefully, it won't be hard, nor easy. Hopefully someone can find something
Loogey03 said:
Has anyone managed to root this phone? I've tried many rooting apps and it has always ended in a fail. I checked to see if the bootloader was unlocked but it seemed to be unknown with no indication of whether its unlocked or not
The specifications of the phone (not sure if needed since I'm a newbie at this kind of stuff):
Name: LGE LG Phoenix 4
Carrier: ATT
Board: msm8937_32
Android Version: 7.1.2 (Nougat)
Processor: Qualcomm Snapdragon 425 (Cortex-A53)
Graphics: Adreno 308
OpenGL: ES 3.0
Architecture: armv7l (32-bit)
This is all I can provide. If this isn't helpful, then I may do a bit more research on this phone. I am really edged about rooting this phone. It could be an easy process unknowingly, or it could be teeth gritting difficult. Hopefully, it won't be hard, nor easy. Hopefully someone can find something
Click to expand...
Click to collapse
Yes I have I looked at the LG Aristro 2 and their both the same device. I used the LG Aristro 2 TWRP recovery and was able to use custom recovery with no problems. There is a custom ROM for that device that can be used on the Phoenix 4 as well. To unlock the Phoenix 4 (including AT&T) in fast boot mode you'll need adb.
Commands:
adb devices
adb reboot bootloader
fast boot devices
fast boot oem unlock
And no prompt just auto erases data and is unlocked. After TWRP flash reboot to recovery by pressing VOL - and power. Release power and press again at the LG logo and should see a "Factory Reset" screen. Go to yes to do so and the device will reboot to TWRP. Take the Aristro 2 ROM and side load it with adb.
WARNING: /data in TWRP will ask for decrypt key for /data. The custom ROM zip will erase the key and allow to have root and full custom recovery
I completely bricked a LM-X210APM trying to install the Aristro 2 ROM. Does not power up...nothing. Just a warning to anyone who comes across this on search and is thinking about attempting it. Just don't
Can bootloader be unlocked for root?
Magisk work?
Anyone have success?
Hello, dear friends. will you be able to install firmware with Redmi 4A on this device? the processor is the same, the RAM is the same. what could go wrong? who is very well versed in this matter?
AustinGarrick1818 said:
Yes I have I looked at the LG Aristro 2 and their both the same device. I used the LG Aristro 2 TWRP recovery and was able to use custom recovery with no problems. There is a custom ROM for that device that can be used on the Phoenix 4 as well. To unlock the Phoenix 4 (including AT&T) in fast boot mode you'll need adb.
Commands:
adb devices
adb reboot bootloader
fast boot devices
fast boot oem unlock
And no prompt just auto erases data and is unlocked. After TWRP flash reboot to recovery by pressing VOL - and power. Release power and press again at the LG logo and should see a "Factory Reset" screen. Go to yes to do so and the device will reboot to TWRP. Take the Aristro 2 ROM and side load it with adb.
WARNING: /data in TWRP will ask for decrypt key for /data. The custom ROM zip will erase the key and allow to have root and full custom recovery
Click to expand...
Click to collapse
Can you tell me where this elusive ROM can be found?
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Probably stupid question, but have you tried the keys: Power and Volume+ while powering up?
That should bring you into recovery mode as far as i know.
When I press the power and volume up it just keeps rebooting With the volume down combined it goes to the boot loader, but there's no recovery option there either.
Did you try to boot without any SIM card and SD card?
rtau said:
Did you try to boot without any SIM card and SD card?
Click to expand...
Click to collapse
Yes I did and did not resolve the issue.
nvaert1986 said:
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Click to expand...
Click to collapse
YOU'RE OUT OF LUCK, IT'S EFFECTIVELY FULLY BRICKED UNLESS YOU BRING IT TO THEIR CUSTOMER SERVICE.
HMD's known for blocking people out of bootloader unlocking, and even if you beg them, they can't anyway (they released incomplete bootloaders for their retail units.) I'd say "call Hikari_Calyx" or something, but I don't think he can help with this issue.
nvaert1986 said:
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Click to expand...
Click to collapse
Give it a try> Maybe this tool can help here
mvikrant97 said:
Give it a try> Maybe this tool can help here
Click to expand...
Click to collapse
is it really okay to use tools for a device on a whole different device though???
WilliamMike said:
Yeah! Its helpful whenever my phone got stuck or displaying black screen ..
Click to expand...
Click to collapse
what's your model, then? Those kinds of phones from Nokia/HMD are never able to enter fastboot/recovery mode though.
AltFantasy said:
is it really okay to use tools for a device on a whole different device though???
Click to expand...
Click to collapse
It is based on ADB commands you can use it
mvikrant97 said:
It is based on ADB commands you can use it
Click to expand...
Click to collapse
but I couldn't use ADB on my X10...