Database Users

[Q] Which rooting method?

I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.

Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.

Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium

frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app

Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.

AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium

frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?

I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk

I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium

Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!

Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk

I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.

Use the fastboot commands
Good to see you alright!

This is like asking "Should I get an automatic or manual car?"

veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.

Look at these lazy people..
Beamed from my Grouper.

Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.

Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!

Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.

OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.

Have I totally bricked my Nexus 7?

Hi,
Regretting this now but was trying to try out a different ROM after a long day so probably missed a step somewhere....
The situation now is that following normal procedure, my Nexus was wiped of user data, new ROM zip file copied across and loaded using recovery mode. After that, it had some error setting permissions with the new ROM and did not install properly (loaded but blank screen, apps, settings etc would not load).
I tried the process again and the same result, but now, I cannot even get adb working, the device is coming up simply as an unknown device and I cannot force install the google usb driver to get adb working again - so now I cannot even copy stock across to the Nexus.
My question is, without adb working now, have I fully bricked it or can someone point me in the right direction?
Thanks

If you can get into boot loader you can fix it.
Home power up and down
Sent from my Nexus 4 @1.5 GHz on Stock 4.2.1

Update ur SDK to get adb working..I faced it for 4.2.2
Sent from my Nexus 7 using xda app-developers app

IRX120 said:
If you can get into boot loader you can fix it.
Home power up and down
Sent from my Nexus 4 @1.5 GHz on Stock 4.2.1
Click to expand...
Click to collapse
To elaborate a little, you'll want to get into the bootloader using the method quoted above, and then use fastboot (or nexus toolkit) to flash a stock image.

Thanks guys, managed to recover back to stock via fastboot and the command line just now .... this will teach me never to try flashing any ROMs when half asleep!
Thanks again :good:

Greed lead to Brick!

Hey guys
I thought I'd just let you all know that my ambition to get 4.3 and lack of knowledge, led to my phone getting bricked today. I'm so devastated. I was following efrant's guide and flashed everything correctly and then as usual I lost half my storage and I followed the other guide to restoring the lost storage, once again i followed everything but i didn't get the storage back, then i did some cmd commands like the guide did. Next thing you know I may have done something wrong and I was at the bootloader screen and I couldn't reboot or go to recovery. Read and read nothing helped, called Google and they couldn't help me. I am now getting a replacement. SO there you go guys, just the greed of getting 4.3 caused me to brick my phone as well as my lack of knowledge I guess. Can't complain. Thought I'd share this with you all.
Div
P.S Moderators if this isn't suitable you guys can delete it no harsh feelings

Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2

If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta

Just flash the stock android image again, after all you have access to the bootloader, everything is fine

teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fabrizziop said:
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
Click to expand...
Click to collapse
This. You're totally not bricked.
Please follow the instructions in this thread:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus⁴ using Tapatalk 4 Beta

Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?

Fataldesain said:
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it's totally worth it

nqk said:
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Click to expand...
Click to collapse
Perhaps
Code:
# dd if=/dev/zero of=/dev/block/mmcblk0

Thats not greedy, your just too excited for 4.3

teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Click to expand...
Click to collapse
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....

Dvash27 said:
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Click to expand...
Click to collapse
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.

miniAndroidian said:
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone

Dvash27 said:
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Click to expand...
Click to collapse
Glad to know that it helped you mate

What about content on phone
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??

leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta

TToivanen said:
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
---------- Post added at 10:45 AM ---------- Previous post was at 09:46 AM ----------
leiftorem said:
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
Click to expand...
Click to collapse
I can see my phone listet under "Advanced Utility, but I cannot seem to pull the files from my phone!
I am getting really frustrated here now!
Anyone??

leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.

Mr. Kostik said:
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Click to expand...
Click to collapse
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)

leiftorem said:
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
Click to expand...
Click to collapse
Oh well you should look in one of those threads on how to root and so on, flashing a recovery using a toolkit should also work. Texts will be gone.
Or from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
But at some point you'd need a custom recovery anyway.

Grouper bricked after latest 4.3 OTA, no recovery

Heya...
On my 16GB Grouper I had installed the stock rooted 4.3 rom. Yesterday a system OTA update message appeared on my screen - 1.7 MB. I let it download and install over night and just went to bed. Came back in the morning to a boot loop where the device got stuck with the four colorful thingies animation. I can access the bootloader, but the recovery seems to be broken. Can't remember if I had anything other than the stock one... Anyways, now I'm strugling to get this thing going again. I am a zero at ADB but willing to learn whatever is necessary to get me started with a working recovery at least. No tool root box will do anything really for me...
Thanks for your help in advance

Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app

hettige677 said:
Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah. It would be dumb to actually learn what you are doing to your device. You should totally use a toolkit.
/s
Sent from my Galaxy Nexus

Honestly, I'm just showing the user one way, I anticipated him of being a newbie. For the record, it shows you all the process's happening.
Sent from my Nexus 7 using xda app-developers app

Thank you guys. You might not believe it, but I'm not a newb to Android or flashing. It's just that I've always been playing around with Samsung devices and there you'd normaly turn to Odin in case something went wrong. Here it's different.
Anyways, with this comprehensive guide I've been able to reflash a recovery image and my old rom. Unfortunately losing all of my data in the process, but there was no way to save it.
http://www.androidupdate.us/recover-bricked-device-fastboot/
In case this happens to anybody else.
Cheers

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: