I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!
Related
I flashed a T-Mobile Kit Kat 20g based rom on my D800 and got a lot of problems and can`t flash back to stock AT&T Kit Kat rom.The problems I`m having with the Kit Kat rom is no Play Store,no internet, and brightness don`t work.I tried tots method and that don`t work.It appears that my D800 is now a D801 with no way to return.If anybody got a fix let me know.
Also I have to reboot several times to get the usb to work to transfer files.
AtrixHDMan said:
I flashed a T-Mobile Kit Kat 20g based rom on my D800 and got a lot of problems and can`t flash back to stock AT&T Kit Kat rom.The problems I`m having with the Kit Kat rom is no Play Store,no internet, and brightness don`t work.I tried tots method and that don`t work.It appears that my D800 is now a D801 with no way to return.If anybody got a fix let me know.
Also I have to reboot several times to get the usb to work to transfer files.
Click to expand...
Click to collapse
Sounds like a mess. Have you tried this method? http://forum.xda-developers.com/showthread.php?t=2663369 If not read the whole first post and at the bottom of it there is a custom DLL you'll need instead of the DLL that comes packed with the tool. Good luck!
Really now said:
Sounds like a mess. Have you tried this method? http://forum.xda-developers.com/showthread.php?t=2663369 If not read the whole first post and at the bottom of it there is a custom DLL you'll need instead of the DLL that comes packed with the tool. Good luck!
Click to expand...
Click to collapse
I all ready tried keeps failing.My device has been converted to a D801.Also my IMEI is null and service is disabled.I can install any T-Mobile stock ROM and even ota if no custom recovery is installed but network services.
Really now said:
Sounds like a mess. Have you tried this method? http://forum.xda-developers.com/showthread.php?t=2663369 If not read the whole first post and at the bottom of it there is a custom DLL you'll need instead of the DLL that comes packed with the tool. Good luck!
Click to expand...
Click to collapse
I found a way to fix my AT&T G2 from thinking it is a T-Mobile D801 bad flash.
AtrixHDMan said:
I found a way to fix my AT&T G2 from thinking it is a T-Mobile D801 bad flash.
Click to expand...
Click to collapse
Good for you! Do you mind sharing for the record and the next person that may face the same issue? I'll bet that's a load off of your mind! :good:
Really now said:
Good for you! Do you mind sharing for the record and the next person that may face the same issue? I'll bet that's a load off of your mind! :good:
Click to expand...
Click to collapse
First make sure your rooted with twrp.Basically what I did was flashed a already stock rooted AT&T rom in twrp which I knew would brick it.That will turn it back to the correct stock ROM which in this case D800 even though the device is brick.Next get out of recovery and get the device in download mode.Then I flashed stock AT&T Kit Kat rom using tot method and the no check DLL file.May work with AT&T DLL.Didn't test.Flash it,should be successful.I will assume this method will work for others on different devices if flashed wrong rom,didn't make a backup,or however they ended up changing the device because of flashing wrong ROM.
AtrixHDMan said:
First make sure your rooted with twrp.Basically what I did was flashed a already stock rooted AT&T rom in twrp which I knew would brick it.That will turn it back to the correct stock ROM which in this case D800 even though the device is brick.Next get out of recovery and get the device in download mode.Then I flashed stock AT&T Kit Kat rom using tot method and the no check DLL file.May work with AT&T DLL.Didn't test.Flash it,should be successful.I will assume this method will work for others on different devices if flashed wrong rom,didn't make a backup,or however they ended up changing the device because of flashing wrong ROM.
Click to expand...
Click to collapse
Good for you, I'm glad that you straightened it out. :good: One last thing, you should edit the title of the thread and insert "Problem solved" or something like that. Have a good one!
Really now said:
Good for you, I'm glad that you straightened it out. :good: One last thing, you should edit the title of the thread and insert "Problem solved" or something like that. Have a good one!
Click to expand...
Click to collapse
I see when I get back on my computer.Thanks.
During debloat on Boost 6.0.1 error 1003 on reboot. Cannot mount sd in recovery mode. When using the 6.0 untouched i get an error after 50%+ when trying to sideload. AIl so it goes on to display dialog in the phone describing basically its can update becouse ther untouched zip is going from 5.1.1 to 6.0 so id imagine i need a 6.0.1 ota update or recovery in hopes of unsoftbricking the device. Anyone got any way of possibly downgrading if the 6.0.1 wont work? A guy in the the dev forum said he was able to overflash but i cannot post in there yet. Help plz i dont like paperweights.
There really isn't a solution for you other than sending it to LG to get unbricked. Right now there is no way of circumventing LAF which is the program that keeps us from writing anything to any partition. I'm assuming that there was an update or change in zv7 that did this as zv4 & 5 both had the ability. Basically the device is checking the system partition and taking note that there have been changes made that we're not supposed to have been. As of right now there isn't anything we can do because we haven't been able to unlock the bootloader. Also, so far the Boost website says zv7 was the 6.0 upgrade and I haven't seen a 6.0.1 ota update and Boost hasn't made any mention of it on their website. When I get my new one tommorrow I'll double check the version but so far I haven't heard of a 6.0.1 ota.
dip_spit said:
There really isn't a solution for you other than sending it to LG to get unbricked. Right now there is no way of circumventing LAF which is the program that keeps us from writing anything to any partition. I'm assuming that there was an update or change in zv7 that did this as zv4 & 5 both had the ability. Basically the device is checking the system partition and taking note that there have been changes made that we're not supposed to have been. As of right now there isn't anything we can do because we haven't been able to unlock the bootloader. Also, so far the Boost website says zv7 was the 6.0 upgrade and I haven't seen a 6.0.1 ota update and Boost hasn't made any mention of it on their website. When I get my new one tommorrow I'll double check the version but so far I haven't heard of a 6.0.1 ota.
Click to expand...
Click to collapse
I have the same problem as the OP. Is it a big deal to send it into LG? What do they say about the 1003 err?
Thank you
Drzaius70 said:
I have the same problem as the OP. Is it a big deal to send it into LG? What do they say about the 1003 err?
Thank you
Click to expand...
Click to collapse
Nah. They don't say anything about it. A bunch of people have sent 'em in. I'm sure they shake their heads though when they power on the phones after taking them out of the box though.
dip_spit said:
Nah. They don't say anything about it. A bunch of people have sent 'em in. I'm sure they shake their heads though when they power on the phones after taking them out of the box though.
Click to expand...
Click to collapse
Cool thanx for the reply. I will send it out tomorrow. How long was the turn around and any tricks or tips?
Drzaius70 said:
Cool thanx for the reply. I will send it out tomorrow. How long was the turn around and any tricks or tips?
Click to expand...
Click to collapse
I think someone said ten days, not really sure. I work for AT&T and usually if someone has to send something to LG that we can't deal with it takes three weeks max.
Search the forum for the 5.1 KDZ and flash it with LG Flash Tool 2014. It will be repaired, although you will loose everything not backed up.
notnola said:
Search the forum for the 5.1 KDZ and flash it with LG Flash Tool 2014. It will be repaired, although you will loose everything not backed up.
Click to expand...
Click to collapse
There is no kdz for the boost mobile stylo.
Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".
Thanks, I was looking for this.
RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!
SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?
SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060
Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.
SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:
edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha
SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.
it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..
khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..
khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude
NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.
najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how
NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.
I had 10ulm and flashed it with the G710AWM and now every time I boot my phone i get:
WARNING: Current version is not available for user. Can't find matched carrier. Check NT-code: FFFFFF : 84
The phone works fine since it was unlocked, but I am getting a ton of calls go straight to voicemail and this may be the issue? How can I fix this?
any help appreciated. Thanks
also wifi calling is nowhere to be found under call settings. It seems like I don't have the setting on this version? thoughts
Don't bother pal, stick with the official rom, I had this same issue best option is to just stick with the same variant as your phone, might not be latest but it works good. FYI I have g710emw and was using g710em rom
rash.m2k said:
Don't bother pal, stick with the official rom, I had this same issue best option is to just stick with the same variant as your phone, might not be latest but it works good. FYI I have g710emw and was using g710em rom
Click to expand...
Click to collapse
You are probably right. What a pain to have to flash again and go back?
How are you guys backing up so that you just restore to the same phone you had without having to set up everything again?
Brighter85 said:
You are probably right. What a pain to have to flash again and go back?
How are you guys backing up so that you just restore to the same phone you had without having to set up everything again?
Click to expand...
Click to collapse
I didn't restore, I tried out the rom first, and then just wiped it. What broke it for me was the wifi mac address somehow became lost while using it, maybe some software glitch only by flashing the same variant was I able to restore it.
Best to root and then backup and restore
Brighter85 said:
I had 10ulm and flashed it with the G710AWM and now every time I boot my phone i get:
WARNING: Current version is not available for user. Can't find matched carrier. Check NT-code: FFFFFF : 84
The phone works fine since it was unlocked, but I am getting a ton of calls go straight to voicemail and this may be the issue? How can I fix this?
any help appreciated. Thanks
Click to expand...
Click to collapse
Just reinstall the kdz with refurbish option
dapolicy said:
Just reinstall the kdz with refurbish option
Click to expand...
Click to collapse
Hey there, how do you do this KDZ with refurbish option? Will this mean flashing again anyways?
I was hoping that by now the official android 10 version from LG would be out for the unlocked 10ulm, but it seems that they will never update this phone for some reason. This was the Google Fi unlocked G7.
Suggestions please. Thanks
Brighter85 said:
Hey there, how do you do this KDZ with refurbish option? Will this mean flashing again anyways?
I was hoping that by now the official android 10 version from LG would be out for the unlocked 10ulm, but it seems that they will never update this phone for some reason. This was the Google Fi unlocked G7.
Suggestions please. Thanks
Click to expand...
Click to collapse
It means flashing the phone again but select refurbish option in lgup
dapolicy said:
It means flashing the phone again but select refurbish option in lgup
Click to expand...
Click to collapse
Thanks for replying.
I noticed you are the leader of the other thread I posted, so I will ask here so not to bug you too much
Will the choosing of refurbish option erase the serial or IMEI or anything else that I should be aware of?
Also, when you say flash again you mean using the canadian version correct? I was wondering about the Korean version vs the canadian and what advantage would there be in any.
If you could, please lead me to the instructions to flash again. When I did it, I used a guide from some dude on youtube and I can't find that again.
Also, read somewhere that the error at boot could be fixed by rooting and then changing something with the explorer app. Not sure if that is worth it. I just hate backing up and restoring to find I am logged out of most every app and all settings have to be set up again. It takes me hrs and I am not that technically savvy as you guys.
Thanks for your time and have a good evening.
Brighter85 said:
Thanks for replying.
I noticed you are the leader of the other thread I posted, so I will ask here so not to bug you too much
Will the choosing of refurbish option erase the serial or IMEI or anything else that I should be aware of?
Also, when you say flash again you mean using the canadian version correct? I was wondering about the Korean version vs the canadian and what advantage would there be in any.
If you could, please lead me to the instructions to flash again. When I did it, I used a guide from some dude on youtube and I can't find that again.
Also, read somewhere that the error at boot could be fixed by rooting and then changing something with the explorer app. Not sure if that is worth it. I just hate backing up and restoring to find I am logged out of most every app and all settings have to be set up again. It takes me hrs and I am not that technically savvy as you guys.
Thanks for your time and have a good evening.
Click to expand...
Click to collapse
Flash with the kdz you used before, Canadian firmware is better than Korean. In lgup select refurbish instead of partition dl. It won't tamper with your IMEI and you will loose all your data
Hi dapolicy,
I am done with the LG G7ULM since it will never be updated officially.
I really like having the fingerprint sensor on the back and it seems that the LG G8 is the last iteration of phones from LG with this feature and it is an upgrade from the G7.
It is cheap here in the US.
Which version of this phone should I look for? I will be using it on Mint Mobile, so an unlocked one sounds great and all, but then you see what happened to the G7 ULM that never got android 10 unless it was tied to a carrier.
So, what do you suggest I do so I can get the next couple of updates for android with the G8?
Thanks man!
dapolicy said:
Just reinstall the kdz with refurbish option
Click to expand...
Click to collapse
I get the sime problem with my LG WING and I don't know to solve it
Daoud ben said:
I get the sime problem with my LG WING and I don't know to solve it
Click to expand...
Click to collapse
If the firehose was available for the Wing/Velvet you can hex the FTM and fix the NT Code on the Wing.You can try the engineering service menu,but I highly doubt the IMPL is 0 under MID.