Please help, I tried to install and it failed, so I did a fastboot oem boot and now the phone works, but I cannot enter recovery, is there anything I can do. I am at a loss, whenever I restart the phone, I have to fastboot oem boot or it will stay stuck in 4 exclamations
I flashed the lboot from that zipfile available at , but now I also cannot enter boot loader.
Ok, I was able to fix all that, by reflashing the RUU again and was able to get it working and successful. Doing the OEM boot removed my twrp recovery, which I had to reflash, and also formatted my sd card.
This was stressful as hell and learned a ton about this phone. The learning experience was worth it, but the stress was not =/
EDIT: WIFI DOES NOT AUTHENTICATE
For those stuck with my problem these are the steps I did.
I reflashed the newer RUU and once everything was peachy, I did a factory reset, that seemed to have fixed everything that was going on with my phone. I then added twrp recovery and reflashed my rom of choice. And that was the end of a very stressful night lol.
nervana1 said:
For those stuck with my problem these are the steps I did.
I reflashed the newer RUU and once everything was peachy, I did a factory reset, that seemed to have fixed everything that was going on with my phone. I then added twrp recovery and reflashed my rom of choice. And that was the end of a very stressful night lol.
Click to expand...
Click to collapse
All the four corner triangle thing means is that it didn't flash the last RUU mode zip completely that was attempted. The phone is still in ruu mode with four triangles. You can simply flash the RUU mode version of TWRP and it will clear the four triangles.
Related
hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.
It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?
I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.
eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?
So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.
Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..
Are you able to get into bootloader?
Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?
same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.
I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.
You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader
So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.
been postponing flashing a ROM for a while, and today i decided to take the big step.
follow everything by the book:
-un-locked the phone as per HTCDev instructions.
-installed twrp 2.6.0.0 recovery
-installed super-user
after all this phone rebooted into a fully restored stock OS.
downloaded CM10.2 (didn't want to mess around with nighties just yet) and copied to phone.
downloaded and copied compatible g-apps.
extracted cm 10.2 to get the boot.img file, and ran the command fastboot flash boot boot.img
didn't get any error messages.
ran the command fastboot reboot.
since then, phone is stuck in splash screen, and won't get past it, wont go into recovery, won't go into boot.....
if i try pressing the vol-down +power button, it will turn off after a while, and the indication light won't turn on if i connect it to the pc.
for the time being, i have managed to get the identification light on again, and put it in the charger.
any help would be appreciated.
------------------------------------------------------------
HTC one s s4
Same thing happened to me. I will tell you what I followed. It was not making any sense to me before but it worked so here it is.
Go into recovery wipe all data including caches 3 times. Now flash the ROM zip again and wipe cache and dalvic cache once. Now reboot.
Really worked for me.
Sent from my HTC One S using Tapatalk
Had the same thing. Nothing worked for me. Had to pay someone to restore to stock. The boot.img is the problem. It corrupts the phone.
I have a one sv which:
is k2 ul
normally boots only to HTC screen (no quietly brilliant) and stays there till the end of times
shows tampered locked, which i now changed unlocked status (htcdev)
s-on
has twrp recovery on, but swipes fail mostly
flashing roms in twrp recovery show success but result is still HTC logo without being quietly brilliant
can not be ruu-ed beucause the ruus i find are i think older than required
hboot 2.21, radio 1.18 version
s-off fails because tho fastboot recognizes phone, adb doesnt in fastboot mode and in bootloader pc thinks it is not attached (tried xp, 7, 8.1 and many different drivers)
i am not sure if usb debugging was on before the phone crashed
so i can't put an older ruu because of s-on, i can't get s-off because rumrunner and moonshine can't work without adb, and basically that is it.
does anyone PLEASE have any idea what to do?
and yes, the warranty is over and the phone has gone to the warranty twice with bootloop before.
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
old.splatterhand said:
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
Click to expand...
Click to collapse
yes i did.
twrp 2.6.3.2
now i have made such progress that twrp tells me it cannot mount int sd and when booting, phone stays on the htc logo for some seconds and then switches off. i believe i have actually made it worse (didnt think that could happen).
EDIT: so i formatted the storage like this http://forum.xda-developers.com/showthread.php?t=2576897 and it BOOTED
EDIT2: the phone now kind of works IF it boots. half of booting times it just switches off, the other half it switches off and then reboots and works. i think something is still kind of not good but i dont have the b***s atm to poke it more.
thank you all for your potential help.
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
old.splatterhand said:
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
Click to expand...
Click to collapse
it was this one http://forum.xda-developers.com/showthread.php?t=2512742 which is, as i understand, your work, thank you very much, donations will happen when im a tincy bit richer
and i will wipe some time later when im at home and courageous enough.
You can also try to restore this TWRP backup.
great news! today the phone restarted itself and froze on the logo. i tried to start twrp but it froze on that logo too. tried to do a factory reset, which removed the "tampered" sign until next reboot but that was about it.
now i can't reflash twrp or anything at all, with the error remote: image update error. oh please save me again.
Does not sound good.
You can boot into bootloader? Is it locked or unlocked? Did you reflash the recovery to check if you can boot into it?
looks bad indeed.
i can boot into bootloader, which is unlocked. and please specify what do you mean by reflashing the recovery (pardon my stupid brain)
When in bootloader, connect your phone to fastboot and try to flash recovery again.
If you can't get into recovery, i don't know, if there is much i can do for you
fastboot basically tells me to go f* myself with the error "remote: image update error" what ever I try to flash. right now Im trying to find a way to reflash twrp from ext sd. not doing so great
Well, about your country flag i suggest you speak (or you can at least read) russian language.
Go to 4pda.ru and look for the posts of "MikG". He has made zip files, similar to RUU. They are flashed from bootloader/Ruu mode. Maybe they can bring your phone back to life.
I can't tell you how to use this files, because i don't speak russian.
I'll try, thanks.
edit: and it just refuses to cooperate. it kind of does something in bootloader, but still doesnt boot past htc logo or if i try recovery, it stays on teamwin logo. i dont know if im doing something wrong or what... maybe i'll wait for the 4.2.2 hboot 2.21 radio 1.18 ruu then because i really dont know what else i could do.
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.