Related
Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
LOBBS said:
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
utesred said:
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
Click to expand...
Click to collapse
I'm loving the G2 so far. It was my back-up choice in case there was something I really didn't like about the M8 so I'm not exactly suffering here. My ultimate goal is to get on an AOSP ROM so I really just need to get back to JB so that I can get root and recovery.
Sent from my LG-D801 using XDA Premium 4 mobile app
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
Click to expand...
Click to collapse
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
Click to expand...
Click to collapse
Damn, that's a bummer! I'm assuming that it's failing while flashing the .kdz, right?
Sorry I can't be of much help on this one. Only thing I could suggest is to try it again. Maybe something went wrong? Make sure you've got the correct files and everything. You probably already know all of that, though.
I hope it works for you the second time around...or at least, the IORoot gets updated to work with our devices soon.
Yeah something has changed since my flash to stock kitkat. When I attempt to boot into recovery it isn't there (that's why ioroot25 won't work) but anyways. I think for one reason or another I am stuck...But that being said I work 12 hour night shifts and its my last night off with nothing to do.. So will attempt this again in a few different scenarios.
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
I used the 'C' .kdz file.
The 'G' one is another update. It is still 4.2.2, I believe.
Use d80110c
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
missiveusa said:
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
Click to expand...
Click to collapse
I may be wrong, but I don't think that the screen artifacts are caused by the D80110G. Using the same process, I went to the 80110C and tried flashing various roms afterwards. I got the artifacts on every other rom, except for the KK stock rom I used above.
From what I've seen and read from other users with the artifacts, they appear only on KK roms, with certain TMobile G2s. It seems that all phones that came with 80110G or 80110A preinstalled have issues.
Of course...I could be completely mistaken. That's just what I've noticed.
Give it time, root will happen for KitKat on T-Mobile.
I hope so, I spent all day yesterday trying until I just gave up. Guess its the waiting game for me.
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
2strokenut said:
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
Click to expand...
Click to collapse
Can you please direct me toward a tutorial that has the TOT method? I tried to find one online but was not able to. I have a D801. The KDZ method doesn't work for me.
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
The biggest issue I have had in this whole downgrade, root, twrp, flash, is loosing twrp. I have tried multiple ways, but every single time I upgrade to 4.4.2 I lose custom recovery.
I even flashed twrp 2.7.0.0 over 2.3.6.2, but I have had no luck.
I have yet to try Flashify, but that will be my next move. I am Loki'd out lol
Help
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
utesred said:
Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Click to expand...
Click to collapse
The problem I think I am having, is in the Flashing TWRP guide, the t-mobile version, even though it states ver 2.6.3.3, its actually 2.6.3.2. I can not get TWRP to stick for the life of me.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
tpaxadpom said:
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
Click to expand...
Click to collapse
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
frigginmike said:
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
Click to expand...
Click to collapse
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo played in the infinite loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
tpaxadpom said:
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo playe in the infinity loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
Click to expand...
Click to collapse
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
frigginmike said:
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
Click to expand...
Click to collapse
So I've looked on the related thread post 2901 (not 2902 as it says in OP), the reset is required. I've tried your method to reset and also one mentioned here but the phone continues to stay in the boot loop. This LG G2 is a PITA to get rooted.
Never mind. You are right. I've tried again your method and it worked. Performing reset now...
Hi All….received the 4.4.2 download this morning on my RMHD and ran through the install. At reboot the phone got stuck on the Red Moto logo… I let it sit for nearly 45 minutes, assuming it was doing its thing in the background. But at that point I figured it was safe to assume something got hosed. I rebooted back into recovery and did a factory reset. That wound up making things worse…now am in a boot loop between the logo and the Android triage guy (recovery)….
Phone was rooted and locked. And I am complete understanding that I was losing root with this OTA. Been reading all posts in here….please ‘flog’ me if I missed something.
With that said…I have two questions on recovering the device.
1) Can I simply download and copy one of the JB images from the Motorola Firmware site to my SD card and install via recovery (since my recovery appears to be OK)?
2) Or should I/need I follow procedures using RSDLite? And recover this way?
Any comments are appreciated!
Thanks
Doug
Never mind. iBolski's thread "Official KK OTA for 9.30.1 (XT926) users - please read" in the general forum looks like it might do the trick for me...and I won't be able to go to a previous (JB) Android version. This looks easy enough.
I have the same issue except I'm in need of a .zip or set of files for the modem firmware that I need to flash in 4.4.2 183.x.x Stock because I tried to downgrade to 9.30.1 jb and the firmware and the modem downgraded. Could someone create a package I can flash in stock recovery to restore my Droid Razr Maxx HD to to 4.4.2 183.x.x
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
yahboyvictorr said:
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
Click to expand...
Click to collapse
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Jkay7 said:
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Click to expand...
Click to collapse
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
yahboyvictorr said:
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
Click to expand...
Click to collapse
Yes it is definitely a reason. Follow the steps from the guide I linked you step by step, it works 100%
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk