i have a Conquest and something happened the other day. I enabled su at boot and POOF it reset and got stuck on a bootloop. i can get into the stock recovery menu though. Every time i try to use ADB to push/install/sideload any zip files i see this on my screen
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted
i made a backup of everything using TitaniumBackup but i have absolutely no idea what i am supposed to do now. i have read and read everything pertionent to my issue and have found no fixes for this. i cannot do anything with the bootloader at this time because the forums are all vague to the content towards Alcatel devices. the bootloader i have is
L4CCY0Y0BQ00
model Alcatel 7046T
manufacturer/brand TCL
Radio: MSM8916
when i view recovery logs everything i see has 0 at the end so i assume its disabled. and i mean EVERYTHING.
i can send a copy of the TitaniumBackup zip file to someone who can help me with this issue. i have the stock recovery also. i am at my wits end at the moment. would someone please help me with this issue and possibly run me through some steps as to what i can do to get this phone successfully working again? I have never had this much trouble with a phone/tab as i am with this one. i am really desperate as i cannot afford to buy a new phone nor do i want to send it in to boostmobile to have the "look" at it. they will laugh at me and say "warranty void".
info from the rec log
I:Got arguments from boot message
locale is [(null)]
stage is [ ]
reason is [(null)]
cant open /dev/tty0: no such file or directory
fb0 reports (possibly inaccurate)
v.bits_per_pixel = 32
vi.red.offset =0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length =8
framebuffer: 0 (720x1280)
found frames = 7
libpng warning: Not recognizing Known sRGB profile that has been edited
Command: "recovery" "--show_text"
then i am assuming it is showing my build.prop information i would post it here but thats alot of typing for me. i really need help. please. i normally dont ask for help i just fix it but i cant this time.
same issue!!
im having the same issue with my friends phone....i rooted it with king root and used supersu me to delete kingroot and install supersu me, and when i "successfully" updated the binary with the newly installed supersu it told me to reboot...i clicked the " reboot" option given by supersu it went to reboot but just stays at the loading screen where it says android and alcatel one touch.
where are you getting these packages you are trying to install with adb ?
i wanna try that too but i woulod rather just use odin to flash the stock rom back onto it, but i cant find the stock rom file anywhere , im assuming because this phone is new ( released july 2015)
can anyone hook me up with the stock rom file for alcatel onetouch conquest 7046t boost mobile???
Could you please upload the stock zip you have.
sosthenisRR said:
i have a Conquest and something happened the other day. I enabled su at boot and POOF it reset and got stuck on a bootloop. i can get into the stock recovery menu though. Every time i try to use ADB to push/install/sideload any zip files i see this on my screen
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted
i made a backup of everything using TitaniumBackup but i have absolutely no idea what i am supposed to do now. i have read and read everything pertionent to my issue and have found no fixes for this. i cannot do anything with the bootloader at this time because the forums are all vague to the content towards Alcatel devices. the bootloader i have is
L4CCY0Y0BQ00
model Alcatel 7046T
manufacturer/brand TCL
Radio: MSM8916
when i view recovery logs everything i see has 0 at the end so i assume its disabled. and i mean EVERYTHING.
i can send a copy of the TitaniumBackup zip file to someone who can help me with this issue. i have the stock recovery also. i am at my wits end at the moment. would someone please help me with this issue and possibly run me through some steps as to what i can do to get this phone successfully working again? I have never had this much trouble with a phone/tab as i am with this one. i am really desperate as i cannot afford to buy a new phone nor do i want to send it in to boostmobile to have the "look" at it. they will laugh at me and say "warranty void".
info from the rec log
I:Got arguments from boot message
locale is [(null)]
stage is [ ]
reason is [(null)]
cant open /dev/tty0: no such file or directory
fb0 reports (possibly inaccurate)
v.bits_per_pixel = 32
vi.red.offset =0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length =8
framebuffer: 0 (720x1280)
found frames = 7
libpng warning: Not recognizing Known sRGB profile that has been edited
Command: "recovery" "--show_text"
then i am assuming it is showing my build.prop information i would post it here but thats alot of typing for me. i really need help. please. i normally dont ask for help i just fix it but i cant this time.
Click to expand...
Click to collapse
You can try to rename the file to "update.zip" and install it that way. It would be best to put the zip on the internal sd if possible, I believe. Also the error you are getting appears to be a signature/oem issue. You could also try editing the zip you have through the meta/google/??? not sure if this is correct folder. You should be able to search on XDA for modifying custom/stock rom. I believe you have to delete or add a few lines in a script file. Needless to say I have the same issue but no access to stock rom. Hope this helps. Please share the zip you have and I will post any results I have witgh my head ache. BTW im not positive, but believe this issue could be a result of a locked boot loader.
---------- Post added at 11:54 PM ---------- Previous post was at 11:46 PM ----------
Another thing you might try is to install via fastboot
"fastboot flash system filename.img" you will have to convert zip.
Alternatively, you could try "fastboot flash zip filename.zip"
Not sure if you can flash tar files this waym but this may be an option also. Using fastboot should eliminate the errors you have described in your post.
---------- Post added at 11:59 PM ---------- Previous post was at 11:54 PM ----------
Another thing you might try is to install via fastboot
"fastboot flash system filename.img" you will have to convert zip.
Alternatively, you could try "fastboot flash zip filename.zip"
Not sure if you can flash tar files this waym but this may be an option also. Using fastboot should eliminate the errors you have described in your post.
all of this seemed good to be honest but did not work on my device. it seems that i do not have the stock recovery i believe as it says in the first few lines of the recovery log that TZDATA is looking for info from Los Angeles and also from a file made in 1970. i video recorded it so i could read it in .25x speed. it was a pain. could anyone use MTK Droid tools to get their recovery and scatter files also with the rom itself so that i may fix this. the device registers as MTK (Media Tek) for some reason. maybe because it was manufactured in China and most Chinese devices run through MTK as a primary then through their subsidary. if anyone c ould try this for me and post their findings i would greatly appreciate it. i am running trough all my ideas at the moment. Thanks guys.
gonna try a new approach i guess.
Has anyone had any further developments on this device? I have even tried to find another one at Boost Mobile but according to the clerk they were sold out across the nation which i find hard to believe. I am sending the device in for the warranty which a representative said they cover just about everything programming wise no matter what really so ill try that next week. Wish me luck everyone. Tnx.
i have the phone in perfect condition. i have hesitated rooting it. Going by the comments i have seen so far most people have either bricked their devices and are not able to get back to stock. i want to use the device with a GSM simcard its only has options for LTE and CDMA. Is it possible like to activate the GSM bands on this phone
Retracted
sosthenisRR said:
Has anyone had any further developments on this device? I have even tried to find another one at Boost Mobile but according to the clerk they were sold out across the nation which i find hard to believe. I am sending the device in for the warranty which a representative said they cover just about everything programming wise no matter what really so ill try that next week. Wish me luck everyone. Tnx.
Click to expand...
Click to collapse
I believe this phone uses the Qualcomm chip set. Mtk based methods wouldn't work with those right?
New info
So I've done some research into the boot loader, and from what I've found, traditional rooting methods will not work. Fastboot it seems is disabled on the device and won't accept any fastboot commands. The only program I've seem successfully unlock the boot loader is Sigma Key, which costs a good deal of money( for those prices you could rebut the phone). I do have a question though, if I got hold of a factory version of the stock ROM, could I reflash it with the boot loader being locked?
Related
Hello to all.
I bought recently a Tengda T94 (also being referred to as Dapeng T94).It has MTK6589 chip.
Me,the smartass,wanted to change the DPI setting of the smartphone,because Real Racing 3 lagged a little bit and thought changing it might fix the framerate.I changed it from 320 dpi to 221 with LCD modder and reboot.Then the surprise struck me,when it didnt start,it just stood on the logo and kept replaying it.I have tried with ADB commands - some works,some not.
I am with stock recovery 3e.
Has only few commands like reboot now,install update from adb,cache,sd card and wiping cache and another option for wiping data to factory settings (and two irrelevant options of restoring/backing up user data).
I tried wiping all data and cache,still bootlooping.
Tried with mediatek firmware adapter tool,but i think it cannot change the build.prop file while bootlooping (it cannot find my device when in recovery mode),because it is either in use,or in read-only mode.
Tried with android commander,but didnt know what to do there.
I downloaded rather late a CWM recovery for my phone,and also if I am not mistaken two roms - one of them is exactly like mine.
But when tried to install thru recovery adb sideload it starts and then says : restating ADBD ....... installation aborted and returns me to main recovery menu. Tried with my backed up build.prop which i have put in flashable zip file.
However,the two roms i have downloaded arent working properly.They are zip,but still adb sideload cannot read them.
And another (i dont know if it is relevant) my external sd card 16 gb default,when i put it in my old gsm to put the two roms and cwm recovery files,first windows wanted to format it and the only option was FAT 32,total of 2.87GB.What has happened to my sd card ?
Still I couldnt install from the external sd card the roms,only zip with build.prop file was listed and gave the same mistake as said above : restating ADBD ....... installation aborted.
PP: I have arrived at the conclusion that the problem is this line ro.sf.lcd_density=221,which is in build.prop file (I might be wrong).So the question is can i somehow modify the prop file or what should i do ?
And why has my sd card shortened from 14,6gb to 2.87 ?
Sorry for the long post.
Problem with T94 too
I tried to modify the build.prop file to enable the soft keys and the phone doesn't work now! stops at the android logo and I don't know how to make it work now. I re-edited the file back to its original using ADB explorers and still the same. Any help on how to recover it would be highly appreciated.
---------- Post added at 04:19 AM ---------- Previous post was at 04:13 AM ----------
if you want the original build.prop file i have got it,
can you tell me how did you do the CWM recovery without the phone being working?
Installing CWM Recovery Tengda T94
My phone has been bricked and after really hard work I could install CWM Recovery and I'm about to try the Spanish rom, so wanted to share what I have reached to before I forget.
----Do at you own risk-----
-My phone was in a boot loop and USB debugging was previously activated before it bricked
-I installed all the necessary drivers, USB_VCOM_Drivers (Available here: http://goo.im/devs/C3C0/THLW8/tools/USB_VCOM_drivers.zip)
I created the scatter file/map using MTK droid tool, and used the CWM Recovery of the Spanish Rom at this link:
http://www.movilesdualsim.com/foro/threads/42700-ROM-Custom-ROM-T94-v1-0b
I'm going to upload the scatter file and the CWMrecoveryT94.img, download this sp flash tool for quad core scatter files
http://www.4shared.com/zip/kf__h7u-/sp_flash_tool_zopomobileshop_q.html?cau2=403tNull
Switch off your phone, open SP Flash Tool Quad Core that you downloaded, choose the scatter file available here, double click recovery and choose the CWMrecoveryT94.img available here and press "Download" press yes for the message that appears and connect your phone, it will confirm the success by a green big circle message.
I will update my further proceeding.
Tengda T94 GPS never works
Does anyone have any idea about fixing the GPS problem? I watched a video in youtube in spanish who showed a working fast GPS but I don't understand what he says but he showed in the description that he added a copper foil piece to the GPS antenna, if anyone had luck fixing it please share.
Here is the video:
http://www.youtube.com/watch?v=hZGk1m25bzA
help tengda t94
i flashed tengda t94 spflash tools stockrom phone works boots but can see nothing phone works in background
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it) and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
AnY-One said:
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
Click to expand...
Click to collapse
What software version are you on?
Chuggers said:
What software version are you on?
Click to expand...
Click to collapse
Hello there and thanks helping me...
I'm AnY-One but i can't log in with; i dont know why...
I dont know what is my software version i only can say to you that the last update i tried to install came about 10-12/01 (EU France) and i bought this phone the 24/12 and i already did a first update.
So my phone stuck in bootloop (Qualcomm HS-USB QDLoader 9008 recognized) when i tried to install the 2nd update 10-12/01 so...
I have all qualcomm developpers tools with qualcomm flash utility and i can access to stock recovery...perhaps just a boot.img should work...
Pleassse help guys...
"and...as you can read; SORRY FOR MY ENGLISH"
---------- Post added at 05:32 PM ---------- Previous post was at 04:52 PM ----------
an update.zip that i can flash from recovery should be welcome
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
Got it, i think software version (viewing in recovery mode) is LTE_D0201121.0_S30_0.017.01
Zi0nlive said:
-snip-
Click to expand...
Click to collapse
Is warranty not an option?
nagalun said:
Is warranty not an option?
Click to expand...
Click to collapse
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Zi0nlive said:
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Click to expand...
Click to collapse
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
nagalun said:
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
Click to expand...
Click to collapse
That's a good question ; yes i can access to QDloader HS-USB 9008 with qualcomm drivers ; I CAN ONLY acces to
recovery holding VOL+ then plugin in USB. Phone off then : POWER + VOL+ doesnt boot recovery.
Wipe Data/factory seems to work, adb sideload; device is regognized in adb shell but most of commands answer are: "FAILED (remote: unknown command)" when i choose reboot in bootloader it's the boot screen with 'DC CHECK MODE' left corner..
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
How extract my proper firmware
Hello
How extract the om from the device
Help Me
Same problem...
I have the same problem too... Please help
sharing my experience in a similar quest
Hello ! You probably must have resolved the issue by now. Like you, I too had a similar issue ( Reliance Jio Lyf Wind4 - Haier L51)
In my nooby quest for a solution have made some progress. The learning is:
One needs : Mprg8909.hex, 8909_msimage.mbn, rawprogram0.xml, patch0,xml to recover.
If you can get hold of a phone similar to yours, you can dump all the partitions. That can then be used to get the required information to make your unique rawprogram0.xml. The process of dumping becomes very easy if the phone is root and you are running an insecure boot. Using basing Linux commands like fdisk,gparted,proc you can get and idea of your partition details. The dd command will help you dump the partitions.
Yes the tools to use is from the QPST suite or look for the stand alone emmcdl.exe
As your phone is showing the QUSB 9008 mode you need to be able to switch the phone to Emergency Download Mode after which you can use MIflash or similar tool to flash the ROm from the dumped images. Thats where the rawprogram0.xml comes in. It details partition information required to revive the phone.
Havent succeeded yet, but am feeling encouraged. Probably need to resolve syntax errors creating the rawprogram0.xml and figure out if just this much is enough to switch the phone to EDL.
After lurking here for months, this is my first post, therefore I request indulgence in case I have inadvertently erred
TooSour
AnY-One said:
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it)
and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Click to expand...
Click to collapse
You will need:
Hi
I have a similar issue with a different phone (Reliance LYF LS 5014 - a.k.a. Haier HL-L51) Service centres will claim that the motherboard needs to be changed (and charge you an arm and a leg ;p) Even if you get the firmware image it wont help. Thats becuase if you are bricked and in the QLoader 9008 , you first have to get the phone in EDL (emergency download mode) only then can you use MI Flash et al to flash your ROM.
The route I am taking is as follows: got hold of a similar phone and dumped all the partitions using the dd command. Then getting hold of all partition information using gdisk/parted/df et al This is so that I can create a partition.xml. From this I could run a Python script ( PartitionTool.py) to get rawprogram0.xml, patch0.xml. Using emmcldl and partiton.xml I can create the 8909_msimage.mbn . Hopefully, armed with these and QPST /Miflash I should be able to revive my phone. I have read that one needs the mprg8909.hex to kick the phone into EDL but am not convinced that without it I will remain stuck. That file seems to be guarded like a state secret by phone manufacturers.
ALl this I have learnt the hard way over almost a fortnight. I confess that I do fall into the "noob" category and cant program/develop to save my life. Therefore it should be easy for anyone with the right amount of enthu
Cheers
Zi0nlive said:
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
Click to expand...
Click to collapse
on continuing my quest for a solution
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
1. Why can't you go to the Rjio service center and get it flashed? Just tell them it got screwed after an update.
2. How did you manage to root the phone? Mine is Flame1 which has same MSM8909 chipset.
I am very not happy with the stock ROM but I don't think anyone has come up with a custom ROM for this cheap chipset.
I have bricked my CAT S30 too. Is there someone who have a solution? Or can somehow make a ROM copy so I can somehow flash it to the phone? I made a lot of searching and can not figure out how to make the phone work again.
hello I need firmware for S30 because I lightened too much after the root and I deleted something I should not, is now locked in the home screen CAT, but I can get into fastboot and bootloader.
thank you guys
file for CAT S30
Hello
I purchased another CAT S30 which has just lit downloaded a system update and I extracted from the cache, now the load so you can work on it.
if you need other things tell me how can I copy them from working phone.
my I crashed after I canceled the DownloadProviderUi.apk files and perhaps I put not compatible. now I can only access the fastboot or DC CHECK mode.
I tried to flash the .zip program but by mistake, I tried to flash the update and installs it by error although it says it has been installed, and still does not start, remains in the white screen CAT
https://www.dropbox.com/s/trqfxvnp90qt8vn/__FUMO.zip?dl=0
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
Hi.. i have a CAT S30 stuck in logo, how i can use your file? thanks
Hi got this same phone only two weeks ago, and broke it trying to root it, got stuck on Bootscreen, however I found an unofficial rom for the device, loaded into an SD card and applied via recovery and boom, its a working phone again.
If you still need help, let me know so I send you a link to the ROM.
Phone bricked stuck on Android screen,access to adb & fastboot logs provided [Solved]
Hello,
I recently messed up my phone. Long story short, I snatched an OTA, modified it and tried to force it on my phone. The vanilla OTA always failed in the check process because I modified some /system files on my phone. In result of that, a couple of files has been wrongly patched ( /system/app/OpenWnn/OpenWnn.apk ; /system/bin/debuggerd ; /system/bin/install-recovery.sh ; /system/priv-app/ApeCloudFileManager/ApeCloudFileManager.apk ; and maybe others indirectly ). I can provide more informations about my slip up if you wish.
Since then when I start my phone I'm stuck at the "Wiko, powered by Android" screen. I can access the stock recovery menu, and the factory mode. I also have access to my phone throught adb, adbd, and fastboot.
My phone is a Wiko Rainbow Lite 4G ( http://world.wikomobile.com/m745-rainbow-lite-4g ), the actual manfacturer is Tinno so the phone is probably sold under different names around the world, Wiko being only a "middle-man".
With that said, I can't flash the ROM using the utility given to me by Wiko. They do not provide "stock rom" with scatter file, but instead use their own software, a sole .exe file ready-to-use, you hook your phone to your pc, restart the phone by pressing random combination of buttons, and voila. However, I managed to extract the system.img, boot.img, etc files from the .exe . So I figured out I could try to use "fastboot flash system system.img" command to restore whatever files are messed up. Might as well not touch /recovery and /boot because I can access the recovery the phone seems to boot correctly ( from what I understand /boot is just a bootloader, so me being a pc-guy I wouldn't see the point of reinstalling GRUB if windows was missing a dll or something like that ) .
But the phone is locked .... Here's the "fastboot oem device-info" result
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
And I when I try to "fastboot oem unblock" :
Code:
FAILED (remote: oem unlock is not allowed)
So yeah .... I'm stuck there. If anyone got an idea, even a vague one of what I could try next to unbrick my phone that would be very kind of you. There's no wrong answers. So please if you got a couple minutes to spare (you already made it through my laïus which is already something ) I would be very grateful.
I'm thinking about extracting files from system.img and copy them on my /system partitions throught adbd with a script .... But I'm not sure if that would help or make it worse.
If you need informations here's the logcat I got under "factory mode" ; part1 : http://pastebin.com/nx7BC8K5 , part2 : http://pastebin.com/eU94B9VE
the pstree (because come on, if a phone can launch all of that, certainly there's something we can do to repair it) : http://pastebin.com/ZWd6vC9q
dmesg : http://pastebin.com/RYfbF0ub
prop : http://pastebin.com/k6T4bYnu
cpuinfo : http://pastebin.com/a6eMQTmd
PS : Yes I'm still a noob when it comes to Android, but please if you have any questions, need more informations, ask and I shall provide.
PPS : @moderators, I apologize if I posted in the wrong section, please redirect me
Since you extracted them, they now have a different signature and can therefore not be flashed onto the device because your bootloader only allows ROMs with their signature to be flashed successfully. Also, to clear things out, boot == kernel, boot =/ bootloader. Also, why exactly can't you flash it using their provided tools? If you are going to flash stock ROM you might as well reflash recovery and boot.
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Aramir said:
Thanks for answering.
I can't flash using their provided tool because the tools fails at 1% progression with a generic message error "oops something wrong happened, good luck with that kido, kisses".
Why do I don't want to flash recovery and boot ? Because these seems to work now, and I'm scared that if I break those I won't even be able to access my phone through adb,fastboot or get to recovery.
About the signature, I've seen plenty of topic/tool/stuff around the internet about how to unpack RUU images (is that what they're called or is RUU specific to htc ?) to update.zip files (eg: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/ ; http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/) . Problem being they're always wayyy outdated and approximative.
Honestly it would help me a lot in my research if I know what is even wrong with my phone.... I can't make sense of the logcat.
EDIT :
Ok I finally managed to reflash it using a more generic flashtool (designed for qualcomm based phone) named QFIL.exe, found it in this archive http://www.mediafire.com/download/4rgr02wi542n4sw/Qualcomm_tools_and_guidance.rar . Then I simply used the file found in the .exe files to populate the form and yabadabadou !
However my flash screen is now completly black .... I do not even have a prompt when selecting between recovery ("Power"+"vol-" then "vol+") and factory mode ("Power"+"vol-" then "vol-")...
Anyway, now that I know how to safely unbrick it. I can mess with it even more. But I probably should port CWM to it and do a backup pretty quick.....
Click to expand...
Click to collapse
YaY, you can now put [SOLVED] in the title to help other in the same issue you had!
Is this the right forum area? I posted over in CF-Auto root with no response, figured I would try here.
http://www.randmcnally.com/product/tnd-tablet
It supposedly has a custom proprietary build Rand McNally uses. It has a built in recovery of which I'll post a screen.
The "reboot to bootloader" option simply hangs on the boot screen.
I've tried kingroot/kingoroot, towelroot, and googled my life away trying to root this GPS/tablet.
There doesn't seem to be a way to flash a custom recovery without bricking it(unsupported device), and there's no way to pull the recovery.img without root!
Can anyone help? The rooting of these devices would open up a world of possibilities.
How is it possible to root this thing if its not recognized by fastboot? Any attempt of rebooting into bootloader even through external tools is stuck on bootscreen.
It allows the Delevoper option of unlocking bootloader, but how if I can't even send the command? Not only is bootloader locked, it seems completely off limits.
Some possibly relevant details from bugreport, and the logcat file???
========================================================
== dumpstate: 2017-08-30 20:23:15
========================================================
Build: LVY48E.20170428-091903
Build fingerprint: 'TNDT80B/tulip_p1/tulip-p1:5.1.1/LVY48E/20170428-091903:user/'
Bootloader: unknown
Radio: unknown
Network: (unknown)
Kernel: Linux version 3.10.65 ([email protected]) (gcc version 4.9.3 20150113 (prerelease) (Linaro GCC 4.9-2015.01-3) ) #3 SMP PREEMPT Fri Apr 28 09:03:37 CST 2017
Command line: enforcing=1 earlyprintk=sunxi-uart,0x01c28000 initcall_debug=0 console=ttyS0,115200 loglevel=0 root=/dev/system init=/init [email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected][email protected]:[email protected]:[email protected]:[email protected] cma=256M androidboot.serialno=74005034440c1c05088e androidboot.hardware=sun50iw1p1
------ MMC PERF (/sys/block/mmcblk0/stat) ------
*** /sys/block/mmcblk0/stat: No such file or directory
Ok, it is now recognized by my system by fastboot, but no fastboot commands will work! Stuck on the boot animation even though recognized.
Any checks for OEM Device info, Locked bootloader, or Tamper flags just hangs...
Down another rabbit hole after finding out this thing is an "AllWinner" brand Android tablet...
Hey, any chance you could upload the Launcher APK and lib s? I'm also investigating root on a TND740 (which is also Android based), so maybe I can help if I find anything out. The launcher would be awesome though. Thanks!
I'd love to put that software on my Asus Tablet <3 hook us up
tnd t80b bootloop no adb permissions
Hey guys, I have a bootloop on this tablet. And I managed to wipe adb certificates off it so I cant even adb in anymore. TND T80B Anyone have a stock Firmware or any clue how to use this tablet again.
Thanks for any help!
How did u get into fastboot mode from engineering menu? I cant seem too, it just reboots too system after about 1 min.
I assume, like to enter recovery menu, there is a key press combo i need too use after choosing fastboot mode, but i dont know what it is
I think you adb reboot ....
it could be .. bootloader.. fastboot..RUU...RRU..recovery..
I cant remember exactly. I had to get root first I think. this device has an Allwinner A64 chipset on a tulip board. Allwinner has everything available on github and a wiki site for building roms for this device and others.
Felmode... look it up... these are unbrickable...
if you find a rom or a Stockrom let me know please
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
if I could ever get a copy of the api or a compiler to work correctly on linux... I'd have my own to flash on.
Also I've never tried but there is another USB port on the back of this thing where the 2nd GPS hooks on. you might be able to boot or access some un secured path through that.
Lostwon said:
I think you adb reboot ....
it could be .. bootloader.. fastboot..RUU...RRU..recovery..
I cant remember exactly. I had to get root first I think. this device has an Allwinner A64 chipset on a tulip board. Allwinner has everything available on github and a wiki site for building roms for this device and others.
Felmode... look it up... these are unbrickable...
if you find a rom or a Stockrom let me know please
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
if I could ever get a copy of the api or a compiler to work correctly on linux... I'd have my own to flash on.
Also I've never tried but there is another USB port on the back of this thing where the 2nd GPS hooks on. you might be able to boot or access some un secured path through that.
Click to expand...
Click to collapse
I guess i should have been more careful when i posted here, i actually have an Rand McNally OveryDryve 8 not a TND series tablet, and thats the one i cant get into fastboot too get the bootloader unlocked and then root and stuff....
If i cant get fastboot commands too works i cant do anything else...
I would use dr.Phone like others have, but it does not install seemless root apparently, it modifies files that break updates, and i dont want that, id prefer Magisk with seemless so i can then install safteynet and gapps properly
How can I get a copy of the truck gps app to load on another tablet?
AllenScott said:
How can I get a copy of the truck gps app to load on another tablet?
Click to expand...
Click to collapse
Short answer.... You cant.... I tried with a previously rooted model too send the apk file, even if it installs on your new device, it wont work without ALL of the RM Services apps as well, and all have too be system apps and setup just right or its not going too work... I gave up and never ened up getting it too work because i couldnt get half of the apks too istall let alone run without crashing constantly...
I've spoken to rand and they seem to think their GPS hardware is better than that found in today's phones like they are Holy as ####. Their systems are junk but the 2.0 navigation is far worse, I want to pull the old software and install it to a newer or different device like y'all. I'm willing to put some money towards the goal, I know some of my friends would do the same, anyone up for starting a fund, or someone have the skills to make it happen? Let's get this rolling!
Side notes, if you look at the older devices specifically the tndt80 that has Google play on it, (newer ones don't!) I at one time had the installation files and installed them onto a cell phone. I was able to run a route comparison before the software realized my Samsung galaxy wasn't a tnd tablet, once it realized it wasn't one of their devices it had a message saying that and closed down.
I'm pretty sure that's on one of my old phones with a busted screen, I'll get some screens ordered and see if I'm right (hopefully!)
So besides the installation files that would be the next hurdle, maybe an emulator to bypass the device name/serial etc to allow it to run?