I tried to use the rooted 3.2.2 rom that was listed under development, but I could never get my wifi to connect. Now I am unable to get my 4G to work. I used to have the option to choose preferred network mode LTE/CDMA, but now that no longer shows. I am on 3.2.2 using build HLK42B.
I was wondering if someone who received their xoom back from the upgrade has the latest image I can try.
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium
I wish I knew.. I will have to research that.
Sent from my PG86100 using xda premium
I just posted an upload link over at http://forum.xda-developers.com/showpost.php?p=18204881&postcount=13
hammer4203 said:
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You need to flash the modded recovery, then in adb shell, run
mount /data
mkdir /data/media/Stock
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img
sync
Then reboot and pull the files, should be in a "Stock" folder on the internal storage.
*Thanks to solarnz for these instructions
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
4G LTE
I got my Xoom back some time ago. I've been waiting to root it until it came back. (Really didn't want to go through it, and have to undo it just to figure out how to do it again)
I'm trying to find the official file from Moto for the HLK42B build that came back on my 4G Xoom. I'm on the Moto Dev site, but they only have up through the 3G upgrade listed. Anybody know where I can get the official file in case anything goes wrong? I want to make sure I have it, before I start.
Thanks
Thanks Ace, it worked for me. It wasn't rooted because I imediately got and updated to HLK57D
AceXMachine said:
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
Click to expand...
Click to collapse
Thanks for the img files. They will save many headaches for a lot of people.
It is a damn shame that Motorola will not post the updated img files though...
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
zarkuu said:
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
Click to expand...
Click to collapse
This is my same exact problem. Can't seem to figure out the baseband problem.
I wonder if anyone has contacted Motorola regarding a way to flash the baseband to the LTE 4G version?
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
You can get the hlk75c which is rooted then take the hlk75d update and reroot using the universal root method. That will put you back.
Sent from my ADR6400L using xda premium
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
Oh, duh, it's so simple. I'll definitely be trying this when I get home from work today.
If it works - you will be my savior.
Scratch that - it didn't even reactivate my 3G.
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
I don't think that will work unless you open it up and physically remove the LTE modem. my understanding is once the LTE modem was installed the internal 3g modem is deactivated. Even if this did work it would deactivate your SIM card so you wouldn't be able to use LTE in the future without getting a new one. I had the idea to switch my currently useless Xoom data plan over to my old OG Droid and then wifi tether. I asked VZW about switching and found I *could* do this but going from a 4g device back to 3g would deactivate the SIM card and I won't be able to switch without getting a new one. Too much trouble in my opinion.
I spent about 2 hours in a Verizon store yesterday after 2 hours on the phone the previous night and eventually ended up with an RMA with Motorola. I'll be returning it to them and hopefully it will come back correct in about a week. Such a hassle when I could probably flash this myself if I had the right files but at this point I don't know what else to try.
Can you repost link please. I am trying to get this on a Mac running OSX and I cant seem to unzip the file. Any suggestions?! PLease HELP!!!
---------- Post added at 09:22 PM ---------- Previous post was at 09:09 PM ----------
how do you unzip HLK75Csystemboot.7z on Mac OSX??? Please Help!!!
download 7zip or use winrar
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
zone23 said:
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
Click to expand...
Click to collapse
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Jewremy said:
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Click to expand...
Click to collapse
It restores your device but it will not bring back 3G/4G. If it does please tell me how because I've flashed it a few times and it did not bring back 3G.
Actually in reading your post a few times you say it yourself that its a borked bootloader. Flashing HRI66 will not fix this. If it did we would be finished and we could close this thread.
Related
Before I begin, I'd like to say that I know we have posted this everywhere.
The reason of this thread is because there are no real clear instructions on how to un-root, and there is no actual thread, hence the reason we get this question asked so much; something I want to eliminate.
How to UNROOT your Mytouch 3G Slide
[Optional] If you are sending back your phone to Tmobile for replacement, make sure you flash the newest radio out as of now. (this at the moment is 7.09) [/Optional]
1) You will need to download "ESPRIMG(2).zip" from this thread (This is all you need, you dont need anything else)
http://forum.xda-developers.com/showthread.php?t=713507
2) Rename "ESPRIMG(2).zip" to: ESPRIMG.zip
3) Place the new renamed file ESPRIMG.zip in the root of you SD card (this means in no folder)
4) Power off your phone any way you like
5) Turn your phone on while HOLDING: VOLUME DOWN and POWER.
This will get you to a screen where you will need to wait for some loading. Let it load.
6) Once above step has finished, phone will give you some options. Hit VOLUME UP to confirm flash
7) It will take some time, and when it's done, you will be unrooted with the stock Espresso.
Credits go to: eugene373, xda-fourms, CaliBoyPhillip, and some guy I cant remember
reserved for future way to unroot
I posted the ESRIMG.zip in the q&a section a few days ago, nice catch on the radio. I totally forgot about that for warranty reasons. This thread should hit the New Bible!
Sent from my T-Mobile myTouch 3G Slide using XDA App
i did this to return my phone but after that i manually updated to the latest official ota that was 1.35. something
Just to be clear, this works even with a custom ROM? just flash esprimg and done? Seems to good to be true lol. Gotta do this to the wifes phone asap!
Sent from my SGH-I897 using XDA App
Need help!!! Recovery
I am looking for some help before I unroot. I fastboot flashed clockworkmod recovery version 2.5 and now when I enter Boolaoder and select recovery I am stuck at the splash. What should I do to get the factory recovery back or how can I get cw recovery to stick permanently??? Not to much of a noob either just a simple mistake..=)
beazie0885 said:
Just to be clear, this works even with a custom ROM? just flash esprimg and done? Seems to good to be true lol. Gotta do this to the wifes phone asap!
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes, its that easy!
lol
poor2rican1 said:
I am looking for some help before I unroot. I fastboot flashed clockworkmod recovery version 2.5 and now when I enter Boolaoder and select recovery I am stuck at the splash. What should I do to get the factory recovery back or how can I get cw recovery to stick permanently??? Not to much of a noob either just a simple mistake..=)
Click to expand...
Click to collapse
ask that in the Question and Answer forum of mytouch 3g slide.. im not too sure of what you're saying, and you'll get more answers there.
Hey Xologist,
Thanks for this post but I have a few things you might want to add on.
Your link to eugene373's ESPRIMG(2).zip works fine, but wouldn't auto update after a week. So instead of waiting to be updated I re-rooted and then un-rooted to 1.27.531.1 using the ESPRIMG that wegarner provided. After that I was able to do the manual OTA update without root.
wesgarner (1.27.531.1)
http://db.androidspin.com/androidspin_filedownload.asp?release=280&type=1
So after someone unroots they can just manually update(root not needed) to the current OTA via ChiefzReloaded's provided files.
-7.09.35.10 radio -1.35.531.1 build
www.4shared.com/file/dNFtt3IV/Nothing.html
https://docs.google.com/leaf?id=0B7...Y2Q0ZGUxZDJjMGIz&sort=name&layout=list&num=50
Same file with a mirror.However, the google one ended up working for me.
I am assuming this will result in a factory wipe/reset as well, correct? I'm considering switching back to stock from Cyanogen 6.1.1 since it's unable to send or receive MMS messages for me but I'm afraid I may lose the pending messages if I revert back and won't be able to recover or view them.
Pandaflux said:
I am assuming this will result in a factory wipe/reset as well, correct? I'm considering switching back to stock from Cyanogen 6.1.1 since it's unable to send or receive MMS messages for me but I'm afraid I may lose the pending messages if I revert back and won't be able to recover or view them.
Click to expand...
Click to collapse
Yeah it'll be a factory reset but you should still the messages as long as the phone hasn't actually grabbed them from the companies server. As for the actual issue, have you verified APN settings? I was having issues with MMS and data when I first flashed CM 7 and ended up switching to T-Mobiles alternate server to fix.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
DonJuan692006 said:
Yeah it'll be a factory reset but you should still the messages as long as the phone hasn't actually grabbed them from the companies server. As for the actual issue, have you verified APN settings? I was having issues with MMS and data when I first flashed CM 7 and ended up switching to T-Mobiles alternate server to fix.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
Thank you for confirming that this would wipe the device. I was also not aware that the MMS messages would still be retrievable if they have not yet been downloaded to the device (good to know!).
I see you have found my post on these forums in regards to my issue, so I will not get into the specifics in this topic, but yes, I have confirmed the APN settings several times now.
I've tried this, but I keep getting this error... "Main Version is older"
I need to unroot because I need to send my phone in for warranty service... my power button stopped working... makes it realy difficult to get into recovery mode or anything (impossible) but I can get into the boot loader
What can I do to remedy this?
Heck, if you could tell me how to corrupt the system folders I would do that so they couldn't tell it was rooted at all...
I've tried doing it this way and I extracted the file to the root of my SD card. But when I followed the steps, all it did was take me through like I was doing a reset of my phone. Didn't remove the actual ROM. Am I not supposed to extract it? What can I do to remove this ROM because I really don't like it on my phone.
you do not extract the zip file. you just put the ESPRIMG.zip file into your root folder. when you boot into recovery mode, the phone should automatically start searching for it (you might want to give it a little time to let everything load up). it will load (this will take a while) then press volume up to update when prompted. thanks to the OP for putting this up. you saved my butt, i have to return my phone for warranty replacement because the touchscreen and all the buttons stopped working.
Hey xologist, I'm sorry but I'm still very new to rooting. I've had some issues with the touchscreen and need to send my phone in for the warranty so I need to unroot it. What do you mean by flashing the newest radio? Where do I get it and how do I flash it?
slide 3g problem
dear friend
i have a problem on my touch 3g slide i have upgrade his firmware from 2.1 to 2.2 but now when i try to open my htc it give me enter sim lock code so if there is any way to free unlock it plz help me as soon as you can thkx in advance
tayseery said:
dear friend
i have a problem on my touch 3g slide i have upgrade his firmware from 2.1 to 2.2 but now when i try to open my htc it give me enter sim lock code so if there is any way to free unlock it plz help me as soon as you can thkx in advance
Click to expand...
Click to collapse
you probably placed a different sim card in your phone because this phone is normally locked to T-Mobile. if you're on T-Mobile and want to use a different sim card, give them a call and they will get you an unlock code for free. if you thought you bought the phone unlocked (not locked to a carrier, T-Mobile), then it's not, return it to the seller or something.
I tried the esprimg.zip on the root of the sd card but every time it tries to apply it it says it is the wrong image and aborts. Any ideas?
no matter what i do i cant get it to install anything, i install and apply the esprimg.zip file, re boot, and still loads CM i may have forgot how to do all this fancey root stuff, i have Cm 7.1, can i pleeeease get a dummy version to unroot
Hi all, in a pickle here. I will be attempting to remove root and am on CM 7.1 stable. My obstacle is my volume buttons don't work. I'm removing root for warranty/return reasons, is there any way to go back to stock other than from the bootloader(sp?)? Thanks, all!
(2/12/12)So I ended up flashing CR's 2.2 rooted rom so that I could upgrade through HTC Sync to the 2.2 stock update. Thanks anyway
Thought I'd share my experience in case it would help anyone.
Got a good deal on a new used US Cellular version tab. Hadn't come here yet to check things figuring all tabs would be the same.... wrong obviously.
First, because not everyone necessarily clearly mentions the difference between the GSM and CDMA versions, I almost went down the wrong path and tried to load a GSM rom. Caught that luckily in time. Rooting sucked as Kies would not, with 6 different computers and just as many different versions of Kies, recognize my device. Luckily I stumbled on the Z4root app which worked great.
All is good, but of course, no one mentions the us cellular version at all when it comes to roms. Studied up and noticed the model numbers and specs between us cellular version and verizon version matched. Great. Loaded beta clockwork mod for verizon, but only the stock recovery would come up when I tried to get into recovery.
Decided to load the voodoo kernal for cdma verizon. This is where it got ugly. Wouldn't convert partition to ext4 and just sat there. Took creators advice and booted into recovery. Suprisingly, it now went to the clockwork mod recovery, but nothing I did there helped, so I rebooted into recovery from clockwork mod recovery as per the instructions so I could do a data wipe and factory reset. Not all I had was a boot loop and it would no longer even go into recovery. Pretty sure I was screwed at this point. Only thing I had going for me was that I could still get into download mode. Got lucky and found the files necessary to go to bone stock verizon vie heimdall. Loaded them up and rebooted. A little hairy, but then I had a running system again. Since I knew I could always redo that, I decided to load the voodoo kernal again and this time it worked (maybe because my system was now basically verizon???).
Anyways, if anyone needs the files to go back to stock, I do have them and would be more than willing to share. I know one thing, if it wasn't for the wealth of information here I would have a bricked tab right now.
So I just bought a used US Cellular tab and wish I'd understood there would be issues.
I just rooted via z4Root as well and now don't know what to do. Were you able to flash any ROMs after getting into recovery? I'd imagine Verizon Roms might work?
I don't care about cellular data as I'm using it as wifi only.
Would you be kind enough to share the stock rom you mentioned? I've run into problems restoring my US Cellular GT. Thanks!
This is the exact same thing that happened to me as well except that I have a vzw tab.
I used sgs kernal to flash which went successful then tried to load a rom through cwm and got stuck in the boot screen.
I was able to go into download mode but had no idea how to use heimdall nor did I know what files I needed.
Luckly I bought through vzw 13 days ago so I just went in and exhanged it.
Wanna try again but would like to have the stock files needed to restore my tab in case I soft brick it again.
Can you please email me the files to [email protected]???
Yes please share the stock files
I would also like to request stock file as well. Thanks!!!!
I was flashing ROMs and had DLed a bunch from a site exclusively for RAZR M phones and some guy had put a bunch of stuff for the XT910 and I accidentally flashed a AOKP GSM zip and now I can't flash anything or RSDLite back to stock, which was always my failsafe out of a soft brick. I still have TWRP and I was able to restore my backup but boot and system files only, data wouldn't restore. Now my phone will boot to the custom splash screen but it just loops. And I first get the red Moto M circle and do NOT get the unlocked boot loader warning. So any help? I will post the RSDLite results when I get home.
ok heres the site I got the file from, this guy should be hung...surdu_petru...http://www.androidfilehost.com/?w=developers&did=70
noone? help is needed please! OK well I restored to a TWRP recovery i had and it worked partially, as long as i unchecked the data partition, the boot and system partitions stuck, so now my unlocked bootloader warning is back as is my custom ROM splash screen, but in a bootloop. I tried RSDLite flashing it again and the 4.1.1 firmware seemed to work but still loops. 4.1.2 and 4.0.4 wont flash because of the "get var, OEM" issue. I had this happen once before aswhile back but was using CWM recovery and juyst switched to TWRP, which fixed it, but not so lucky this time around. So I am wondering if i flash some other partitions like the persist forthe radio, esp since i flashed a xt910 GSM file which is why my phone now thinks its a xt910. Any ideas? please!!!
ok PROBLEM SOLVED. aFTER LOSING THE CUSTOM RECOVERY BY TRYING TO FASTBOOT WITH RSDLITE I DID THE "delete the Getvar and OEM LINES FROM THE FACTORY FIRMWARE OF 4.1.2 (THE .78 VERSION) AND SINCE THE xt910 ROM WAS 4.2.2 AND MY RADIO HAD PREVIOUSLY BEEN UPDATED TO .78, I FIGURED THE .78 4.1.2 WOULD BE MY BEST SHOT, AND SO IT WAS. THAT "GETVAR" ISSUE IS DEFINATE PROBLEM THAT SHOULD BE RESOLVED ANYWAY. wELL ANOTHER TRAGEDY AVERTED, AND IM GETTING PRETTY GOOD AT THIS, LOL, AVOIDING MISTAKES WOULD BE BEST THO. sO BEWARE OF THE "ANDROIDFILEHOST" SITE, THEY HAVE A GUY POSTING XT910 ROMS UNDER XT907 FOLDER! almost cost me a phone Close this thread
Edit does not work on either of my razr m phones
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Here is my Feedback for you...
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The phones will accept the edit and will work on GSM if you unlock with RadioComm. He ran into issues because he didn't unlock with RadioComm.
Sent from my Droid RAZR MAXX HD using xda app-developers app
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
Sorry but they both unlocked. The issue was (I think) that I was typing "01" but only needed to actually type "1" and then the window shows "01". It was something like that anyway.
soft bricked now
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
rocketrazr99 said:
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
Click to expand...
Click to collapse
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
RikRong said:
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
Click to expand...
Click to collapse
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
rocketrazr99 said:
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
Click to expand...
Click to collapse
OK, Rik was right, I didnt have to wait for a new firmware release. I kept trying to flash the most recent version of 4.1.2 and kept hitting a wall at 17/21, which is the flashing of the system image. Occasionally it would fail before that at 16/21, which is CDROM files. That always happened the first attempt after I unhooked the phone and restarted everything, so I started thinking, what is causing the flash to fail for no apparent reason. Then it finally hit me....it was as if my phone was running out of storage space. But that just isnt possible when you are flashing with RSDLite since it wipes out everything first. So I then remembered that my PC has very little room left on its hard drive. Could it be that RSDLite needed more space to work? Hmmmmm, so I deleted a few videos and moved the firmware file to that area (it may or may not help) of the drive and tried again. After the initial fail at 16/21 I was met with a successful flash, although it took a very long time to flash the system image, which I attribute to low disk space. So there you have it.... of course I had to modify the XML file and remove the "getvar" line, and realized I had forgot a golden rule.... all programs and apps need a certain amount of disk drive space in order to operate, and RSDLite is no exception! So now my locked phone will get the carrier unlock edit and Safestrap installed with an extra ROM in slot 1, then it goes on eBay, lol. I have my other RAZR M in semi retirement, it has the BL unlocked as well as the carrier, but I couldnt pass up a new Nexus 5 for $250, but I will surely be swapping the SIM card back and forth because I really miss my RAZR M already. Wish they would make a RAZR M with the processing power of the Nexus 5. Anyhow, PLEASE CLOSE THIS THREAD, TY.
Use this I used it when I bricked mine
Sent from my XT907 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using Tapatalk
I'm having a similar problem with my xt907. The phone will boot and loop on the boot loader. I have tried to restore with rsd lite bit haven't had any luck. Any suggestions, I know it may not be enough information. If you ask I might be able to give you more details.
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
Also I can't get into recovery.
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
I am sorry to say that you are uninformed and the XT907 CAN have van NV edit which allows it to be used on GSM networks. The phone is already setup to be comparable with GSN since Verizon made it a "global" handset, but....they also blocked any GSM capabilities in the U.S., until of course you do the NV edit. So please remove your post.
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
Also to anyone who actually uses AVG the pro version is free on amazon appstore today only.
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
If I had to bet I'd say you'll get the USA notifications but we will find out on next update.
famewolf said:
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
...
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
Click to expand...
Click to collapse
Totally correct on the TWRP thing, though I prefer it to stock recovery, and updates work just fine with TWRP as well.
As for the not wiping - again, correct, I just come from the 'do a total wipe' school of flashing things, to avoid any possible weirdness
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
Click to expand...
Click to collapse
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.
Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Click to expand...
Click to collapse
I mean that when the next update comes out, if I can't use the OTA update, I'll wait for someone to upload it here, and then I'll manually apply it. If you follow the directions in my post, you'll be totally up-to-date as of August 15th, 2015 - I'm referring to the next update, whenever that may be.
Thanks for the guide!
Was able to update my Canadian idol 3 without installing twrp
Just fastbooted into it and did a backup of my old CDN setup and restored with the file above the whole update process took about 15min
If **** hits the fan I can still restore back to the original CDN ROM with twrp and my backup.
Dt2w works every time now and chrome scrolling is vastly improved definately worth updating. I may flash back to Canadian system image when they finally release it
To anyone on stock Canadian firmware please post once an OTA is available (and what carrier you are on)
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
jpfk said:
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
Click to expand...
Click to collapse
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
famewolf said:
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
Click to expand...
Click to collapse
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
jpfk said:
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
Click to expand...
Click to collapse
you probably tried this but... check that the APN didn't get changed/reset from when lte was working.
That was actually the problem, i did not realize it was a different APN for LTE so it looked normal when I first checked. Thank you very much
Has anyone gotten the Canadian stagefright update pushed to their phone yet?
doesn't work for me!
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!
Click to expand...
Click to collapse
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread
Click to expand...
Click to collapse
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
punkal said:
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
Click to expand...
Click to collapse
Step 1) Make a backup on the device so it creates the directory path you need.
Step 2) Take the time datestamp folder from the backup you have and put it in the folder that has the other time datestamp folders. It's not a complicated process. Installing the "root" from the zip file does you no good because the time datestamp folders need to be under a folder with your device id (ie what shows up when you do adb devices).
While the restore process IS the same your questions should be asked in the system image thread if you don't have a 6045i.
According to @petrov.0 it's better for you to install the official 10 06 update (or his modified one in the system image thread) as it updates files in SEVERAL partitions other than system and boot. Again discussion needs to be there.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
purple.epod said:
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
Click to expand...
Click to collapse
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
famewolf said:
Step 1) Make a backup on the device so it creates the directory path you need.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
Click to expand...
Click to collapse
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
punkal said:
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
Click to expand...
Click to collapse
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
famewolf said:
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
Click to expand...
Click to collapse
Really sorry!
i've been taken by terror and panic.!
Is this do-able with out unlock.bin??
I've tried using adb/fastboot. ADB reports the device OK; fastboot can't see the device.
I've tried all manner of drivers to load........ I know there are separate drivers for adb and fastboot.
This is driving me nuts.
Finally, are there different SUB-variants of the 996?? One generic and one US Sprint??
Thanks
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
ROMSG said:
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
Click to expand...
Click to collapse
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Graf_Eberstein said:
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Click to expand...
Click to collapse
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. I did some fairly general "looking" for that ROM elsewhere, found a couple of articles when Google-searching, but haven't had a chance to check those out (that will have to wait until tomorrow). If it turns out that there is no alternate link to the ROM, are there any other ways of getting it, short of looping @Tilde88 in?
Graf_Eberstein said:
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. Since I haven't gotten past the first post yet, I'm going to see if I can find that elsewhere and report back.
Click to expand...
Click to collapse
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Darnrain1 said:
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Click to expand...
Click to collapse
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Graf_Eberstein said:
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Click to expand...
Click to collapse
Your welcome,
Stock Oreo Rom, flash in order But there are a lot more roms for the Lgv20 you can look around if you want.
LG V20 ROMs, Kernels, Recoveries, & Other Developm
US996 DIrtysanta Rom
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Graf_Eberstein said:
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Click to expand...
Click to collapse
Your phone is rooted great.
DUMP backup with LGUP. Might not be to late. Just hold vol up and plug in usb to phone and computer. Go into LGUP and choose DUMP all files. You don't need to dump system or cache. This will save all the files on your computer. Back the files up like google drive or something.
Take battery out and put back in. Then you want to boot into twrp and do a format.
Then your ready to install an OS on your phone. Why don't you check out my rom I made it's stock Oreo debloated. There are some good guides on there also you can follow. link
If you need any more help just ask. I don't mind.
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Graf_Eberstein said:
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Click to expand...
Click to collapse
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Darnrain1 said:
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Click to expand...
Click to collapse
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Graf_Eberstein said:
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Click to expand...
Click to collapse
Not a problem. Because I only have an H910 I didn't get all the bloatware on other lgv20 phones. But that Mobile Services Manager is a huge bloatware that installs more bloatware. So I thought I would try and find it and remove it in the latest version. You can update Auto_Debloat and it should get rid of that Mobile Services Manager for you. All you have to do is just flash the new version in twrp and reboot.