[FIXED] Can't flash roms - Asus Eee Pad Transformer Prime

I am unlocked, rooted, on the latest TWRP. And can't flash any roms. Every time i do a wipe and go to flash it immediately tell me failed. However I can flash my recoveries. TWRP doen't see my internal storage (sdcard). But does see my external and I still can't flash from there. I am stuck on energize rom 4.1.1 How do I get past it? Mind you I am sitting on a mil base in Iraq net is slow but I still try.

Related

[Q] Flashed Custom ROM and Kernel, Now Can't Access Internal SD

Hoping someone here can help me fix this problem without having to RUU and start all over...
I'm S-On with 2.09 HBOOT.
I had been running MeanBean for the last 6 months or so, but decided to finally give an AOKP ROM a try because I wanted to check out HALO. First, I did a Nandroid backup of MeanBean using TWRP. Then I downloaded the latest DirtyUnicorns build, placed it in on my SD card and flashed through TWRP (2.3.1), inlcuding the attached GApps and the CM10.2 data fix. It wouldn't boot at first, and I realized that my old kernel for MeanBean was Sense-based, so wasn't compatible with AOKP. I extracted the boot.img file from the ROM and flashed using fastboot. After that I was able to boot up and was up and running with Dirty Unicorns on Mazda's supplied kernel.
DU is pretty awesome and there is so much to do in the ROM, plus HALO is awesome. I wish that was incorporated into every ROM. But my battery life the first couple of days left much to be desired. Even using Kernel Tuner to underclock with screen off and Llama to turn stuff off when I didn't need it, I was approaching 30% by lunchtime. So in an effort to try and fix this, I tried to flash the latest Haunted HC kernel (DU thread says people have flashed this and it runs) through Flash Image GUI since I am S-On. Unfortunately, the phone went into a boot loop after this and wouldn't get past the HTC screen. When I got home I reflashed the DU kernel through Fastboot, but then my WiFi wasn't functional.
After trying to flash a few times and it not working (WiFi still broken), I decided to just go back to MeanBean using the Nandroid. Used TWRP to do this, but then the phone wouldn't boot past the HTC screen after this. Was stuck at my girlfriend's and didn't have fastboot available, so I reflashed DU off of my SD card and it booted up and runs, but now I can't access my internal storage. This means I can't use Swiftkey and the Gallery app isn't functional either. When I try to mount internal storage in TWRP to reformat it, it just says internal storage cannot be mounted. Does anybody know how to fix this??? Everything I could find on here says that I should be able to mount using TWRP at least, but I can't even get that to work.
TLDR - Been flashing ROM's/kernels and now can't mount internal storage.
FIXED - Was able to use Rumrunner to obtain S-Off (had attempted while on MeanBean and would not work), then updated recovery to the latest TWRP and used the Advanced Wipe feature to reformat the internal storage. After that, I just reflashed DU and was up and running. Only issue I had was phone lost connectivity to Sprint, so I had to go back to MeanBean just to update my profile.

Mega...semi-bricked??

So I have a Sprint Galaxy Mega and it seems as though it may be semi-bricked. It will not boot past the GALAXY MEGA logo. It will just continuously power cycle to and from that logo. If I attempt to put it in recovery, it will say "RECOVERY BOOTING" in blue letters as usual, then power cycle right back to the GALAXY MEGA screen. It will boot into Odin mode and accept Odin files, but after attempting do do a typical "stock Odin" scenario, nothing has changed. I looked around for the Pit but cannot seem to find it. Does anyone has a reliable link to the latest Odin stock restore and the PIT file that matches it?
Maybe an error with your system data. So you can't reboot into recovery ? If you can try to wipe data and cache and reboot.
It may be an abnormal re-partition when flashing stock rock, and then I can't help you (have the i9205 international model). Some members of this section have the Sprint version, try to send them a PM if nobody can help you
Nope, no recovery. I was considering flashing a custom recovery to it to see what it does but I don't wanna kill the phone any more than it already is...
Yes I understand. But flashing custom recovery can solve your problem, only if you can boot on it. I think it can't make more damages to your phone, he just always stuck on boot phase like a brick, but if you don't want to try, wait for a developer making you a PIT file. More safe, the Galaxy Mega have a too poor development support for risk anything...
Well I went ahead and flashed TWRP to it. It will boot into TWRP just fine. Tried flashing the stock L900 ROM zip and it still won't boot.
Well I installed a custom ROM, SlimKat, and the phone boots. If I install the stock ROM located in the following link, OP's signature, the phone goes right back to bootlooping. ???
I need either the stock ROM or a ROM with dialer codes because this phone will be flashed to a regional carrier.
what recovry version you use bro. maybe recovery problem. try use your custom rom to flash another recovery from philz. the latest one. some time recovery dont work properly to downgrade from 4.4.2 to stock 4.2.2.
Great, so with Philz Touch Recovery, I never had problems for downgrade and I do this often for testing roms. Now it should not bootloop if you reflash stock.
I am using "CWM-based recovery 6.0.4.7"
I will try Philz recovery
After trying Philz recovery to flash the stock file I found, it once again bootlooped. Is there another stock ROM floating around somewhere or possibly a custom ROM that has dialer codes such as ##3282# enabled?
No idea... But actually the most complete stock based custom rom is MegaFire I think. Flash V5 (not V5x !) it should be enabled.
I don't see what is the problem while flashing stock rom... Oh ! Maybe you haven't enabled USB Debugging, I forgot to do that one time and I had some issues, in case you try to flash a firmware where Knox or others features are on with a modem without these, may cause bootloop. I've searched for 2 days before solve that little problem...
Have you tried another firmware ? If you can flash custom rom, something went wrong before flash... Odin folder is complete ?
Strange...once again a boot loop after flashing the MegaFire ROM
I'm almost certain I need the PIT file. I cannot find it anywhere.
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
I'm having the same problem too dude, I
I download n flash all.the firmware I could find online, since I have no idea what the country of origin is. But most of them work, but no WiFi, Bluetoothand the sim card slot don't read
VirtueToVice said:
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
Click to expand...
Click to collapse

[Q] I am about to give up. There must be a solution but I cant find it

Hi everyone
My sister updated her MEGA OTA last month. She cant remember which version she was on. I am assuming it was 4.3. shes doesnt know much,
Her phone got stuck in bootloop.
Initially a got a hard time even getting into restore mode. however after a lot of goggling and trials and errors here is where i am today :
1- I can install TWRP and/or Philz recovery and boot into them.
2- I can enter download mode
3- I have tried installing many ROMS and different versions. I was only partially successful with 4.4 versions because I get a passed message in Odin however upon restart the phone enters boot loop again.
4- I have tried multiple wipe data/dalvik cache/cache and restoring factory settings but i still get the same results.
5- Only in Philz recovery i can mount the external SD card and copy zip files. I was able to root the phone that was (but im not sure if it still is). However all ROMs zip files I tried to install (both from PC and from extSD card) wouldnt open in recovery mode.
Because I get a passed message when I install a ROM from Odin , I dont know what the issue could be. But there is something wrong that happens as soon as this phone boots up.
I seriously do not know what to do anymore. I just need this phone to be working again. At this point I dont care about warranties/ROM versions/stock or custom...
Please help and sorry for my bad English
It sounds like you need to download the stock rom and flash it in Odin (you gotta put the phone in download mode to flash in Odin). The stock rom can be found on the sammobile website in the firmware section. That should get you back to square one (stock rom, stock recovery, no root). Then you start over from scratch.
Sent from my SGH-M819N using XDA Free mobile app
Thanks
I did and I still get the same problem.
In fact after installing stock rom, i could not enter "stock" so I installed philz recovery, logged in philz and wiped cache a couple of time, did a factory reset.
and yet when i restart , the phone is stuck in bootloop.
Maybe she has a Galaxy Mega with a repaired screen. Starting with 4.4 Samsung only supports a digitizer with Synaptics brand chip. It's a big mess and there are countless screens and digitizers made worthless. I think unofficial 4.4 by Cyanogen and others might work, but not official Samsung. With some Galaxy Megas you get a bootloop. With others it boots however the digitizer and touch functions no longer work. I don't know how to go back after you are on official 4.4 because last I saw, there was no root for it. If I'm wrong, someone else please clarify and continue to help.
IMHO only one way out from such situation is try to flash MegaFire MJ2 which is derived from stock 4.2. It's only one 4.2 ROM which can be safely flashed onto KK.
Iformation about MegaFire you can find HERE

Phone won't install a ROM.

Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.

Stuck in boot loop and internal storage is 0 MB(TWRP) and I can't conect to PC

Hi,
I have seen topics where people discuss similar problems to mine:
https://forum.xda-developers.com/galaxy-s3/help/stuck-boot-loop-internal-storage-0-mb-t3057201
https://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
https://forum.xda-developers.com/showthread.php?t=2391616
But the thing is that I can't connect to my PC because my connection port was broke too. I have recharged my battery with an external recharging.
Is there any way to install the RESCUE FIRMWARE without Odin using only an SD? Or some other solution?
Tks
Needs more info. Rooted? Stock? Recovery? Android version? History? Is it a proper I9300 or a variant?..
As far as I know there is no way to flash stock files from sd without using mobileOdin. This could be where you come unstuck in the attempted recovery of your phone.
I presume you have a lot of "e: failed to mount xxx" errors appearing in recovery mode. This along with the 0mb issue could be the phones final moment from nand failure. But it may not. It could be a fault with the recovery as it is recovery which mounts the filesystem for the os to boot. Therefore we blame the recovery.
If you have a custom rom you can only try this with official CUSTOM recovery cwmr or twrp as these are known 'trusted' but in my view the only recovery we can trust is stock. If you flash a stock recovery with a custom rom you'll instantly kill it.
Custom rom + stock recovery = bad idea!.
If you have a stock rom on it you can try any of them but inevitably you need to end up with the stock recovery.
So the plan is:
In recovery mode:
Custom rom = flash either cwmr or twrp official (make sure they work with that rom!). You can even try a downgrade of the recovery.
Stock rom+custom recovery = flash either an official custom recovery or the official stock recovery. I would do twrp to cwmr to stock.
Stock rom + stock recovery = flash the same version stock recovery as what is already on it.
If none of those work then your phone has officially handed its dinner plate in.
If you cannot enter recovery mode then see the previous sentence.
Hi, thanks.
It is a proper I9300. I have lineage 14.1 installed.
And I can't access the sd card. It is saying that has 0mb. I can't wipe or install anything neither. The only thing that I can do is enter the recovery mode using twrp official. It shows some folders, but with nothing on there.
In that case I'd try to flash another custom recovery that isn't twrp and see how far it gets. It cant get any worse than it is now except for permanent power off.
DO NOT flash the stock recovery.
If that doesn't work then official firmware is the only chance and your usb is borked...

Categories

Resources