Database Users

Error: Black Screen on reboot - Help.

I installed a modified home.apk to leave the dock transparent, but forgot to put the permissions, rebooted the phone and now he does not leave the black screen.
It is with the SONY logo on the screen.
I tried to restart and hold the menu button, but could not reboot.
Please, I need someone to help me: how to solve this problem?
My phone is: 2.3.4, root only, bootloader locked. Firmware 0.283.
Thanks !
----------------
I flash again. Solved.
Thanks !

Reflash with the Flashtool.

If you have ADB connected use that method to replace the Home.apk with proper permission and you can save some time

ShyamSasi said:
If you have ADB connected use that method to replace the Home.apk with proper permission and you can save some time
Click to expand...
Click to collapse
You can't connect using adb when the phone is stuck at boot which is why they'll have to reflash.

XperienceD said:
You can't connect using adb when the phone is stuck at boot which is why they'll have to reflash.
Click to expand...
Click to collapse
Yes you can. Use recovery and manualy mount data, system partitions. Then you can use "android commander". It makes this job fast and right. Experiensed users can use adb for pushing pulling apps. I reccomend commander because its grafical UI and easy to use.
Regards
Taavi
Sent via MT15i Nightly v14®

taaviu said:
Yes you can. Use recovery and manualy mount data, system partitions. Then you can use "android commander". It makes this job fast and right. Experiensed users can use adb for pushing pulling apps. I reccomend commander because its grafical UI and easy to use.
Regards
Taavi
Sent via MT15i Nightly v14®
Click to expand...
Click to collapse
Not with a locked bootloader you can't.
Sent via CM7-FXP45

That's right.
Sent via MT15i Nightly v14®

Device stuck on boot animation.

Hello,
I Flashed Beanstalk rom on my Nexus 4 but the rom just won't boot up.
The device is stuck on boot animation and I'm trying to get into Recovery mode-with no success.
I'm able to enter to Download mode but I don't know what should I do.
I just want my Nexus 4 to boot up.
Please help me.

Wassupdog said:
Hello,
I Flashed Beanstalk rom on my Nexus 4 but the rom just won't boot up.
The device is stuck on boot animation and I'm trying to get into Recovery mode-with no success.
I'm able to enter to Download mode but I don't know what should I do.
I just want my Nexus 4 to boot up.
Please help me.
Click to expand...
Click to collapse
Hold power+volume buttons until the phone shuts down. Then, release the buttons, and immediately press them all again. You will be booted in bootloader. Select recovery, and restore your backup, if you did one, or flash another ROM.

abaaaabbbb63 said:
Hold power+volume buttons until the phone shuts down. Then, release the buttons, and immediately press them all again. You will be booted in bootloader. Select recovery, and restore your backup, if you did one, or flash another ROM.
Click to expand...
Click to collapse
You are a lifesaver!
Thanks a lot!
I'm now in recovery mode, how can I install another rom from this condition?

Wassupdog said:
You are a lifesaver!
Thanks a lot!
I'm now in recovery mode, how can I install another rom from this condition?
Click to expand...
Click to collapse
Use adb push a rom to the phone
adb push nameofrom.zip /sdcard/
From my BLACKED OUT N4

spaceman860 said:
Use adb push a rom to the phone
adb push nameofrom.zip /sdcard/
From my BLACKED OUT N4
Click to expand...
Click to collapse
How exactly I do that?

Wassupdog said:
How exactly I do that?
Click to expand...
Click to collapse
Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Then use the command that youve been provided

chromium96 said:
Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Then use the command that youve been provided
Click to expand...
Click to collapse
Thanks!
I will try it now, hope it would work.

Wassupdog said:
Thanks!
I will try it now, hope it would work.
Click to expand...
Click to collapse
It didn't work.
I could not send zip from the computer to the sdcard.
I wrote in the CMD " adb push Rom.zip/sdcard/Rom.zip " and nothing happened in the phone .
Please help me!

Wassupdog said:
It didn't work.
I could not send zip from the computer to the sdcard.
I wrote in the CMD " adb push Rom.zip/sdcard/Rom.zip " and nothing happened in the phone .
Please help me!
Click to expand...
Click to collapse
You then go to "install zip from sd-card" and install the rom.

abaaaabbbb63 said:
You then go to "install zip from sd-card" and install the rom.
Click to expand...
Click to collapse
But I only have BeanStalk rom and thats the rom that made all this mess.
I want my Nexus back.

Wassupdog said:
But I only have BeanStalk rom and thats the rom that made all this mess.
I hate this stupid rom !!!
I want my Nexus back .
Click to expand...
Click to collapse
Download another ROM onto your pc and push it. No need to freak out, its quite easy to fix.

Thank God!
I managed to flash stock rom.

Wassupdog said:
Thank God!
I managed to flash stock rom.
Click to expand...
Click to collapse
Next time, before doing something you don't have a clue about, try doing some reading, and even asking through the numerous help threads.

abaaaabbbb63 said:
Next time, before doing something you don't have a clue about, try doing some reading, and even asking through the numerous help threads.
Click to expand...
Click to collapse
I did.
I just didn't knew that rom gonna stuck on boot animation.
Thanks everyone!

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.

spontaneous boot loop?

my rooted G2 with stock 4.2 suddenly quit accepting a charge and appears to be caught in a boot loop. when I have it in via usb to my laptop it (laptop) responds by recognizing 12 different devices while saying they they all need to be reformatted. when I unplug the device they go away on the laptop. when I hold power (device) the LG logo will appear then quickly disappear leaving only the very dim backlight as proof that it isn't completely dead. any ideas? thank you
one more thing, the fiddling I have been doing is xposed modules. the last one I think I activated was xblast tools (very cool sh*t by the way).

You need to flash the xposed disable zip that's automatically put on the root of the storage directory. The latest module or change you added is most likely the cause. After flashing the zip, you'll need to reinstall xposed. Remember to disable the module that caused the bootloop.
Sent from my phone using some app

You dun got ATT'ed.
They're pushing OTA's out without asking now.
http://forum.xda-developers.com/showthread.php?t=2647654

Do one thing flash the .tot file for your phone if you can get to download mod, it should bring it back to factory defaults but it will format your sdcard as well so all personal data will be gone.
Here is the link to instructions:
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/

se1988 said:
You need to flash the xposed disable zip that's automatically put on the root of the storage directory. The latest module or change you added is most likely the cause. After flashing the zip, you'll need to reinstall xposed. Remember to disable the module that caused the bootloop.
Sent from my phone using some app
Click to expand...
Click to collapse
I can flash even though I can not enter download mode?

abhinav.tella said:
Do one thing flash the .tot file for your phone if you can get to download mod, it should bring it back to factory defaults but it will format your sdcard as well so all personal data will be gone.
Here is the link to instructions:
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Click to expand...
Click to collapse
I cannot enter download mode I'm afraid.

khaytsus said:
You dun got ATT'ed.
They're pushing OTA's out without asking now.
http://forum.xda-developers.com/showthread.php?t=2647654
Click to expand...
Click to collapse
What exactly do you mean? I glanced at the link and either your joke went right over my head or I missed it in the lot her thread.

pollutedmuse said:
I can flash even though I can not enter download mode?
Click to expand...
Click to collapse
can't you enter recovery?
If you can't enter recovery or download mode, you have a softbrick. Search on how to solve softbrick issues. Im sorry I cant help you any further if it is a softbrick, as I am completely new to LG

se1988 said:
can't you enter recovery?
If you can't enter recovery or download mode, you have a softbrick. Search on how to solve softbrick issues. Im sorry I cant help you any further if it is a softbrick, as I am completely new to LG
Click to expand...
Click to collapse
Do you mean hard brick?

pollutedmuse said:
my rooted G2 with stock 4.2 suddenly quit accepting a charge and appears to be caught in a boot loop. when I have it in via usb to my laptop it (laptop) responds by recognizing 12 different devices while saying they they all need to be reformatted. when I unplug the device they go away on the laptop. when I hold power (device) the LG logo will appear then quickly disappear leaving only the very dim backlight as proof that it isn't completely dead. any ideas? thank you
one more thing, the fiddling I have been doing is xposed modules. the last one I think I activated was xblast tools (very cool sh*t by the way).
Click to expand...
Click to collapse
When you plug it into your computer do you see a yellowed out device in Windows device manager?
If so try this - http://forum.xda-developers.com/showpost.php?p=48361867&postcount=68
or alternately, install the pdanet drivers.
If you can then get adb access to your device there are several paths you could take.
I used this thread (I had recovery but not twrp), as it's the least destructive - http://forum.xda-developers.com/showthread.php?t=2451696
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/show....php?t=2582142
(actually kind of sounds like fun to me)

pollutedmuse said:
Do you mean hard brick?
Click to expand...
Click to collapse
No, hard brick is when the device won't even turn on. OPs device turns on, but is stuck in limbo.

se1988 said:
No, hard brick is when the device won't even turn on. OPs device turns on, but is stuck in limbo.
Click to expand...
Click to collapse
Oh, F'n sweet! Thank good sir! I am gonna work on your advice immediately.

CxanDroid said:
When you plug it into your computer do you see a yellowed out device in Windows device manager?
If so try this - http://forum.xda-developers.com/showpost.php?p=48361867&postcount=68
or alternately, install the pdanet drivers.
If you can then get adb access to your device there are several paths you could take.
I used this thread (I had recovery but not twrp), as it's the least destructive - http://forum.xda-developers.com/showthread.php?t=2451696
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/show....php?t=2582142
(actually kind of sounds like fun to me)
Click to expand...
Click to collapse
Thank you my friend!

pollutedmuse said:
Oh, F'n sweet! Thank good sir! I am gonna work on your advice immediately.
Click to expand...
Click to collapse
Good luck!!
Sent from my phone using some app

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: