Related
So I've had my Atrix for a few months now, and it's mostly awesome. I'm coming from having owned an iPhone before, and it's just fantastic. I've stayed away from modding it too much however, since I knew the bootloader was locked and not a lot could really be done. But, according to several posts I see here, the bootloader seems to have been unlocked recently. Yay?
So, I ask that you forgive my ignorance. What does this mean? Does a given ROM need to be modified to work with every model of phone? If so, which ones presently work with the Atrix? Any? (It looks like the unlock was found very recently.) How does that process work exactly? Is there any way to ensure a recovery path if something were to go wrong, so that I don't brick my phone?
I'm just curious here. Presently, my phone is on the stock firmware without any upgrades at all, and I've simply rooted it and installed the webtop mod so I could play games on my TV. Other than that, it's been lots of Android Market for me. I'd like to branch out, and I don't even know where to begin.
There aren't any custom rom's for this yet, there's work being done, so it's just a matter of time. However, there is a developer build from Asia that can be flashed. There are a few issues with it, so if you are averse to troubleshooting or dealing with issues then just wait a few days.
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
schlupp88 said:
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Click to expand...
Click to collapse
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
_Dennis_ is right. You should sbf_flash -x to extract the UK firmware and use fastboot to flash just boot.img (CG56 in Froyo) and system.img (CG57 in Froyo). If you want to flash the radio, use a custom .sbf (for AT&T) with only the radio. We don't yet know whether you can replace your bootloader with a UK bootloader. We still flashed a signed bootloader to our phone. In the worst case, if you flash a UK signed bootloader and your boot ROM is looking to find an AT&T signature in your bootloader: BAD! It is fairly unclear that the unlock ALSO tells boot ROM not to care about signatures, it may very well still care. And the order of RSD: erase,write,verify is a little dangerous...
I as well, don't know much about this... but as far as I know, this will mean that developers will be able to create real operating systems for the phone and not have to wait for att/moto to do that...
in the past it was an OS from att/moto, and all the "roms" in xda were actually the same OS but with some skins and mods added to them...
Yes, if you look at the development forums for just about any other android phone, you will see full customized ROMs that can be installed. That's where we are headed.
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
I did a test with this.
I flashed 1.8.3 SBF over my unlocked bootloader to see if I could use moto-fastboot to flash over a 'stock' bootloader. It works to flash system (since it is still technically unlocked) but fails to flash boot.
So DO NOT TRY TO SBF FLASH A INTERNATIONAL VERSION unless you want to be stuck on the version with no way to get your phone back off.
I also would not flash the boot.img of a international version for the same reason.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
climo said:
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
Click to expand...
Click to collapse
I think that the backup will be found in a Clockwork folder on your sd card. I also think that when you do the backup you will get to choose the destination. Either sd or external sd.
I haven't used the bl unlock or the new ClockworkMod (Just waiting on a nice rom). But that is how it went for me on the previous CWM that didn't require the unlocked bootloader.
Maybe someone who has this newer stuff can shed a little more light on it.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
Does this essentially create an image of your device? Or does it just back up the firmware?
When CWM backs up ur files it creates a image file of
Boot.img
Cache.img
Data.img
recovery.img
system.img
so yes it does use a image.
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Viamonte said:
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Click to expand...
Click to collapse
+1.
ROMs will sometimes require you to have the custom kernel associated with them. CM7 for the Captivate comes to mind. With custom kernels, the Captivate was a beast. We had the VooDoo lagfix, which actually made the device usable on bootup. We were able to convert all partitions to ext4, and kind-of make the GPS work.
Overclocking is a possibility too. There's so much that is able to be done. It's a bit difficult coming from an iPhone where customization was limited, even with jailbreaking. But you'll soon get the hang of it.
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Viamonte said:
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Click to expand...
Click to collapse
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
JayRolla said:
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+2
It shouldn't take that long to lock on. Mine locks on instantly.
I'm interested of developing for this phone.
I have built roms from AOSP and ported roms before for my tablet so I do have pretty good knowledge of that part.
The things I'm worried about is if I brick it.
Lets say if I brick system partition can I easily flash a new one?
How about boot?
As I understand we are only able to flash the system partition right now?
Look into the Official ROM thread, there's a full flash available (for non-US Razrs). So as long as you can still boot up the phone into fastboot mode, you would be able to recover from whatever you screwed up.
If you softbrick it, you can easily flash the whole signed partitions via RSD Lite.
At the moment of writing, this is possible only on GSM RAZR as we've only got something for it.
Thanks both of you!
Then I will see if I can do some fun.
But we still suffers from not being able to flash a unsigned boot partition
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?
Just a heads up. I've got my RMP since today. As a usual nexus user as I was, the first thing was to unlock the bootloader and flash whatever I can. My destination was -> unlocked bootloader -> smiui with root.
What happened it the following:
1) I unlocked my bootloader following guides (unofficial way)
2) Installed TWRP
3) Flashed SMIUI
And welcome brick. I was in emergency port (9003), and the only way to get the device running was the disasembe way. Well it worked. Now I'm on 7.2.3 with root, but guys - watch what you are flashing. This is my 3rd device (Desire HD, Nexus 4, and now RMP), and this was the first time that I had such a headaches.
SMIUi contains the locked bootloader file, so if by any chance you decide to unlock it by the unofficial way - don't flash it.
Read...read....read and one more time read there are many threads explaining how to do it without getting bricked .
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
ktomov said:
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
Click to expand...
Click to collapse
Hello ktomov,
I made the same mistake. I couldn’t wait 10 days for the official unlock so I used the unofficially unlocked bootloader. Then I flashed TWRP and a Xiaomi EU ROM thinking that it’s probably gonna be OK since that’s not an official Xiaomi ROM. Nope! Bricked my device and had to use the testpoint method.
Now my question for you is what to do if want to flash a Xiaomi EU ROM again in case I don’t get the official unlock permission (is it even possible that I don’t get it?). Do I just need to replace the emmc_appsboot.mbn in the ROM’s ZIP file? I’m asking because there is a huge thread on this forum on how to maintain future OTA updates with unofficial unlock and I’d rather just stick with a TWRP-compatible ROM.
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Click to expand...
Click to collapse
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
Click to expand...
Click to collapse
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Filip013 said:
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
Click to expand...
Click to collapse
Don't replace it. Just delete it from the archive prior flashing.
ktomov said:
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Don't replace it. Just delete it from the archive prior flashing.
Click to expand...
Click to collapse
Roger that!
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
devtherockstar said:
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
Click to expand...
Click to collapse
unlocking bootloader does not void your warranty
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 ?