Database Develop

Nexus one wont start up

Helloo...
I had my nexus one updated to cm 6.1.1 stable.
The next day i noticed he keeps restarting the phone.
I thought let me pull out de battery and turn the phone on.
Now its stuck at the coloured x and i cant get in recovery.
When i boot into recevory it gets stuck again at the coloured x.
I have flashed stock kernel frg33 and flashed amon recovery with fastboot and tried the passimg method to but it still gets stuck.
My phone is rooted and unlocked bootloader.
What can i do now?
Thnxx in advance

Can you get into bootloader by--> holding down volume-dwn, then pressing the power button, and the releasing the power button while still holding down volume-dwn?
You might need to remove you battery in between tries of this (plus pressing the power button i hear, with the battery removed to drain and remaining power..for 5 secs at least).
If that doesn't work, you could try the three finger salute for Android: Volume dwn+trackball pressed, then tapping power button and letting go of power button, and then the other two.

in most cases you will still be able to use adb
try running 'adb reboot recovery'

Like i sad, i can boot into recovery using the bootloader. But when it start up in recovery it gets stuck at the coloured x.
Fastboot is working but i cant get the adb to work.
Fastboot sees my device an adb doesnt.
What can i do to make adb work?
I installed new sdk and htc sync.
Running on windows 7

try to flash a new recovery through fastboot
download amon ra
open up a cmd
"cd " to directory where you downloaded it
rename amon-ra-recovery.xxxx.img to recovery.img
fastboot flash recovery recovery.img
then try to boot to recovery again

I tried that 10 times but it doesnt work.
Still gets stuck at the coloured x

Fastboot flash the system, bootloader, userdata, etc, and seem if it will boot to system?
Sent from my Nexus One using XDA App

this might sound a bit daft but try taking your sdcard out of the phone and rebooting to recovery

Tried that all. But doesnt work

What sort of error messages are you getting?
Sent from my Nexus One using XDA App

Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App

Nothing!!
Everything what i try to do goes wel.
Update with passimg goes wel.
Fastboot system, boot, userdata, bootloader, everything goes wel.
I dont get any error.
But when i start my phone it gets stuck by the coloured x.

Looks like hardware failure, then...
Sent from my Nexus One using XDA App

Oke that is not good cause i have no waranty anymore.

danger-rat said:
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What is the fastboot command to erase dalvik?

Good question - I've used the erase cache command, and just assumed there would be an erase dalvik command. I may be wrong...?
Sent from my Nexus One using XDA App

Ashvan said:
Oke that is not good cause i have no waranty anymore.
Click to expand...
Click to collapse
When did you get your phone?
Sent from my Nexus One using XDA App

I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?

What is a dalvik cache exactly?
Does nobody knows the fastboot command to erase it?

Ashvan said:
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
Click to expand...
Click to collapse
The very first nexus phones are just coming up to a year old, so the chance is that yours is still in warranty. Call HTC, and see what they say...
Sent from my Nexus One using XDA App

[Q] Bootloop hell

I apologize in advance if this same issue has been replied to elsewhere. I'm in kind of a unique situation and couldn't find an answer anywhere.
I'm got an N1 with 2.3.6 stock ROM, rooted. Recently I downloaded Titanium Backup PRO and while attempting to integrate dalvik cache to ROM, my phone rebooted into a bootloop. I'm assuming this is a bootloop. I get the colorful splash screen, it freezes for a second of two, then continues on, and on, and on....
Is there a way to get me out of this loopwithout having to wipe all my data, so I can backup all my stuff before I flash a custom ROM?
Everything I see about bootloops, mentions unlocking the bootloader and wiping all your data. I've seen downgrading using PASSIMG and loading stock rom. I'd really just like a simple way to get out of this loop hell and get my phone back up. It's in teh ship now getting it's power button fixed.
Thanks in advance

first thing i do on bootloops is pull battery
if no go pull battery and then pwr on by pressing pwr and trackball at same time--you can then get to recovery and maybe wipe dalvik and cache and reboot
i have never used TB for anything other than backup/restores, so can't help with dalvik integration

You might be able to fix it by wiping your cache from recovery.
Sent from my Nexus One using xda premium

Thanks for the advice! I'll give it a try as soon as I get my phone back from being fixed.

Hey guys, I hope you can help. I got my phone back with new power button, Yay! When I try to boot into recovery, teh Nexus X logo comes on for a moment and then I get a white triangle with an orange exclamation point. Do I need to use ADB to try and go to recovery and wipe my cache? I've never installed a recovery image. Do I need to do that or should there be a stock image already on my phone? Am I SOL?

One more thing that might help. I notice that when I go into HBOOT, the phone searching for 4 images from my SD card and can't find them. They go by too fast to write them all down but I think some are PASSIMG, PASSDIAG, etc. Again, do I need to load a recovery like clockworkmod on my phone first and then go into recovery to attempt to wipe my cache?

I get the same passimg all the time--no problem
If your phone came back from repair, you are probably unrooted and hence the triangle. At least that is the way I remember it, but has been two years since I rooted
If that is comfirmed by someone else, you wil need to reroot and install a recovery
A good time, if you haven't, to install android sdk and root/install recovery the right way and have full adb/fastboot features
there other ways I am not familiar with
does the lock show unlocked on the screen, they could have relocked bootloader
the wiki has the instructions, just have to navigate to the htc smartphones and N1

jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk

Thanks I'll check. I only had teh power button fixed and not by HTC so I doubt they unrooted it. I'm still in a bootloop but I can use superoneclick still, so I'll give that a try.

so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.

holtonhj said:
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
Click to expand...
Click to collapse
You really know nothing huh. The triangle is the recovery. Press power button and volume up at the same time, it will the show you some options like wipe cache.

n1newbie said:
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Did you miss the "stuck in boot loop" part?

sorry,
meant that the triangle is your stock recovery--
you install recovery thru fastboot not adb
i would still, if you haven't, install android sdk on pc-unlock bootloader (fastboot oem unlock) and fastboot recovery--all in wiki
i think it was mentioned--holding down pwr and tb will get you into fastboot mode--phone connected and usb debugging selected on phone
you'll just have more flexibility with flashing roms etc and getting out of trouble

HTC One Bricked - Keeps Booting into Recov but then Restarts.

Here is what happened:
1) Installed Android Rev HD, worked fine.
2) Installed Xposed mod and bricked device (got stuck at Beats Audio)
3) Booted into recovery, restored Nandroid backup (of STOCK rom).
4) That worked fine and I was able to boot back into stock.
5) Then I went back in Recovery to Install Android Rev HD back, after that was installed, I got a prompt in Recovery that root might be removed and asked if I wanted to restore it or something. I clicked yes and my phone immediately turned off.
Now I am stuck in a loop. The phone keeps restarting and then booting into recovery but the recovery screen only flashes for 1s before the phone restarts and completes the whole cycle again. I am only able to boot into the bootloader. Even if I power down the device, once I turn it back on, it tries to boot back into recovery again and starts the whole loop. Please help.
Update: I tried reflashing recovery using the All-In-One-Toolkit but it says "error: device not found". However, the command "fastboot devices" does detect the device.
Update 2: Tried using adb to "fastboot flash recovery" but it wouldn't work. I tried reflashing CWM (downloaded from their website) and TWRP but both of them suffer the same "load up for a split second" and then restart issue.
Update 3: Wiped the cache and now im able to boot back into recovery.

You need to force it to turn off me thinks. Not sure how you do it on the One. On my old sensation it was power+volume keys. Once off connect it to a charger, see if it charges, if yes then it should get passed flash screen. Try flashing a Rom but make sure you are fresh flashing, not flashing over something.
The quick restart thing sounds like a command that's stuck. Once it gets to fastboot it's rebooting as the commands there, but not clearing the command.
Sent from my HTC One using XDA Premium HD app

OllieArmageddon said:
You need to force it to turn off me thinks. Not sure how you do it on the One. On my old sensation it was power+volume keys. Once off connect it to a charger, see if it charges, if yes then it should get passed flash screen. Try flashing a Rom but make sure you are fresh flashing, not flashing over something.
The quick restart thing sounds like a command that's stuck. Once it gets to fastboot it's rebooting as the commands there, but not clearing the command.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Im able to turn it off via bootloader but it isn't doing me any good since once I power the phone back on, it goes back into the loop again.

If you can turn it off in bootloader, can you not flash recovery?
Sent from my HTC One using XDA Premium HD app

OllieArmageddon said:
If you can turn it off in bootloader, can you not flash recovery?
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
I was able to reflash recovery via adb but the "new" recovery still had the same problem of immediately closing. However, I wiped the cache via adb and now it works.

In bootloader->recovery, conncect your phone to pc, use this command line "fastboot erase cache" under a folder which contains fastboot.exe and related stuff. This will fix the problem.
Sent from my HTC One using xda app-developers app

yhd4711499 said:
In bootloader->recovery, conncect your phone to pc, use this command line "fastboot erase cache" under a folder which contains fastboot.exe and related stuff. This will fix the problem.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks this resolved my issue

Good job man thanks saved my day. This fixed my bootloop and restarts thankssssssss

A bizarre series of events and my desperate recovery attempt [cliffhanger!]

So I started having trouble after flashing a rom. The old infinite htc boot logo. The troubling part was when I tried to reboot to recovery and TWRP blackscreened and device turned off.
I tried re-flashing recovery.img with identical results.
Now my phone locked while attempting a fastboot flash boot.img with a known working boot.img just in case the rom I flashed had a corrupt boot image.
I left the cmd window open and its been "sending boot.img" for about forty-five minutes now. I am terrified to ctrl+c the command or restart my device.
So boned or no boned?
On a scale of one to boned how boned where do I fall on the bonage spectrum?
Any ideas on what to do next, or if rebooting to fastboot is safe?

You have to wait the final of the sending.
Probably your USB cable is *****d up, and i'm advising you because i had the same issue.
A flash of a boot.img was of 15 mins.

Tried fastboot erase cache to get back into twrp?
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 9.1.0
Bulletproof 4.3

Afraid to stop the current fastboot operation to try to clear cache. Tried running from another window and it just sits there, cursor blinking, like its waiting for the other operation to complete.
Waiting for it to complete seems fruitless as its been almost two hours now for a 5836kb flash.
-update-
Okay so I took a couple valium and quickly switched out the usb cable. The cmd window running the flash operation crashed, but fastboot on the device became responsive again. I feel like this is a fact that might be useful to others in the future.
Fastboot stalls out--don't panic, just disconnect the usb cable...
I'm still scared to reboot it, even to reboot to fastboot. Is fastboot part of boot.img? If this botched op boned up my boot.img is it possible that fastboot might not work after a reset?
Gonna give cache erase a shot and report results.

Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?

hypocritelecteur said:
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
Click to expand...
Click to collapse
After the cache's erase you can boot in recovery.

Guich said:
After the cache's erase you can boot in recovery.
Click to expand...
Click to collapse
Phone still reboots right after TWRP logo is displayed!

hypocritelecteur said:
Phone still reboots right after TWRP logo is displayed!
Click to expand...
Click to collapse
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.

Yeah, I tried that before posting but for sake of thoroughness I did it again.
erased cache
reflashed m7 twrp
erased cache
Going to try CWM now.
Really appreciate the guidance and support in a problem you have no personal stake in. Being on the receiving end of the goodwill of strangers makes me all warm and tingly.
Also switched USB cables and did a fastboot reboot to make sure commands were being passed on... nothing wrong on that front.

Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Aaaand CWM worked for whatever reason.
Odd, since I've never had a problem with TWRP before but plenty with CWM... Every duck has its day I guess.
---
Well... CWM loads properly but executing any command that touches phone data causes a reboot.
Factory reset -> reboot
Install zip from sdcard -> reboot
Trying sideload next... it goes into sideload mode fine. I'm guessing that as soon as it tries to write something it will reboot, but I'll have to wait till I've re-downloaded and double checked md5s like a paranoid bastard first.
adb sideload ohdeargod.zip
---
Hmm, wiping cache partition alone works.
--
Noticed that on booting into CWM it displays the message:
Warning: No file contexts.
--
formating /system alone works
formatting dalvik causes reboot
formatting data causes reboot
--
sideload seems to have worked although its taking a long time to boot. I'll give it another 15 minutes.

Which firmware are you running?

Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Guich said:
Which firmware are you running?
Click to expand...
Click to collapse
Aaaand bingo gringo. It's booted.
Its a tmo m7. I haven't touched firmware afaik.
Resolved just in time for me to take it sailing today and drop it into lake Huron.

hypocritelecteur said:
[snip]....drop it into lake Huron.
Click to expand...
Click to collapse
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4

altimax98 said:
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Okay so I have a brand new HTC TMO One I got last week and its waterlogged. I drilled a hole in the back of the case to drain it and then left it on the radiator to make sure all that moisture is gone. I can't get it to post to TWRP.
Please help.
Deciding after recent events that XDA can be a dangerous place for sarcasm. So--thanks all, problem solved, no, no phone was damaged during the making of this thread. It was just my business partner, Lloyd, who fell in and became waterlogged. No amount of drilling or radiator baking could revive him.
Please help.

[Q] Soft/Hard Bricked, Lost Root, Lost Recovery, USB Not Recognized

Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.

grimzen said:
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. This is completely normal, you should have just rebooted the phone and been done I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. Again totally normal, thats the bootloader use the vol to move down and choose recovery and hit power this will boot you to TWRP I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Why ? Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. You should not have Sync installed only the drivers I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
Click to expand...
Click to collapse
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?

clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.

grimzen said:
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
Click to expand...
Click to collapse
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
flash in recovery
use adb push UPDATE-SuperSU-v1.86.zip /data/media/0
to get the file on the phone
Reboot to bootloader / fastboot USB
and from command line on pc
fastboot erase cache
fastboot reboot

I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?

clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
bihslk said:
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
Click to expand...
Click to collapse
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.

grimzen said:
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
Click to expand...
Click to collapse
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?

bihslk said:
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
Click to expand...
Click to collapse
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.

grimzen said:
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
Click to expand...
Click to collapse
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.

bihslk said:
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
Click to expand...
Click to collapse
I've tried a few different cords and all 3 ports I have still nothing but the HTC manager thing. It will recognize it but only for a split second while booting up but it says HTC BUTTERFLY as the drive and i'm not sure if that's a problem or not but it won't recognize it at all through fastboot.

you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers

bihslk said:
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
Click to expand...
Click to collapse
Ok will try that now. thanks so much for the help.

I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app

jpaulpra said:
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm not familiar with the red triangle screen is there a way to boot into it?

Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk

grimzen said:
I'm not familiar with the red triangle screen is there a way to boot into it?
Click to expand...
Click to collapse
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I think @jpaulpra was telling him to reflash stock recovery
then boot to it and do clear cache.. then reflash twrp

When I got into bootloader, I lost the Twrp recovery. So when I selected recovery I got the screen with a "triangle and exclamation mark". If you leave it will reboot the system after couple of minutes. But if the audio up key is pressed, it will show a system recovery screen, where cache can be wiped
Sent from my LT26i using Tapatalk

bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Basically all I'm trying to do now it's find a way to get my computer to recognize my phone as a drive. When I go into viper settings and go to advance menu (with the short time I have before boot loop) there is an option to mount drive. When I select the option to do so it hands on splash screen and I have to hold power button to recycle back on. Once back in it's no longer selected. I've never seen a boot loop go pay the flash screen. Is this normal?

Pretty SOL with my son's Nabi2
I'm having a issue with my sons Nabi2 pretty similar. I messed up bigtime guys I rooted it and started messing aroung with the system files. Then didn't get a boot afterwards, wiped everything from twrps system, data, the whole shabang! Even lost my root! and access to on board flash cause I've been trying to recover using twrp with absolutley no luck. I still have the original stock unrooted backup saved to my pc from when I first installed twrp. Can someone please help me? I'm really out here trying to reach out for some help. didn't even know where to post this. Thank you guys. Note to moderators: If this is the wrong place to post this then please point me to the right direction and I apologize.