Hi guys,
I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.
HELP HELP HELP HELP HELP HELP HELP HELP HELP
Jz flash any cm rom zip just a soft brick easily recoverable
Shibazeet said:
Hi guys,
I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.
HELP HELP HELP HELP HELP HELP HELP HELP HELP
Click to expand...
Click to collapse
adb push a rom zip onto your sdcard and flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
adb push a rom zip onto your sdcard and flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Can you sideload in TWRP?' It's even faster than pushing for the unpatient folk like me. lol
And yeah jd I still have the Rocket.
that was his first and only post, i bet he wont be back. sounds like a root toolkit child.
How?
Having said that I cannot detect the phone in the PC, how can i put the ROM in a folder?
Guess what? He's back!
@Shibazeet
You need to follow this thread to setup adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2588979
Use NRT nexus root toolkit 1.8.4
& recommend to install stock image nexus from official google website , just search " stock image nexus 5 "
SORRY FOR MY BAD EN !!
Sent from my Nexus 5 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2277112
Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.
Lokke9191 said:
http://forum.xda-developers.com/showthread.php?t=2277112
Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.
Click to expand...
Click to collapse
My friend, you don't use fastboot to flash "ROMs".
Sorry woke up 5min before writing that. Running on 4hrs sleep now. Meant use fastboot to install stock image, flash a recovery. Then use custom recovery to flash future roms. Just pointing him in the right direction. With a little reading, he'll figure it out.
Related
hey guys i tried rooting my nexus s and now when trying to boot up the phone im stuck at the google boot screen with the unlocked padlock at the bottom. i can get into clockwork recovery and i flashed super user but i cant get onto android OS is there anyone who can help me please?
Have u installed a rom from zip?
Sent from my Nexus S using XDA App
Also, you should specify which nexus S version you tried to root and which guide you followed.
jj, u need to flash new ROM of your choice from zip file under CWR.
The reason why u stuck on the Google screen is cos when u rooted and unlocked the boot loader u also erase all data including the stock ROM. But u should know that cos its mentioned in every root & bootloader unlock procedure
So just go into Nexus S Android Development where u can find and download the ROM of your choice.
After just boot into CWR and install the ROM from .zip file.
U will find whole procedure how to flash it under every ROM thread.
addles said:
hey guys i tried rooting my nexus s and now when trying to boot up the phone im stuck at the google boot screen with the unlocked padlock at the bottom. i can get into clockwork recovery and i flashed super user but i cant get onto android OS is there anyone who can help me please?
Click to expand...
Click to collapse
rikardo1979 said:
jj, u need to flash new ROM of your choice from zip file under CWR.
The reason why u stuck on the Google screen is cos when u rooted and unlocked the boot loader u also erase all data including the stock ROM. But u should know that cos its mentioned in every root & bootloader unlock procedure
So just go into Nexus S Android Development where u can find and download the ROM of your choice.
After just boot into CWR and install the ROM from .zip file.
U will find whole procedure how to flash it under every ROM thread.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't erase the existing os..it just wipes all the data and apps. It would still boot into the stock Android image until he flashes a custom ROM.
Sent from my Nexus One using Tapatalk
Rooting & bootloader unlocking procedure wipe EVERYTHING from the phone or am I wrong ?
Read here >>>http://forum.xda-developers.com/showthread.php?t=895545
When I did my NS 1st time I had the sake situation until I've flashed new ROM
uansari1 said:
Unlocking the bootloader doesn't erase the existing os..it just wipes all the data and apps. It would still boot into the stock Android image until he flashes a custom ROM.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus S using XDA Premium App
rikardo1979 said:
Rooting & bootloader unlocking procedure wipe EVERYTHING from the phone or am I wrong ?
Read here >>>http://forum.xda-developers.com/showthread.php?t=895545
When I did my NS 1st time I had the sake situation until I've flashed new ROM
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
No. It wipes the sd and all user data. It has the same effect as using stock recovery to do a factory reset.
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Tried flashing another version of the recovery?
The K-Zoo Kid said:
I am on brainmasters miui rom, and whenever I try to go into recovery the phone just gets stuck on the Google logo and doesn't move, forcing me to pull the battery. I have tried reflashing the recovery numerous times and idk what to do from here. Any help would be greatly appreciated.
Sent from my Nexus S
Click to expand...
Click to collapse
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
+1
I also made the experience that flashing recovery through rom manager doesn't always work...had the same problem, also using brainmaster's MIUI rom.
simms22 said:
reflash recovery. did you flash recovery through rom manager the first time? flash recovery through fastboot.
Click to expand...
Click to collapse
How would i go about doing this?
Check the rooting guides for the directions.
Sent from my Nexus S 4G using xda premium
I tried looking for directions on how to do it and for some reason I can't seem to find them.
Sent from my Nexus S
You obviously didn't try very hard
http://forum.xda-developers.com/showthread.php?t=1067813
[REF] Complete List of Roms | Kernels | Rooting/Other Guides for Nexus S (GSM)
I am not linking you to the direct directions, but I hope you will find your answer by finding a root guide from the first post.................
Sent from my Nexus S 4G using xda premium
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
zenithz said:
I got the same problem after flashing the Clockworkmod 5.0. Then I flashed the 4.0x version (found in the rooting guide on XDA) and it's now working smoothly
Click to expand...
Click to collapse
You should make sure you are erasing the old recovery before flashing a new one. This can be done as a fastboot command or through the advanced options in rom manager.
Sent from my Nexus S 4G using xda premium
I accidentally flashed the auckf1 radio on my i9023. And I'm not able to flash into any thing else. I keep getting a signature error. Please help. Thanks in advance.
Sent from my Nexus S using XDA App
Someone? My phones turned into an android iPod touch.. please help
:/
Sent from my Nexus S using XDA App
I did the same thing with my I9020T, I accidentally used the 4G one click unroot and it installed a 4G rom on my T-mobile NS. Now when I try to flash a stock rom for the I9020T it gives me a signature verification errror, I'm still trying to figure it out
I haven't tried it out yet but I have a theory. The recovery on my phone I realised is the default Google one. Not CWM so I'm gonna try and reflash CWM and try to install an i9023 stock rom.
It you have a comp around try it would you? I'm not getting home for a while :/
Sent from my Nexus S using XDA App
Go get the correct rom then rename it to update.zip move it to the root of your sd
Go in stock fastboot mode
Go to recovery hit the power button and when you see the the android question mark guy hold volume up and power
Go to apply update.zip and when your on your correct rom do this process to flash any stock rom
You should just flash the correct ICS rom ,good luck and please read read and when you think you got it read some more
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Another way I can think of is to flash koushs recovery img in fastboot mode and restore one of your backups, hopefully you didn't delete them because there still there but you have to fastboot flash recovery recovery.img to see them
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I tried using the default Google recovery to flash back. Hopeless. I keep getting the security error. I'm pretty sure Koush’s cwm will be able to fix it but I need a damn computer!
Sent from my Nexus S using XDA App
Solved. I flashed CWM. Flashed a rom(CyberGR) and a baseband(XXKB3) and I realized my efs was screwed. I restored my efs with Root explorer. And done. Problem solved.
I have the same problem too, and I used this http://forum.xda-developers.com/showthread.php?t=1396224 to boot using recovery mode. It works!
Hi all,
Got mine today, tried to install a ROM and it got stuck in bootloop.
I did a number of stupid things not to mention wiping the SD and im in serious trouble.
I can get into bootloader and CWM but thats it.
Ive heard restoring a RUU can cure it but I have a MAC and cant find anything to help.
Can anyone help? Im gutted....and fell like an idiot.
Ive got an S4 on the three network.
Thanks
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hi,
It enters into bootloader but then what?
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
blackcell1 said:
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Its sent and wrote the recovery file but what now?
mikejasonsmith said:
Its sent and wrote the recovery file but what now?
Click to expand...
Click to collapse
Specifically you'll have to flash the ROM zip file from the recovery and then use fastboot flash boot boot.img.
You can find boot.img inside the ROM zip file
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
mikejasonsmith said:
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
Click to expand...
Click to collapse
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
mikejasonsmith said:
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
Click to expand...
Click to collapse
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
mikejasonsmith said:
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
Click to expand...
Click to collapse
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
mikejasonsmith said:
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
Click to expand...
Click to collapse
so ive managed to get the h3g rom and flashed rom and boot.img.
locked bootloader and run RUU but i keep getting error 155???
Somebody please help me before this thing goes out of the window.....:crying:
Search adb push
Sent from my HTC One S using Tapatalk 2
danevianta said:
Search adb push
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Finally seem to have done it and managed to RUU
The phone is locked to 3 but as a noob I spent 2 days flashing a generic euro ROM.
When i realised i need a ROM to match CID i downloaded 1.53. Tried this a number of times with no joy.
Just tried 1.78 and it seems to be working
Thanks to everyone for your help - us noobs must be sooooooo annoying.
Htc One S bricked
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
FaLLeN_BtB said:
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
Click to expand...
Click to collapse
Bootloop does not mean your bricked...means you need to fastboot flash boot.img
Sent from my HTC One S using xda premium
blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
This little post just pulled me out of missery. Love ya man!
all you guys getting sorted
make a nandroid and sdcard bu NOW and put them on pc,
obviously leave a copy of nandroid on phone also
makes it a lot easier if you get in trouble again
and you/we will
Mounts and Storage --> Format everything --> Now Mount USB Drive --> Put Gapps and ROM
Flash it, erase cache & and Dalvik...Blah blah blah. Flash boot.img in fastboot, and there you go.
Everybody, please remember this and there won't be noob q&a anymore...
TWRP v 2.2.2.1 I can't flash Jelly Bean 4.2.2 .zip on HTC one s (s3)
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
mikebryant2807 said:
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Click to expand...
Click to collapse
See other reply.
So I installed the lateat CM12 nightly, wasn't really impressed yet and went to go restore my backup and once it's done restoring, it get stuck at the bootscreen animation. Just keeps going and going abs going. I used the latest cwm touch recovery as CM12 is not compatible with MultiROM. I would just flash the factory img back but my computer decided to it doesn't ever want to recognize adb avid fastboot on Linux.
Anyone know where I can find a flashable zip for the factory 5.0.1 ROM? Any help would be appreciated!
Try googling Nexus 5 factory image...
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Niflheimer said:
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Now I'm assuming I'd have to unroot it and flash stock recovery and lock the bootloader to get it to update to 5.0.1?
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
jd1639 said:
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I was talking about the 5.0.1 update but thanks.
Niflheimer said:
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
Click to expand...
Click to collapse
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
asd87 said:
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
Click to expand...
Click to collapse
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
asd87 said:
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
Click to expand...
Click to collapse
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
asd87 said:
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
Click to expand...
Click to collapse
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I've spent hours trying to get it work one night. I'll do some note searching for more advice and again thanks.
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did some more digging, got it install, and flashed the factory img for 5.0.1 and twrp recovery then superSU through twrp.
Mods please lock the thread thanks.
Get wugfreshes Toolbox. It has access to all factory images. Some people are not fans of "one click solutions" but this has never let me down.
There's a flushable zip on here also. Put it in a search in the app and you should come across it. It IS the full version.
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
one7dchevy said:
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
Click to expand...
Click to collapse
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
asd87 said:
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
Click to expand...
Click to collapse
Yea figured something like that.
Got TWRP installed, will try to update after my next nandroid restore so that any old CWM users will know..