TWRP installed but nothing else, how do I install a ROM now? - XDA Assist

Long story short, as title says, after trying to desperatly fix my phone and having troubles with various ROMs I ended up wiping eveything because in desperation.
At the moment the only thing that appears to be working is TWRP, everything else is completely wiped so I can't seem to push files to the phone or activate the USB debug mode.
I don't know how to push files (like the ROM Zip ) to the memory since unluckly it doesn't have an external SD or how to flash em directly to the phone, is there a way to fix this problem?
I have a Galaxy Nexus GSM (Samsung I9250).
TWRP v2.8.7.0
Windows 8.1
Phone drivers should be installed since I could use the phone fine before, but I'd like to know if there is a way to be sure of that.
Last note, even reverting the phone to it's original state and ROM would be fine, atm I just need an usable phone!

Related

[Q] NS4G is possesed

I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??
Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.

I finally made it, Soft-Brick in another Way... -.-

Yeah, i finally made it. I bought a TMO-DE One S (With S4 Processor) 5 Days ago, unlocked the Bootloader (HBoot 1.09), rooted and SuperCID´d it, installed CWM Touch and installed TrickDriod V8.0 incl. its Tweak Package. After that i installed another Radio and everything was fine. It could have been SO easy, but i just HAD to do more, and now its soft-bricked.
At all TrickDroid is a really good ROM, but i hated the thingy that it shows G symbol instead of H when getting HSPA speeds. So i decided to dump it and go for a 4.0.4 / Sense 4.1 Stock Rom without branding instead until a JB / Sense Rom comes out. And thats were the trouble started. i flashed the stock rom with CWM, installed the boot.img that came shipped with it and booted it up. I did a full wipe before flashing. It booted up, Sense Stock Background Image came on and it showed "Unfortunately Wiper App is closed" at the "Preparing phone storage" stage. After OK´ing that another Screen came up about some system service wouldnt respond (dont know the exact Text anymore) wich i could close or wait for it. No matter what i do, or if i do nothing, after ~20 seconds the phone crashes and restarts. After the first restart the phone only boots into a black screen but with the Android bar at the top is working with time, battery-charging and a warning smybol. But the Phone wont react to anything i do except for lockscreen button. When its "online" i can push files via adb to the internal SDCard so i thought it wouldnt be a big problem. i pushed ONE MaximuS V2.5 ROM to the SD Card, booted into CWM and installed it. then flashed the boot.img of it via fastboot and booted it up. but nothing happens. still black screen with bar on top and not reacting phone that reboots every 20 seconds. i allready tried full wipe, cache wipe, dalvik cache wipe and i dont really know what to do now.
A broken SD Partion cant be since i can push files via ADB to it and install them with CWM. But whatever i try to install every ROM boots only in this blackscreen. its clearly not hanging in bootloader, but in android itself. I dont really know what to do, and returning to my dealer is no option since Rooting, SuperCID´ing and flashing another ROM. You maybe have a Idea what to do now?
Peace
TK
PS: Sorry for my bad english, hope you can understand it
Edit: Okey, i got something. i formatted everything i could in CWM, and now (as its now supposed) it hangs in bootloader since no system is there for booting. The good thing is in CWM i get ADB Connection so i can still push files to the SDCard. Im now trying installing a ROM again. So at least i have a starting Point if it fails again
Edit 2: Okey, found it. The "Stock" ROM is broken, not my Phones Fault. and MaximuS just doesnt install right so nothing was changed. Installed TrickDroid again for testing and everything is fine again. Close this one...

[Q] I've tried everything and looked everywhere

Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.
Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.
You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.
I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.
If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.
To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.

Original Shield Tablet (WiFi) bricked or kill-switch engaged?

When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet

LineageOS mtp not working, twrp lost after flash, cant boot to twrp from fastboot

hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..

Categories

Resources