Hi everyone!
It was yesterday, when I plugged a 3.5 audio jack from a speaker to my Xiaomi Redmi Note 4x (Mido), the LED light flash red, and the phone turned off.I tried to turn it on, and all I got is bootloop (Mi logo with Unlocked >> Mi logo with Android, again and again)
I did a full backup in TWRP, and flashed a new rom, AND... the bootloop continue...
So I did some researches, and found a solution:
After flash a new rom, make a backup of that rom using TWRP > go to Wipe > Wipe Dalvik/Cache and wipe Cache > restore the backup and reboot.
I passed the bootloop, the MIUI 9 logo show up, setup somethings like language, accept Terms and Conditions, and... wait, there's no wifi, no signal, and definitely can not sign in to Mi Account, can not do anything, just sit there and staring at the login screen...
Then I think about the full backup up there ^
Restored, no bootloop, no Mi Account, just stuck at lockscreen, its said wrong password > back to TWRP > Advance > File Manager > /data/system > delete gatekeeper.key (2 files), locksetting (3 files), reboot and I got in to the screen.
So the problems are, there is no Wifi, no MAC address, unknown baseband, no signal.
MEID, IMEI still there, TWRP, fastboot still working.
Can someone help me about this case please!
Thank you so much!
P/s: Sorry about my English, my bad presentation ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you tried to flash full dev firmware with Mitools? That was useful for my when I lost my EFS folder.... But first, format data and system with TWRP.
ramping said:
Did you tried to flash full dev firmware with Mitools? That was useful for my when I lost my EFS folder.... But first, format data and system with TWRP.
Click to expand...
Click to collapse
Do you mean XiaoMiTool?
If XiaoMiTool, I tried once, and fall to bootloop
tunglam24111993 said:
Hi everyone!
It was yesterday, when I plugged a 3.5 audio jack from a speaker to my Xiaomi Redmi Note 4x (Mido), the LED light flash red, and the phone turned off.I tried to turn it on, and all I got is bootloop (Mi logo with Unlocked >> Mi logo with Android, again and again)
I did a full backup in TWRP, and flashed a new rom, AND... the bootloop continue...
So I did some researches, and found a solution:
After flash a new rom, make a backup of that rom using TWRP > go to Wipe > Wipe Dalvik/Cache and wipe Cache > restore the backup and reboot.
I passed the bootloop, the MIUI 9 logo show up, setup somethings like language, accept Terms and Conditions, and... wait, there's no wifi, no signal, and definitely can not sign in to Mi Account, can not do anything, just sit there and staring at the login screen...
Then I think about the full backup up there ^
Restored, no bootloop, no Mi Account, just stuck at lockscreen, its said wrong password > back to TWRP > Advance > File Manager > /data/system > delete gatekeeper.key (2 files), locksetting (3 files), reboot and I got in to the screen.
So the problems are, there is no Wifi, no MAC address, unknown baseband, no signal.
MEID, IMEI still there, TWRP, fastboot still working.
Can someone help me about this case please!
Thank you so much!
P/s: Sorry about my English, my bad presentation ^^
Click to expand...
Click to collapse
seems like a firmware issue, i would suggest u to format data and reinstall miui
Theres a thread on the dev subforum with firmware extracted from miui full rom. Flash that via twrp.
Maybe is firmware.
Look at this.
MyNameIsRage said:
seems like a firmware issue, i would suggest u to format data and reinstall miui
Click to expand...
Click to collapse
coldplug said:
Theres a thread on the dev subforum with firmware extracted from miui full rom. Flash that via twrp.
Click to expand...
Click to collapse
jqm_ said:
Maybe is firmware.
Look at this.
Click to expand...
Click to collapse
I've tried flash a few roms for a dozen times, the result return the same.
But I will try these after work.
Thank you guys so much! :fingers-crossed::fingers-crossed::fingers-crossed:
download the modem files for mido. flash the zip. that will solve this issue. i had the same problem. flashing the modem files solved it.
MyNameIsRage said:
seems like a firmware issue, i would suggest u to format data and reinstall miui
Click to expand...
Click to collapse
coldplug said:
Theres a thread on the dev subforum with firmware extracted from miui full rom. Flash that via twrp.
Click to expand...
Click to collapse
jqm_ said:
Maybe is firmware.
Look at this.
Click to expand...
Click to collapse
My lastest backup was from a global MIUI rom flashed via XiaoMiTool.
"mido_global_images_8.1.18_20180118.0000.00_7.0_global_c557dab2eb"
(this is what I got in XiaoMiTool/rom folder in my PC).
At that thread's step 4, after flash those things, when I reboot it's show "No OS Installed, continue?"
Tried several times, same result
AND: The backup I had after I get the bootloop, not a backup when my phone still working.
i have same issue 2 weeks ago
the solution is to restore a file qcn and xqcn of the same model of your device (the exact same model)
you can restore this files by a program called QPST and you have to install qualcom driver before use of program
to use program you have to put your device in diagnostic mode enable USB debug in developer mode then use this code *#*#717717#*#* to enter diagnostic mode ( no need for root to do this )
after this your device will work but you have to restore your serial number, IMEI, wifi mac, bluetooth mac use the qualcom special tool to do this.
if you don't have the mac of wifi and bluetooth keep the one given to you by the qcn file you restored as no chance to be on same network with the same device .
NB. you can try to get your serial, IMEI, mac adresses use qualcom special tool before you start anything, so you can restore them later, you must be in diagnostic mode also to use qualcom special tool.
dr.moh1976 said:
i have same issue 2 weeks ago
the solution is to restore a file qcn and xqcn of the same model of your device (the exact same model)
you can restore this files by a program called QPST and you have to install qualcom driver before use of program
to use program you have to put your device in diagnostic mode enable USB debug in developer mode then use this code *#*#717717#*#* to enter diagnostic mode ( no need for root to do this )
after this your device will work but you have to restore your serial number, IMEI, wifi mac, bluetooth mac use the qualcom special tool to do this.
if you don't have the mac of wifi and bluetooth keep the one given to you by the qcn file you restored as no chance to be on same network with the same device .
NB. you can try to get your serial, IMEI, mac adresses use qualcom special tool before you start anything, so you can restore them later, you must be in diagnostic mode also to use qualcom special tool.
Click to expand...
Click to collapse
Tried this method yesterday, and when I try to restore, there's always an error, like "this qcn is not for my device" something, even I force it to restore, there're still an error. (I already edit the QCN file to my IMEI)
But as I said, my IMEI still there, so I stop trying that.
Now I'm stuck at bootloop, AGAIN...
tunglam24111993 said:
Tried this method yesterday, and when I try to restore, there's always an error, like "this qcn is not for my device" something, even I force it to restore, there're still an error. (I already edit the QCN file to my IMEI)
But as I said, my IMEI still there, so I stop trying that.
Now I'm stuck at bootloop, AGAIN...
Click to expand...
Click to collapse
Have u tried flashing latest firmware through twrp and then flash rom?
akisg said:
Have u tried flashing latest firmware through twrp and then flash rom?
Click to expand...
Click to collapse
You mean first format, wipe > install firmware > install rom?
akisg said:
Have u tried flashing latest firmware through twrp and then flash rom?
Click to expand...
Click to collapse
You mean:
Format dada/Wipe all > install firmware.zip > install rom.zip?
Let me try!
Do a full wipe and install the global dev ROM using TWRP. I've had that issue and it was solved using that process. Just wipe system, data, caches then install the global dev ROM using TWRP. Backups that have the firmware and bootloader partition included won't work.
tunglam24111993 said:
Tried this method yesterday, and when I try to restore, there's always an error, like "this qcn is not for my device" something, even I force it to restore, there're still an error. (I already edit the QCN file to my IMEI)
But as I said, my IMEI still there, so I stop trying that.
Now I'm stuck at bootloop, AGAIN...
Click to expand...
Click to collapse
ok my frist prolem also was bootloop
i tried every thing for 1 month even opened my device and connected the test points to reflash room as hardbricked device.
and at once every thing goes right after many failed trials now fully working device.
my advice is to read every tetourial carefully and try to read it from many sources always some small parts are missing like the correct drivers , disable windows signature enforcement, run as administrator , types of port and COM seen in device manager.
i am sure your device will work cause i have the same and no one helped in maitenance and company tell they will replace the chipset.
already i reached hard brick once in my trials there was no fastboot nor EDL.
don't stop.
---------- Post added at 04:38 PM ---------- Previous post was at 04:33 PM ----------
"this qcn is not for my device"
i got that error too when i used the one provided from internet
then i tried again with qcn i take from a friend phone we buy same models at same time
and it worked fine and no error
this is why i told you to get qcn from the same exact model
Now I'm stuck at bootloop, AGAIN... [/QUOTE]
It's hardware problem.
There's one guy get the same issues with me, he take his phone to a repair service, they replace the mainboard.
I think because of the high power (idk how to say) of the speaker, it get my device shock?
However, I send my phone to a repair service too, and still waiting for their call.
Thank you guys for your support, I really appreciated!
Same happened with me exact same with speaker
tunglam24111993 said:
It's hardware problem.
There's one guy get the same issues with me, he take his phone to a repair service, they replace the mainboard.
I think because of the high power (idk how to say) of the speaker, it get my device shock?
However, I send my phone to a repair service too, and still waiting for their call.
Thank you guys for your support, I really appreciated!
Click to expand...
Click to collapse
Same happened with me exact same with speaker
tunglam24111993 said:
It's hardware problem.
There's one guy get the same issues with me, he take his phone to a repair service, they replace the mainboard.
I think because of the high power (idk how to say) of the speaker, it get my device shock?
However, I send my phone to a repair service too, and still waiting for their call.
Thank you guys for your support, I really appreciated!
Click to expand...
Click to collapse
Could you solve the problem?
Related
Hi my friends In this guide i will teach you how to root your Jiayu g5s+
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steps:
1.Drivers
2.Rooting
3.backup with mtkdroidtools
4.Install cwm through mtkdroid tools
1.DriversDownload the drivers and mtkdroidtools from here : https://mega.co.nz/#!z9oXgCpD!5Vil8gYSC3rwUdTIImt0PYKRObbZVc17i4GpVx7RKQw
extract the archive and connect your phone with debugging enabled
then go to start and type device manager you will see that adb driver arent installed double click on it locate usb folder you extracted and your done
or google how to install adb drivers
2.RootingThere are many tools to root this phone
the tools you can use to root your jiayu are
1.Cydia Impactor
2.Kingoroot <-i recommend this how to root go here -> http://androidxda.com/root-android-device-using-kingo-root
3.Vroot <-Becareful this one is backdoored run it via sandboxie http://sandboxie.com/
3.Backup with mtkdroidtoolsdownload scatter file https://mega.co.nz/#!KwpWURQC!8CGoDjsE-BsGwBOT08Ljzu9XsXlfIFo3uBKRYb-VvaU and put in mtkdroid tools directory
copy scatter also in backup directory of your phone
open mtk droid tools connect phone with usb debugging enabled then go to "root,backup,recovery" tab click on backup and wait till its funished
then click on "to prepare blocks for flash tool" then choose files.md5 and wait till its finished
4.cwm recoverythere are many tools you can use to install cwm recovery
but these two i used are good
1.open mtk droid tools go to "root,backup,recovery" tab click on "recovery and boot" button
Please check always your phone the tools ask you for revoke acces you have to allow them
2.Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY
http://forum.xda-developers.com/showthread.php?t=2748169
Download here my backup : https://mega.co.nz/#!DlhEGKJC!GJYxUBaJIaiEMuqnCMmctgO7XYnvcrlpo9aJ1S1wCac
Many thanks my friend, you have saved my phone, it works correctly now
We will keep alive this thread for any news for this phone.
Again, thank you very match.
Amazing timing, I just started looking for ROMs for this phone yesterday and today you post!
Subscribed for future updates
Have any one problemes with TitaniumBackup ?
I can not backup any thing, restore any things !
the sdcard contains already app backups (from an other phone) TB already see them but no way to restore.
bricked Jiayu G5S+ (Elephone P6i)
Hi!
I tried to change the ROM for a friend's fake Jiayu G5S+ phone (a have some previous experience with flashing ROMs but neither me and especially my friend didn't know about this being a fake) so I tried to flash a G5S ROM and the phone now is bricked. The SP_Flash stops after the red stripe, "DA Download 100%" and that is all. From time to time I hear the sound of a new connected device in my PC speakers and the MTK USB port reappears in Device Manager.
Any idea how could I revive this phone, even it is a fake ?
My friend is very sad as I ruined his phone. Anyway, he couldn't use it with the original ROM because the touchscreen keyboard wasn't calibrated, he could not type almost anything.
L.E.: I tried to flash the backup that Gr4nDT3R0R posted above, now I get this error BROM ERROR: S_CHIP_TYPE_NOT_MATCH. I guess the ROM is not for my chip(set):
In the picture, I see that you do not provide the preloader.bin, you must give it (it is a part of the backup).
Then you have also to provide android, cache and data images, even from other ROM (system.img is in the backup, and you can extract cache.img and userdata.img from an p6i ROM)
Use, as you do, "format all + download" and it must works (if your phone is JY-G5S+, otherwise, use an entire ROM from elephone p6i)
Sent from my ZOPO ZP990+ using XDA Free mobile app
Yes, it might be wrong what I showed in that picture, I guess I tried a dozen of times to flash different ROMs. Today I finally managed to flash the original ROM provided by the author of this topic. It seems that after plugging in the phone to the USB port, right after the "ding-dong" sound you have to insert the battery. So I could see the so long waited yellow bar. After this I used the MTK Droid Tools and which showed that in fact the phone is a Quad Core MTK i6, 4.4.2, ALPS.KK1.MP1.v2.13 phone (instead of Jiayu G5S+, full HD screen, octa core...). I don't know how but after repeated tries now the phone is showing the real specs in About phone section.
Anyway, the reason I tried to change the ROM is that the touchscreen is acting weirdly, it is not calibrated, it is impossible to tap a text using the virtual keyboard. Even the menu items are very hard to tap as they don't respond to touching but the ones from vicinity. I have found a few recent videos with the same problems on Youtube but none have the solution. The screen is 540x960 and I guess the LCD driver is not the proper one.
Right know I am glad I managed to revive my friend's phone but I am pretty sad of his loss (I recommended him to by another trusted phone but he wouldn't listen to me).
Maybe in time, some smart guys will find any workaround for these Jiayu G5S+ fakes.
Jiayu g5s+ fake
Hi I Jiayu G5S + fake. I downloaded the rom elephone P6I update. The sp falasha tool I put the firmware upgrade. All went well. But the phone is now dead. When I try to give my deposit so still lists the error. If you give the firmware upgrade takes place so blue about three times and then prints cheksum failed. If so I will just download again writes PMT changed for the rom, it must be downloaded. Please if anyone know help us some advice.
fake Jiayu G5s+
doldik611 said:
Hi I Jiayu G5S + fake. I downloaded the rom elephone P6I update. The sp falasha tool I put the firmware upgrade. All went well. But the phone is now dead. When I try to give my deposit so still lists the error. If you give the firmware upgrade takes place so blue about three times and then prints cheksum failed. If so I will just download again writes PMT changed for the rom, it must be downloaded. Please if anyone know help us some advice.
Click to expand...
Click to collapse
sorry for my english
I'd done so.
I used this version of SP.FlashTool v3.1320.0.174.
In addition to the files for flashtool is in this post, add the two missing (cache and userdata) of this rom.
http://www.needrom.com/download/elephone-p6i/
Then select all and give a firmaware upgrade and also mark "DA DL All whit check sum" and has to work.
luck:good:
:good::good::good::good::good::good:
Super. Already mobile lives. It is everything. Your procedure is a 100%. Had 24 hours of suffering.
I also do not know English. I am from Slovakia.
Once again many thanks.
doldik611 said:
:good::good::good::good::good::good:
Super. Already mobile lives. It is everything. Your procedure is a 100%. Had 24 hours of suffering.
I also do not know English. I am from Slovakia.
Once again many thanks.
Click to expand...
Click to collapse
Glad many, it is a pleasure to help
Just do not understand why he had killed the recording rom from elephone P6I.Everything passed smoothly until final confirmation.Everything passed smoothly until final confirmation. I used SP_Flash_Tool_v5.1352.01.A choice of upgrade.Through net download it would not let me on.Well, after reboot phone has not responded to anything.Then somehow after about 50 experiment has released a record at least preloader.The display has been seen batteries.Again, after several attempts we have recorded the entire archive.But the phone cycles through the android logo.They let me into the start menu via the minus button and start.No I did not find the file from the backup to SD card.Meanwhile told me the phone and I revived to full finery.I also tried older flash tool, but not load file scater.I wanted to remove the fake hardware information.Therefore, I recorded the rom elephone.And he made I have a lot of joy instead of worry.I did not know that the phone is fake when buying.But when I gave her ignorance was added resellers deceive my next concern.I do not know what a cell phone.What is hardware and what rom fit into it.I would be grateful if someone figured out how rom is good for this model.
fake
doldik611 said:
Just do not understand why he had killed the recording rom from elephone P6I.Everything passed smoothly until final confirmation.Everything passed smoothly until final confirmation. I used SP_Flash_Tool_v5.1352.01.A choice of upgrade.Through net download it would not let me on.Well, after reboot phone has not responded to anything.Then somehow after about 50 experiment has released a record at least preloader.The display has been seen batteries.Again, after several attempts we have recorded the entire archive.But the phone cycles through the android logo.They let me into the start menu via the minus button and start.No I did not find the file from the backup to SD card.Meanwhile told me the phone and I revived to full finery.I also tried older flash tool, but not load file scater.I wanted to remove the fake hardware information.Therefore, I recorded the rom elephone.And he made I have a lot of joy instead of worry.I did not know that the phone is fake when buying.But when I gave her ignorance was added resellers deceive my next concern.I do not know what a cell phone.What is hardware and what rom fit into it.I would be grateful if someone figured out how rom is good for this model.
Click to expand...
Click to collapse
http://service.elephone.hk/forum.php?mod=forumdisplay&fid=98#.VGzQbvmG8Zn
looking here
Thanks.You do not have to quote such a long post.
Original rom for ELPHONE not want to work. I run the risk of custom rom?
doldik611 said:
Thanks.You do not have to quote such a long post.
Original rom for ELPHONE not want to work. I run the risk of custom rom?
Click to expand...
Click to collapse
developments???io find nothing , the custom MIU , goes just as bad , I've tried, and locks the touch
You have Jiayu G5S +?Use the old rom how did you get it?You rom works by elephone P6I?
doldik611 said:
You have Jiayu G5S +?Use the old rom how did you get it?You rom works by elephone P6I?
Click to expand...
Click to collapse
Yes, I hold Jiayu G5S +, but I do not keep the rom originale.l'ho lost by putting a rom Jiayu G5S original (wrong) and I raised up with this post.
you have the original rom Jiayu G5S + ?????
Have a little different.Because I put the factory settings.And then I made a backup.When you try to load the rom elephone I had a brick.After recording my backup files from + 2 elephone I do not have computer and boot logo Jiayu, but android.Rom of elephone not want to work.I tried to put preloader.bin from my backup, but hangs at log elephone.
The information on phone type I: i6 and quad core.
Online test of CPU-Z as follows: http://valid.canardpc.com/a/2amvfb
doldik611 said:
Have a little different.Because I put the factory settings.And then I made a backup.When you try to load the rom elephone I had a brick.After recording my backup files from + 2 elephone I do not have computer and boot logo Jiayu, but android.Rom of elephone not want to work.I tried to put preloader.bin from my backup, but hangs at log elephone.
The information on phone type I: i6 and quad core.
Online test of CPU-Z as follows: http://valid.canardpc.com/a/2amvfb
Click to expand...
Click to collapse
we get closer to the truth.
try this (looks much better).
You'll say
http://www.needrom.com/download/zlr-i6/
I tried and the phone did not work - brick.I do not remember what rom would be good.To show the actual hardware.And there are still other data.We do not know what brand and model really is.While we remain in a false indication.Therefore, I would like to prefer the original rom.I did not have to look for information under the designation as a fake.So no elephone P6I.It just seems so outwardly.But (intestines) hardware is different.Perhaps better, but also can be worse.While this is a mystery.:laugh:
I've already tried many apps, such as kingoroot, kingroot, one click root, framaroot, etc. i really need help. Thx in advance
kebakkaran said:
I've already tried many apps, such as kingoroot, kingroot, one click root, framaroot, etc. i really need help. Thx in advance
Click to expand...
Click to collapse
I have same problem
Sent from my SM-J320FN using Tapatalk
imrandewana said:
I have same problem
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Same issue here as well, nothing I try works on this phone, it's driving me insane.
EDIT: It's android 6, so you can't root the phone without a custom recovery.
WELP. So I just spent the past 2 days wasting my time on this god awful phone. I can't even access fastboot on this piece of crap, it comes up for 2 seconds and then disappears and no amount of "properly" installing usb drivers for it has helped. I even tried disabling driver signing and installing the drivers through adding legacy hardware. Nothing worked at all. So I thought I'd just install a custom recovery with sp flash tool. So I downloaded a stock rom for the vfd300 (my phone) from here: https://androidmtk.com/download-vodafone-stock-rom-models and ported TWRP using an ASUS Zenfone GO's TWRP.img.
Custom Recovery works fine, the phone does not. It is now stuck in a bootloop. Tried formatting everything (from TWRP) doesn't work. Tried flashing the rom again (even with the stock recovery) still stuck at bootloop, tried about 3 other vfd300 stock roms that people have uploaded to http://forum.gsmhosting.com and none of them have worked either. Currently downloading yet ANOTHER one and tbh I don't have high hopes. (EDIT: It didn't work)
Any help at this point would be appreciated.
Holy crispy crap it started............................. So I managed to find a working rom from (what appeared to be) some Vietnamese file hosting website .
You follow the instructions below at your own risk. No one is responsible for any damage done to your device but you.
I officially have root working on this device.
Now that I've done it, it's a surprisingly simple procedure. As I stated in the edit in my reply above, the VFD300 has Android 6 on it, which requires (afaik) a systemless root to be installed from recovery.
I ported the custom recovery from this thread (since the Z00VD has the same chip as the VFD) which you can download here.
Download the latest version of Chainfires beta SuperSU installer from this thread and transfer it to either your phones internal storage or SD card.
Also download a copy of SP Flash tool (if your fastboot works, use that instead). Finally, you will need this scatter file.
Unplug your phone from the computer and shut it down. Open SP Flash tool and click the download tab at the top.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click "choose" next to the Scatter-loading file box and select the path to the scatter file you downloaded. IMPORTANT Make sure all boxes below except recovery are unchecked and select Download Only in the drop-down box. Double click on recovery in the Location column and point it to the custom recovery image you downloaded.
Click the Download button at the top and then plug your phone back in. The bottom bar will turn red, then purple, then yellow and once it is fully done flashing you will get a pop-up box with a green tick as confirmation.
Unplug your phone and reboot into recovery (Power+Vol-Up). In the custom recovery, select install, go to the directory you transferred Chainfires beta SuperSU.zip to, install it and reboot. TWRP will ask you if you want it to install root, DO NOT LET IT INSTALL ROOT. Your phone may loop a few times and can take up to 10 minutes to boot the first time, but it will be successfully rooted.
If you need a copy of the stock rom, download this one. If you want to flash this rom, make sure you use the scatter file in the roms archive and select firmware upgrade from the Download Only box on SP Flash Tool.
EDIT: I'm so sorry I borked the hyperlink order. Instead of linking to the scatter file I linked to the entire rom and vice versa with the stock rom link
Vikeyev
vikeyev please contact me at [email protected]
Hey ummm, this is a great tut. I have problem with mine though unfortunately :/. I've done all steps correctly, with each of them followed thoroughly but then I get to the point where my device isn't identified when I connect it to the computer. None of those colored 'bottom bars' pop up nor the green tick as confirmation concept. PLEASE HELP ME !
[UPDATE] When I disconnect my device, some BROM error comes up but idek what it means.
InevitableDefeat276 said:
Hey ummm, this is a great tut. I have problem with mine though unfortunately :/. I've done all steps correctly, with each of them followed thoroughly but then I get to the point where my device isn't identified when I connect it to the computer. None of those colored 'bottom bars' pop up nor the green tick as confirmation concept. PLEASE HELP ME !
[UPDATE] When I disconnect my device, some BROM error comes up but idek what it means.
Click to expand...
Click to collapse
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
kathy9911 said:
vikeyev please contact me at [email protected]
Click to expand...
Click to collapse
....why?
stuck on loading
hi i'm a bit stumped here i followed all the steps to root my vfd 300 i got custom recovery installed but now when i reboot it the phone just sits on the loading part about 30 minutes i been waiting is there any thing i have missed or can do to solve this
thanks in advance
putzwon said:
hi i'm a bit stumped here i followed all the steps to root my vfd 300 i got custom recovery installed but now when i reboot it the phone just sits on the loading part about 30 minutes i been waiting is there any thing i have missed or can do to solve this
thanks in advance
Click to expand...
Click to collapse
Sounds like a boot loop. You need to download the stock rom (it should be about 700mb or so and in rar format). Once you've downloaded the stock rom, extract the archive to a folder somewhere (you will need something like 7zip or Winrar). Open SP Flash tool, load the scatter file from the extracted folder and make sure you select every box. There should be a check mark in each box. Change SP Flash tools dropdown box to firmware upgrade (by default it is on Download Only) and then flash it similar to how you did with the recovery (make sure you change the recovery to the custom one from above).
If my instructions aren't clear enough, I can do it again to my phone and take pictures of the entire process to make it easier to follow.
vikeyev said:
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
....why?
Click to expand...
Click to collapse
Yeah man! I've done that as well but had no luck .
1. I've enabled USB Debugging Mode and I've shut my phone down (NOTE: It has not been connected to the computer)
2. I opened the SP Flash tool and I clicked the download tab at the top
3. I then choose next to the scatter-file thing and have relocated it to the scatter file that I've downloaded from your link
4. ALL boxes are unchecked except recovery with download-only in the drop-down box
5. I've done the recovery image and everything and then...
6. I plug my phone in (Yes, it's completely shut down from step 1) with the USB cable and nothing shows up (Colored bars, tick etc.)
7. When I unplug it, an error comes up and then I'm completely stuck with no idea of what to do next
[UPDATE] - Does my phone have to be on the latest version?
Same problem
I'm having the same issue. I follow the instructions, phone off, press download, etc. I dont get any bars changing colours.
Did you manage to sort it out yet?
[update] managed to work it out. the MT65xx drivers werent installed properly. Use the instructions here (I cant post links!!! google: sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices) to get them working first, make sure the battery is out of your phone and the main instructions in this thread work first time.
huggies15 said:
I'm having the same issue. I follow the instructions, phone off, press download, etc. I dont get any bars changing colours.
Did you manage to sort it out yet?
[update] managed to work it out. the MT65xx drivers werent installed properly. Use the instructions here (I cant post links!!! google: sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices) to get them working first, make sure the battery is out of your phone and the main instructions in this thread work first time.
Click to expand...
Click to collapse
My brother, you're a genius . Thanks for helping out! It was worked. God bless!
stuck with a white circle runs
hi bro, i met the same issue.
I've done all the step successfully, and after i reboot my phone, it shows up with the logo of Vodafone, then a big circle became a smaller one, and then, the small circle runs endlessly.
I can go in recovery, but cannot boot the system.
I also did a memory test, got tow error
ERROR: NAND Flash was not detected!
ERROR: UFS was not detected!
I tried many times, and format whole flash and download all of them again.
it just doesn't work.
please help, thank you in advance.
frepeak said:
hi bro, i met the same issue.
I've done all the step successfully, and after i reboot my phone, it shows up with the logo of Vodafone, then a big circle became a smaller one, and then, the small circle runs endlessly.
I can go in recovery, but cannot boot the system.
I also did a memory test, got tow error
ERROR: NAND Flash was not detected!
ERROR: UFS was not detected!
I tried many times, and format whole flash and download all of them again.
it just doesn't work.
please help, thank you in advance.
Click to expand...
Click to collapse
Bro I got the EXACT same issue now because I accidentally installed Supersu through TWRP (which is pretty stupid because it was mentioned to AVOID the Supersu prompt when exiting TWRP). I've been stuck on bootloop for a couple of days now .
---------- Post added at 11:39 PM ---------- Previous post was at 11:14 PM ----------
vikeyev said:
Did you make sure to power off your phone and unplug the USB, then press download and reconnect your phones usb? Don't turn the phone back on, just replug it in after you hit the download button.
....why?
Click to expand...
Click to collapse
Bro, I accidentally installed Supersu when the prompt came up as I tried to exit TWRP. I know you said to NOT let it install, which was pretty stupid that I didn't read carefully what you wrote. Now I'm stuck in bootloop -_-.
Please help bro; I've tried flashing it to the stock rom, removing dalvik cache and everything etc. Nothing's working. Please help!
successfully got a rooted vfd 300
InevitableDefeat276 said:
Bro I got the EXACT same issue now because I accidentally installed Supersu through TWRP (which is pretty stupid because it was mentioned to AVOID the Supersu prompt when exiting TWRP). I've been stuck on bootloop for a couple of days now .
---------- Post added at 11:39 PM ---------- Previous post was at 11:14 PM ----------
Bro, I accidentally installed Supersu when the prompt came up as I tried to exit TWRP. I know you said to NOT let it install, which was pretty stupid that I didn't read carefully what you wrote. Now I'm stuck in bootloop -_-.
Please help bro; I've tried flashing it to the stock rom, removing dalvik cache and everything etc. Nothing's working. Please help!
Click to expand...
Click to collapse
I was stuck in bootloop, but we don't share the same reason. I think there is something wrong with the rom above.
I found another rom, flash it, and problem solved, pretty simple. Now, I have a rooted vfd 300, even better than the stock rom, but you need to delete some app you don't like before you enjoy it.
you can find this rom by searching MT6580_S00_EMMC_MRA58K__6.0_VFD-300_Vodafone.zip
frepeak said:
I was stuck in bootloop, but we don't share the same reason. I think there is something wrong with the rom above.
I found another rom, flash it, and problem solved, pretty simple. Now, I have a rooted vfd 300, even better than the stock rom, but you need to delete some app you don't like before you enjoy it.
you can find this rom by searching MT6580_S00_EMMC_MRA58K__6.0_VFD-300_Vodafone.zip
Click to expand...
Click to collapse
can you provide link please google z not giving results for me
Vodafon VFD300 Firmware + TWRP + ROOT
As recommended above, Vodafon vfd 300 as a result of the phone turned on until the endless download -TWRP was not requested, sr1-SuperSU-v2.82 - sr120170608224931 and flash driver SP Flash Tool 3.1352.01 (5.1352.01) did not fit. I decided to solve the problem - the vfd 300 flashed through the firmware MT6580_S00_EMMC_MRA58K__6.0_VFD 300_Vodafone_356774071726533_08_19_2016_09_02_53 (1) (2), the flash driver SP_Flash_Tool_v5.1648_vin - the next way (remove the battery, hold the volume (-) until the end of the firmware, Download, connect the cable to the phone (the firmware will go to Emergency port about 8 minutes)
****************Next, we flash the TWRP - the flash driver SP_Flash_Tool_v5.1648_ the scatter and the TWRP are recommended - (MT6580_Android_scatter.Tht and
*Recovery-TWRP-VFD300.img) flashing.
**********We check TWRP (we clamp simultaneously ON-volume (+) release ON-opens TWRP.
**********Get Root rights ---- copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to the phone folder, turn off the phone, go to TWRP find Install - SuperSu - Swaipe to instal - Dj not Install. All made happy, good luck. There will be questions [email protected]
InevitableDefeat276 said:
Yeah man! I've done that as well but had no luck .
1. I've enabled USB Debugging Mode and I've shut my phone down (NOTE: It has not been connected to the computer)
2. I opened the SP Flash tool and I clicked the download tab at the top
3. I then choose next to the scatter-file thing and have relocated it to the scatter file that I've downloaded from your link
4. ALL boxes are unchecked except recovery with download-only in the drop-down box
5. I've done the recovery image and everything and then...
6. I plug my phone in (Yes, it's completely shut down from step 1) with the USB cable and nothing shows up (Colored bars, tick etc.)
7. When I unplug it, an error comes up and then I'm completely stuck with no idea of what to do next
[UPDATE] - Does my phone have to be on the latest version?
Click to expand...
Click to collapse
you need to make sure you click download on flash tool then plug the usb in to phone and pc (also remember the battery has to be out of the phone for it to flash)
then you should see the red,yellow, green colours.
Hi all. I will be attempting to root my Vodafone VFD-300 tomorrow,after reading through the entire thread there seems to have been many issues with getting it done successfully. I also saw that it was suggested to provide step by step screenshots of the entire process. If anyone who managed to do the whole rooting with no problems could please do so again and provide us with the step by step screenshots,it would be greatly appreciated. Thanks in advance.
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
File not found on your drive
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
Update ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rafaello21 said:
Update ?
Click to expand...
Click to collapse
update possible for official rom :
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/open?id=1WjXKj8abnghy_OjfUW5TYkAppjWg0amH
I am looking for a stock rom of The Alpha X 6/128.
Have you any news ?
Thanks!
Originally posted here
Flash v03, root and recover lost IMEI
I have the 6/64 version. I'll share my method with you. The only one that didn't stuck me in booting TWRP over and over again.
First, I used fastboot flash recovery recovery.img and immediately after fastboot flash boot boot.img . It's the only way I managed to escape the problem. Now, I flashed the ROM provided by them, linked in this post here #123 and I lost IMEI. I used chamelephon to insert IMEI and the IMEI is there but I can't get any signal. What to do?!
Later edit: that didn't work the second time I tried. Neither camelephon.
New method: The last thing I tried was also successful. So, I flashed the ROM they gave me (coolicool store), which you can find here. I selected "auto flash" and "except bootloader" options in SP Flash Tool, pressed "start" and let it on for 3 second and pressed "stop". Then I selected "format all+download", pressed download and connected my phone while holding VOLUME UP. I kept it pressed a few seconds after seeing the red bar getting to 100%. After flashing I started the phone and installed the latest version OTA, v04. After updating I flashed recovery by fastboot flash recovery recovery.img. Of course, I was stuck in booting in TWRP like every other time so I thought of recovering boot from a backup, and since I didn't have one of my own, I used the one provided by @dreambo found here (thanks dude). When I was prompted to select the items I want to recover, I thought of choosing only "boot", in order to restore boot, but I said why not try restoring "nvram" and "nvdata" too, maybe it will solve my other problem , the lost IMEI problem. And it worked.
I finally succeeded to restore my IMEI and boot, thanks to a recovery, which, now I see, is mandatory before every modification you implement on your phone. Especially when you don't have original ROM.
Sorry for the long post and I hope it comes in handy
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
I have a Maze Alpha X 64GB in which I can only see a black screen will not turn on at all. Only the red charging LED light turns on to say that the phone is charging and connected to the computer.
I have tried flashing the ROM in the link in your post in this thread but only receive BROM errors in the SP Flash Tool.
I have tried the second link full rom V03 6/64GB Rom Official Stock as well but this one does not have a Preloader so I cannot use this ROM to unbrick my phone as my phone will not turn on it needs a Preloader for the phone to turn on.
My phone is being detected by my computer as it makes a sound when connecting the USB cable and also shows up in the Device Manager. Have also tried another computer and tried another USB Type-C cable but only receive BROM errors in the SP Flash Tool.
I have also uninstalled and re-installed the latest Mediatek drivers.
Any ideas?
I'm pretty sure it does have a preloader, since I have used it twice to install with SPFlash Tools.
amonapophis said:
I'm pretty sure it does have a preloader, since I have used it twice to install with SPFlash Tools.
Click to expand...
Click to collapse
This ROM does not contain a Preloader:
full rom V03 6/64GB Rom Ofifcial Stock
That ROM would work if your phone is turning on. My Maze Alpha X does not turn on at all hence the need for a ROM that has a Preloader so that I can get the phone to turn on again.
I have tried the ROM in the first post in this thread I keep getting "could not get PMT info" error messages in the SP Flash Tool. That ROM has a Preloader included.
I have installed the Mediatek drivers that are on the Maze Mobile Download Center and have tried different computers with different USB Type-C cables with no luck. My Maze Alpha X is still dead and won't turn on only the red charging light turns on and stays on when connected to USB or Mains. The charging light does not go green to show that the phone is fully charged even if the phone has been plugged in for 6 to 8 hours.
Any ideas?
Don't use the one provided by OP. Use the one I got from Maze, it's complete. Download here, it's the official version. I haven't tested the one provided by OP, but the one posted by me here is the one that works. You will find a folder named 18-02-06... and inside one named R14. There you will find all the files needed, including preloader. I have to warn you, though, you will lose IMEI by flashing it ( I don't know why) and the method to restore it is quite complicated, but I wrote it above. Good luck restoring your phone!
shinystar77 said:
This ROM does not contain a Preloader:
full rom V03 6/64GB Rom Ofifcial Stock
That ROM would work if your phone is turning on. My Maze Alpha X does not turn on at all hence the need for a ROM that has a Preloader so that I can get the phone to turn on again.
I have tried the ROM in the first post in this thread I keep getting "could not get PMT info" error messages in the SP Flash Tool. That ROM has a Preloader included.
I have installed the Mediatek drivers that are on the Maze Mobile Download Center and have tried different computers with different USB Type-C cables with no luck. My Maze Alpha X is still dead and won't turn on only the red charging light turns on and stays on when connected to USB or Mains. The charging light does not go green to show that the phone is fully charged even if the phone has been plugged in for 6 to 8 hours.
Any ideas?
Click to expand...
Click to collapse
amonapophis said:
Don't use the one provided by OP. Use the one I got from Maze, it's complete. Download here, it's the official version. I haven't tested the one provided by OP, but the one posted by me here is the one that works. You will find a folder named 18-02-06... and inside one named R14. There you will find all the files needed, including preloader. I have to warn you, though, you will lose IMEI by flashing it ( I don't know why) and the method to restore it is quite complicated, but I wrote it above. Good luck restoring your phone!
Click to expand...
Click to collapse
I have tried that link just now downloaded and installed everything properly followed the instructions to a tee but still get the same errors.
I have installed the Drivers that came with the ROM that you have given to me which like you said are official directly from Maze but this has not made a difference for my Maze Alpha X 64GB.
I tried flashing with the Maze Alpha Flash Tool but just receive a DA error:
I tried flashing with the SP Flash Tool but receive a failed to get PMT info error:
Any Idea as to what I am doing wrong here or is my phone just hard-bricked?
I have noticed that on SPFT you selected "firmware upgrade". You should use "format all and download". Maybe this fixes your problem. I am not that much of a techie but I hope you will solve your problem.
amonapophis said:
I have noticed that on SPFT you selected "firmware upgrade". You should use "format all and download". Maybe this fixes your problem. I am not that much of a techie but I hope you will solve your problem.
Click to expand...
Click to collapse
I have tried Format All + Download but get this error:
I have also tried Download only but get this error:
shinystar77 said:
I have tried Format All + Download but get this error:
I have also tried Download only but get this error:
Click to expand...
Click to collapse
I'm sorry to hear that. Unfortunately, this forum seems dead and I can't help you, since I don't know that much either... It might help if you get to those phone servicing shops.
Hello guys, I was one the unfortunate guys who tried to downgrade from an updated XLOADER version FW to an older and failed to do so, resulting a hard brick. I managed to get my phone up and running again with free tools without DC-Phoenix, I include everything detailed in my post, even a preconfigured virtualbox linux system for the initial steps. I also included an UPDATE.app splitter too.
So, this is not an XLOADER downgrade tutorial, with this you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
What you need for this whole thing:
This archive, it contains the firmware, the tools, the preconfigured linux, and the drivers.
VirtualBox downloaded and installed, just google it.
A physically opened phone, unscrewed motherboard, as the testpoint is on the other side, and something to short your testpoint.
First steps:
After you downloaded the archive, just unzip the whole thing to a folder where you have enough space ( the archive is ~7.8GB unzipped)
Now you need to download and install VirtualBox, and import the HIKEY.ova virtual system I included in the zip.
Here's how you can do it
Step one, The HIKEY.ova file is located in the virtual machine folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step two, Leave the settings at default and import it
Setting up your phone and computer:
You need to open up your phone physically, here is a good video of the disassembly https://www.youtube.com/watch?v=Zkj7YVeSzS4
Now, if you got your motherboard unscrewed, you must leave the cable with the big arrow connected to it.
Plug your usb cable into your phone and into your computer, now you must short your testpoint, I included an image about where the testpoint is. https://i.imgur.com/q9ZNGgx.jpg
Just use metal tweezers or a bent metal paperclip, one end on the test point, and the other end to something you can ground it with, the metal shields next to it are good to use.
If you did everything right, your computer should recognize a new device named USB SER, if this is the case, you now must install the huawei android phone drivers. Now the USB SER is now recognized as HUAWEI USB COM 1.0 in the device manager.
Starting the revive process:
After you got the HUAWEI USB COM 1.0 set up, you need to start the virtual linux machine.
The first thing it will ask for is hw login, just type this with lowercase letters.
Code:
hw
hw (again)
Now, you need to add your HUAWEI USB COM 1.0 to the virtual machine.
To do this you need to click the USB icon in the lower right corner and select HUAWEI USB COM 1.0.
.
.
It should have connected as ttyUSB0, you can check it with the command
Code:
dmesg
Now you need to type
Code:
cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0
(if it asks for sudo password its hw again, also if your device is connected as other ttyUSB number, then you should use that number)
You should see this written from the console if it succeded
With this, you now have a special fastboot booted in your phone.
Flashing the system:
You can now exit the virtual machine, and run first batch, named 1. revive flasher.bat.
It will give you two options after it finished flashing the system, check the one you need, VTR-L29 or VTR-L09.
After the batch is done and you felt that the phone rebooted from the fastboot mode, you can now disconnect the phone from the computer.
You now need to connect the LCD cable, the battery cable, and buttons cable back to your motherboard, no need to re screw the mobo yet, just leave everything hanging in case you need to do the process again with the testpoint.
Now manually boot back into fastboot, Hold volume down while connecting your usb to your computer.
Now you need to flash a TWRP with 2. TWRP recovery.bat.
After that, boot into TWRP, wait for it to completely boot up, and flash an oeminfo with one of the oeminfo batches 3a or 3b.
With this, you should now be able to boot into the system, if there are still problems like bootlooping, do a factory reset from recovery.
Big thanks to:
@goodwin_c for the special fastboot/hikey_idt combo.
@Pretoriano80 for the TWRP recovery
@ante0 for the splitupdate.exe
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
NowLearn said:
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
Click to expand...
Click to collapse
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
yoghurt13 said:
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
Click to expand...
Click to collapse
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
NowLearn said:
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
Click to expand...
Click to collapse
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
yoghurt13 said:
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
Click to expand...
Click to collapse
bro, u didnt have to do that, but I appreciate it. Let me pm u. Thank you again
Would it be possible to rebrand VTR-L09 to VTR-L29 using this method?
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
volpula said:
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
Click to expand...
Click to collapse
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Ekenfo said:
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Click to expand...
Click to collapse
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
I can give you only my instagram.beacause I dont have a backup phone rightnow just waiting to fix my phone.if I can fix that buy a new phone but never huawei again.
yoghurt13 said:
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
Click to expand...
Click to collapse
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
volpula said:
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
Click to expand...
Click to collapse
Then there is the problem, try to install HiSuite, or my android driverpack, and try to see if the phone shows up in device manager.
Ekenfo said:
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
Click to expand...
Click to collapse
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
yoghurt13 said:
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
Click to expand...
Click to collapse
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Ekenfo said:
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Click to expand...
Click to collapse
There is currently no way to downgrade from XLOADER2, huawei did some black magic with it, and there is a checker built in the phone that checks if its a loader1 or 2.
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Ekenfo said:
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Click to expand...
Click to collapse
I literally have no ideai yet how to fix our IMEI, since the NVME partition does not contain the information we need, I just tested one from a working phone, and it was the same as before, zeroed out IMEI.
[LOOK AT POST #2 FOR UPDATES]
Good Morning/noon/afternoon/night whatever. Since I'm the dumbest man alive, I've messed up my tablet once again. Yesterday, I wanted to flash Valera's Project Treble zip, and i followed each and every single instruction UNTIL before flashing the GSI. I was following a guide on XDA and it said that no heavy modifications (SuperSU or Magisk) can stay. So I was worried because I still had magisk installed (T820 Tweaked by @rorymc928). Then in Valera's forum it was written that if i flash @ashyx TWRP, i can format everything and all would be good to go. BUT when I used Valera's TWRP to flash ashyx's TWRP image, nothing worked. It was stuck on download mode. So the next day (today) I used ODIN to flash the Stock ROM, but while doing that the Tab rebooted for no reason. And now the Tab is showing "An error has occured while flashing the device software" and whatever mode I went to, it kept rebooting after some time, so I can't flash ANYTHING. As a last ditch effort, I nand flashed the Stock ROM and that failed too. Now I'm desperate to do anything. Please help. I beg
Edit: Now I've messed up real bad. Since download mode wasn't staying on for more than 30 seconds, I decided to flash the OS in parts. First, I flashed the bootloader (BL). This is where the problems began. While flashing, the fricking tab rebooted and now my tab is in a veggie state. Nothing works, doesn't respond to ANYTHING. Upon connecting to PC, it displays "Qualcomm HS-USB QDLoader 9008". From what I can see, the entire boot partition and some core Qualcomm files got messed up. So I beg anybody for a solution. (Especially the people I trust: @rorymc928 @JordanBleu and @ashyx)
On YouTube I saw someone using EMMC Dongle to fix their Samsung phone, using a raw dump of the device. So i would ask anybody to give me a raw dump of the SM-T820 32 GB version OR tell me how to solve this problem please (I can't stress this enough)
NullCode said:
Edit: Now I've messed up real bad. Since download mode wasn't staying on for more than 30 seconds, I decided to flash the OS in parts. First, I flashed the bootloader (BL). This is where the problems began. While flashing, the fricking tab rebooted and now my tab is in a veggie state. Nothing works, doesn't respond to ANYTHING. Upon connecting to PC, it displays "Qualcomm HS-USB QDLoader 9008". From what I can see, the entire boot partition and some core Qualcomm files got messed up. So I beg anybody for a solution. (Especially the people I trust: @rorymc928 @JordanBleu and @ashyx)
On YouTube I saw someone using EMMC Dongle to fix their Samsung phone, using a raw dump of the device. So i would ask anybody to give me a raw dump of the SM-T820 32 GB version OR tell me how to solve this problem please (I can't stress this enough)
Click to expand...
Click to collapse
Hello, and sorry for what happened to your tab.
Infact, it wasn't recommended to flash the OS in separate parts like you did, but when you were flashing them you should have seen if the "auto reboot" case in Odin was checked or not (and you should have unchecked it).
I must to be clear : you have to tell us if TWRP still works (which isn't probable) or if your download mode (Odin mode) still works, which is the basic of all, even on bricked devices.
If it works then you can reflash all the firmware again, BUT COMPLETELY AND NOT IN PARTS, if it doesn't work, then.... Your tab is deeply bricked and won't recover in an easy way.
JordanBleu said:
Hello, and sorry for what happened to your tab.
Infact, it wasn't recommended to flash the OS in separate parts like you did, but when you were flashing them you should have seen if the "auto reboot" case in Odin was checked or not (and you should have unchecked it).
I must to be clear : you have to tell us if TWRP still works (which isn't probable) or if your download mode (Odin mode) still works, which is the basic of all, even on bricked devices.
If it works then you can reflash all the firmware again, BUT COMPLETELY AND NOT IN PARTS, if it doesn't work, then.... Your tab is deeply bricked and won't recover in an easy way.
Click to expand...
Click to collapse
Uh oh. Yeah TWRP and Download mode all don't work. Nothing works. Only after connecting to the PC it shows QDLoader 9008 mode. And the reason I flashed it in parts is because THE DAMN TAB WOULDN'T STAY ON, EVEN AFTER I LET IT CHARGE FOR 5 HOURS. And even after I flashed it in parts it just rebooted and the bootloader flash failed. So yeah, hard bricked.
Oh and @JordanBleu I wonder if you have an SM-T820. Do you?
NullCode said:
Edit: Now I've messed up real bad. Since download mode wasn't staying on for more than 30 seconds, I decided to flash the OS in parts. First, I flashed the bootloader (BL). This is where the problems began. While flashing, the fricking tab rebooted and now my tab is in a veggie state. Nothing works, doesn't respond to ANYTHING. Upon connecting to PC, it displays "Qualcomm HS-USB QDLoader 9008". From what I can see, the entire boot partition and some core Qualcomm files got messed up. So I beg anybody for a solution. (Especially the people I trust: @rorymc928 @JordanBleu and @ashyx)
On YouTube I saw someone using EMMC Dongle to fix their Samsung phone, using a raw dump of the device. So i would ask anybody to give me a raw dump of the SM-T820 32 GB version OR tell me how to solve this problem please (I can't stress this enough)
Click to expand...
Click to collapse
NullCode said:
Uh oh. Yeah TWRP and Download mode all don't work. Nothing works. Only after connecting to the PC it shows QDLoader 9008 mode. And the reason I flashed it in parts is because THE DAMN TAB WOULDN'T STAY ON, EVEN AFTER I LET IT CHARGE FOR 5 HOURS. And even after I flashed it in parts it just rebooted and the bootloader flash failed. So yeah, hard bricked.
Oh and @JordanBleu I wonder if you have an SM-T820. Do you?
Click to expand...
Click to collapse
If you are talking about the wifi version, then sadly no (I only have the cellular variant, SM-T825).
I hope I can help you even with the cellular version.
JordanBleu said:
If you are talking about the wifi version, then sadly no (I only have the cellular variant, SM-T825).
I hope I can help you even with the cellular version.
Click to expand...
Click to collapse
Thanks a lot for giving your help. My plan is this:
My tab is in EDL Mode, and I saw on Google that EDL Devices can boot to SD Card when the eMMC Fails. So what I want to do is flash the bootloader and the PIT File to an SD Card, using the image pulled from your Tab.
Now the problem is:
1: The tutorials I found for doing this are OLD (like Galaxy S3 old).
2: I have no clue where the bootloader is stored on Samsung devices.
And also here is the tutorial I found for the Galaxy S3:
"1: Boot the device to TWRP and connect it to PC and open ADB (if you don't have it install "minimal ADB and Fastboot")
Now type the following commands:
ADB devices (to check if your device is detected).
If it is OK then do:
ADB shell
dd if=/dev/block/mmcblk0p1 of=/external_sd/part1.img
dd if=/dev/block/mmcblk0p2 of=/external_sd/part2.img
dd if=/dev/block/mmcblk0p4 of=/external_sd/part4.img
OK you see one number is always changing... we need this with following numbers:
1 2 4 5 6 7 10 11 14 15
Partition 10 and 14 are a bit larger so the command may look like it's stuck but it isn't."
Could you mind performing these steps and sending the files to AndroidFileHost?
Thanks in advance if you do.
And if it works I'll make a guide for everyone who has a hard bricked Tab.
By coincidence, without knowing your post, I recently read something about EDL I didn't know anything about before.
Perhaps this helps.
https://www.the***********.com/qualcomm-edl-mode-guide/
This adress seems censored so you have to replace the star by (custom) followed directly by (droid).
I've asked that guy if it's possible to build such a flashable file from the stock ROM but didn't get an answer yet.
bmwdroid said:
By coincidence, without knowing your post, I recently read something about EDL I didn't know anything about before.
Perhaps this helps.
https://www.the***********.com/qualcomm-edl-mode-guide/
This adress seems censored so you have to replace the star by (custom) followed directly by (droid).
I've asked that guy if it's possible to build such a flashable file from the stock ROM but didn't get an answer yet.
Click to expand...
Click to collapse
Good morning. Yeah I've tried that site because @rorymc928 gave me that website a long time ago (and it didn't go well). EDL devices can boot from the SD, so I wanted the bootloader image from anybody's Tab S3. I'd be very happy if you managed to give me.
NullCode said:
Good morning. Yeah I've tried that site because @rorymc928 gave me that website a long time ago (and it didn't go well). EDL devices can boot from the SD, so I wanted the bootloader image from anybody's Tab S3. I'd be very happy if you managed to give me.
Click to expand...
Click to collapse
Giving you the boot.img is not the problem but mine is for T825.
Don't know if they differ.
You could extract it from of the stock T820 ROM files couldn't you?
If you still want it, just tell me.
But as far as I understand the a. m. site the tool can only flash .elf or .mbn files didn't read about .img files.
bmwdroid said:
Giving you the boot.img is not the problem but mine is for T825.
Don't know if they differ.
You could extract it from of the stock T820 ROM files couldn't you?
If you still want it, just tell me.
But as far as I understand the a. m. site the tool can only flash .elf or .mbn files didn't read about .img files.
Click to expand...
Click to collapse
Man that's a bummer. You didn't understand my request. I don't need the boot.img (I already have it). What I need is the image of the BOOTLOADER (apdp, NON-HLOS, sec, tz, rpm, cmnlib etc) all combined in an img file. That's only possible if another person with the same device grabs one and sends it to me
bmwdroid said:
Giving you the boot.img is not the problem but mine is for T825.
Don't know if they differ.
You could extract it from of the stock T820 ROM files couldn't you?
If you still want it, just tell me.
But as far as I understand the a. m. site the tool can only flash .elf or .mbn files didn't read about .img files.
Click to expand...
Click to collapse
Also @bmwdroid well there's nothing to lose, so I'm giving you the thread which mentions how to do it (it was made for the Note 4, so idk if it still works) https://forum.xda-developers.com/note-4/general/tutorialhow-to-make-debrick-image-t3488082
Sorry that I misunderstood you.
You'll need to reinstall the stock OS with Odin on Windows
NullCode said:
Also @bmwdroid well there's nothing to lose, so I'm giving you the thread which mentions how to do it (it was made for the Note 4, so idk if it still works) https://forum.xda-developers.com/note-4/general/tutorialhow-to-make-debrick-image-t3488082
Click to expand...
Click to collapse
Hi @NullCode!
I've googled for the recovery process because I would use custom ROM on my SM-T590, so I want to make sure it can be restored if something goes wrong, and found your thread.
For me, in the downloaded official Samsung ROM there is a BL_T590(...) file which you can open with WinRAR (of course, download the FW for your model, for example with Frija). Then it will give you files like aboot.mbn.lz4 (I think this one is the Android bootloader), apdp.mbn.lz4, cmnlib.mbn.lz4, etc. You can decompress these files with LZ4 command line tool, and then you may be able to reflash them in EDL mode.
Edit: On some forums I found that they didn't decompress LZ4 files, so I have no idea which way could work.
Also there are some solutions to generate rawprogram.xml files for flashing, but I'm not sure if it's allowed to link them here.
Good luck, and let me know if this worked!
Tools:
Frija: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
LZ4 tool: https://github.com/lz4/lz4/releases/tag/v1.9.3
UDPSendToFailed said:
Hi @NullCode!
I've googled for the recovery process because I would use custom ROM on my SM-T590, so I want to make sure it can be restored if something goes wrong, and found your thread.
For me, in the downloaded official Samsung ROM there is a BL_T590(...) file which you can open with WinRAR (of course, download the FW for your model, for example with Frija). Then it will give you files like aboot.mbn.lz4 (I think this one is the Android bootloader), apdp.mbn.lz4, cmnlib.mbn.lz4, etc. You can decompress these files with LZ4 command line tool, and then you may be able to reflash them in EDL mode.
Edit: On some forums I found that they didn't decompress LZ4 files, so I have no idea which way could work.
Also there are some solutions to generate rawprogram.xml files for flashing, but I'm not sure if it's allowed to link them here.
Good luck, and let me know if this worked!
Tools:
Frija: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
LZ4 tool: https://github.com/lz4/lz4/releases/tag/v1.9.3
Click to expand...
Click to collapse
Hello! Well I would like to thank you for trying to help, but flashing with EDL mode isnt a possibility. Because even if i have the full ODIN firmware [which I do] I would need the official signed Samsung Firehose loader with the Sahara protocol. If that was a bit too complicated [no offence], basically I need to hack into Samsung's servers OR persuade a Samsung repair employee to give me the loader to flash my tab with. Alas, since this isnt a possibility, I am planning to send this tablet to its homeland [America] and get it JTAG flashed, because that is the only thing that can be done for this
NullCode said:
Hello! Well I would like to thank you for trying to help, but flashing with EDL mode isnt a possibility. Because even if i have the full ODIN firmware [which I do] I would need the official signed Samsung Firehose loader with the Sahara protocol. If that was a bit too complicated [no offence], basically I need to hack into Samsung's servers OR persuade a Samsung repair employee to give me the loader to flash my tab with. Alas, since this isnt a possibility, I am planning to send this tablet to its homeland [America] and get it JTAG flashed, because that is the only thing that can be done for this
Click to expand...
Click to collapse
Are you sure about that? I mean, isn't the EDL interface universal among Qualcomm SOCs? I think it is, there are lots of tools for flashing, also I haven't seen anything about Samsung locks this option, the only manufacturer that blocks 3rd party flashers is Xiaomi as far I know, but there is a modded flasher software for Xiaomi too. As I can see, there are threads about Galaxy S8 being reflashed and is working fine, so in theory Samsung doesn't lock bootloaders.
Also there is a file for MSM8996 for Galaxy Note 8 which is Snapdragon 820 in your tablet. It's in the G930XU5 folder.
https://forum.xda-developers.com/showpost.php?p=77904842&postcount=2
UDPSendToFailed said:
Are you sure about that? I mean, isn't the EDL interface universal among Qualcomm SOCs? I think it is, there are lots of tools for flashing, also I haven't seen anything about Samsung locks this option, the only manufacturer that blocks 3rd party flashers is Xiaomi as far I know, but there is a modded flasher software for Xiaomi too. As I can see, there are threads about Galaxy S8 being reflashed and is working fine, so in theory Samsung doesn't lock bootloaders.
Also there is a file for MSM8996 for Galaxy Note 8 which is Snapdragon 820 in your tablet. It's in the G930XU5 folder.
https://forum.xda-developers.com/showpost.php?p=77904842&postcount=2
Click to expand...
Click to collapse
No no Samsung doesn't block EDL mode at all (in fact, my tablet ONLY goes to EDL mode now), the problem is the flash loader, which is specific to each device. Xiaomi used to generously provide Fastboot ROMs which used the loader we are talking about and EDL mode to flash things, but they don't do that anymore.
Also, I tried the G930XU5 thing the day I wrote this thread, and it was stuck at 50% and didn't do anything else (I think this happened because the loaders are also flash chip dependant and the one in the Note 8 thread is UFS while the Tab S3 uses eMMC). Oh another thing, could you tell me the names of flashers that use EDL mode? I've only heard of QFIL and MiFlash
NullCode said:
No no Samsung doesn't block EDL mode at all (in fact, my tablet ONLY goes to EDL mode now), the problem is the flash loader, which is specific to each device. Xiaomi used to generously provide Fastboot ROMs which used the loader we are talking about and EDL mode to flash things, but they don't do that anymore.
Also, I tried the G930XU5 thing the day I wrote this thread, and it was stuck at 50% and didn't do anything else (I think this happened because the loaders are also flash chip dependant and the one in the Note 8 thread is UFS while the Tab S3 uses eMMC). Oh another thing, could you tell me the names of flashers that use EDL mode? I've only heard of QFIL and MiFlash
Click to expand...
Click to collapse
Final update: Well, someone from a mobile service explained me how it works, basically without a firehose file which is signed by Samsung specifically for the device, we can't do anything. I hope the files will be available for the public, because this way Samsung just forces their users to pay for a "repair" which could be done at home using the official Qualcomm solutions.
QPST - Official Qualcomm flasher
emmcdl - I think this one can do the flashing with multiple files since it has options like sector address, etc, also you can find a fota.zip (password for fota.zip is fotatest1234) inside the official Samsung ROM which has some partition table informations
Z3X Samsung Tool PRO - Looks like it can do many things, but doesn't start up for me, says "Card not found"
blankflash - This one is for Motorola devices, but who knows
sahara - You can find it on GitHub, there is an example .xml file too
And possibly many others which I haven't found yet.
Update: I found an app called PIT Magic, it can show partition table info and memory addresses after unpacking CSC and selecting the .pit file. Maybe that can be useful when used together with emmcdl, like flashing SBL back with emmcdl -p ttyUSB0 -b SBL1 C:\path_to_sbl1.mbn or with using these adresses in .xml files.
Update #2: There are some firehose files on "OneLabsTools" GitHub page for MSM8996 too.
https://forum.xda-developers.com/showthread.php?t=1916936
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NullCode said:
Edit: Now I've messed up real bad. Since download mode wasn't staying on for more than 30 seconds, I decided to flash the OS in parts. First, I flashed the bootloader (BL). This is where the problems began. While flashing, the fricking tab rebooted and now my tab is in a veggie state. Nothing works, doesn't respond to ANYTHING. Upon connecting to PC, it displays "Qualcomm HS-USB QDLoader 9008". From what I can see, the entire boot partition and some core Qualcomm files got messed up. So I beg anybody for a solution. (Especially the people I trust: @rorymc928 @JordanBleu and @ashyx)
On YouTube I saw someone using EMMC Dongle to fix their Samsung phone, using a raw dump of the device. So i would ask anybody to give me a raw dump of the SM-T820 32 GB version OR tell me how to solve this problem please (I can't stress this enough)
Click to expand...
Click to collapse
You could try flashing twrp . It dont take more than 5 second. You only have to be prepare to enter to recovery mode because your device reboot automaticly
UDPSendToFailed said:
Final update: Well, someone from a mobile service explained me how it works, basically without a firehose file which is signed by Samsung specifically for the device, we can't do anything. I hope the files will be available for the public, because this way Samsung just forces their users to pay for a "repair" which could be done at home using the official Qualcomm solutions.
Click to expand...
Click to collapse
yeah I did say that a while before but I'm glad you understood. Without this "programmer" there is nothing we can do.
there's also a high likelihood that Samsung won't provide the firehose files because every company just wants money nowadays