Database Users

4.3 cm-10.2

Has anyone tried the 4.3 cm10.2 ROMs found over here (http://androidhosting.org/Devs/Dhacker29/cm-10.2/)? I was going to give it a go last night but for some reason my device got stuck on the "warning your boot loader is unlocked" screen and had to use Matt's utility to give it life... I may give it a try tonight when I'm not expecting any calls...
Sent from my XT907 using xda app-developers app

Yeah, I'm running the latest version of it now. I had the same problem. What worked for me was the following:
1. Wipe everything - system, data and both types of cache.
2. Install CM 10.2 and NOTHING else. Boot the ROM. It should go through now.
3. Once you get to the main screen, reboot into recovery.
4. Install the 4.3 GAPPS version. Reboot, get to the main screen and reboot into recovery.
5. Now flash the 4.3 version of Supersu for CM 10.2
6. Boot one last time into CM 10.2
All the links for everything you need can be found with a Google search. Later I may edit this post to include those links.
Sent from my XT907 using Tapatalk 4

Thank you kindly for the reply... I got it booting finally but couldn't get su permission on TiB and what not... I didn't know about needing the 4.3 su ...I'll flash that now... again thank you kindly
Sent from my XT907 using xda app-developers app

TWRP isn't supported either from what I understand. You need to run CWM.

Any time I install 4.3, it won't reboot. It starts up initially, but I can't get it to get past the Motorola logo upon second boot.
I have tried the normal install method and this method.
Then recovery doesn't see the /data folder so something is wrong with the 4.3 install I presume.
Does it change the location of data?

Yeah I Tried It But It Had No Sound So I Changed Over To 4.2.2 AOKP.

grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I was using CWM on my first attempt... this time around I switched to TWRP...
Sent from my XT907 using xda app-developers app

grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I use TWRP, works ok. Got sound, data, everything working fine. Battery life sucks, but no surprise there.

My 2c
I'm running it right now. I must have missed the part about flashing SuperSu, because I can't do anything as root. I had trouble the first time I flashed with the phone bootlooping, but I flashed again and that fixed it. Battery life is somewhat poor, but I just found the performance page today (Icon was different, silly me!) so we'll see how it goes with a different governor. I've been having issues with Navigation and Bluetooth audio on anything except stock. Bluetooth audio locks the phone and I have to soft-reset it. Navigation crashes if you try to multi-task while using it.

HOW TO Install CM 10.2 (Android 4.3) for Razr M (xt907)

I am running CM 10.2 by Skrilax - http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907 (Might be fine with the DHacker version also, but this is what I used.
Pretty much everything seems to work including GPS. I do not have Bluetooth anything so I can't speak to that. Some (maybe most) people seem to have difficulty getting it installed, but it can be done. There are a few tricks to it. Here's what worked for me:
I highly recommend using TWRP 2.6.0 as that's what I use and I know it works. Not sure whether other recoveries will function the same or not.
What you need:
1. The most recent version of CM 10.2 from the link above.
2. Gapps Core 4.3 - http://goo.im/devs/BaNkS/GApps 4.3
3. Root for 4.3 - http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
1. Erase everything except the external sdcard. Do it three times. (Don't ask, just do it.)
2. Also Format Data - what the heck, do that 3 times too.
3. Install the CM 10.2 ROM, wipe dalvik and cache again and reboot into the system. DO NOT install anything else at this time for best results.
4. Let the OS boot all the way to the desktop.
5. Unlock the developer options by going into Settings\About Phone and tapping 8 times on Build number. (Only needs done one time, updates do not hide it again.)
6. In Developer options, change Root Access to "Apps and ADB". (Go ahead and set up whatever else you want in Settings.Do not install any apps or updates at this time.)
7. Reboot into Recovery. Install Gapps Core 4.3
8. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
9. Once the phone boots all the way, reboot into Recovery again and install Root using Supersu 1.43.
10. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
11. Once System has booted, you can update SuperSu in the Google Play Store. The first time you open it, it will want to update the binary. It's very important that you choose the option to do it from Recovery. Your phone will reboot into Recovery, update the binary and then boot back into System.
12. Once all this is done, so are you. Restore your apps, allow Google Play to do any updates, and customize the layout to your tastes.
Note: Once you get a successfully installed 10.2 setup, you can dirty flash the nightlies. Always clear dalvik and cache. And always backup your apps before flashing anything if you want to make your life easier.
ENJOY!!!

Going to give it a go with CWM I'll let you know how it goes.

Well I got the rom to work but I could not get it to boot after loading gapps. I tried wiping data but no joy!

Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip

Flashed TWRP and I was able to get it up and running having the same issue with root going to try the file above and I'll update again.
edit
*** the supersu 1.51 file worked for me as well. ***
---------- Post added at 04:43 PM ---------- Previous post was at 03:47 PM ----------
I'm still having issues. I got the root to work but everytime I reboot the device I have wipe data or it hangs on the boot logo.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
Restored back to carbon rom 1.8. I may try again after a few more dailies are out. As this is my primary device I can not have the issues I saw. Admittedly it may be something that I did wrong and not the rom.
Sent from my XT907 using xda premium

Got this up and running last night and no issues so far for me. I'm wondering though if any custom kernels work with 10.2? I was curious about the vanquishpuppiesn12 kernel.

kensdavid said:
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Click to expand...
Click to collapse
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4

Thanks for sharing , make a mark

netizenmt said:
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
can you confirm if rear mic is working when taking videos? this has been the only hangup for me on the 4.2.2 ROMs...
I doubt it, since that functionality is probably kernel related, but still just curious...
thanks!

Ok I noticed that I had somehow installed the wrong TWRP I installed 2.6.0 today and I have so far had good luck phone is up and running and seems to be stable. At first I had some issues with a few apps throwing errors during the mass install when I sync'ed with Google but a manual download after and they installed just fine. Also the new camera app called focal has some issues for me it opened and took pics but images in gallery are blank. However the stock camera app seems to working fine at least for stills I have not tried video yet.

I've got this all working too, including root. But I've been noticing about a second delay when pressing power to unlock the phone. Sometimes it delays so long that I press power again. So when the phone does wake up, the screen goes off again from my double press of impatience. I'm running the 0907 nighlty
Sent from my XT907 using XDA Premium 4 mobile app

FWIW, never needed to wipe data multiple times and I flashed everything at once. That said, still a good procedure to follow
Also, @georgeascott, that's a known bug. It tends to SOD on occasion... Not much to do to fix except maybe overclocking
Sent from my XT907 using Tapatalk 4

Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app

zombolt said:
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4

sloosecannon said:
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I have no clue how to do those things. I got really spoiled on the dinc. So many people spoon feeding contributions to a fabulous device. It sure is a shame it's impossible to unlock my boot loader
Sent from my XT907 using xda app-developers app

everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.

netizenmt,
Thx a lot for your help. I`m now on cm10.2, too.
But there seemed to be some bugs.
1.I cannot install any apps from Google Play Store, or it hangs on the MOTO logo after reboot.
2.I can take calls, but cannot reach the 3G network.
P.S.When I try to use QPST to configure the phone, the QPST tells Serious error encountered, write to phone aborted.

I've installed CM10.2 two weeks ago and everything is working great! The first time I flashed it I got stuck at the CM boot animation... After ten minutes spent watching it I forced it to reboot: stuck again. At this point I booted back to recovery, followed thoroughly netizenmt instructions (wipe three times, really!!!), installed CM10.2, Installed gapps, installed supersu v1.43 and so on (follow all the steps netizenmt told us!)... Everithing worked fine then. At this point I changed build.props to make the phone works in GSM mode.

fargles said:
everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
Click to expand...
Click to collapse
If you go to settings/developer options and scroll down to HW overlays. Check the box to disable HW overlays. That should help with the tearing/chopping.

Also, maps FC all over the place as soon as you're using GPS.
Sent from my XT907 using xda app-developers app

[Q] UI Stops Working EVERY DAY!!!

No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???

System UI errors
alwaysbelieve1 said:
No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???
Click to expand...
Click to collapse
Did you freeze any of your system apps?

mcapozzi said:
Did you freeze any of your system apps?
Click to expand...
Click to collapse
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com

Launcher
alwaysbelieve1 said:
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
Click to expand...
Click to collapse
What launcher are you using?
-Mike

mcapozzi said:
What launcher are you using?
-Mike
Click to expand...
Click to collapse
Nova Prime

alwaysbelieve1 said:
Nova Prime
Click to expand...
Click to collapse
You didn't by chance accidentally freeze the stock launcher?
-Mike

mcapozzi said:
You didn't by chance accidentally freeze the stock launcher?
-Mike
Click to expand...
Click to collapse
No

Here is a thread regarding the issue, but none of the "fixes" worked for me: http://forums.androidcentral.com/sa...0371-unfortunately-system-ui-has-stopped.html
I deleted Facebook so we shall see if that does the trick.

When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app

Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4

ezknives said:
When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.

evastonian said:
Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes that is exactly what I do every time. Today I started completely fresh and installed everything manually so I can better narrow down any issues.

alwaysbelieve1 said:
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.
Click to expand...
Click to collapse
Yea I backup everything on my external hard drive (that after I back anything up I bubble wrap and put in my fire safe< a bit paranoid) every week, so that if anything happens I can just wipe it clean and start fresh (I have never used rsd lite but I'm guessing its somewhat like option one of Matt's utility) that restores your phone to a moto flashed like state... ready to be sold as a certified like new device (as Verizon would call it)...
Sent from my XT907 using xda app-developers app

Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.

RikRong said:
Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.
Click to expand...
Click to collapse
Don't even know how to do this or what this means exactly...

Nexus 4 w/ PAC 4.2.2 Bricked, need help in recovering data

Background
- I'm using PAC 4.2.2 ever since I bought my Nexus 4 and was quite happy with the ROM until yesterday
- I started losing out the GSM signal for the past 2 weeks, it would intermittently go off and then come back by itself after a few seconds, at times few minutes (never thought it could be a ROM issue, is it?)
- Google started pushing its update and I had to manually stop data for Google Services from Settings -> Data Usage
Problem
Yesterday while updating Angry Birds from the Play Store the Play store crashed. I tried to open it but it would continue to crash as soon as it would try to load it.
I rebooted the device however since then its stuck on the google logo and doesn't proceed.
I have TWRP recovery installed and when it boots in to (Fastboot is it called?) it shows Secure Boot - enabled and Lock State - unlocked.
Few foolish things that I tried yesterday (in desperation) that might have already screwed up my phone beyond recovery....
1. Wiped Cache and Dalvik Cache and tried to reboot but it didn't work
2. Flashed the new PAC 4.2.3 version that I had downloaded way back but still no success
3. Tried to take a backup from TWRP recovery however while restoring it fails and shows the message 'Restore Failed'
I really wish to recover the media that is in the phone and contacts if possible.
I have Google Nexus 4 Toolkit (not sure of the version but its like 8-10 months old) installed in my laptop and if I connect the phone and start the toolkit it recognizes the phone against adb (shows a serial number) but when I try to back it up it stops at 'Waiting for adb mode...'
I'm a total noob when it comes to recovery etc. so would really appreciate any help that leads to data recovery in my phone somehow, thanks!

Internal memory is accessible through ADB over recovery so you could easily get your data if it is still there. About the contacts - if they are Google contacts and saved to your gmail - happy days, nothing to worry about. But if they are phone contacts I don't think you'll be able to restore them.
Do you know what is the worst thing about smart phones? That the owner should be smarter than the device in order to operate it.
Sent from my Nexus 4 using xda app-developers app

evdrmr said:
Internal memory is accessible through ADB over recovery so you could easily get your data if it is still there.
Click to expand...
Click to collapse
What would be the steps that I'd have to follow for this? I have TWRP recovery installed.
EDIT: I even tried a complete wipe but it doesn't work. Also tried using CWM as recovery, that didn't work either. Installed the Unified_Android_ToolKit (latest version), updated all USB/adb drivers but whenever I try to backup anything through the toolkit all I get is that it is waiting for the adb mode or its waiting for the USB debugging to be enabled (which I can't since I can't get the phone to boot up).
Any ideas?

Don't try to restore any data after full wipe. It won't work. Flash factory images to get your device into operable state again but before that go to Device Manager and make sure that the phone is recognized by the computer and the drivers for it are properly installed. Good luck. Can you still access twrp recovery?
Sent from my Nexus 4 using xda app-developers app

evdrmr said:
Don't try to restore any data after full wipe. It won't work. Flash factory images to get your device into operable state again but before that go to Device Manager and make sure that the phone is recognized by the computer and the drivers for it are properly installed. Good luck. Can you still access twrp recovery?
Click to expand...
Click to collapse
After having given up all hope to retrieve any data or contacts I wiped the entire phone, format data I mean. However, with that I've ended up with no OS on the phone, I can access TWRP though. Not sure how badly I've ended up screwing the phone. :silly:

Not badly at all... Reboot your phone into Boot loader mode. Download the Google factory images of your choice and run the flash-all.bat file. Enjoy your fully restored phone in a couple of minutes.
Sent from my Nexus 4 using xda app-developers app

evdrmr said:
Not badly at all... Reboot your phone into Boot loader mode. Download the Google factory images of your choice and run the flash-all.bat file. Enjoy your fully restored phone in a couple of minutes.
Click to expand...
Click to collapse
How exactly do I run the flash-all.bat file? I tried flashing the factory image using the Unified Toolkit however there comes an error message stating that there is some issue in the program and it has to close. This happens somewhere midway when it starts flashing system.img and recovery.img
EDIT: I can't get in to recovery mode any more and neither can I flash any recovery
EDIT2: Don't ask me what I did, somehow managed to get the phone running in the 4.2.2 version of stock factory image. 4.4 wasn't working for some reason. Setting it up for use now.
Question: Can I simply download 4.4 factory image and install it on my Nexus 4 which came with 4.2.2. when I bought it?

Simply: Yes
Sent from my Nexus 4 using xda app-developers app

evdrmr said:
Simply: Yes
Click to expand...
Click to collapse
Even when I wasn't able to follow any of the instructions you provided (my bad though) I would like to thank you for just posting on the thread man! :good:
BTW a good news that I'd want to share is that my contacts were backed up I lost on the media but its fine I think, probably a good lesson for future.
I'm updating to 4.3 from system update as of now, will use it as it is for time being and move on to 4.4 sometime later maybe. Not sure whether 4.4 will be available for update OTA once I move to 4.3 but I'm happy with whatever's left of the phone for now...thanks again!

Persistent problem

Hello,
SOOOOooooo I posted a thread a few days ago. Bear with me, this introductory post is long BUT it is worth including all details I can right from the start to cut down unnecessary communication.
Here goes the continuation in some kind of a bullet form timeline format:
-Bought fully functional d801
-rooted (using ioroot) and unlocked succesfully
-attempted to install twrp using freegee (it didnt work giving me comparable results to this: http://forum.xda-developers.com/showpost.php?p=50501346&postcount=867)
-went on to install it manually from terminal emulator (I installed the rogers version as suggested by another user here as this is exactly my situation: http://forum.xda-developers.com/showpost.php?p=50502408&postcount=869
***
PROBLEMS STARTED HERE
***
-Tried many things
-Lost sleep
-Flashed succesfully using flash tool to the original firmware (D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone) I even flashed it twice. (still had the exact same issues
-Hard resetted countless times
-lost faith in humanity
Thats basically it so far.
Here are the symptoms:
-Imei = null
-Phone resets/reboots randomly and consistently every 5 to 15 seconds
-I can get all the way through to the android os all seems normal Except:
-No keyboard. ever.
-no wifi
-camera even works
-cant get into security and settings (crashes automatically into reboot)
Very good recent news thanks to advice from a memeber on here:
I tried in vain connecting to adb (always giving "offline") until someone suggested trying a different architecture (x64vsx86) or just different pc altogether.
It worked. Now the device is recognized and it says : "some serial number" device
and not "offline" as before
inputting "adb shell" yields: "[email protected]:/ $"
I am open to answer any question.
I am open to try anything.
This phone is a total loss right now so I am obviously open to anything. :laugh:
Phone is still rooted according to "download mode" interface.
Stock recovery installed right now.
I have what I believe to be EFS backups outputted by the initial Ioroot rooting automation (modemstat1.img and modemstat2.img)
You folks are the best.
Much peace and love.:good:

Your t-mobile, right. D801? (Not 100% on that) if you are, you need lg flash tool. I don't have a link because I'm on my phone but it's around. You need to download the T-Mobile files in the 1st post of the thread. Just follow the directions. Wish I had links
Sent from my LG-D800 using xda app-developers app
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Using that will bring you back to stock. From there you can root, twrp, and flash custom rom. Good luck
Sent from my LG-D800 using xda app-developers app

I am not with t-mobile.
Phone is from Videotron (Canadian phone)
I have reinstalled the stock .kdz using flash tool and am also already rooted.
Still have the same issues.
I cannot install anything from wifi since it isnt working...
Any guides on how to install twrp using adb interface?
Or any other suggestions?
Will a custom rom really solve these kinds of issues?
Thanks a lot for the advice I really appreciate any input at this point.:good::good::good:

zprovo said:
I am not with t-mobile.
Phone is from Videotron (Canadian phone)
I have reinstalled the stock .kdz using flash tool and am also already rooted.
Still have the same issues.
I cannot install anything from wifi since it isnt working...
Any guides on how to install twrp using adb interface?
Or any other suggestions?
Will a custom rom really solve these kinds of issues?
Thanks a lot for the advice I really appreciate any input at this point.:good::good::good:
Click to expand...
Click to collapse
Have you tried this http://teamw.in/project/twrp2/197 method.
Initially I tried almost everything but only this worked after couple of tries. http://forum.xda-developers.com/showthread.php?t=2449670

andro ninja said:
Have you tried this http://teamw.in/project/twrp2/197 method.
Initially I tried almost everything but only this worked after couple of tries. http://forum.xda-developers.com/showthread.php?t=2449670
Click to expand...
Click to collapse
Ok really good news :laugh::good:
Making slow but certain progress here.
So just to update also: I now CAN acces the phone from my computer when I put it in PTP (camera) mode.
First I realized that root was installed but that I did not have the supersu installed. I realized this because I could not access "su" in adb shell.
So I reinstalled the ioroot. Complete success. Super su is in the apps and su commands work.
Next I went on to download the rogers TWRP file (even though my phone is a videotron phone) and install it using this:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Which worked!!!
I went to hard reset data and booted into the twrp interface.
I wiped everything from within twrp and went to reboot. it then informed that supersu was NOT installed on my phone and to slide the bar over if I wanted to install so I said yes...
But kind of bad news now:
Stuck at lg logo...:silly: Stays at lg logo and led is lit up changing from blue to green.
So what now?
Any suggestions?
Thanks a lot for the help everyone.:good:

See if you can get into recovery using adb or the holding the vol+pwr keys
Sent from my LG-D800 using XDA Premium 4 mobile app

andro ninja said:
See if you can get into recovery using adb or the holding the vol+pwr keys
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like into the TWRP interface?
Easily yes, I absolutely can.
Next?
(it also seems I can no longer access the internal storage from windows explorer, although the phone is being recognized in devices and printers as "modem LG G2"... It attains this status when it is stuck at the lg boot loading screen)

zprovo said:
Like into the TWRP interface?
Easily yes, I absolutely can.
Next?
Click to expand...
Click to collapse
Did you take any backup using TWRP earlier? If yes then restore it.
If no then you can push another ROM for your device on to sdcard using ADB and install it and see.

andro ninja said:
Did you take any backup using TWRP earlier? If yes then restore it.
If no then you can push another ROM for your device on to sdcard using ADB and install it and see.
Click to expand...
Click to collapse
Ok I will try this now.
If you could provide with adb code example for copying a file to /sdcard i would really appreciate it.
Where do I go within the twrp recovery afterwards?
Thank you so much.:highfive:

adb push <local> <remote>
Sent from my LG-D800 using XDA Premium 4 mobile app

andro ninja said:
adb push <local> <remote>
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ooouuuufff.
New problem
Houston we have a problem:
adb devices = nothing.
How can I get adb devices to work if I cant boot into os and it is not recognizing it when in recovery?
Ahhhhhhhhhhhhhhhhhhhhhhhhh:silly:

zprovo said:
ooouuuufff.
New problem
Houston we have a problem:
adb devices = nothing.
How can I get adb devices to work if I cant boot into os and it is not recognizing it when in recovery?
Ahhhhhhhhhhhhhhhhhhhhhhhhh:silly:
Click to expand...
Click to collapse
Windows ****!! Follow this thread http://forum.xda-developers.com/showthread.php?t=2263822 and install that driver and try.
If not then find yourself a linux box and try. I am sure It'll work.

andro ninja said:
Windows ****!! Follow this thread http://forum.xda-developers.com/showthread.php?t=2263822 and install that driver and try.
If not then find yourself a linux box and try. I am sure It'll work.
Click to expand...
Click to collapse
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:

zprovo said:
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
Click to expand...
Click to collapse
You don't really have to burn a CD/DVD, you can use a USB drive.
I don't know much though. I've been doing these things for quite some time now so have experience and I am totally free now so helping you here.

zprovo said:
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
Click to expand...
Click to collapse
It WORKED!
Awesome fix.
adb devices now gives:
(device number) recovery
Ok going to copy a rom and kernel and try to install.

Tried two different roms. Same result
Failed.
set_metadat_recursive: some changes failed
E:Error updating updater binary in .zip '/sdcard/...zip'
Wow just wow.
Any ideas?
This was with omni and cm11. Going to try with a stock rooted rom as soon as it finished downloading.

zprovo said:
Tried two different roms. Same result
Failed.
set_metadat_recursive: some changes failed
E:Error updating updater binary in .zip '/sdcard/...zip'
Wow just wow.
Any ideas?
This was with omni and cm11. Going to try with a stock rooted rom as soon as it finished downloading.
Click to expand...
Click to collapse
look here http://forum.cyanogenmod.com/topic/86979-cm-11-20140124-set-metadata-recursive-some-changes-failed/
---------- Post added at 11:57 PM ---------- Previous post was at 11:23 PM ----------
Just get a latest version of the recovery for your device and install it.

andro ninja said:
look here http://forum.cyanogenmod.com/topic/86979-cm-11-20140124-set-metadata-recursive-some-changes-failed/
---------- Post added at 11:57 PM ---------- Previous post was at 11:23 PM ----------
Just get a latest version of the recovery for your device and install it.
Click to expand...
Click to collapse
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)

zprovo said:
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
Click to expand...
Click to collapse
I remember I had same problem. I use to restore only the boot partition from a backup of a stock rom.
So try installing a stock rom like this one http://forum.xda-developers.com/showthread.php?t=2595586. If it works then boot into recovery and take a backup then install whatever you want to and the just restore the boot partition if your are stuck at boot logo.

zprovo said:
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
Click to expand...
Click to collapse
Ok just finished installing the stock bell rom from the site I linked in a previous post.
Stock D803 rom with stock D803 kernel, both installed succesfully.
Phone is back to exactly how it was when I started this thread. EXCEPT that I now also have TWRP running alongside it.
So that includes:
-*#06# = IMEI Null
-phone reboots randomly every 5 to 15 seconds
-keyboard never comes up
-widgets always have a "loading" circle spinning on them
-trying to enter security and settings = auto reboot
-all other options are accesible and useable as long as no keyboard is involved since it never comes up
-no wifi
Wow, this is one hard to fix phone.
Or it simply has hardware damage. but I doubt it since it has no issues running recovery.
Any ideas?:laugh: