My cousin got me this phone from China. According to him, the phone model is Coolpad 7296.
The first problem seems to be that the phone is actually different from the official Coolpad 7296, which is shown in the first attached image. But my phone looks more like the second attached image. I have the link for both phones the official site and a online seller selling a phone 99% like mine while claiming it to be a Coolpad 7296. I can't post the links due to the forum policy requiring me to have a least 10 posts. In other words, there is a very good possibility that my phone is not a legit Coolpad or it may be a variation of the Coolpad 7296.
When i first wanted to unlock the bootloader to root my phone, it was impossible. After booting to fastboot mode, any fastboot command would get stuck. For example, if i did the following:
Code:
fastboot oem unlock
It would get stuck and only show:
Code:
...
Click to expand...
Click to collapse
Or if i tried erasing the user data:
Code:
fastboot erase userdata
It would get stuck and only show:
Code:
erasing...
Click to expand...
Click to collapse
Later, I was able to root the phone via a Chinese app which literately translate to "Baidu One Click ROOT". After some playing, i tried to flash the phone via fastboot, then i literally broke the recovery mode. Most likely, the recovery partition was damaged. After more playing around, i broke the system image. I was still able to boot to fastboot mode back then. Afterwards, i broke fastboot mode as well.
After some time, i was able to install the VCOM Preloader USB Drivers by disabling the digital signatures required for installing the drivers in Windows 8. Then, I flashed the phone using the SP Flash Tool and an official ROM of Coolpad 7296 manufacturer. I am able to turn on the phone and the screen would light up in a black blank screen. The computer is able to recognize the phone via USB and i am able to use ADB commands as well as ADB Shell on it. In addition, i downloaded a program called 刷机精灵, which is a ROM flash tool for Chinese phones. This program is able to show exactly what was supposed to be showing on my phone screen. If i press the Power Button, it shows the phone's pop up window asking for if i want to power-off, reboot or put in airplane-mode. The screenshot is shown in the third attached image.
Sorry for the long post but i thought it would help if i told the whole process. Now are the real questions:
1) I never backed up my phone. So, i can't get it back to the original ROM i had. I wonder if it is possible that the screen doesn't work because the phone doesn't have the right radio image with the proper drivers. I mean, I could assume that the phone is a variation of the current official Coolpad 7296, and it is not compatible with the current official ROM.
2) Or, what are the chances that i burned my screen by charging the phone when the recovery and system images were dead. At that time, the phone could only work on fastboot mode and i left it charging overnight. Next day, the phone camera was extremely hot. And i am not sure if fastboot mode was dead first or the screen stopped showing stuff first.
3) Right now, the phone cannot reboot to neither recovery or fastboot mode (no matter how much i try with the ADB reboot or power & vol key press methods). I believe that the possibility of a somewhat incompatible phone radio, recovery and fastboot images are the cause of my current problem. So, i wonder if anybody have the same phone and know a compatible ROM.
Edit: I also want to mention, that i tried to flash the phone with other official Coolpad ROMs too. The only one that were flashable ere Coolpad 7295 and 7296. When i flash it with Coolpad 7295, i have the same problem plus the phone cannot see my SD Card. On the other hand, when i flash it with Coolpad 7296, i recognizes my SD Card. I have confirmed this via ADB shell and i can see my old files in the SD Card too.
Edit2: Another things i wanted to mention was that when i entered to fastboot mode in the past, the device id was mt6589_phone_720pv2 which means the cpu must have been a mt6589 chipset. However, i remember that when i ran a phone hardware app, it showed that the CPU was a 2.0Ghz mt6592 which was weird. And when i check online, mt6589 the CPU freequency is 1.2Ghz. On the other hand, documents online show that mt6592 has 2.0Ghz frequency but it is a octa core. My phone is definitively a quadcore.
I found a working ROM. It says it is for Coolpad 8750 but it is identical to my original ROM. The irony is that when i download the ROM of Coolpad 8750 from the official site, it doesn't work with my phone.
Code:
pan.baidu.com/share/link?shareid=1988426388&uk=2802944333
Click to expand...
Click to collapse
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 !
Hello all,
I recently picked up a ulefone armor 2s and was attempting to root it and ended up bricking my device... i followed a guide for flashing the 2 variant not the 2s. I found a stock rom and ended up flashing it and got the device back to working status. I do want to root my device with twrp but i am unable to flash it because there is no bootloader on the device at the moment.
Powering up the device i get a message that says device is in a red state i am not sure what that means. I have found a copy of trwp that is corresponds to my chipset and kernel and want to flash it. Attempting to enter download mode or recovery just gets me to a black screen.
I have tried to flash the device using adb, adb doesn't detect my device. I have all the proper drivers, usb debugging is enabled and is oem unlocking.
Cpu-z says that i have an unknown bootloader and when i try to access it nothing happens
Is there a way to put a bootloader on it?
Thanks
-Malice
I'll be very direct, I wanted to install twrp on nokia 5.4 so I was going to apply an update from adb but android recovery only gives me the Reboot system now;Enter fastboot;power off functions within fastboot:Reboot system now;enter recovery;Reboot to bootloader and Power off. Does anyone know how to solve this problem? I didn't find anything on the internet
unlocking nokia 3.4 bootloader
Hi iv got every thing setup to unlock the boot loader but now find out you need a pin which nokia doesnt give out (only nokia 8) was hoping to root with magisk but not sure how to continue without unlocking the boot loader. Is there some way to...
forum.xda-developers.com
This is intended, as triple-color company doesn't want us wipe data on a stolen phone.
To enter sideload mode, execute "adb reboot sideload" under normal OS.