Related
Hello!
I need some help and I know this is the place to find it!
I have searched for several days all over the internet trying to read and gather information, and I am coming up short.
I know Bruno Martins has posted some information on his blog on how to "readback" (backup) your current rom for your phone, but there is no information on how to flash the entire ROM package back to your phone (at least with regard to the errors you may receive).
Basically, I am looking for some help on how to backup one of my phones entire rom package and put it on my other phone that I messed up via the Smart Phone Flash Tool (the exact same model: Star Touch Diamond 2 B2000 MT6573).
The new phone works perfect, I have never touched it, my old phone which is the same model I deleted and formatted the system so I need to put the stock rom on.
I was able to do a "backup" of my new phone, but when i try to flash the preloader and uboot, etc, the sp flash tool says error loading file, or region too large with overlap.
Any help would be greatly appreciated!
By the way, my phone is not bricked, but I cannot access recovery! I was able to find and install another fully assembled rom to my phone and the phone does power on with lights, but it doesnt have the display driver I need so I cannot see anything.
The reason I flashed another rom was because the phone was essentially bricked and wouldnt do anything, and that was the only rom I could find on the internet that was a full package (preloader, uboot, system, etc) but isnt compatible with phone.
Anyhow, if I understand correctly I need to use hexadecimal calculator to find length of partitions of original phones rom, readback the files, somehow edit the preloader file? then flash them back to the old phone?
Please help!
I would love to make a tutorial of this method with pictures and possible errors for everyone if we could get this solved!
Please point me in the right direction!
And I wanted to thank BRUNO in advance for his hard work and help!!
have you tried the neutrino rom from notorious? its reallllly small around 50mb. you may be able to install that since it so small, then work your way back down? not too sure and i can say im no grandmaster but it might work!
***derp. neutrino... thats for atrix only. but hey same concept. maybe a small barebones rom will get you running enough to get things done properly.
Hello stokemonkey!
No, I have not tried the neutrino rom. My main goal is to take my working phone and copy the firmware to my other phone which is the same model. I attempted to flash a rom and then it didnt work out so well (phone still lights up, drivers are not compatible).
I all else fails I can attempt the neurtino rom (as long as you dont have to install from sd card zip file because I cannot!)
the neutrino is an Atrix 4G rom only, so you cant use it and it also needs to be installed via internal so its a no go either way. isnt your phone the china "htc" model? i dont have much user time on an htc so im not too sure what you can do?
again id try to find a barebones that you can flash the way you did with the rom that gave you errors. ill try to do some searching too and see what i can find. let me know if you get anything workin! and if there is someone else out there that can enlighten the both of us help would be appreciated!
and isnt yours like an evo 4g? maybe one of those roms will work?
Thanks for your response and suggestions. I will try to dish up a small tutorial with how far I can get in the backup/flashing process. I can check for an evo 4g rom and see what the specs are. The current rom I used i believe works, but doesnt have the video driver so the screen has no image. I believe each partition of ram has a set size so you can only flash a rom for the mt6573 chipset which will fit in the available space for each partition and also happens to contain the video, audio, bluetooth, etc drivers.
I have used SP Flash Tool and was able to backup all of the partitions of my working phone but the SP Flash Tool gives all sorts of errors when I try to load the files and flash them to my non-working phone.
The funny thing is that I downloaded files for a different phones rom and was able to flash those to the non-working phone, as mentioned in my previous post, which allows the phone to power on, but the phone doesnt work besides lighting up.
I know it is possible to make a backup of my good phone and flash that rom onto my non-working phone, I just dont know what I am doing wrong.
So far, this is what I have done . . .
1. Installed SDK tools for android
2. Obtained my scatter txt file by using command prompt
3. Used MTKRomStudio to open that file which tells me the addresses of all the partitions and their file sizes
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
5. Confirmed the file sizes of each of the above files to what MTKRomStudio said the file size should be
6. Attempted to load these files into SP Flash Tool and get errors such as "partition too large, failed to load", or "partitions overlap".
7. I was able to open some of the partitions such as android, and usrdata but when attempting to flash I receive errors such as "dram error".
8. I was able to download an entire backup of all "readback" files for a different model phone, and each one of those files loaded fine and downloaded to my non-working phone.
9. Just to mention, my non-working phone was completely dead (no power up, no lights) before I flashed the random phone rom I found online, and now at least it powers up (lights up).
Anyone have any information? I have created a small visual representation of what I have been looking at and messing around with. Let me know!
Mt6573 phone flash help
Hi all, I need help. I used sp flash tool and flashed the original files to my phone. I then restarted the phone and it would not go past the blue android screen. I let se overnight and still no success. After that i flash the boot and still no progress. Finally i flashed the uboot and now it only lights up but no picture at all. I have used sp flash to try to flash the entire file system back to the mt6573 but it will not flash the recovery, android, or sec_ro files. Can anyone help?
CrimsonX said:
Hi all, I need help. I used sp flash tool and flashed the original files to my phone. I then restarted the phone and it would not go past the blue android screen. I let se overnight and still no success. After that i flash the boot and still no progress. Finally i flashed the uboot and now it only lights up but no picture at all. I have used sp flash to try to flash the entire file system back to the mt6573 but it will not flash the recovery, android, or sec_ro files. Can anyone help?
Click to expand...
Click to collapse
Same problem here except I can't flash dsp and preloader
UPDATE : flash worked finaly.my phone is fixed
Sent from my GT-P5110 using xda app-developers app
Whistler011 said:
Same problem here except I can't flash dsp and preloader
UPDATE : flash worked finaly.my phone is fixed
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Please share how you did it, i'm in the same position with a MT6573 phone that are stuck on boot, and wont accept the preloaderfile
nsxtas said:
Please share how you did it, i'm in the same position with a MT6573 phone that are stuck on boot, and wont accept the preloaderfile
Click to expand...
Click to collapse
Same here.
Can somebody please post all the files .
I have an Alcatel one touch 918 not d/m/n
It`s the second phone that i have bricked.
Sharing it`s caring.
LeStonga said:
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
Click to expand...
Click to collapse
I'm using MTK6573 phone but could i know how do you start the "readback" using SP Flash. I'm not able to start it while holding VOL-UP button and connect the USB data cable into your phone. Are there any other methods to start it. Thanks for your help.
CM
Why don't you make a try with CyanogenMod?
LeStonga said:
Thanks for your response and suggestions. I will try to dish up a small tutorial with how far I can get in the backup/flashing process. I can check for an evo 4g rom and see what the specs are. The current rom I used i believe works, but doesnt have the video driver so the screen has no image. I believe each partition of ram has a set size so you can only flash a rom for the mt6573 chipset which will fit in the available space for each partition and also happens to contain the video, audio, bluetooth, etc drivers.
I have used SP Flash Tool and was able to backup all of the partitions of my working phone but the SP Flash Tool gives all sorts of errors when I try to load the files and flash them to my non-working phone.
The funny thing is that I downloaded files for a different phones rom and was able to flash those to the non-working phone, as mentioned in my previous post, which allows the phone to power on, but the phone doesnt work besides lighting up.
I know it is possible to make a backup of my good phone and flash that rom onto my non-working phone, I just dont know what I am doing wrong.
So far, this is what I have done . . .
1. Installed SDK tools for android
2. Obtained my scatter txt file by using command prompt
3. Used MTKRomStudio to open that file which tells me the addresses of all the partitions and their file sizes
4. Used SP Flash Tool V.2.11.29.00 to "readback" (backup) each individual rom file (preloader, uboot, bootimg, android, dsp, etc)
5. Confirmed the file sizes of each of the above files to what MTKRomStudio said the file size should be
6. Attempted to load these files into SP Flash Tool and get errors such as "partition too large, failed to load", or "partitions overlap".
7. I was able to open some of the partitions such as android, and usrdata but when attempting to flash I receive errors such as "dram error".
8. I was able to download an entire backup of all "readback" files for a different model phone, and each one of those files loaded fine and downloaded to my non-working phone.
9. Just to mention, my non-working phone was completely dead (no power up, no lights) before I flashed the random phone rom I found online, and now at least it powers up (lights up).
Click to expand...
Click to collapse
I have a MT6575 phone and I have exactly your nr. 7 issue (BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)). Were you able to get this working somehow? I am confident that the selected partitions are for this phone as I read them out myself. But flashing back won't work. Does anyone have any leads?
e-lime said:
I have a MT6575 phone and I have exactly your nr. 7 issue (BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)). Were you able to get this working somehow? I am confident that the selected partitions are for this phone as I read them out myself. But flashing back won't work. Does anyone have any leads?
Click to expand...
Click to collapse
If you have the correct files use the newest version:
http://forum.xda-developers.com/showthread.php?t=1982587
It is easy to mess things up if you try random files.
MTK 6577 and SP Flash Tool
I too am also having problems with the flash tool. I am trying to help a friend bring his chinese note 2 clone back to life. He somehow got CWM onto the phone and the custom recovery seems to be functioning properly, but I cant find any sort of ROM file to flash in recovery.
Now I am going back and trying to restore the phone to factory using the flash tool. Installed the VCOM drivers, then went to load the scatter file we obtained from the factory (Bro Tech) it says the scatter file is incorrect format?
My question is: are there any roms we could try to flash on this phone from CWM or do we have to use the Flash Tool? I'm hoping since CWM seems to be working that I can simply flash an acceptable rom with that instead of trying to find a scatter file.
Maybe someone can suggest some ROMs to try flashing with CWM. The phone is: Goophone N2 7100 I believe. Thanks for reading, I really want to help him resurrect this interesting piece of copyright infringement (the phone looks amazingly like a Note 2 till you get close to it)
Evita Carbonized
GTab 2 7 AOKP'd
DollarStrawz said:
I too am also having problems with the flash tool. I am trying to help a friend bring his chinese note 2 clone back to life. He somehow got CWM onto the phone and the custom recovery seems to be functioning properly, but I cant find any sort of ROM file to flash in recovery.
Now I am going back and trying to restore the phone to factory using the flash tool. Installed the VCOM drivers, then went to load the scatter file we obtained from the factory (Bro Tech) it says the scatter file is incorrect format?
My question is: are there any roms we could try to flash on this phone from CWM or do we have to use the Flash Tool? I'm hoping since CWM seems to be working that I can simply flash an acceptable rom with that instead of trying to find a scatter file.
Maybe someone can suggest some ROMs to try flashing with CWM. The phone is: Goophone N2 7100 I believe. Thanks for reading, I really want to help him resurrect this interesting piece of copyright infringement (the phone looks amazingly like a Note 2 till you get close to it)
Evita Carbonized
GTab 2 7 AOKP'd
Click to expand...
Click to collapse
Create personalized file scatter for your device with MTK Droid. Here: http://forum.xda-developers.com/showthread.php?t=2160490
[email protected] said:
Same here.
Can somebody please post all the files .
I have an Alcatel one touch 918 not d/m/n
It`s the second phone that i have bricked.
Sharing it`s caring.
Click to expand...
Click to collapse
Have a alcatel 4033a Phone Got bricked and needs to be flash any help on that ..? plz i need help
Alecupid said:
Have a alcatel 4033a Phone Got bricked and needs to be flash any help on that ..? plz i need help
Click to expand...
Click to collapse
hi, i've made a mistake.
I've installed an odex version from a modified recovery(with dalvick cache). Can anyone help me?
Hi,
I have a Motorola atrix 4g. The phone will not boot up. It turns on and the Motorola logo come then the red light stars blinking. after a minute or so the phone restarts and repeats the process. I tryed factory hard reset but no luck.
i fount this on the web http://forum.xda-developers.com/showthread.php?t=966405 but has no idea how to do this.
Pleas help me
thank you
Pgeorge
It happens if there is somthing wrong when you install a rom
try to find another rom and flash it if you unlocked the bootloader
or flash ATT 4.5.91 Rom via RSD Lite ONLY IF YOU HAVE LOCKED BOOTLOADER
Jack Krauser said:
It happens if there is somthing wrong when you install a rom
try to find another rom and flash it if you unlocked the bootloader
or flash ATT 4.5.91 Rom via RSD Lite ONLY IF YOU HAVE LOCKED BOOTLOADER
Click to expand...
Click to collapse
hi,
thank you for the fast replay. I have rsd installed, but where can i find this rom
Softbrick
Is bootloader unlocked? Says on m logo?
Sent from my MB860 using xda premium
stevendeb25 said:
Softbrick
Is bootloader unlocked? Says on m logo?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
It is not unlocked. There is nothing on the logo. Only the m
help
kinggeorge3287 said:
It is not unlocked. There is nothing on the logo. Only the m
Click to expand...
Click to collapse
help please
go here to download any atrix related files
visit that site, it contains everything for the atrix and the best place to get roms, tools, utilities, mods, tweaks, and so forth....
but first download the zip file below this message. I uploaded the zip file for you that has adb, fastboot & moto-fastboot(lets you install .img over 100mb), the necessary dll files & atrix recovery image & command.bat which just opens the command prompt window for you and puts you into the folder so you dont have to navigate anywhere in command prompt to located folders.
first try this, download the zip file, extract to any folder like c:\fastboot
then run the command.bat file to quickly bring up a command prompt and type these commands
Code:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
that may solve your issue if your kernel installed properly and the boot.img file was properly written to the boot partition. If it doesn't solve your problem, go to that link above to find the kernel for whatever rom you're on, att, cm7 or cm9. Get the correct kernel thats compatible, pull out the boot.img from that zip file and also place it into your fastboot folder, then go to fastboot mode again and type "fastboot flash boot boot.img" and then fastboot reboot.
android-DEP said:
go here to download any atrix related files
visit that site, it contains everything for the atrix and the best place to get roms, tools, utilities, mods, tweaks, and so forth....
but first download the zip file below this message. I uploaded the zip file for you that has adb, fastboot & moto-fastboot(lets you install .img over 100mb), the necessary dll files & atrix recovery image & command.bat which just opens the command prompt window for you and puts you into the folder so you dont have to navigate anywhere in command prompt to located folders.
first try this, download the zip file, extract to any folder like c:\fastboot
then run the command.bat file to quickly bring up a command prompt and type these commands
Code:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
that may solve your issue if your kernel installed properly and the boot.img file was properly written to the boot partition. If it doesn't solve your problem, go to that link above to find the kernel for whatever rom you're on, att, cm7 or cm9. Get the correct kernel thats compatible, pull out the boot.img from that zip file and also place it into your fastboot folder, then go to fastboot mode again and type "fastboot flash boot boot.img" and then fastboot reboot.
Click to expand...
Click to collapse
Hi,
I tryed doing this, but i get a error " Failed to process command flash: recovery error (0x180002)
I think when i tried to flash rom with RSD LIght may have done something to the files. and it was no help. I dont get a flashing red light now. only the phone stops booting at M logo.
Now How do i flash new rome ? Do i use RSD Light or something else. I know that RSB Requires .sbf file but all the files i see in the site you gave me are .zip.
i also tryed the fastboot flash boot boot.img and no luck, it gvies me the error "Failed to process command flash: recovery error (0x180002)"
thank you for the replay
Pgeorge
do you have clockworkmod recovery installed or any custom recovery installed? if not, then thats why it wont flash, your bootloader is locked.
the whole idea behind using clockworkmod recovery is to avoid using RSD to flash sbf files which can brick the phone easily. Its best to avoid using RSD to flash sbf files on your phone at all costs and leave only as a last resort method if you just cannot recover the phone.
Flashing a new rom would normally be done by already having your phone rooted and unlocked with clockworkmod recovery or some other custom recovery installed so you can boot into recovery and choose "install from zip" and point to the zip file that has the rom. The custom recovery does the flashing for you and its a safer method of flashing roms on the phone than RSD.
If you got no other choice and I know what thats like, i been there too. Download RSD Lite v5.6, should be a free download online somewhere, and then search online for "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", then use RSD to flash that sbf onto phone.
Before trying that, goto http://samcripp.com/files/ and in the folder OTA Updates, download the first file named Blur_Version_91.4.5.141.MB860.ATT.en.US.zip and put it into the fastboot folder, boot into fastboot again and try "fastboot update Blur_Version_91.4.5.141.MB860.ATT.en.US.zip" and you may be able to get away with just using fastboot to flash that update onto the phone to restore corrupt files. I would try this before using RSD to flash the phone
android-DEP said:
do you have clockworkmod recovery installed or any custom recovery installed? if not, then thats why it wont flash, your bootloader is locked.
the whole idea behind using clockworkmod recovery is to avoid using RSD to flash sbf files which can brick the phone easily. Its best to avoid using RSD to flash sbf files on your phone at all costs and leave only as a last resort method if you just cannot recover the phone.
Flashing a new rom would normally be done by already having your phone rooted and unlocked with clockworkmod recovery or some other custom recovery installed so you can boot into recovery and choose "install from zip" and point to the zip file that has the rom. The custom recovery does the flashing for you and its a safer method of flashing roms on the phone than RSD.
If you got no other choice and I know what thats like, i been there too. Download RSD Lite v5.6, should be a free download online somewhere, and then search online for "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", then use RSD to flash that sbf onto phone.
Before trying that, goto http://samcripp.com/files/ and in the folder OTA Updates, download the first file named Blur_Version_91.4.5.141.MB860.ATT.en.US.zip and put it into the fastboot folder, boot into fastboot again and try "fastboot update Blur_Version_91.4.5.141.MB860.ATT.en.US.zip" and you may be able to get away with just using fastboot to flash that update onto the phone to restore corrupt files. I would try this before using RSD to flash the phone
Click to expand...
Click to collapse
Well i tryed everything you provided, but no luck. I tryed the RSD but it dont go past the M logo after flash. any other way you know?
thnak you
pgeorge
http://forum.xda-developers.com/showthread.php?t=1163342
you said that site doesnt have any SBF files to download, this is a good example of why the owner decided against posting the sbf files online. A lot of people from what I heard, were either soft bricking their phones into temporary hat weights or going full out hard into brick city on a one way ticket joy ride. Flashing sbf files is very risky and RSD tool isn't really meant for the public to be downloading to use at home and flash full roms over their devices. Thats a Motorola utility and it's not exactly a risk-free method of flashing the rom inside these phones. Plus getting SBF files online, you rarely know 100% if its compatible with your model phone or where came from exactly and that it's integrity can be checked for 100% consistency that nothing half-way through the file is missing any chunks of code or is corrupt. Try sticking to only using fastboot & adb & get clockworkmod recovery to make FULL and complete devices backups.
Now that I learned my lesson a few times, no matter what, first thing I always do in recovery is make a backup before I flash anything at all, just in case of just in case, its better to measure twice and cut once.
try that link above and restore stock gingerbread 2.3.4, phone doesnt need to be unlocked or root, and make sure to use "moto-fastboot.exe" it lets you push\pull & install files larger than 200MB onto phone through fastboot, the regular fastboot has some limit on file sizes
Hi,
to give you a update noting worked. The link you provided dont have any working lnks to download. I tryed some other once and no luck. It gave me "failed to boot 1". so i flashed this file "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf" it went away, but no boot after the logo. I don't know what i am doing wrong. Any other ideas?
Thank you
Pgeorge
android-DEP said:
http://forum.xda-developers.com/showthread.php?t=1163342
you said that site doesnt have any SBF files to download, this is a good example of why the owner decided against posting the sbf files online. A lot of people from what I heard, were either soft bricking their phones into temporary hat weights or going full out hard into brick city on a one way ticket joy ride. Flashing sbf files is very risky and RSD tool isn't really meant for the public to be downloading to use at home and flash full roms over their devices. Thats a Motorola utility and it's not exactly a risk-free method of flashing the rom inside these phones. Plus getting SBF files online, you rarely know 100% if its compatible with your model phone or where came from exactly and that it's integrity can be checked for 100% consistency that nothing half-way through the file is missing any chunks of code or is corrupt. Try sticking to only using fastboot & adb & get clockworkmod recovery to make FULL and complete devices backups.
Now that I learned my lesson a few times, no matter what, first thing I always do in recovery is make a backup before I flash anything at all, just in case of just in case, its better to measure twice and cut once.
try that link above and restore stock gingerbread 2.3.4, phone doesnt need to be unlocked or root, and make sure to use "moto-fastboot.exe" it lets you push\pull & install files larger than 200MB onto phone through fastboot, the regular fastboot has some limit on file sizes
Click to expand...
Click to collapse
kinggeorge3287 said:
Hi,
to give you a update noting worked. The link you provided dont have any working lnks to download. I tryed some other once and no luck. It gave me "failed to boot 1". so i flashed this file "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf" it went away, but no boot after the logo. I don't know what i am doing wrong. Any other ideas?
Thank you
Pgeorge
Click to expand...
Click to collapse
when rds end flashing the sbf the phone gets a bootlop or failed to boot error again?
lucamibel said:
when rds end flashing the sbf the phone gets a bootlop or failed to boot error again?
Click to expand...
Click to collapse
it starts up, the M logo comes and it freezes there. To turn the phone off i have to pull the battery.
thank you
Pgeorge
Restore Your Motorola Atrix 4G Back to 4.5.91 Stock Firmware
it helps to remove any problem related to rom..
With so many Android phones literally flooding the market these days, it’s no wonder that there are also so many firmware upgrades and custom firmware being developed and released every now and then. A superior device with great stuff neatly packed into it, the Motorola Atrix 4G is one of the devices for whom developers have devoted significant firmware love.
One reason for the attention that devs give to the Atrix 4G is that it is a fantastic device with a dual-core Nvidia Tegra 2 processor and robust ability for handling impressive graphics and video without choking. Together with its powerful processor and 1 GB of RAM, the Atrix 4G is a mean powerhouse that can be further exploited with the use of third-party applications and custom ROMs.
In an age where technology is constantly changing at an alarming pace it is important to always have a trusted source to get your updates in a timely fashion. Custom ROMs and factory firmware updates have played a crucial role in the development in many of our devices.
For those of you who have rooted your Atrix 4G and already have installed custom ROMs, then you might already have some bad experiences with regards to unofficial firmware sources. Unofficial firmware such as custom ROMs are literally filled with many bugs and disabled features. In many cases, these ROMs are not stable for daily use.
Luckily for owners of the Motorola Atrix 4G, there’s an escape hatch for reverting to stock, functioning firmware and return the phone to its factory state.
In this tutorial, you will learn how to roll back your Motorola Atrix 4G to the official firmware version 4.5.91, regardless of your current firmware
HERE IS THE LINK FOR YOUR PROBLEM....BEST OF LUCK
kinggeorge3287 said:
it starts up, the M logo comes and it freezes there. To turn the phone off i have to pull the battery.
thank you
Pgeorge
Click to expand...
Click to collapse
then you can now try unlocking and flashing cwm recovery and flash a custom rom to avoid using rds again
sikkijazz said:
Restore Your Motorola Atrix 4G Back to 4.5.91 Stock Firmware
it helps to remove any problem related to rom..
With so many Android phones literally flooding the market these days, it’s no wonder that there are also so many firmware upgrades and custom firmware being developed and released every now and then. A superior device with great stuff neatly packed into it, the Motorola Atrix 4G is one of the devices for whom developers have devoted significant firmware love.
One reason for the attention that devs give to the Atrix 4G is that it is a fantastic device with a dual-core Nvidia Tegra 2 processor and robust ability for handling impressive graphics and video without choking. Together with its powerful processor and 1 GB of RAM, the Atrix 4G is a mean powerhouse that can be further exploited with the use of third-party applications and custom ROMs.
In an age where technology is constantly changing at an alarming pace it is important to always have a trusted source to get your updates in a timely fashion. Custom ROMs and factory firmware updates have played a crucial role in the development in many of our devices.
For those of you who have rooted your Atrix 4G and already have installed custom ROMs, then you might already have some bad experiences with regards to unofficial firmware sources. Unofficial firmware such as custom ROMs are literally filled with many bugs and disabled features. In many cases, these ROMs are not stable for daily use.
Luckily for owners of the Motorola Atrix 4G, there’s an escape hatch for reverting to stock, functioning firmware and return the phone to its factory state.
In this tutorial, you will learn how to roll back your Motorola Atrix 4G to the official firmware version 4.5.91, regardless of your current firmware
HERE IS THE LINK FOR YOUR PROBLEM....BEST OF LUCK
Click to expand...
Click to collapse
Hi,
doing this gave me SVF:108:1:2
fail to boot 3
starting rsd mode
lucamibel said:
then you can now try unlocking and flashing cwm recovery and flash a custom rom to avoid using rds again
Click to expand...
Click to collapse
So how do i go about doing this? is there a link i can use?
thank you
Pgeorge
kinggeorge3287 said:
So how do i go about doing this? is there a link i can use?
thank you
Pgeorge
Click to expand...
Click to collapse
help please
kinggeorge3287 said:
help please
Click to expand...
Click to collapse
I am able to get into android recovery. It has a option to update from sdcard. Can i do something with this?
Pleas help
Pgeorge
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Laitas said:
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Click to expand...
Click to collapse
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Aerieana said:
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Click to expand...
Click to collapse
Well i spend best part of this morning trying to a different aproach , i managed to find a ROM file (in kdz format, whitch woulve been useless for mtk tools anyway) whitch i extracted for a Recovery.img and tried to port the various recovieries with no awail for now. From what i've seen the filesystem inside the rom is a mess some of the files have the MTK headers others have the android ones and I'm trying to make this work entirely by trial and error.. If I'll manage to boot into the recovery I'll let you know. Wish me luck
Ok I managed to make a port from K10 that actually boots to recovery. I'll post updates as I work on it (all trial and error~)
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
what K8 do you have? MTK or Qualcomm Version?
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery :
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
how you extract the recovery img from the kdz? thanks.
tomi.gutierrez.i said:
how you extract the recovery img from the kdz? thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Laitas said:
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Click to expand...
Click to collapse
i flash the image you give, and it cant mount system, so it cant flash supersu, the lg k10 have the same problem that this recovery (it might be for the port), so we have to wait a super su version for lg k10 and k8 and a functional TWRP
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : LINK
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Yasser Da Silva said:
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Click to expand...
Click to collapse
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Have u found a way to root a lg k8
Maveroik said:
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Click to expand...
Click to collapse
Have u found a way to root a lg k8
Declan nalced said:
Have u found a way to root a lg k8
Click to expand...
Click to collapse
Nope man :'c
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : xxxxxxxxxxxxxxxx
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
hackwilliam said:
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
Click to expand...
Click to collapse
That was step 1 you have to go to fastboot form adb and unlock it from there
I've got the k8 us375 model today and its running 6.0 with an update waiting to install. I'm sure it won't matter much but I'm going to avoid updating anytime soon.
With little research into the device I'm reading people trying kingroot and getting stuck with a semi brick and error. From what I've read about marshmallow is the root needs to be accepted from the boot.img which also needs to be insecure.
So unlocking the bootloader is first.
Second is modifying the kernel and
Then recovery needs to be made so that superSu can be flashed.
I'm no expert but neither am i a newbie to this process, however I'm a little rusty. If anyone knows a better way to describe the processes needed please enlighten me. I'll be away from my PC till this weekend but have a laptop i can tinker with tonight. Until i completely understand what needs to be done I'll continue to do research. Thanks
Sent from my LGUS375 using Tapatalk
justlovejoy said:
If anyone knows a better way to describe the processes needed please enlighten me.
Sent from my LGUS375 using Tapatalk
Click to expand...
Click to collapse
I've been trying to root my k8 (k350n) - european version the last few weeks... so far i got:
(here i try to post a url i can't yet... you can find my topic on chinaphonearena - i describe everything there - search "lg k8 k350n twrp" on google - it will be the second result)
the twrp boots but i'm afraid it's not a perfect port so it migth not handling the partitions well... i mean when i try to install supersu i think it cannot find the boot.img (it seems to find but can't patch it).
The newest supersu supposed to patch the boot.img automatically so i believe the only thing we should manage to get a working twrp...
if you want to try i have to warn you that sometimes when i mess with the twrp i have to make a hard reset the get my phone working again. When you boot to the twrp it asks if you want to make your system writeable - you don't have to do that in order to install supersu - however if you allow twrp to make your system writeable you might lose data (i only lost data if i did a format in the twrp but only writeability doesnt clear data in my case...)
edit1:
so i found that supersu can only patch boot images compress by "gzip". The boot im. of our k8 is compress using "lz4" method. I also realized that my twrp works so far as the supersu tries to decompress the boot image... so
We either wait till supersu deals with lz4 or if we could somehow take (dump to pc) the boot image in fastboot "re"compress to gzip - flash back to the device - restart twrp (not boot to android yet - which obviously would not work), install supersu - restart to fastboot take the boot image "re"compress to lz4 and flash the patched boot.img back to the device.
well it's just an idea which actually stucks at dumping the image without root and who knows what other reasons...
or if we knew what tweaks needs to be done to the boot image and we could just make it on pc and flash it in fastboot (i have the stock boot image - i have the whole firmware actually)...
Any advice would be appriciated
Here we go guys...
http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
I actually had to return it. It was brand new in the box but the imei was linked to a delinquent account and I couldnt activate it. I'm subscribed if anything.
Looking to start a discussion on rooting the unlocked version.
I have tried the root for other variants for this phone and does not work
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Duhjoker said:
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
Click to expand...
Click to collapse
We are now in this forum. Why some dork mod moves these too early?
Why here, why not to the K8 forums instead?
The link I posted should work with your device...
Just got told to go to the k8 forums because im really just trying to get the bootloader unlocked. Temp root is nice but my plans involve a recovery and a fully rooted phone. Im trhing to develop a way to compile apps and operating systems completely on the device but i need full access.
Im looking for firmware for LG K8 2018 X210ULMG. Where can i find it ?
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Duhjoker said:
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Click to expand...
Click to collapse
I can't fin anywhere for X210ULMG. Try and when you will find paste here link because anywhere is this rom.
which android version do y0u have 9n your k8. I also need you to go to settings system software info and tell me the software versiion. And just for SandG no seriously, open up a terminal in terminal emulator and type getprop. im looking fir the value of
ro.lge.swversion_arb
to be of further assistance may i ask what exactly you are using it for? ie reflash stock fix brick or other. i can help you with the best plan of action and any other how to.
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Duhjoker said:
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Click to expand...
Click to collapse
I have problem because one month ago I flashed My K8 ULMG with kdz for Aristo 2 . I downloaded the software from Aristo 2 and made Brick through it.
Now it doesn't turn on, gives no sign of life, nothing. When connected to a laptop, the computer can only see Qualcomm HS-USB QDLoader 9008.
Do you know solution for it ?
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Duhjoker said:
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Click to expand...
Click to collapse
Did you found some method for unbrick this phone without motherboard change ?
Hi,
I bought a new Moto G Play 2021 (XT2093-4) to experiment with changing the stock ROM. The ROM version is RZAS31.Q2-146-14-7 and I downloaded the stock ROM from https://mirrors.lolinet.com/firmware/moto/guamna/official/RETCA/ since I couldn't use the Rescue and Smart Assist (LMSA) (https://support.lenovo.com/ca/en/downloads/ds101291) to obtain one. And the reason for that is that I use Ubuntu on my laptop and using wine to install LMSA ended up being a horrible experience. I used these two guides to install Magisk: https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ and https://topjohnwu.github.io/Magisk/install.html using the boot.img in the Stock ROM I downloaded from lolinet. This went all good and I had root access. I should also mention that I already had the bootloader unlocked.
Then I installed system-squeak-arm64-ab-floss.img.xz from https://github.com/phhusson/treble_experimentations/releases/ using this guide more or less: https://forum.xda-developers.com/t/...moto-g-play-2021-guamna.4260871/post-86389207. This all went good as well. It flashed the ROM successfully but the touch screen does not work anymore. I know it's not frozen cause I used SCRCPY to access phone from my computer and operate it.
I tried flashing the boot from lolinet stock ROM but that didn't help, neither did flashing the Magisk again. I also tried the gapps version of the treble instead of the floss but that didn't help either. Again all flashes work but the touch screen doesn't, although I get this error right before the rest of the flash goes through: Invalid sparse file format at header magic. I also tried to flash the stock ROM following this guide: https://forum.xda-developers.com/t/x-force-how-to-manually-flash-official-firmware.3282077/ but when I try to run this fastboot command, flash system super.img_sparsechunk.0, I get this error, Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition').
So I don't know what to do anymore, if anyone knows a fix for this please help!
Thanks!
Anyone try any GSI ROMs on the G Power 2021?
It's pretty standard hardware as far as phones go. No weird under display fingerprint reader or anything. Anyone try a GSI ROM? It might "just work" or "almost just work but you need to run a few commands to fix something".
forum.xda-developers.com
The link goes to post #37. Check if that solution for the G Power works the same for the G Play. I'm confident it will.
mario0318 said:
Anyone try any GSI ROMs on the G Power 2021?
It's pretty standard hardware as far as phones go. No weird under display fingerprint reader or anything. Anyone try a GSI ROM? It might "just work" or "almost just work but you need to run a few commands to fix something".
forum.xda-developers.com
The link goes to post #37. Check if that solution for the G Power works the same for the G Play. I'm confident it will.
Click to expand...
Click to collapse
I can not believe this worked! I can't thank you enough. I was almost giving up. Thanks again!