Hello!
I'm new at posting threads, so I ask you not to be aggressive with me XD.
However, I'm writing this thread since I have experienced a hard brick on my Moto G8 Play because of flashing a wrong firmware while trying to root my phone with this tutorial: Root your phone with One Macro Firmware.
I struggled a lot in order too repair my phone, but finally I managed to solve the brick following a tutorial designed for the One Macro (the YouTube video is in Spanish and if you can understand it, you can check the link at the end of this thread). I hope this would help more people who experience a hard brick on their cellphones.
.
.
.
.
.
First of all, you've gotta install the Motorola Drivers.
Later on, you need to install the Mediatek drivers in order to get your phone regonized (if you are not sure whether your phone is recognized or not, you can check at the Device Manger). In the video, the guy installs also the Qualcomm drivers but, in my case, I had installed the Mtk Drivers because of being able to use the SP Flash Tool (which didn't work haha).
I would suggest you to also install the Qualcomm Drivers (you never know xd...).
Finally, you have to download the Blankflash of the Motorola One Macro (that is the file that worked for me, if your file did not work, you can use this one.
When you download everything, you'll have to open your Command Prompt and type the following commands (whiout the quotes): "bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS" and "bcdedit -set TESTSIGNING OFF". Before you reboot your system, proceed to install the Motorola, Mediatek and Qualcomm Drivers. After you did that, you can reboot your system.
When you rebooted your system, be sure to have connected your phone. When your phone is connected, extract the contents of the blankflash, navigate to the folders and when you achieve the sub-folder with some files, search for the blank-flash.bat and, when you feel ready and think you've prayed enough XD, execute the file.
.
.
.
.
.
If everything went ok, you would have booted on the Fastboot Mode (your phone is alive again! ). Sadly, this is not victory yet. You have to flash the stock rom of your phone, which you can download from here (you just search for the version you want or corresponds to your phone and proceed to download it).
.
.
.
.
.
This is my first thread and I hope to have helped some people in serious trouble with their G8's, since this forum is not very alive .
However, this tutorial is not mine. I just tried to explain it for people who don't speak Spanish nor knew about this.
Here's the link of the original tuto (f you speak Spanish, go ahead ).
.
.
.
Credits to Erick Romero!!
Thanks for reading!!!!
RandoMike said:
Hello!
I'm new at posting threads, so I ask you not to be aggressive with me XD.
However, I'm writing this thread since I have experienced a hard brick on my Moto G8 Play because of flashing a wrong firmware while trying to root my phone with this tutorial: Root your phone with One Macro Firmware.
I struggled a lot in order too repair my phone, but finally I managed to solve the brick following a tutorial designed for the One Macro (the YouTube video is in Spanish and if you can understand it, you can check the link at the end of this thread). I hope this would help more people who experience a hard brick on their cellphones.
.
.
.
.
.
First of all, you've gotta install the Motorola Drivers.
Later on, you need to install the Mediatek drivers in order to get your phone regonized (if you are not sure whether your phone is recognized or not, you can check at the Device Manger). In the video, the guy installs also the Qualcomm drivers but, in my case, I had installed the Mtk Drivers because of being able to use the SP Flash Tool (which didn't work haha).
I would suggest you to also install the Qualcomm Drivers (you never know xd...).
Finally, you have to download the Blankflash of the Motorola One Macro (that is the file that worked for me, if your file did not work, you can use this one.
When you download everything, you'll have to open your Command Prompt and type the following commands (whiout the quotes): "bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS" and "bcdedit -set TESTSIGNING OFF". Before you reboot your system, proceed to install the Motorola, Mediatek and Qualcomm Drivers. After you did that, you can reboot your system.
When you rebooted your system, be sure to have connected your phone. When your phone is connected, extract the contents of the blankflash, navigate to the folders and when you achieve the sub-folder with some files, search for the blank-flash.bat and, when you feel ready and think you've prayed enough XD, execute the file.
.
.
.
.
.
If everything went ok, you would have booted on the Fastboot Mode (your phone is alive again! ). Sadly, this is not victory yet. You have to flash the stock rom of your phone, which you can download from here (you just search for the version you want or corresponds to your phone and proceed to download it).
.
.
.
.
.
This is my first thread and I hope to have helped some people in serious trouble with their G8's, since this forum is not very alive .
However, this tutorial is not mine. I just tried to explain it for people who don't speak Spanish nor knew about this.
Here's the link of the original tuto (f you speak Spanish, go ahead ).
.
.
.
Credits to Erick Romero!!
Thanks for reading!!!!
Click to expand...
Click to collapse
Thank you friend, i managed to revive my phone, thanks to you!!!
Amendowins said:
Thank you friend, i managed to revive my phone, thanks to you!!!
Click to expand...
Click to collapse
Hahaha... you're welcome, mate.
I'm glad this also worked for you. You can be now safe if you wanna mess up with your phone hahaha.
As you said, this is not victory yet .
I was trying to root my G8 Play using the same tutorial you've mencioned, but something got wrong and my phone bricked.
Fortunetly, i managed to revive the poor guy following the instructions here by entering in fastboot mode.
Then i've downloaded the last version of the stock rom uploaded in 26-02-2021 03:25 (moto > lima_32 > official > retail) and tried to flash it, but without success. My phone is stuck at the Motorola logo.
Also tried to use Rescue and Smart Assistant, but the program says that can't read my phone's firmware and returns the message "unable to match the appropriate firmware some key information cannot be read from the device".
If anyone can help me, I will be very grateful!
PS: Sorry for my english, i'm from Brazil
Amendowins said:
As you said, this is not victory yet .
I was trying to root my G8 Play using the same tutorial you've mencioned, but something got wrong and my phone bricked.
Fortunetly, i managed to revive the poor guy following the instructions here by entering in fastboot mode.
Then i've downloaded the last version of the stock rom uploaded in 26-02-2021 03:25 (moto > lima_32 > official > retail) and tried to flash it, but without success. My phone is stuck at the Motorola logo.
Also tried to use Rescue and Smart Assistant, but the program says that can't read my phone's firmware and returns the message "unable to match the appropriate firmware some key information cannot be read from the device".
If anyone can help me, I will be very grateful!
PS: Sorry for my english, i'm from Brazil
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Amendowins said:
As you said, this is not victory yet .
I was trying to root my G8 Play using the same tutorial you've mencioned, but something got wrong and my phone bricked.
Fortunetly, i managed to revive the poor guy following the instructions here by entering in fastboot mode.
Then i've downloaded the last version of the stock rom uploaded in 26-02-2021 03:25 (moto > lima_32 > official > retail) and tried to flash it, but without success. My phone is stuck at the Motorola logo.
Also tried to use Rescue and Smart Assistant, but the program says that can't read my phone's firmware and returns the message "unable to match the appropriate firmware some key information cannot be read from the device".
If anyone can help me, I will be very grateful!
PS: Sorry for my english, i'm from Brazil
Click to expand...
Click to collapse
Searching through the internet, I found a blankflash which corresponds to our beloved G8 Play, this is the link. If it asks you for a decryption key, there it is: ZyN4NTUuC_V6TWDPe5ECDy0H5RrpvrJVSOFQtDBKB48. You can download this, reboot your phone, open the blankflash.bat and connect the phone to the computer, let it flash and reflash all the entire rom you downloaded.
It may be worth a try!
If this doesn't work, you can try flashing the One Macro's Rom with the file I shared at the beginning of the thread.
Please let us know if your phone revived!
RandoMike said:
Searching through the internet, I found a blankflash which corresponds to our beloved G8 Play, this is the link. If it asks you for a decryption key, there it is: ZyN4NTUuC_V6TWDPe5ECDy0H5RrpvrJVSOFQtDBKB48. You can download this, reboot your phone, open the blankflash.bat and connect the phone to the computer, let it flash and reflash all the entire rom you downloaded.
It may be worth a try!
If this doesn't work, you can try flashing the One Macro's Rom with the file I shared at the beginning of the thread.
Please let us know if your phone revived!
Click to expand...
Click to collapse
Blankflash won't work unless the device is in EDL mode
sd_shadow said:
Blankflash won't work unless the device is in EDL mode
Click to expand...
Click to collapse
I know, but the device always starts on EDL/Mediatek Preloader Mode before getting screen signal. If you can open the blank flash before turning on the phone, the phone itself will load on the Preloader first and will flash the blankflash without a trouble.
[Edit] As a curious fact, my phone never hardbricked again after doing some blankflashes, I can't tell you how many times my phone needed exactly, but I can confirm that it happened. I was trying to get GSI to work on the phone, and I had to flash One Macro's firmware, expecting to trigger a hardbricked. To my surprise, the phone didn't do that. It may be a particular case or not. I also wanna say that by the time that I wanted to flash the Macro's firmware, my phone had updated to Android 10, I don't know if that exactly triggered that "condition", but I leave this in order to confirm of not my hypothesis haha.
Just used this thread to revive the g8 play sitting in my armoire. Thanks for the project!
hi, im following all the steps but when starts blank flash, after a few seconds it shows "download fail! please try again... trying again same happens...
any help?
{
"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"
}
RandoMike said:
Hello!
I'm new at posting threads, so I ask you not to be aggressive with me XD.
However, I'm writing this thread since I have experienced a hard brick on my Moto G8 Play because of flashing a wrong firmware while trying to root my phone with this tutorial: Root your phone with One Macro Firmware.
I struggled a lot in order too repair my phone, but finally I managed to solve the brick following a tutorial designed for the One Macro (the YouTube video is in Spanish and if you can understand it, you can check the link at the end of this thread). I hope this would help more people who experience a hard brick on their cellphones.
.
.
.
.
.
First of all, you've gotta install the Motorola Drivers.
Later on, you need to install the Mediatek drivers in order to get your phone regonized (if you are not sure whether your phone is recognized or not, you can check at the Device Manger). In the video, the guy installs also the Qualcomm drivers but, in my case, I had installed the Mtk Drivers because of being able to use the SP Flash Tool (which didn't work haha).
I would suggest you to also install the Qualcomm Drivers (you never know xd...).
Finally, you have to download the Blankflash of the Motorola One Macro (that is the file that worked for me, if your file did not work, you can use this one.
When you download everything, you'll have to open your Command Prompt and type the following commands (whiout the quotes): "bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS" and "bcdedit -set TESTSIGNING OFF". Before you reboot your system, proceed to install the Motorola, Mediatek and Qualcomm Drivers. After you did that, you can reboot your system.
When you rebooted your system, be sure to have connected your phone. When your phone is connected, extract the contents of the blankflash, navigate to the folders and when you achieve the sub-folder with some files, search for the blank-flash.bat and, when you feel ready and think you've prayed enough XD, execute the file.
.
.
.
.
.
If everything went ok, you would have booted on the Fastboot Mode (your phone is alive again! ). Sadly, this is not victory yet. You have to flash the stock rom of your phone, which you can download from here (you just search for the version you want or corresponds to your phone and proceed to download it).
.
.
.
.
.
This is my first thread and I hope to have helped some people in serious trouble with their G8's, since this forum is not very alive .
However, this tutorial is not mine. I just tried to explain it for people who don't speak Spanish nor knew about this.
Here's the link of the original tuto (f you speak Spanish, go ahead ).
.
.
.
Credits to Erick Romero!!
Thanks for reading!!!!
Click to expand...
Click to collapse
Gracias brother, gracias a ti pude revivir mi moto g8 play que intente rootear con el tutorial que mencionaste
hello, maybe this is a dumb question but how can I know which file is the correct rom for my moto g8 play? I see a lot of folder and tbh I don't know what each mean
Related
THIS WILL ONLY WORK WITH DEVICES USING EMMC PARTITION LAYOUT!
otherwise flashtool cannot properly readback needed files wich will cause a bricked device. for rooting mt6573 or mt6575 without emmc partition layout,
refere to this method by rua1: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
You need to upload the needed files to your Computer using the Read Page Only feature.
ALSO, MAKE SURE YOUR DON'T TRY THAT ON AN ALCATEL (OR SIMILAR) DEVICE, INDICATOR HERE IS A CUSTPACK PARTITION IN SCATTERFILE.
those devices have mt65xx, but have a totally different partition strukture. You can try this tutorial, BUT IF YOU BRICK YOUR DEVICE; I CANNOT HELP YOU OUT!!!
since a lot of devices have different hardware - e.g. Display or Camera - making a Backup of your device should have highest priority. Flashing a wrong ROM can brick your phone!!
What is needed:
VCOM Driver, thx to n2k1
ADB, thx to n2k1
MTK Droid Tools V2.46
If you wan't to use the newest Versionof MTK Droid Tools, refere to here:
http://forum.xda-developers.com/showthread.php?p=38337401#post38337401
also, you can buy Master Shifu rua1 a coffee for his great tool!
Support for the newest Version of Droid Tools is NOT given in this thread! I personally don't use his tool so if something unexpected happens, its not my fault.
SP Flashtool V3.1224 for mt6589, newer flashtool is needed!!! if there are some problems with reading back or flashing the device, newer flashtool is needed.
Install the needed drivers. installing VCOM drivers might take a while, because it will show up just a few seconds while connecting the phone(off).
and now the Step-by-Step tutorial to backup your boot.img, recovery.img and system.img for rooting.
1. enable USB-debugging under Settings-Development->USB debugging
2. phone should now get recognized as "Android Phone - Android Composite ADB Interface" -> if this is a Unknown Device, you should install the ADB drivers.
3.Open MTK Droid Tools
{
"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"
}
4. Connect device to USB (USB Debugging has to be enabled)
5. Device informations has been loaded, Press on "Blocks Map"
We'll need to find the lines bootimg, recovery and Android. We'll need to write down Start-adress(Scatter) and the Size for every line.
(i made a screenshot, writing down isn't necessary.)
In MY Case, this is:
bootimg: 00F88000 size: 00600000
recovery: 01588000 size: 00600000
Android: 026E8000 size: 31900000
6. Now we'll need to click on "Create Scatter File" and you can save it as "MT6577_Android_scatter_emmc.txt"
7. You can Close MTK Droid Tools now.
8. Now we need to open SP Flash Tool and we need to load the scatter file.
9. Now we'll need to click on "Read Back" in the top of SP Flash Tool.
Click on "ADD" 3 Times, we will create "ROM_0", "ROM_1" and "ROM_2".
10. Doubleclick on "ROM_0", and select a place to save it, e.g. C:/N9770_backup/ and rename it to"boot.img"
11. now it will ask you for the Start Adress and lengh for bootimg, we wrote down earlier.
this is in my case: Start Address: 0x00F88000; Lenght: 0x00600000. the first "0x" MUST remain at its place!
12. the same thing you'll need to do for "recovery" and "android".
13. disconnect, shut down and remove the battery of your Device.
13. Now we'll need to click on "Read Back", insert your battery and connect your device to USB. (VCOM driver is needed now, you'll need to install it before getting to the next steps)
14. if this were correct, a red bar should appear on the bottom of SP Flash Tool. you'll need to wait until the green ring appears.
15.Flash Tool now read back the 3 files. system.img isn't that important, but boot.img and recovery.img should be around 6 MB. if the file is smaller or bigger, the length is different to my device or there was a failure while reading back your firmware. So make sure, that at least recovery or boot.img has the right size!!
16. Back to droid tools. reconnect your device to USB , debugging should be enabled, too. switch to "root, backup, recovery" tab in MTK Droid Tools.
select "to choose the boot.img" and press on "Recovery and boot". select your backup boot.img and recovery,img. MTK droid tools will patch boot.img, so you obtain permanent shellroot.
(optional) a window will pop-up and ask you, if you want to install CWM-r. i cannot tell you if that will work, but you can try it, since you backed up your recovery before. )
(optional) a window will pop-up and ask you for the name of your device(you connected it before starting droidtools, so this should not ask you for the name). you can just press enter or you can enter a name for your device.
17. Droid Tools should have modified the boot.img. "--a task is complete--" text should show up in the right of droidtools.
18. Back to Flashtool
You'll need to load the Scatter (like in Step 8)
select boot.img and recovery.img. make sure you select the modified files. (.../Droidtools/recovery/boot.img and recovery.img)
only boot and recovery should be selected!!
19.disconnect, shout down and remove the battery of your device. press on "Download", a window will show up that you have not selected all images. you can press on "OK".
20. insert the battery and connect your device to USB. Flash process should start and if it worked, green ring will appear.
21. Back to DroidTools. device needs to be connected and debugging enabled. switch to "root, backup, recovery" again and press on "SuperUser". this will push superuser, SU binary and busybox to your device.
22. Your Device is rooted now. you can make a Full backup with Droid Tools now.
thx to n2k1 and tommy0815 for the needed files and the original tutorial!!
if i helped you, don't forget to press on "thanks"
reserved for future updates
Testing on my Acer Z120 MT6575 base, I hope this will work, feedback later *fingers crossed*
FEEDBACK:
It totally worked, My Acer z120 is now rooted.
(optional) a window will pop-up and ask you, if you want to install CWM-r. i cannot tell you if that will work, but you can try it, since you backed up your recovery before.
Click to expand...
Click to collapse
Do not use CWM, it will cause your phone not to boot properly, that is my experience on my phone.
Thanks!
yeah never tested it though, thx for the reply!
Re: [HOWTO][GUIDE] Root & Backup of almost EVERY MT65xx based Device
is there anyone here who tried to follow this thread and successfully rooted his android phone?lenovo s720 user here.waiting for more positive feedbacks.
Will this method work on a Vodafone Smart III (975N) probably with 6575?
Guys, this will work on every mt65xx device, if you installed all drivers sucessfully .this whole thing basically changes a value in Boot.IMG To obtain permanent root in the shell. This is the same on EVERY mt65xx based smartphone. Basically you are rooted now. Just needs To push busybox, su and superuser To your device. Thos whole thing seems complex, but you make a backup oft your modified files before modifiing. I never Had device this tutorial was not working every mt6575, 6577 and 6589 should work without an problem. Mt6573 can be a Problem because oft their YAFFS partition strukture.
Chrizzly92 said:
Guys, this will work on every device, if you installed all drivers sucessfully .this whole thing basically changes a value in Boot.IMG To obtain permanent root in the shell. This is the same on EVERY mt65xx based smartphone. Basically you are rooted now. Just needs To push busybox, su and superuser To your device. Thos whole thing seems complex, but you make a backup oft your modified files before modifiing. I never Had device this tutorial was not working every mt6575, 6577 and 6589 should work without an problem. Mt6573 can be a Problem because oft their YAFFS partition strukture.
Click to expand...
Click to collapse
Thanks, I will try!
Sent from my Samsung I9300 with tapatalk4
thank you for this :thumbup:
Sent from my PICOpad GEW using xda app-developers app
dbius said:
Will this method work on a Vodafone Smart III (975N) probably with 6575?
Click to expand...
Click to collapse
Yes, i rooted my vodafone 975N with this method (CWM recovery working) :good:
Gynekolog said:
Yes, i rooted my vodafone 975N with this method :good:
Click to expand...
Click to collapse
:good: That sounds great! Thx man for the informations!
Edit:
Now i tried to root the phone. Everything is went fine till phase nr.19. At this point when the flashtool tried to write back the modified boot.img and recovery.img it gave back me the attached error window.
What should be the problem? I went through the steps with doublecheck and everything was fine till that point. I tried this step two or three times more, but every time gave me this error message.
What should I do now? If it helps I can upload the log folder content here.
Make sure the scatterfile is correct and the files should not be bigger than 6 MB. Flash tool tells you that you need to flash a full image cause the scatter is different from you phone.
Sent from my Star N9770 using xda app-developers app
Chrizzly92 said:
Make sure the scatterfile is correct and the files should not be bigger than 6 MB. Flash tool tells you that you need to flash a full image cause the scatter is different from you phone.
Sent from my Star N9770 using xda app-developers app
Click to expand...
Click to collapse
!EDIT!
Thanks for your answer!
Tonight I found a newer version for flash tool (v3.1304.0.119). Using that version rooting the phone was successful, so thanks, finally it worked.
VCOM Ports
Gynekolog said:
Yes, i rooted my vodafone 975N with this method :good:
Click to expand...
Click to collapse
I still cant root my device. I think its the VCOM ports, because i cant flash
When i click "Read Back" the device is not there..
Can you help me?
Thanks!
This will be very helpful. I have a china phone running on MT6577. I've successfully installed a ported V970 ROM to ZA-985 (which is compatible to my unit in terms of hardware and appearance). I wanna try porting a JB V970 Lewa OS ROM to Kata i1 (identical to ZA-985).
dbius said:
!EDIT!
Thanks for your answer!
Tonight I found a newer version for flash tool (v3.1304.0.119). Using that version rooting the phone was successful, so thanks, finally it worked.
Click to expand...
Click to collapse
thx for your reply, i updated Post #1 , that for mt6589 newer flashtool is required nad sumtimes youll need to play with them. this is because the widely spread devices, they are not the same and sometimes big differences in partitionlayout, SoC revision and so on.
@verntechguy: after rooting, make sure you get a full backup of your device using mtk droid tools. porting lewa is not that hard, but you maybe need to try different platforms to port from. you can refere to here, master shifu yuweng made a pretty good tutorial abut porting Roms.
@Beirajunior: is your device recognized as "mt65xx preloader" when connection to USB? (phone should be off) if not, you can try pressing VOL Up or down while connecting to USB. for flashing, VCOM port 1-16 should be assigned to the drivers.
6
Chrizzly92 said:
thx for your reply, i updated Post #1 , that for mt6589 newer flashtool is required nad sumtimes youll need to play with them. this is because the widely spread devices, they are not the same and sometimes big differences in partitionlayout, SoC revision and so on.
@verntechguy: after rooting, make sure you get a full backup of your device using mtk droid tools. porting lewa is not that hard, but you maybe need to try different platforms to port from. you can refere to here, master shifu yuweng made a pretty good tutorial abut porting Roms.
@Beirajunior: is your device recognized as "mt65xx preloader" when connection to USB? (phone should be off) if not, you can try pressing VOL Up or down while connecting to USB. for flashing, VCOM port 1-16 should be assigned to the drivers.
6
Click to expand...
Click to collapse
Can you help me by team viewer ? :x i still cant do the flash..and the phone is reconized as "mt65xx preloader" but after a while he disconect.
My email is: [email protected]
I appreciate any help.
Cheers
no, i cannot help you via teamviewer, my internet connection is too slow, cause i`m on tethering. some additional infos will be helpfull. device? mt6573,75,77,89?
if the device gets found, everything should work. you`ll need to assing the VCOM ports. just look in the driver settings or google it. i`m sure there is some kind of tutorial for it. also, trying another PC or OS will help, too. alot of guys have problems with that, just switching to XP or so will mostly help without tweaking the drivers.
device should be disconnected and battery should not be inserted. now press readback in flashtool, insert battery and connect the device to USB. now phone should be found by flashtool. if not, like i said, check VCOM ports.
Chrizzly92 said:
no, i cannot help you via teamviewer, my internet connection is too slow, cause i`m on tethering. some additional infos will be helpfull. device? mt6573,75,77,89?
if the device gets found, everything should work. you`ll need to assing the VCOM ports. just look in the driver settings or google it. i`m sure there is some kind of tutorial for it. also, trying another PC or OS will help, too. alot of guys have problems with that, just switching to XP or so will mostly help without tweaking the drivers.
device should be disconnected and battery should not be inserted. now press readback in flashtool, insert battery and connect the device to USB. now phone should be found by flashtool. if not, like i said, check VCOM ports.
Click to expand...
Click to collapse
Hi,
Im already done, but im receiving this error when i try to modified the backuped files (boot and recovery) on MTK Droid Root.I sai no to similar CWM, and i get this error:
"--- ERROR :Boot unthe public mailing list [email protected]"
" --- task is complete ---"
What do you suggest ?
Cheers!
what SoC? mt6573?
Good morning.
I got a problem yesterday with my LG L5 II Dual phone: I caught my sisters pressing any buttons on it and when I saw what they did, there was an Android image on it. Now, every time I try to boot it, it cannot finish the initial setup, saying "Unfortunately, LGSetupWizard stopped."
I've rooted this phone some time ago, but the root seems to have no effect now. For instance, I deleted the following apps:
- Facebook
- Twittter
- All of "TIM" resources ("TIM Recarga, TIM Música, TIM this, TIM that"); "TIM" is the mobile operator of my phone.
I tried to follow the steps described in this post: "[Tutorial] Flashing KDZ on LG L5 II (E455/E460) and other LG phones", but I can't get my phone detected under "Download Mode", what I accessed using (Vol Up) + (Vol Down) keys while booting the phone. Unfortunately, it couldn't be detected in any workaround provided by this guide.
When connected under "Download Mode", I see a device called "LGE AndroidNet USB Modem" under "Modems" category on Windows Device Manager. It seems to be the only mode my phone could be detected under this mode.
Playing around with it, I could access a "Recovery Mode" by (Vol Up) + (Quick Access) keys while booting up the phone. I tried to get some info about it and I could, at least, use it with ADB. But I have read-only access, not read-write anymore. Searching more trying to get an answer to "ADB Force Root Mode", I got some things to notice, like the file "default.prop" under the phone's root system.
This "default.prop" shows the following 6 first lines:
Code:
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
persist.sys.usb.config=charge_only
persist.service.acm.enable=0
which means, I think, the phone now isn't configured for USB debugging neither for system write permission.
What can I do to, at least, try to delete some files on it, specifically the 4 setup wizard ones, located at "/system/app/" under the names "LGSetupWizard_JB.apk", "LGSetupWizard_JB.odex", "SetupWizard.apk" and "SetupWizard.odex", since these are the ones which I'm dealing with?
Ah. I tried on computers running Windows 8.1 and Windows XP SP3. No luck.
(edit: 2014-04-02, 23:16 UTC -03:00)
I've playing around with ADB trying to run it with another mode. I don't know if this can help, but sending the phone to recovery mode using ADB
Code:
adb reboot recovery
I get an Android lying with a red triangle sign over it... Still searching for a procedure or an answer to fix the phone, but still with no luck.
[Solved] Guide to solve this kind of problem
After looking for a while on how to fix the problem either by trying to run an ADB shell as root either by flashin the ROM, I could figure another way to flash the original "TIM" rom for my phone instead of the one described on the topic "[Tutorial] Flashing KDZ on LG L5 II (E455/E460) and other LG phones". Here's the way out:
1. Downloading firmware KDZ Flash ROM
First, you have to download the original KDZ ROM for your phone. It can be found at the link below:
LG Optimus L5 II Firmware List
The ones for Brazilian users are described in the page. For TIM users, I suggest using firmware 33 BTM/TIM(BRAZIL), size 599.09 MiB.
Since my phone was sold by TIM, I can't tell about another mobile operators, like Claro, Oi, and VIVO.
2. Extracting a binary file from the KDZ Flash ROM
After that, you will need to extract the KDZ file using LGExtractor (and not DZExtractor).
You can download it from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Extract.
Put your KDZ file on an easy access folder. I will assume you will use C:\RecoverE455\ROM for this.
Launch an Administrator command line prompt, and run this command:
Code:
C:\RecoverE455\Extract\LGExtractor -kdz C:\RecoverE455\ROM\<KDZ-ROM-FileName>.kdz
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
3. Getting a most recent version of LGFlashTool
After this procedure, you will have to download LGFlashTool in order to flash you newly extracted BINARY rom.
You can download it from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Flasher.
Run the Setup program attached within it and it will install itself under the folder C:\LG\LGFlashTool. Overwrite the file MegaLock.dll under this folder with the one you just extracted in C:\RecoverE455\Flasher.
4. Install the correct LG Support Drivers for your E455 phone
Instead of installing the most recent version of LG Drivers provided by LG, you will install the following ones:
LG United Mobile Driver 3.8.1
LG Windows Mobile 1.0
LG SmartPhone DUN Modem Driver 1.0
They are packaged and you can download them from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Drivers. Install them in the order described above then restart your computer.
5. Put your phone under Download Mode
To do this, turn off your phone either directly either removing and reinserting the battery.
Plug the phone - WHILE TURNED OFF - on your computer by the USB cable.
Hold (Vol Up) + (Vol Down) and turn on the phone. Keep holding (Vol Up) + (Vol Down) until you see the line "==>Download mode" in bottom of the screen. If it doesn't appear, try until you get this.
6. Configuring your computer to flash under USB download mode
After plugging your device under Download Mode, open Windows Device Manager and search for some LGE AndroidNet USB Serial Port (COM##):
{
"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"
}
If it is not (COM41), you must set it to port (COM41). Set properties of the serial port, select tab "Port Settings", then click "Advanced":
Here, select (COM41) for COM number port.
7. Launch LGFlashTool and flashing
Open your newly modified LGFlashTool (yes, the one you downloaded here and replaced some DLL). It immediately will ask for your BINARY rom and a DLL:
Click the "..." button and select the LGUP***.DLL in the same folder as your .BIN file you extracted in step 2.
Click the "Add" button immediately below (side S/W box), then select the LGE***.BIN you extracted in step 2.
Click OK.
Click the serial port button --
--, and let this dialog be equal as this one, with only "16 ports\Port 1 ~ Port 16\1" marked:
And now click the forward button --
.
It will display READY on box with port COM41.
Disconnect your phone, turn it off, then turn it on under Download Mode as described on step 5.
If you manage to turn it on Download Mode without connecting to your computer, plug it back to the computer.
It will begin flashing by itself. No action needed.
DO NOT DISCONNECT YOUR PHONE. I DON'T KNOW WHAT MAY HAPPEN IF YOU DO SO, BUT PROBABLY YOU WILL BREAK DEFINITIVELY YOUR DEVICE.
After all, your phone will restart with all its original configuration and LGFlashTool will display an error. After you manage to finish LGSetupWizard on the phone, you may close everything.
Man, you are a HERO.
I was having trouble debranding and updating my phone, but with your tutorial, it was EASY! Now I have a debranded and updated phone (V10K).
MANY MANY MANY THANKS!!!
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
i couldn't find these, i've done instructions carefully ... help me pleasee !!! :crying:
reresatria said:
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
i couldn't find these, i've done instructions carefully ... help me pleasee !!! :crying:
Click to expand...
Click to collapse
solved :laugh: , just doin' little mistake ... thanks man for tutorial
Hi! I'm here again!
I'm trying to do everything again, but now in my new phone, a D685 (LG G Pro Lite Dual).
But, when I connect it in download mode, FlashTool give me an error just after "USB Connection established". No description of the error, just a "F0000002"...
You know how to solve this?
LG 455 IMEI Problem
Hi,
I flash my phone following this instructions a month ago, all gone ok but yesterday both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
niconiconico111 said:
Hi,
I flash my phone following this instructions a month ago, all gone ok but yesterday both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
Click to expand...
Click to collapse
The AT commands worked for me. In putty, be sure to get "IMEI changed" as response, and check the number. If I remember, the IMEI is comma seppareted.
[SOLVED]
romulocarlos said:
The AT commands worked for me. In putty, be sure to get "IMEI changed" as response, and check the number. If I remember, the IMEI is comma seppareted.
Click to expand...
Click to collapse
Hi, thanks for the reply!
Yes, finally the solution was simple, instead of using AT+EGMR command I use AT%IMEI=, that worked!!
can u solve it ?
romulocarlos said:
Hi! I'm here again!
I'm trying to do everything again, but now in my new phone, a D685 (LG G Pro Lite Dual).
But, when I connect it in download mode, FlashTool give me an error just after "USB Connection established". No description of the error, just a "F0000002"...
You know how to solve this?
Click to expand...
Click to collapse
hii, how about this problem ? have you solved it ? can u tell me how do it ... i've got same problem,
reresatria said:
hii, how about this problem ? have you solved it ? can u tell me how do it ... i've got same problem,
Click to expand...
Click to collapse
FlashTool can't work with this phone. Instead, search here on XDA about flashing KDZ larger than 1Gb. Is an offline method.
help
romulocarlos said:
FlashTool can't work with this phone. Instead, search here on XDA about flashing KDZ larger than 1Gb. Is an offline method.
Click to expand...
Click to collapse
thx for reply, i'm using L5 II E455 before i've tried your method about twice and it's work, but since i restart my phone and got an android laying with a red triangle over it, i can't flashing again, it got problem error F0000002 ...
goo(dot)gl/R43Jmj if you don't mind click the url
reresatria said:
thx for reply, i'm using L5 II E455 before i've tried your method about twice and it's work, but since i restart my phone and got an android laying with a red triangle over it, i can't flashing again, it got problem error F0000002 ...
goo(dot)gl/R43Jmj if you don't mind click the url
Click to expand...
Click to collapse
I'm sorry, I make a mistake. My answer above was for another thread.
This method works with E455, just check the drivers and everything else again, and if possible, use a clean computer.
Again, sorry for my mistake.
still can't
romulocarlos said:
I'm sorry, I make a mistake. My answer above was for another thread.
This method works with E455, just check the drivers and everything else again, and if possible, use a clean computer.
Again, sorry for my mistake.
Click to expand...
Click to collapse
still i can't flash my phone,
Thank you very much, I could not recover the phone all the time, the update always stuck to 4%. When this has helped me! Just when I launched the BAT extractor, it deleted all the contents of the parent folder.
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:
Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful
[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