Hi guys I really really need help.
I successfully rooted and flashed custom ROM on Q maxi, but I had some issues with network unlock so I decided to go on stock ROM.
I went into SP flash tool, and did Auto Fromat, With Recovery options ticked.
Then I loaded my backup Scatter file, and downloaded "all" (I can see that my scatter file doesnt have RECOVERY, CACHE, USRDATA.) files to phone successfully.
After that phone boots into my carriers logo only and wont go past that, I even waited around 15 min but nothing happened.
When I try to boot into recovery with vol up + power it throws me some weird words like Emergancy call and some other stuff and nothing is usable and phone doesnt react to vol buttons for scroll.
But main thing is that recovery is deleted and cant use it.
Since my phone wont boot into my original ROM what other stuff can I try to put it normal state or stock state.
This is my girlfriends phone and I wanted to make it faster and to network unlock but it ended in bricking.
So please help or I wont see the light anymore :crying:
EDIT: In another words, I have phone that wont boot past logo screen, dont have usable recovery BUT I have android_scatter backup and have CWM backup of original rooted ROM. What can I do to get it into working state, please
Nailed said:
Hi guys I really really need help.
I successfully rooted and flashed custom ROM on Q maxi, but I had some issues with network unlock so I decided to go on stock ROM.
I went into SP flash tool, and did Auto Fromat, With Recovery options ticked.
Then I loaded my backup Scatter file, and downloaded "all" (I can see that my scatter file doesnt have RECOVERY, CACHE, USRDATA.) files to phone successfully.
After that phone boots into my carriers logo only and wont go past that, I even waited around 15 min but nothing happened.
When I try to boot into recovery with vol up + power it throws me some weird words like Emergancy call and some other stuff and nothing is usable and phone doesnt react to vol buttons for scroll.
But main thing is that recovery is deleted and cant use it.
Since my phone wont boot into my original ROM what other stuff can I try to put it normal state or stock state.
This is my girlfriends phone and I wanted to make it faster and to network unlock but it ended in bricking.
So please help or I wont see the light anymore :crying:
EDIT: In another words, I have phone that wont boot past logo screen, dont have usable recovery BUT I have android_scatter backup and have CWM backup of original rooted ROM. What can I do to get it into working state, please
Click to expand...
Click to collapse
do you made a backup with mtkdroidtools?
if yes, you should find a scatter file named "MT6572_Android_scatter.txt in your backup!
load it in spflashtool and it will load automaticaly all files except cache and data if your scatter file in a folder named "Files_to_flashTool"
if your scatter is in the backup folder you will get loaded all file except system, cache and data.
in backup folder system.img files are named system.ext4.img and is not readed by spflashtool(you should load it manualy).
if you dont have this "Files_for_flashTool", you can prepare it with mtkdroidtools from your backup(only if it is made with mtkdroidtools)
So, i think you dont have a system and recovery instaled after formating.
Zte Blade Q Maxi is hard to brick it, if you dont flash it with other pfone scatter(in that case your girlfiend will kill you too )
vaserbanix said:
do you made a backup with mtkdroidtools?
if yes, you should find a scatter file named "MT6572_Android_scatter.txt in your backup!
load it in spflashtool and it will load automaticaly all files except cache and data if your scatter file in a folder named "Files_to_flashTool"
if your scatter is in the backup folder you will get loaded all file except system, cache and data.
in backup folder system.img files are named system.ext4.img and is not readed by spflashtool(you should load it manualy).
if you dont have this "Files_for_flashTool", you can prepare it with mtkdroidtools from your backup(only if it is made with mtkdroidtools)
So, i think you dont have a system and recovery instaled after formating.
Zte Blade Q Maxi is hard to brick it, if you dont flash it with other pfone scatter(in that case your girlfiend will kill you too )
Click to expand...
Click to collapse
I managed it out.
Maybe this can be like kind of tutorial for others what I managed to did wrong and how I get out of it:
I formated whole phone with format tab in SP flash tool.
When I loaded backup android scatter file and downloaded it to phone, my phone went full hard brick, meaning it didnt react to power button so I couldnt even power it up. I was so f****d up and scared that I bricked it forever.
Using Common logic I looked at my android scatter file and noticed that UBOOT, RECOVERY, CACHE, USRDATA was missing (path line was empty).
Thing that I did is I pressed line for UBOOT so I load file, and in backup folder I found UBOOT file and pressed it so it loads.
Then when I flashed it I could power up my phone (so freaking happy), but then I encountered problem. It wont go past my logo screen of stock backup (problem from this thread), I saw from some users that after you go back on stock you need to go to recovery and wipe data/factory and cache.
But my recovery wasnt installed and couldnt get to it. Again using common logic and help from Vasebanix; if I formated whole phone and in scatter file there wasnt line for recovery thereby I must load recovery img into RECOVERY line of SP flash tool and flash it to phone. CWM recovery.img i downloaded from internet didnt worked and SP flash tool when i pressed download throws "incompatible chip" error.
Again then I looked into my backup folder and found blablamaxiq-recovery.img and then I loaded that file into android scatter file and flashed it to phone.
And then I had my sweet sweet recovery back.
Then I did factory and cache wipe, and my backup stock ROM booted up normally without stucking on logo screen.
So happy!
Thing why my phone hard bricked and didnt want even to powerup using power button was because I formated whole phone, and UBOOT file was not loaded into scatter.
Of course thats the same reason why I didnt have recovery too.
If anyone encountered this kind of problem but he/she did whole backup with MTK dorid tools.
You dont have to worry, and I hope someone my expirience with hard brick and soft brick will help.
Cheeeers people
And thank you Vaserbanix for beautiful ported ROMs that I am trying out currently.
Ps, sorry for paragraphing I was typing from phone
Related
I really hope someone can help me out. I think I bricked my phone.
I tried to recover my phone back to stock with stock recovery so I can send it in for repair. When I installed 2.3.4 OTA update through zip, I accidentally clicked yes for updating 2.3.6. I didn't know, went to washroom and my phone won't boot. I thought no worries I'll install the zip again. Going into recovery, there's an android picture with an exclamation mark. I can't boot into phone and cannot load recovery. Someone please help >_<
download CWM and try to flash it through fastboot, and use that to flash a new img. im assuming you've done this before, having a custom recovery before now. if not, make sure you have fastboot setup, and if you don't go look through a rooting guide how to set it up then once you have it set up, move the new recovery you downloaded to the same folder as fastboot, then type
fastboot flash recovery name_of_recovery
of course replace the name_of_recovery with the exact filename of the recovery you downloaded. you can get the ClockworkMod recovery I think at www.clockworkmod.com
then boot into the new recovery and go to Mounts and Storage and Mount USB, and take the update.zip that you have and load it onto your SD Card, then go into the recovery and do as you would to flash the zip
Problem is, I don't think usb debugged was enabled. I tried to lock bootloader so I can just take it back to my carrier and say phone is screwed up, but when I tried, it said device not found.
The only way I think is using odin.
[Q] TCL Idol X S950 Bootloop - Recovery can't mount internal storage "sdcard"
I have installed S4 themed ROM for s950 but after i did the wipe and at reboot appeared a notification "can't read sd card....format?" so i returned to recovery but says "e:can't mount cache\.." "e:can't open.." etc etc.
can someone help me?
PS. Sorry for my bad english
I have the exact same problem, did you found a solution?
bootloop
Hi guys, i have the same problem.After using TCL upgrade tool my device kept rebooting after the manufacturer logo was showing up.At first i could get into CWM recovery i tied everything from fixing permissions to wiping cache , dalvik etc. Then i tried to reflash CWM using sp flash tool
and now i cant even get into recovery. After that i tired with adb-fastboot but my device doesn't get recognized by adb.Its weird cause when i have the device plugged into powersource the device starts rebooting , and when i have it unplugged does nothing even i i press power button.
Anybody has an idea of what the problem might be?
Thanks in advance
errikozz said:
Hi guys, i have the same problem.After using TCL upgrade tool my device kept rebooting after the manufacturer logo was showing up.At first i could get into CWM recovery i tied everything from fixing permissions to wiping cache , dalvik etc. Then i tried to reflash CWM using sp flash tool
and now i cant even get into recovery. After that i tired with adb-fastboot but my device doesn't get recognized by adb.Its weird cause when i have the device plugged into powersource the device starts rebooting , and when i have it unplugged does nothing even i i press power button.
Anybody has an idea of what the problem might be?
Thanks in advance
Click to expand...
Click to collapse
If you have backup, try to flash it via sp flash tool. From sp flash tool format phone, and then flash everything checked, with original preloader. I had similar problem and that solved it.
If you don't have original backup, do not format phone from sp flash tool. Instead, try flashing official rom 4.4.2 (search on forum) and do as described. Just do not flash recovery from that rom. Download philz touch recovery (on same thread you have link), replace and flash. Conect phone, click Download on sp flash tool and press and hold power button until phone restarts.
Put_Nick said:
If you have backup, try to flash it via sp flash tool. From sp flash tool format phone, and then flash everything checked, with original preloader. I had similar problem and that solved it.
If you don't have original backup, do not format phone from sp flash tool. Instead, try flashing official rom 4.4.2 (search on forum) and do as described. Just do not flash recovery from that rom. Download philz touch recovery (on same thread you have link), replace and flash. Conect phone, click Download on sp flash tool and press and hold power button until phone restarts.
Click to expand...
Click to collapse
Thanks man , i flashed 4.4.2 and philz touch and the only diference now is that i can turn on the phone when is not connected to the power adapter.
im trying to enter recovery but still nothing ...
hei there i'm from romania and i don't know english to good, i hope ur understand.
ok so.....i'm rooted my phone and i've put cyanomogen mod and i didin't do a backup at stock rom...i've simple instal cyanomogen and i've deleted the past. ok, and today i was trying to instal stock rom, i don't know what i've done because now, my phone is stuck at recovery mode (i've formated everything in my phone, i just have twrp recovery and nothing) even if i mount my sd card on pc with twrp mount mode, i download a costum rom for him....and gapps, i put into phone then i install them...but finally still stuck at recovery and even if i reboot...still boot just recovery and i don't push the vol + or -.
i was trying the stock rom with update.app, i've downloaded huawei extractor, but when i put the update.app there....invalid or uknown file.
please i just want my phone back
I was running B618 on my phone (rooted and tweaked a little bit), A few days ago I realized that I am running an outdated version so I decided to update to B630. I downloaded the update extracted it with HUAWEI UPDATE EXTRACTOR and while extracting I saw there was an option to make flashable zip so I decided to try to flash it through TWRP (my biggest mistake). I restarted phone into recovery mode, wiped everything and flashed the zip and restarted the phone, at restarting TWRP warned me about NO OS INSTALLED but I ignored and restarted and boom.... I was holding a bricked phone, Nothing on screen not a single sign of phone being alive, just notification light blinking red and green when power button is pressed. Googled it on internet and found that it can be fixed through jtag box.
I took my phone to a repairer and he promised me that he can take my phone to fastboot mode by JTAG BOX and further software flashing I will do it myself. After 2 days he called me that your phone is successfully in fastboot mode you can take it. I took the phone from him paid him his fee and came back home, Now my phone was running a very basic version of EMUI 2.0 which was looking like EMUI 3.1 with no apps in it just some testing apps shortcuts and gallery and other basic apps. In about phone section it was showing android version 4.3 and EMUI 2.0 and internal storage was just 450mb.
I restarted into fastboot mode flashed the boot, cust, recovery, system and rebooted the phone and boom..... Once again a bricked phone with just total red screen. I googled and again found nothing, then I saw fastboot log on cmd and the issue was that the phone's eMMC is partitioned at just 450mbs and the 2.26GB system.img file is not able be saved into phone.
Is there a way I can fix this now, Its also not booting into recovery I've tried all the commands, and when I try to format through fastboot it gives an error saying that formatting is not allowed on file system type 0.5
PLEASE IF THERE'S ANY WAY TO FIX THIS PLEASE TELL ME
I WILL BE VERY THANKFUL TO YOU GUYS.
hbilalshah said:
I was running B618 on my phone (rooted and tweaked a little bit), A few days ago I realized that I am running an outdated version so I decided to update to B630. I downloaded the update extracted it with HUAWEI UPDATE EXTRACTOR and while extracting I saw there was an option to make flashable zip so I decided to try to flash it through TWRP (my biggest mistake). I restarted phone into recovery mode, wiped everything and flashed the zip and restarted the phone, at restarting TWRP warned me about NO OS INSTALLED but I ignored and restarted and boom.... I was holding a bricked phone, Nothing on screen not a single sign of phone being alive, just notification light blinking red and green when power button is pressed. Googled it on internet and found that it can be fixed through jtag box.
I took my phone to a repairer and he promised me that he can take my phone to fastboot mode by JTAG BOX and further software flashing I will do it myself. After 2 days he called me that your phone is successfully in fastboot mode you can take it. I took the phone from him paid him his fee and came back home, Now my phone was running a very basic version of EMUI 2.0 which was looking like EMUI 3.1 with no apps in it just some testing apps shortcuts and gallery and other basic apps. In about phone section it was showing android version 4.3 and EMUI 2.0 and internal storage was just 450mb.
I restarted into fastboot mode flashed the boot, cust, recovery, system and rebooted the phone and boom..... Once again a bricked phone with just total red screen. I googled and again found nothing, then I saw fastboot log on cmd and the issue was that the phone's eMMC is partitioned at just 450mbs and the 2.26GB system.img file is not able be saved into phone.
Is there a way I can fix this now, Its also not booting into recovery I've tried all the commands, and when I try to format through fastboot it gives an error saying that formatting is not allowed on file system type 0.5
PLEASE IF THERE'S ANY WAY TO FIX THIS PLEASE TELL ME
I WILL BE VERY THANKFUL TO YOU GUYS.
Click to expand...
Click to collapse
Did you try twrp and flashable b630 rom from hicloud?
same here need the dump file to try to unbrick my phone
Adi5 said:
Did you try twrp and flashable b630 rom from hicloud?
Click to expand...
Click to collapse
TWRP isn't booting up (TRIED EVERY METHOD)
hbilalshah said:
I was running B618 on my phone (rooted and tweaked a little bit), A few days ago I realized that I am running an outdated version so I decided to update to B630. I downloaded the update extracted it with HUAWEI UPDATE EXTRACTOR and while extracting I saw there was an option to make flashable zip so I decided to try to flash it through TWRP (my biggest mistake). I restarted phone into recovery mode, wiped everything and flashed the zip and restarted the phone, at restarting TWRP warned me about NO OS INSTALLED but I ignored and restarted and boom.... I was holding a bricked phone, Nothing on screen not a single sign of phone being alive, just notification light blinking red and green when power button is pressed. Googled it on internet and found that it can be fixed through jtag box.
I took my phone to a repairer and he promised me that he can take my phone to fastboot mode by JTAG BOX and further software flashing I will do it myself. After 2 days he called me that your phone is successfully in fastboot mode you can take it. I took the phone from him paid him his fee and came back home, Now my phone was running a very basic version of EMUI 2.0 which was looking like EMUI 3.1 with no apps in it just some testing apps shortcuts and gallery and other basic apps. In about phone section it was showing android version 4.3 and EMUI 2.0 and internal storage was just 450mb.
I restarted into fastboot mode flashed the boot, cust, recovery, system and rebooted the phone and boom..... Once again a bricked phone with just total red screen. I googled and again found nothing, then I saw fastboot log on cmd and the issue was that the phone's eMMC is partitioned at just 450mbs and the 2.26GB system.img file is not able be saved into phone.
Is there a way I can fix this now, Its also not booting into recovery I've tried all the commands, and when I try to format through fastboot it gives an error saying that formatting is not allowed on file system type 0.5
PLEASE IF THERE'S ANY WAY TO FIX THIS PLEASE TELL ME
I WILL BE VERY THANKFUL TO YOU GUYS.
Click to expand...
Click to collapse
If You are able to get TWRP or stock recovery WIPE ALL DATA FAST I had same problem, and after that it solves your issue! If not Open fastboot and Flash Userdata.img then boot, go in recovery and Wipe all data again! Keep me updated!
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
Mehdi008 said:
same here need the dump file to try to unbrick my phone
Click to expand...
Click to collapse
For Your issue, I recommend dc phoenix tool! It is ULTIMATE TOOL! BEWARE OF MEGA BRICK! If You will do all right. Your phone if boot in no time! Keep me updated!
RootingPro-18 said:
If You are able to get TWRP or stock recovery WIPE ALL DATA FAST I had same problem, and after that it solves your issue! If not Open fastboot and Flash Userdata.img then boot, go in recovery and Wipe all data again! Keep me updated!
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
For Your issue, I recommend dc phoenix tool! It is ULTIMATE TOOL! BEWARE OF MEGA BRICK! If You will do all right. Your phone if boot in no time! Keep me updated!
Click to expand...
Click to collapse
WHERE DO I GET USERDATA.img ???
hbilalshah said:
WHERE DO I GET USERDATA.img ???
Click to expand...
Click to collapse
From update.app extract and flash
Yesterday I tried to get rid of the ugly green UI on the TicWatch E following https://forum.xda-developers.com/smartwatch/other-smartwatches/ticwatch-e-chinese-version-ticwear-t3781183 . It worked, and my watch looked beautiful. But Bluetooth didn't work correctly. This wasn't a new issue, as the very first day I got the watch, I had the same issue. I tried to reboot, and many other solutions but had to reset like the first time. This time, it booted into TWRP as I had rooted my watch. I proceeded as normal, wiping the user data partition and cache, and rebooting. This time, the watch didn't reboot but went into TWRP instantly. I tried to reboot a couple of times, but ended up in TWRP every time. So I decide to do the most idiotic thing: try to reset again. This time, the watch simply shut off and dint respond to pressing the button. No sound, no vibration, nothing. Thankfully, it showed up in Mediatek flashing tool, so I followed https://forum.xda-developers.com/smartwatch/other-smartwatches/ticwatch-e-chinese-version-ticwear-t3781183 and got it to boot up. I messed up in flashing the userdata.img as well, but I doubt itll have any consequences as I then erased that partition using fast boot. Now, it has been showing the weird circle-throwing-ball animation for the last 4 hours.
For anyone finding this thread, this 7z worked for me
mega.nz/#!tw4hEZyA!xZD7RkSvnuXKcOayeHSvU3DMUat_NGLi0WI3nwIGU1A
Model WF12066
AutismicPootatoe said:
Yesterday I tried to ...
Click to expand...
Click to collapse
drive.google.com/open?id=1cLp_ALZhG-xdqd3fSj5xD7xj5UWfz95p
To explain more, that previous link was for android 5. It got the watch up and booting again. I found an Android 7 ROM on XDA, spliced in the img files and that booted too. Managed to get into TWRP and load my backups. Rerooted and enabled the black menus.
Above is a dump from my ticwatch e after all is said and done (except for userdata, that's still from the same link from above). The recovery is TWRP, system and boot are my restores from TWRP (running oreo), oem is preserved (to keep my oem.prop changes). The rest of the img files are from that mega link above (filename TicwearToAndroidWear.7z). Note: I haven't tested it, but if my SP Flash reading skills need some work, you should be able to replicate my steps ( download TicwearToAndroidWear.7z, replace recovery with TWRP, splice in the boot, system, userdata from forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3786600, then find a TWRP backup to restore from. I can probably provide my boot and system WIN files if my img files don't work.