First rule, never purchase device without hard access to recovery (if you are in position to check it).
So, my tablet don't have hard (buttons) access to recovery, just trough the ADB (also in recovery, but I cant enter in recovery or in screen).
Tablet simply stuck on ANDROID until battery let it to loop. ZERO access.
ANY IDEA, please?!?!?
More device info on image.
If I note it well, it is just slightly modified generic and (very) basic AOSP.
komitaltrade said:
First rule, never purchase device without hard access to recovery (if you are in position to check it).
So, my tablet don't have hard (buttons) access to recovery, just trough the ADB (also in recovery, but I cant enter in recovery or in screen).
Tablet simply stuck on ANDROID until battery let it to loop. ZERO access.
ANY IDEA, please?!?!?
More device info on image.
If I note it well, it is just slightly modified generic and (very) basic AOSP.
Click to expand...
Click to collapse
I have the same problem could somebody help us?
In meantime I dumped ROM and I can upload it, but it will be useless except if somebody will not be avalable to solve following issues>
01) ROM is without recovery.img and boot.img, what mean that ROM developer used busybox to script that. It mean that most likely recovery will be unacessible except somebody is not capable to find and replace tohse scripts with some recovery and boot images.
02) ROM permissions should be fixed (AT LEAST THIS IS MOST IMPORTANT).
03) Somebody should to find the way how to enter in recovery and.or fastboot. VERY IMPRTANT and I beleive that it must be easy to find in dumped ROM for some REAL ANDROID DEVELOPER (commands are scripted inside the system image).
SOME VOLONTIERS???
PLEASE!!!
Related
Hi all
first of all I apologize if this is not the right place to put my inquiry in, but I could not find the specific forum for this device.
I have serious problem with this android mobile phone. it is pretty good phone very useful with dual sim function one of them is 3G with WiFi Hotspot but the problem that I have rooted the phone with superoneclick and I have installed a lot of apps in it modifying some language files then when I restart the phone to let the changes take effect then the mobile keep restarting for infinite. Tried to get in to the recovery mode by using Call Button+Volume up+Power but the screen became blank. I spent the whole day searching the the internet to find the solution but with no clue. the problem the device is new and not supported that much in the public forums. could not find Stock Rom. Huawei website and bulletin was not useful.
is there any way to do it through USB or sdcard and How?
thanks in Advance
I am still trying to find a solution...
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
bl88drg said:
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
Click to expand...
Click to collapse
Hi, Can you help me and upload the boot img. I accidentally erase the boot partition.
Many Thanks.
Hello,
I have a Allview Speed City tablet, and after i installed root on it, i changed the dpi using an app..
(root thanks to mad_ady, root availible at http://forum.xda-developers.com/showthread.php?p=40740061#post40740061 )
After this, the tablet is stuck in a boot loop.
I tried to do a factory reset from recovery mode, but this didn't solved the problem.
(the tablet has only 2 buttons, power and home. The recovery can be accessed pressing and holding both buttons until the recovery boot).
I located the file where the dpi is changing, /system/build.prop , and tried to flash another file from Onda 701 ROM (a very similar tablet). I didn't managed to find the original file. Anyway, the flashing didn't succeeded, "instalation aborted" appeared on the screen.
I found on some forum a flashable zip with build.prop from another device, and i replaced the build.prop file with the one from Onda ROM, signed it with a tiny program and still fails.
What options do i have to replace/edit the build.prop file? Before bricking, the ADB was not turned on on the tablet, and i read that i cannot use the SDK (anyway don't know how to use it). I contacted Allview and they don't want to give me the ROM from the tablet. And so, i call anybody that can give me a backed up rom from the tablet, anyone who have the knowledge about AD ROMS and are willing to help me..
Thanks folks!
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
this worked for me for full reset
crististan said:
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
Click to expand...
Click to collapse
this has been done with the allview speed city
I had a simular problem...
here my solution, hold on and home button at the same time until the screen gets back
wait until you get the boot screen...
use both, 1. erase card and 2. media options...
then to be save I choosed the other option say something like for factory reset.
the I used the apply update from ADB...
the tablet shows the same screen for 5 or 6 minutes
after it booted normaly, but I still had some problems
and I used a needle for a reset...
after that the tablet worked fine
the only thing what I dont understand is why its still root
Thank you for this tutorial, but i solved my problem with warranty. Even so, i erased all cache, factory reset from recovery but still i had no access to system files, and factory reset didn't changed the build.prop (system settings) to defaults.
It's normal. build.prop is part of /system (and the su binary is installed under /system as well), and any changes you make to /system files are permanent until you flash a different firmware.
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
Welcome dear xda_dev user,
Model:Prestigio Multiphone 5451 DUO
My device in the past months stuck in a boot-loop, and.. I googled for loads of threads to read,but they don't really help.
This is what the phone do, and not do:
Can/Works:
ADB sideload (PC see the device!)
Stock Recovery Menu
Can turn off/on the device,screen vibration,etc. works.
No/Not Works:
Can't listen to ADB while booting.
NO TWRP and other Recovery menus installed, only the stock android one.
NO official ROMs available from this company.
Click to expand...
Click to collapse
This is what I tried:
Tried to load 1-5Mb "firmware" updates via ADB Sideload /throwing permission problems/
Tried to Wipe data/cache /didn't boot after this/
Tried to unplug battery <- make it 0% (uncharge)
Tried to load non-company driven ROMs via ADB /permission problems/
Click to expand...
Click to collapse
NO official ROMs available from this company, I asked them to share, but they said I need to go a city (200km) away from me who have "authorized access"..
I kept this thread as simple as possible, BTW I have bought a new device, I still need this mobile because it still worth $50 I think..
Thank you if you can help, and ignore the grammar problems.
Not sure if these are legit firmware files for the duo but seeing you are in this fix it is worth a look i think
https://androidmm6.com/deviceinfo_1701.html
http://www.needrom.com/download/prestigio-pap-5451-duo/
Probably Scam/fake.
The file (rar) is locked via password and it's nowhere published, and it's only 1.65Mb so not really a ROM.
Anyways, I star you up for first and probably last replyer.
If you are able to sideload , then i think you can recover your phone in no time.
First I need you need to know that this procedure is complicated but You can recover your device.
go to mtkroms.com and Download any rom from there as per your wish.
-Remove boot.img from zip file and save it else where
-Sideload the rom
-After sideloading ,reboot device into fastboot by pressing power and both volume keys together until Boot Menu appears where you have the choice to Normal Boot , Boot into Fastboot(Bootloader) and Boot into recovery.
-Use Volume Down to navigate to Fastboot and press Volume Up (or Power button in some devices)
-After booting into fastboot , extract boot.img from .zip file to C:
-type in , fastboot flash boot "C:\boot.img"
-type fastboot reboot
If you are lucky , your device might boot (very slight chance to actually boot)
If it doesnt , no issues , this is where you show your skills as rom porter xD
You wont have access to Android OS , but after dalvik cache has been build , access to adb will be granted.
In the same above mentioned website , there is a tool which can port cwm for any mediatek device.
Download it in your PC , PC should not be windows 10 , Compatibility mode wont work.
Make sure you have Drivers necessary to proceed.
Use the tool and Click automatic porting and follow on screen option to Complete Porting recovery , once the recovery has been ported , reboot into recovery.
Now you will have complete access to adb without any problem.
Once you have a proper working recovery , with adb shell , do the following,
Code:
-adb shell
-df
-cat /proc/partitions
Once you have access to the mount points , you can start DeCompiling kernel and do the necessary changes in fstab
To decompile kernel , there are many tools for Windows and Linux
Google it , if you have any problem , PM me or reply back , I'll be happy to assist you
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 !