Okay, so I have a slight problem. I was trying to install Cyanogen mod. I followed the directions, first installing the zip from TWRP, then i flashed the boot.img. After that, i tried booting it up. For some strange reason, it wouldn't boot up. it would get to a certain point, then it simply rebooted all over again. After trying a few more things, I finally decided i should reset it to the stock rom. The only problem is, i do not have S-Off, and to get S-Off, i need to boot into the normal mode. I then remembered i could probably do that from the SD card, but when i tried, ADB complained with a permissions error. Upon further investigation, I then found that I couldn't even mount the SD card. I tried using a different version of TWRP, and every other version couldn't even start up. When i tried, it rebooted before actually getting to the recovery. I decided to try CWM. That at least opened fine, but it also was unable to mount the SD card. I also tried flashing the stock rom zip files using the rebootRUU command, but that came up with an "Unknown error". At this point, i think this could all be resolved if i had S-Off, but i cannot do so. I was wondering if anyone knew how to do it with only fastboot, or if anyone had any other ideas on how to get it working.
Thanks in advance.
Related
I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!
Hello,
I am trying to install custom rom and I cannot get anything to flash. I have had the phone rooted and romed before was trying to change roms so i wipped everything and cleared all caches and tried to flash and it came across an error. Tried to fix errors and ended up soft bricking it, fixed the soft brick but now I am back to step 1.
The error i am getting is:
Opening .zip file
Cannot open .zip
aborting
I was using CWM, thought that was the problem so I switched to twmp and still get the same thing. It will not install any zips. I have downloaded tons of different roms and none of them work, also i cannot install the bootloader unlocker or su now because it will not open the zip. I have tried it on external sd card and internal neither work. Any help appreciated.
I figured it out. My external sd card was somehow causing the problem. I removed all important files and formatted it from twrp and restarted and was able to flash again. Dunno how that caused the problem but that was my fix to this solution for anyone else that comes across this problem in the future. Really was a frustrating two days.
Sent from my SCH-I535 using Tapatalk 2
Okay. Here's the deal.
My friend gave me a used HTC One S. My idea was to flash a new custom ROM on it (preferably something like CM12). He told me it was rooted, so it seemed like it was no problem. Although, it was S-On.
When I turned out on the phone, I first noticed some things. It stayed on the "HTC: Quietly Brilliant" logo, however, it had that red "This build is for development purposes only" text underneath it. After waiting almost an hour, I realized something was up. After a few attempts, I was able to get into bootloader and loaded up TWRP recovery. I poked around in the files to see what the issue could be, when I realized something. The phone was Romless! The /sdcard folder was completely empty, besides a TWRP folder. If I moved up one level, the only folders were:
and-sec
boot
cache
data
dev
devlog
etc
sdcard
license
proc
recovery
res
root
sbin
supersu
sys
system
tmp
usb-otg
and they were all empty.
Okay, so it didn't have a ROM. No big deal, right?
My first idea was to use the CM12 installer. It didn't work; for some reason it thought the device was a Samsung galaxy S2?!
So my next idea was to connect it to my pc and transfer files. Unfortunately, since it was in TWRP, it wouldn't show up on my PC so I could edit the files. So, first I tried mounting storage, but it failed, saying "E: Can't mount /sdcard". So, my next idea was to use USB OTG. After putting the CM12 file on my flash drive and connecting it to the phone, it showed up and I was able to browse the files to install CM12. On my first try, I flashed it straight from the flash drive and rebooted. When this happened, it was on the HTC logo for a good minute, then it rebooted again straight into TWRP. After that, I decided that maybe I'd have to create folders inside /sdcard. So, after a few minutes, I created the empty folders Android, Download, DCIM, Pictures, etc. in /sdcard. I copied CM12 into download and flashed it. Instant failure, giving the same "Can't mount scard" errors.
I tried rebooting. But when I did, all the folders I made as well as CM12.zip were gone!
I also tried using adb push and sideload commands. It still did not work. Still got sd card mounting errors.
Interesting. With that, I turned to XDA for help. After reading a few forums, I downloaded Hasson's All-In-One-Toolkit and tried reinstalling TWRP recovery. No luck. After that, I switched the recovery to PhilZ Touch 5. Still, once again, got internal sd errors for mounting.
Not knowing what else to do, I settled on one other option. RUU. After doing some searching online and finding the right RUU, which was RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2 .exe.
I followed instructions online about RUU and looked for a temp file. While I expecting only one ROM.zip, there were two files called rom_01.zip and rom_02.zip. They both had the same files with the same file names in them, the only difference was rom_01. zip was 35 Mb, while rom_02 was 681 mb. I tried both. They'd give me the same "please flush again immediately" the first time, but after flashing again, every time it would give me "signature verify fail."
With that, I am unsure what else to do. The only thing on the phone at the moment is PhilZ touch 5. Mounting storage does not work, and installing via sideload doesn't either. Any help with this situation is very, very appreciated.
I apologize for how long this post was.
http://forum.xda-developers.com/showthread.php?t=1630459
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.
You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.
For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot
Sent from nowhere over the air...
Rapier said:
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.
You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.
For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot
Sent from nowhere over the air...
Click to expand...
Click to collapse
The phone is S4/Ville.
It's on 2.15 hboot as well.
The TWRP version it had was 2.5.0.0.
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.