Urgent help required..bricked x10i - General Questions and Answers

Hi Friends,
I have X10i, which was accidentally bricked last month. I have tried various options but couldn't find a solution.
Thorough analysis suggested that of all other failed methods...I found these clues..
when I use flasher tool from wotan to flash my mobile it says
ERROR: file header write failed.
few google searches suggested that this might be an issue where "NAND RAM" might be corrupted...
But, while flashing my phone with flashtool, I get a message that kernel.sin was flashed however i'm unable to flash "loader.sin" in my phone,
so if i'm not worng, please correct..if i'm........ if 'm able to flash kernel into my phone that means my NAND ram is not corrupt (no hardware problem)?
here some senior member has posted that
http://forum.xda-developers.com/showthread.php?t=1457458
how to flash a GalaxyS2, for the same problem, however ODIN doesn't work for Xperia X10i.
Looking out for suggestion, other than using the phone as paperweight...
Thanks in advance

u can try boot sin files using fastboot.
i think commands are:
fastboot flash boot kernel.sin
fastboot flash userdata userdata.sin
fastboot flash system system.sin
fastboot reboot
Click to expand...
Click to collapse
U get sin files after unpack ftf file with rom

Related

[Q] [FIXED] HELP! Possible Brick on Xoom MZ607 WIFI

Hey! I need all your help, please. Yesterday, I saw that Motorola reveled a tool to unlock the bootloader of our tablet (I know, late). I read all the information about the process, and I could do this on my mz607 wifi. I downloaded all that I need, drivers and android sdk. After that, I rebooted the xoom on bootloader using adb command but....I can't do anything on this!!
I looked for some information about this, and I found in all forums that I can unlock bootloader with "fastboot oem unlock" command. It's false, I cant do nothing!! I rebooted my tablet and now, always run on bootloader and not boot system.
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
I found a germany forum with the same problem (I think) but I don't understand how they solved this.This the link
After this, I looked for other solutions and I found a tool of Motorola, RSDLite. I downloaded the correct file for my model, and when it flashing (7 step for the tool) not flash the boot.img! It's flash correctly other file packages (recovery.img, fastboot, etc) but it can't flash boot.img
Now, when I do "vol up+vol down+power" and select "Normal Boot", It doesn't do anything, the system would be missing!
I think it's can be a soft brick....or no, I dont know. I'm very worried about this and I would appreciate all your help.
Thanks. I'm waiting your answer.
Anybody can help me????
Ok, Anybody wants to help me!
Bye.
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Joshbone said:
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
runandhide05 said:
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
Click to expand...
Click to collapse
So I have to find the same files for my MZ607? boot, recovery and system?
runandhide05 said:
You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Click to expand...
Click to collapse
Joshbone said:
So I have to find the same files for my MZ607? boot, recovery and system?
Click to expand...
Click to collapse
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Mjamocha said:
Click to expand...
Click to collapse
What??
Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Anybody more??
Joshbone said:
Anybody more??
Click to expand...
Click to collapse
Runandhide told you everything you need to know. You need to find the right regioned fastboot file for your mz607 and flash it. And that ypur bootloader is not unlockable. Any tutorial you were reading to unlock it would have to have been for the original xoom, not xoom2.
HELP! Possible Brick on Xoom MZ607 WIFI
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
f5bud said:
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
Click to expand...
Click to collapse
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Like the genius I am I've bricked mine too. It's a UK MZ607 that's been updated to JB from the US MZ609. I managed to delete the stock browser whilst trying to install a CyanogenMOD browser (long story) so figured I'd just repeat the steps that I used to flash the US MZ609 firmware. What I'd forgotten is that the first stage is to flash the US MZ609 ICS ROM then do an update to JB meaning I was effectively trying to downgrade. Everything flashes successfully except the boot partition which gives an error that it doesn't exist. Any ideas out there? I tried what I believe to be the original Fastboot file but no luck
Joshbone said:
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Click to expand...
Click to collapse
Also tried this and it fails when flashing the boot partition. I just ordered a factory cable to see if it can bring it back to life...
Is this zip still available?
alecbond said:
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
Click to expand...
Click to collapse
anybody who still has the mz607 files for a restore? The possible stock files link doesn't work any more...
http://sbf.droid-developers.org/xoom2/list.php

[SOLVED] Issues Booting on a XT925 - Unlocked device

Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Here some more infos I got while using DroidHD Utility Deluxe :
The command "fastboot flash aboot file.mbn" leads to a "error: cannot load 'folder/file.mbn'"
I managed to get a functional Driod Razr XT925 OS working by using the tool I mentioned before : DriodHD Utility Deluxe
Everything works well except those :
I can't read any backups made with TWRP before that (I mean the backups which were functionnal but that I couldnt manage to get back on).
I can't make my SIM work anymore, it says, unknown sim, and no network available when I'm trying to use my phone with GSM functions.
Managed to get my backups work again. The folder was under another name, which is why TWPR couldnt find it.
One last problem, my /efs partition has left me You already see the problem ? No IMEI around !
So I managed to find my IMEI number again and trying to use that http://forum.xda-developers.com/showthread.php?t=1960918 to write it back on my phone.
But...cause there's a but, I cant seem to use my USB drivers when I boot up in "BP Tools".
So impossible to access the phone, and impossible to write that "recovered" IMEI...
Anyone has a solution roaming around ?
Well at least I can feel like not being a total dumb ^^ Managed to install manually the driver for QC Diag Port, by selecting "Motorola" > "Motorola QC Diag Port" manually.
So, the BP tools mode can now be accessed from my computer, but here is another problem, I can communicate with the phone and even write my IMEI, but not on the phone Sounds like the entry 555 (which was totally absent) is in read-only mode :/
Here is the error given by RF NV Manager :
NvManager::writeToPhone(comPort, nvItems, throwException) -Unable to write 'NV_UE_IMEI_I' to the phone. (Parameter is write-protected and thus read only)
A clue ? Anyone ? Before I find it alone again, I think I'll soon be bald considering how I tear my hair since some hours...
Edit :
Ok so I tryed the QPST thing on a 32bits XP computer. Same problem.
I also tryed flashing my ROM into the stock one with RSD Lite, which is called like that :
9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC
Found it here : http://forum.xda-developers.com/showthread.php?t=2032284
Under that name :
Branding: Retail France/Retail Central Europe
Version: 9.8.2Q-8-XT925_VQU-22 FULL
Android Version: 4.1.2
Bootloader Version: N/A
Requires RSD Lite 6.0
Click to expand...
Click to collapse
And got an error (even after removing the getvar command) which is :
Failed flashing process. 2/22 flash partition "partition_signed"->Phone returned FAIL
Click to expand...
Click to collapse
Here is what the fastboot screen says :
Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
Final Edit (#Request lock) :
Ok so I finally got out of trouble.
Flashed to the stock rom with that rom : 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P 007_A004_CFC
Found it here : http://forum.xda-developers.com/show....php?t=2032284
And applyed that homemade script (which gets rid of the cache memory problem before system flash) :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen bcomes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot reboot
Then when I came back on my phone, my IMEI was back itself like a big one
4 days of SMS came back at that time, I'm saved
Hybris95 said:
Hi everyone,
I end up here after loads of searchs and manipulations unsuccessful...
Well here is my problem :
Edit : The problem much advanced, but is still not resolved, see 5th post for more information of current status
Final Edit : Problem solved, see the 5th post.
I have a Motorola Razr HD XT925 which is Unlocked.
I tryed flashing a custom rom on it, and failed hard.
Before failing that hard, I had some backups which were working perfectly, those, don't work anymore ...
So here is what I can access :
Fastboot (works perfectly, I can access it from my PC also without any issues)
Recovery (works "perfectly", the only thing is I cant restore any backups and I can't flash any ROM well yet, tryed Factory Reset also, does not work)
Normal boot just remains on "Warning bootloader unlocked"
By the way, by doing all that my backups have gone from my phone, so I only have em on my computer which is a bit hard when you want to try a restore (on a backup that was working perfectly before).
Another thing I noticed, when trying to Factory reset for example, It says "Unable to mount '/data'" which is a bit hard if you want to write data ^^
If anyone has an idea, feel free to make a comment, any idea is accepted since I can't use my phone at all...
Feel free to ask any question if you need more information or if you did not understand something.
Click to expand...
Click to collapse
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
Click to expand...
Click to collapse
i realy need your help
arinata1983 said:
i have a same problem, could you tell me step by to solve it.. thanks before
---------- Post added at 01:35 PM ---------- Previous post was at 01:02 PM ----------
i realy need your help
Click to expand...
Click to collapse
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Hybris95 said:
My post clearly says the steps I made to get rid of my problem.
If you don't understand a step or want more information on a step, tell me which one at least.
Click to expand...
Click to collapse
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
arinata1983 said:
i dont understand where and how should i start for the homemade script...
where can i find the firmware?
Click to expand...
Click to collapse
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Hybris95 said:
You should be able to find your stock rom here (for JellyBean 4.1.2) :
http://forum.xda-developers.com/showthread.php?t=2032284
And here (for Ice Cream Sandwich 4.0.4) :
http://forum.xda-developers.com/showthread.php?t=1943879
Extract your stock rom into a folder then copy these files into this folder :
"fastboot.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
And about the script, write it into a file called "flash_fastboot_hybris.bat" using your favorite text editor (notepad or notepad++ for example).
Then copy this file into the stock rom folder.
Then boot up your smartphone into fastboot mode, plug it to your computer and execute "flash_fastboot_hybris.bat".
Follow the script insctructions, and your smartphone should be back to its stock recovery.
Tell me if you need some files or more information.
Click to expand...
Click to collapse
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
arinata1983 said:
flashing succes, but it stuck on red circle motorola boot animation. i think i can't find a correct firmware...
and than, i try to flash stock firmware using droidHD utility 2.0 lite, i flashed it without modem (fastboot restore 4.1.2 stock (dont flash modem) )
and now my xt925 running on verizon's droid razrhd firmware without imei,everything running great,but the network stuck in edge.
what should i do now??
Click to expand...
Click to collapse
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
fixed
Hybris95 said:
For my own story, when I had successfully flash with droidHD utility, I flashed back using my own script and it worked.
If it doesn't then your problem is probably different from mine (your IMEI is probably corrupted), you could try using QPST and modify entry #550 with your own IMEI.
Click to expand...
Click to collapse
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
arinata1983 said:
hey brother.. the problem was solved today
i tried to QPST, but it said that the system is write protected, and then i've find this post http://forum.xda-developers.com/showthread.php?p=46476292#post46476292
there are three steps, on the first step i really frustrated, flashing via rsd not work at all even i edit the script as told.
but i remember your " homemade script" it work perfectly....
i get my imei back just by flashing an ICS france firmware..
THANKS brother..
Click to expand...
Click to collapse
You're welcome, I had been stuck like you which is why I made that homemade script

can i hope to restart my huawei mate 7?

hi guys, i have done issues on issues on this phone, at begin I accindentally formatted the system by a cwm recovery, i tried all to make another one,after a lot of process i realized that it was not possible, i had first tried to flash a rom b cwm and he gived me and error like,func NO:10(func_BOOt_recovery)
error NO:2. I solved this with a program that gived me a recovery stock, I was 4.4 on my phone before the accident, i tried all the update, 4.4,5.1.6.0 with normal combination (power but, butt + butt-) with stock recovery, it start the process but at 98% stop, in every case. so I tried to create a flashable rom with cwm thanks to huawei update exatractor, tried the process, and now i'am really blocked, if i try to go in recovery the phone give me the problem error: NO:12 (func_load_iom3) error NO:1,I tried to change recovery by fastboot mode, but nothing, whit any recovery the phone say to me the same error. can u help me? sorry for my bad eng thank you.
Do you remember what firmware you have before format system in Cwm???? If you remember download that same firmware and extract using huawei update extractor and flash this partitions in fast boot.
If you have 4.4.2 flash system.img , boot.img , recovery.img, userdata.img and after this try go to recovery and write what it's happan
Send from ? . If I help you buy me ?
chudy_85 said:
Do you remember what firmware you have before format system in Cwm???? If you remember download that same firmware and extract using huawei update extractor and flash this partitions in fast boot.
If you have 4.4.2 flash system.img , boot.img , recovery.img, userdata.img and after this try go to recovery and write what it's happan
Send from . If I help you buy me
Click to expand...
Click to collapse
i have 4.4.2 but when i try to flash system.img or something else fastboot say to me
target reported max download size of 471859200 byte
error: cannot load 'recovery.img': No error
Unlock bootloader again with your code
Send from ? . If I help you buy me ?
chudy_85 said:
Unlock bootloader again with your code
Send from . If I help you buy me
Click to expand...
Click to collapse
in my phone screen appear fastboot and rescue mode phone unlocked, anyway i tried but adb don't recognize my phone
Install hi suite and then install adb on C:/
Cmd as admin and then write this command
cd C:/adb
Fastboot devices
And check do you have here your S/N number
Send from ? . If I help you buy me ?
chudy_85 said:
Install hi suite and then install adb on C:/
Cmd as admin and then write this command
cd C:/adb
Fastboot devices
And check do you have here your S/N number
Send from . If I help you buy me
Click to expand...
Click to collapse
when i try fastboot oem unlock it give me this error:
FAILED (remote: data parse fail)
finished. total time: 0.002s
It's mean you have unlocked bootloader. You break your system partition and you must flash only backup using twrp or you must try flash img file by fast boot. If you can you can try repair your mate 7 using DC unlocker. Search in google and check how they repair smartfone but you must buy some credits to work!!! 4 credits it's 4 euro. Read how much you need
Send from ? . If I help you buy me ?
chudy_85 said:
It's mean you have unlocked bootloader. You break your system partition and you must flash only backup using twrp or you must try flash img file by fast boot. If you can you can try repair your mate 7 using DC unlocker. Search in google and check how they repair smartfone but you must buy some credits to work!!! 4 credits it's 4 euro. Read how much you need
Send from . If I help you buy me
Click to expand...
Click to collapse
with a program i have flashed system.img cust.img recovery .img but I read on internet that the problem is the file senshorhub.img, this programm didn't flash it, and i can't by fastboot for various issues,also if i flash recovery or system recovery's phone doesn't work. i have an answer why fastboot should not work instead dc unlocker can work?
correct you must use dc phoenix. This program can flash full firmware. Read about here ----> https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

How to restore my hard bricked zte q505t

Hello,
I'm new to XDA and I really need help in fixing by hard bricked ZTE Q505T (4g) device. I just got this phone like last month and I successfully rooted it, and then i edited something in the build.prop which began my problem. Whenever i boot the phone, logo shows but then the screen starts flashing white and black and vibrates on key press. At then I could boot into my recovery, which I figured out that my device was soft bricked. Allelujah!!! at then, i boot into recovery, downloaded my stock rom which was in a .zip format, copied it to my SD card, tried to "install update from SD card" option (I don't have a custom recovery since my device was too rare), got "E: signature validation error, installation aborted" error, I tried using the "apply update from ADB" option as well and the adb sideload program on my PC, got same error on my phone. Since my device was a qualcomm device, I googled "How to unbrick a qualcomm device" and came across a site where it said (among its steps to follow) to use miniTool partition to format my device's partition, and I did, and that began the second phase of my problem , cos I later got to realize i just deleted my recovery image as well and the other step to follow to restore it with QFIL was to have my firmware image not a .zip type and that was the only one I could online, a firmware.zip that Just contained the boot.img, META.INF folder and system folder, no recovery.img
and the other stuffs needed. I tried my luck if I could use the extracted .zip for flashing back to my stock rom, but got a Sahara Failed/Error report. Right now I'm stuck :crying: don't know what to do, except if someone here could help me to get a backup firmware image with all its needed files for my phone let me try again. My device has an inbuilt battery but thank goodness it is a qualcomm HS-USB QDLoader 9008 driver. Right now the device can't boot up or show any logo or even charge or show the LED, but my system recognizes it as a qualcomm HS-USB QDLoader 9008 whenever i plug it in, that gave me alot of hope, I know i messed big time, Please just help me :crying::angel: !!!!!
Hello, I have the same phone, and I have the same problem as you, I have not been able to solve my case, do you know any solution?
No, not YET:crying:
RyanRaphael said:
Hello,
I'm new to XDA and I really need help in fixing by hard bricked ZTE Q505T (4g) device. I just got this phone like last month and I successfully rooted it, and then i edited something in the build.prop which began my problem. Whenever i boot the phone, logo shows but then the screen starts flashing white and black and vibrates on key press. At then I could boot into my recovery, which I figured out that my device was soft bricked. Allelujah!!! at then, i boot into recovery, downloaded my stock rom which was in a .zip format, copied it to my SD card, tried to "install update from SD card" option (I don't have a custom recovery since my device was too rare), got "E: signature validation error, installation aborted" error, I tried using the "apply update from ADB" option as well and the adb sideload program on my PC, got same error on my phone. Since my device was a qualcomm device, I googled "How to unbrick a qualcomm device" and came across a site where it said (among its steps to follow) to use miniTool partition to format my device's partition, and I did, and that began the second phase of my problem , cos I later got to realize i just deleted my recovery image as well and the other step to follow to restore it with QFIL was to have my firmware image not a .zip type and that was the only one I could online, a firmware.zip that Just contained the boot.img, META.INF folder and system folder, no recovery.img
and the other stuffs needed. I tried my luck if I could use the extracted .zip for flashing back to my stock rom, but got a Sahara Failed/Error report. Right now I'm stuck :crying: don't know what to do, except if someone here could help me to get a backup firmware image with all its needed files for my phone let me try again. My device has an inbuilt battery but thank goodness it is a qualcomm HS-USB QDLoader 9008 driver. Right now the device can't boot up or show any logo or even charge or show the LED, but my system recognizes it as a qualcomm HS-USB QDLoader 9008 whenever i plug it in, that gave me alot of hope, I know i messed big time, Please just help me :crying::angel: !!!!!
Click to expand...
Click to collapse
Try a Google search for:
"Unbrick qhsusb qdloader 9008"
You'll find many different guides for fixing this, try them all, just make sure that the tools and files you use are for your specific model number.
tygans77 said:
Hello, I have the same phone, and I have the same problem as you, I have not been able to solve my case, do you know any solution?
Click to expand...
Click to collapse
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
zteQ505T
RyanRaphael said:
No, not YET:crying:
Click to expand...
Click to collapse
My problem is with partition tables I can not install any ROM with recovery, I use twrp, but I do not know how I can repair the partitions.
tygans77 said:
My problem is with partition tables I can not install any ROM with recovery, I use twrp, but I do not know how I can repair the partitions.
Click to expand...
Click to collapse
Do you have the stock firmware for your device?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Do you have the stock firmware for your device?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
If I have the original stock firmware for my device, the bad thing I can not install,
tygans77 said:
If I have the original stock firmware for my device, the bad thing I can not install,
Click to expand...
Click to collapse
Do you have a PC with adb/fastboot installed and set up correctly?
Can you boot to TWRP and successfully connect to adb?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
RyanRaphael said:
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
Click to expand...
Click to collapse
The file you have is not the stock firmware, it's a copy of your stock ROM that has been converted into a flashable.zip that is designed to be flashed in custom recovery(TWRP). Or its a stock update that only contains a bootloader update and a system update.
It isn't a copy of what you need.
If you can get into fastboot mode then you can flash TWRP then use TWRP to flash the stock.zip that you have.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
RyanRaphael said:
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
Click to expand...
Click to collapse
Well, the only help I can offer you since I can only get there, this is the TWRP recovery link http://pan.baidu.com/s/1c0BGANQ
After downloading, you should install it using Fastboot by running this command "fastboot -i 0x19d2 boot twrp-2.8.7.0-q505t.img"
---------- Post added at 01:53 PM ---------- Previous post was at 01:37 PM ----------
Droidriven said:
Do you have a PC with adb/fastboot installed and set up correctly?
Can you boot to TWRP and successfully connect to adb?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
If I have TWRP on my device I can connect adb and fastboot correctly, but I could not install the ROM via Zip or fastboot or adb since I have problems with the partitions
tygans77 said:
Well, the only help I can offer you since I can only get there, this is the TWRP recovery link http://pan.baidu.com/s/1c0BGANQ
After downloading, you should install it using Fastboot by running this command "fastboot -i 0x19d2 boot twrp-2.8.7.0-q505t.img"
---------- Post added at 01:53 PM ---------- Previous post was at 01:37 PM ----------
If I have TWRP on my device I can connect adb and fastboot correctly, but I could not install the ROM via Zip or fastboot or adb since I have problems with the partitions
Click to expand...
Click to collapse
Find the full stock firmware. Then extract the firmware until you get to the individual .img files inside the firmware (boot, system, recovery, etc...)
Then use fastboot to flash each .img by itself.
Or
Use adb shell and dd commands to dd the individual .img files to their correct partitions. If you don't understand how to use dd commands then this method is too dangerous for you, if you don't get the dd commands exactly right then you'll only damage your device worse and then you won't be able to fix it at all.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
---------- Post added at 09:15 AM ---------- Previous post was at 09:06 AM ----------
RyanRaphael said:
I don't even have a recovery installed at all on my device cos I deleted my device's partition, The stock firmware I have is a .zip format, with only a META.INF, System Folder and a Boot.img file in it and a ".sh" file extension etc. I don't know where to get a "Stock firmware" for my device with a boot.img, cache.img, recovery.img, .mbn and .xml files etc.
Click to expand...
Click to collapse
You need the full stock firmware and you need to do the Google search I suggested:
"Unbrick qhsusb dloader 9008"
Those search terms will show you many different guides for solving your issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
pls Tygans can u send me d firmware u have??
UPDATE!!!
Now I was able to get the firmware, but each time I try using other qualcomm flashing tools (except QFIL as i keep getting Sahara Error report), my device just can't be detected for some reason I'm not aware of, anytime I try, either I get stuck at the "Waiting for Device" or a "Can't detect device" error, what can I do please, ANY HELP is greatly appreciated
RyanRaphael said:
UPDATE!!!
Now I was able to get the firmware, but each time I try using other qualcomm flashing tools (except QFIL as i keep getting Sahara Error report), my device just can't be detected for some reason I'm not aware of, anytime I try, either I get stuck at the "Waiting for Device" or a "Can't detect device" error, what can I do please, ANY HELP is greatly appreciated
Click to expand...
Click to collapse
I have been looking for the name of the sahara.xml application that I could not get, we were there, you do not have cell phone backup?
tygans77 said:
I have been looking for the name of the sahara.xml application that I could not get, we were there, you do not have cell phone backup?
Click to expand...
Click to collapse
Yes, Can you give me the format of your firmware? like the order of files and folders, just trying to be sure of what i downloaded....
Cos I have an error with ZTE Tool Studio-eMMC Download Tool, says missing tpsfw0109.mbn stuff....
THANKS IN ADVANCE...

Phone vibrating with blackscreen after flashing new boot.img

So, i was trying to flash a new boot.img but when i rebooted my device the screen went black and started vibrating.
I do have a recovery image but the problem is that i can't get it to recovery or to the bootloader.
Any ideas on how to fix it?
EDIT: the image was patched using magisk
Here is the boot.img
Hi! So the problem seems to be that your device is Hard Bricked. Can you boot to recovery or fastboot/bootloader? If you can just flash the boot.img file without it being modified. Hope this helps
No, I wasn't able to get it to anywhere.
While searching for a fix i saw that other people were having the same issue.
Did you try using SP Flash Tool?
If you did and got errors just send them here.
NOTE: Do not use SP Flash Tool V6, the best option is latest SP Flash Tool V5
EDIT: If you get errors also try V3.x
NoveNoki said:
Did you try using SP Flash Tool?
If you did and got errors just send them here.
NOTE: Do not use SP Flash Tool V6, the best option is latest SP Flash Tool V5
EDIT: If you get errors also try V3.x
Click to expand...
Click to collapse
ERROR : STATUS_SCATTER_FILE_INVALID (-1073545215) , MSP ERROE CODE : 0x00.
The scatter file format is invalid!
[HINT]:
Please select a valid load or ask for help.
What device do you have. Also, that user prob not gonna respond, they have been inactive for a year.

Categories

Resources