Related
Hey,
So I installed Cyanogenmod nightlies from rom manager on my nexus 7 and it downloaded and installed fine, but then the device rebooted and has been stuck on a loop of the cyanogenmod splash screen for a hour or two. What did I do wrong and how can it be fixed?
Thanks
agoramilio said:
Hey,
So I installed Cyanogenmod nightlies from rom manager on my nexus 7 and it downloaded and installed fine, but then the device rebooted and has been stuck on a loop of the cyanogenmod splash screen for a hour or two. What did I do wrong and how can it be fixed?
Thanks
Click to expand...
Click to collapse
Did you wipe data/factory reset from CWM after flashing?
comminus said:
Did you wipe data/factory reset from CWM after flashing?
Click to expand...
Click to collapse
yes
Reboot into recovery and try again.
Billchen0014 said:
Reboot into recovery and try again.
Click to expand...
Click to collapse
when i try reboot,m it just goes to the cyanogenmod splash and loops
agoramilio said:
when i try reboot,m it just goes to the cyanogenmod splash and loops
Click to expand...
Click to collapse
Hold down all three buttons and keep holding them. You should be able to get in to fastboot mode.
comminus said:
Hold down all three buttons and keep holding them. You should be able to get in to fastboot mode.
Click to expand...
Click to collapse
so i think i have a new problem...i managed to reboot and go into recovery, but now its stuck on the Google splash
Did you flash a new ROM for the n7?
Billchen0014 said:
Did you flash a new ROM for the n7?
Click to expand...
Click to collapse
all i did was install rom manager and then install cyanogenmod nightly
agoramilio said:
Hey,
So I installed Cyanogenmod nightlies from rom manager on my nexus 7 and it downloaded and installed fine, but then the device rebooted and has been stuck on a loop of the cyanogenmod splash screen for a hour or two. What did I do wrong and how can it be fixed?
Thanks
Click to expand...
Click to collapse
Which android version are you on? Did you already unlock the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Apocalypse487 said:
Which android version are you on? Did you already unlock the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
jelly bean and no
agoramilio said:
jelly bean and no
Click to expand...
Click to collapse
I think you have unlock the bootloader. I might be wrong, but that’s what I did. I unlocked and rooted my N7. Then I flashed a rom, but I was on 4.1.1 then.
Sent from my SAMSUNG-SGH-I747 using xda premium
dp you have a adb setup or maybe wugs toolkit? Correct me if im wrong but the old bootloader had a bug when manually going into the recovery vai button holding at power up
if you have adb setup try a adb reboot recovery and see if that gets you into clockworkmod/twrp, report back
so i have a new problem....i can boot the nexus 7 into recovery mode, but none of the volume buttons work to change the choice, and the nexus 7 toolkit doesnt see the device
now the screen is going nuts https://dl.dropbox.com/u/3678314/20121017_190402.jpg
Hi everyone,
I've just bricked my nexus 10 by installing paranoid rom. My devise is blocked at the Nexus Logo and when I plug it on my pc I hear a sound but I don't see it in my windows explorer. I've used mrskip tool to unbrick my device but it fail at the extraction of the official rom even if I see it on the menu of the tool.
Thanks in advance.
Cyr
cyr807 said:
Hi everyone,
I've just bricked my nexus 10 by installing paranoid rom. My devise is blocked at the Nexus Logo and when I plug it on my pc I hear a sound but I don't see it in my windows explorer. I've used mrskip tool to unbrick my device but it fail at the extraction of the official rom even if I see it on the menu of the tool.
Thanks in advance.
Cyr
Click to expand...
Click to collapse
You may want to post this on the PA thread.
Go to nexus10root.com. it will unbrick it. If u know how to follow his fast boot instructions
Sent from my Nexus 10 using XDA Premium HD app
cyr807 said:
Hi everyone,
I've just bricked my nexus 10 by installing paranoid rom. My devise is blocked at the Nexus Logo and when I plug it on my pc I hear a sound but I don't see it in my windows explorer. I've used mrskip tool to unbrick my device but it fail at the extraction of the official rom even if I see it on the menu of the tool.
Thanks in advance.
Cyr
Click to expand...
Click to collapse
Its not bricked. You just need to learn a bit more...
Get into recovery and wipe data, if that fails try to flash a stock rom or wipe system and flash paranoid again.
problem solved
TheBlueRaja said:
Its not bricked. You just need to learn a bit more...
Get into recovery and wipe data, if that fails try to flash a stock rom or wipe system and flash paranoid again.
Click to expand...
Click to collapse
Thank you very much I've just done a wipe data in recovery and it solved my problem :laugh:
Hi, does anyone know how can I install the drivers for ADB for the Nexus 4 with Build LGEP02? This is currently running 4.2 and it says it is up to date. I want to flash it with the 4.2.1 image.
Also, there are two testing tools on the phone, Hidden Menu and CKE Setting.
-------------------
Fixed!
Here's what I did.
1. Download this LG Driver and install.
2. Make sure USB Debugging is ticked/checked and plug it into your PC.
3. Now that it is finally installed properly, follow the instructions on this thread to flash it with stock image.
4. ???
5. Profit? Done.
To moderators, kindly move this thread to the appropriate section. Thanks! :good:
Just delete data for Google service framework in applications and you should receive the update immediately
Sent from my Nexus 4
WPMan said:
Hi, does anyone know how can I install the drivers for ADB for the Nexus 4 with Build LGEP02? This is currently running 4.2 and it says it is up to date. I want to flash it with the 4.2.1 image.
Also, there are two testing tools on the phone, Hidden Menu and CKE Setting.
Click to expand...
Click to collapse
Drivers can be found in this thread.
noodles2224 said:
Just delete data for Google service framework in applications and you should receive the update immediately
Sent from my Nexus 4
Click to expand...
Click to collapse
Did that, still no update.
abnormalreply said:
Drivers can be found in this thread.
Click to expand...
Click to collapse
I also already tried that before I posted here. It seems this unit uses an LG hardware ID instead of Google's, I think.
Try the drivers from here. http://forum.xda-developers.com/showthread.php?t=1996051
Make sure you delete your current installed drivers first.
Sent from my Nexus 4 using xda premium
I finally managed to install stock 4.2.1. I will add the steps I did on the first post, so whoever runs into a similar device with the LGEP02 build can flash it with Google's build.
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
kujhawk1977 said:
Hi guys,
I'm a noob here so pardon any dumb questions. I tried to do the 4.4 OTA update and it failed. When I rebooted my phone it is stuck in a bootloop. My Nexus 4 is rooted and has CWM. However, USB debugging is not enabled and I cannot enable it do to being stuck in a bootloop.
What are my options here?
Click to expand...
Click to collapse
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
playya said:
hi noob quick question you tried to do OTA with CWM installed already? If so thats problem 1. Why do OTA if you are already rooted just go to a thread and install a rooted KitKat rom and done
Click to expand...
Click to collapse
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
kujhawk1977 said:
Yes you are right. I should not have tried the OTA install. opps on my part. So can I still do the rooted KitKat rom without having USB debugging enabled? It seems my laptop can not see my Nexus and I figured this was the issue.
Click to expand...
Click to collapse
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
CWM will not be able to flash OTA successfully. You need to sideload it through stock recovery or TWRP.
playya said:
well you either have to download a rom or push it to your device to flash kitkat. Have you tried it in recovery? See if you pc recognizes your phone then
Click to expand...
Click to collapse
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
kujhawk1977 said:
Yes I want to try the side load option. I am not familiar with the process but I was thinking USB debugging needed to be enabled. I am in Recovery and connected to my laptop. Not recognizing the device.
Click to expand...
Click to collapse
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
playya said:
Is it xp? Nothing will popup so check in device manager to see if it shows up. then you will need to use adb
Click to expand...
Click to collapse
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
kujhawk1977 said:
Not XP I have Windows7. Okay thanks for the tip. Android device is showing in Device Manager. I have downloaded adb and the lastest 4.4 image. So how do I side load this?
Click to expand...
Click to collapse
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
Click to expand...
Click to collapse
I what to do whatever I have to do to fix my problem and I am not sure what that is.
playya said:
whoa I thought you had CWM and want to flash a rom not the img file
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
download adb platform tools then use adb to push a rom over to your phone then flash the zip... simple
Click to expand...
Click to collapse
OK I have adb platform tools. And I have the krt16s.zip Where can I find instructions on how to push the rom over to my phone and flash?
kujhawk1977 said:
I what to do whatever I have to do to fix my problem and I am not sure what that is.
Click to expand...
Click to collapse
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
playya said:
ok well then you can simply go to development and get a stock rooted 4.4 kit kat rom and transfer it over to your phone.
You are going to have to do some research though,
look for rom - search development
obtain adb tools - search google
then use adb to push it over to your phone. - tutorials are out there
go into CWM then flash rom
Other option is do a search for the one click 4.4 Factory image setup which is the easiest or flash images the normal way using adb. - this method is done through bootloader
Click to expand...
Click to collapse
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
kujhawk1977 said:
Okay well I did all that it everything seemed to be going good. But when I rebooted the phone instead of being in a bootloop with the colorful loading logo....it is now stuck on Google logo that first comes up when reboot.
Click to expand...
Click to collapse
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
playya said:
I am driving now but your problem is a problem that can be found with a little searching
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
!!!!!!!!!!
So I still have the problem and cannot find a fix. Anyone here up for the challenge?
I was stuck in a bootloop and a failed OTA 4.4 update.
My nexus 4 is rooted and has CWM so yes I know i should have updated manually in the first place, but I didn't. After the update failed, it was stuck in a bootloop.
The next step I did was to side load the update. It ran through the install and at the end when 100% is says Installation Aborted. When my device is rebooted it is now stuck on the screen Google in white font.
Some other notes that MIGHT be related: USB Debugging is NOT enabled, as I can not boot into my device.
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
---------- Post added at 07:37 PM ---------- Previous post was at 07:31 PM ----------
Hi @kujhawk1977 did you sort your problem? Sounds similar to whats happened to my phone, got stuck in bootloop, failed update and computer not recognizing device. Do you have any tips for me?
No one has answered your question yet. I will.
Edited to say I did find a way to bridge (adb) files over without having USB Debugging selected on the phone.
Updated drivers and used ADB / SDK to move new Recovery and ROM over to my phone using CWM. Never trusting TWRP again
Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
Go to “Advanced”
Choose “Wipe dalvik-cache”
Now go to “Mounts & Storage”
Choose “Wipe /cache”
Reboot your phone
The bootloop should be gone now. If it still persists, do this.
Boot the phone again into CWM Recovery
Now go to “Mounts & Storage”
Choose “Wipe /data”
Choose “Wipe /cache”
Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
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: