Related
If this is in the wrong area please mods answer and redirect it into the correct area.
I was wondering if your phone is looped at the first bootloader screen and you cannot access recovery or bootloader is there a way to unbrick your device using a code in the adb?
Please answer...... and move if nessasary.
Thank You
I had been running Cyanogen 3.5.2 and then switched to JACHero 2.2 to see the changes. Then when I tried to switch back to Cyanogen and I kept getting the bootloop. No matter what I did, wipe, flash, wipe again, flash again. Nothing. I assume it might have something to do with the Apps2SD setup but I have no idea. I just reflashed back to JACHero and it is working fine.
chuckhriczko said:
I had been running Cyanogen 3.5.2 and then switched to JACHero 2.2 to see the changes. Then when I tried to switch back to Cyanogen and I kept getting the bootloop. No matter what I did, wipe, flash, wipe again, flash again. Nothing. I assume it might have something to do with the Apps2SD setup but I have no idea. I just reflashed back to JACHero and it is working fine.
Click to expand...
Click to collapse
Did you reflash using the ABD. If you did not then you would have to use the recovery or bootloader mode on the device. Therefore not using the abd commands at all. Im not bashing you or anything btw.
about cyan to jachero same happened to me... it has somthing to do with apps2sd your correct. somthing like the .odex files from hero saving on ur sd partion and ruining the whole setup on cyans. so what i did was use paragon partion manager to completely reformat my sd card and then remade my ext3 partion on it. and it works fine. im never switching off of cyans rom thoe. anymore to much of a headache and stuff.
(as you can tell im drunk and i really dont understand all this rom lingo lol bare with me i hope i helped you?)
nickryan0612 said:
If this is in the wrong area please mods answer and redirect it into the correct area.
I was wondering if your phone is looped at the first bootloader screen and you cannot access recovery or bootloader is there a way to unbrick your device using a code in the adb?
Please answer...... and move if nessasary.
Thank You
Click to expand...
Click to collapse
There are other posts on this but if you can't get into recovery or bootloader you are toast adb may not connect(really it should connect to adb when on the boot screen but many have been through this and haven't been able to get their phones working. I bet you tried flashing the Haykuro SPL("Danger" SPL) right?
It is brick you will have to look into a replacement/exchange if possible.
savethechicken said:
There are other posts on this but if you can't get into recovery or bootloader you are toast adb may not connect(really it should connect to adb when on the boot screen but many have been through this and haven't been able to get their phones working. I bet you tried flashing the Haykuro SPL("Danger" SPL) right?
It is brick you will have to look into a replacement/exchange if possible.
Click to expand...
Click to collapse
Oh no was just wondering cause i am thinking about rooting my phone but under the right direction. Not the posts they have here cause they are to hard to follow. If you or someone could help me i only wanna upgrade to a hero that has flash player and can put notifications out like this one : http://4.bp.blogspot.com/_Q-JSg53A3...AFD4/6TWLdeIi3VY/s400/rosie7-lock-screen2.jpg
I also had bootloop when switching back from jachero to Dude's 1.3. I had to pull the battery out to get it to shut down, but then I was able to use recovery to flash Dude's... how is it that you're unable to get into recovery mode? Have you tried pulling ythe battery?
ohnoezmahfone said:
I also had bootloop when switching back from jachero to Dude's 1.3. I had to pull the battery out to get it to shut down, but then I was able to use recovery to flash Dude's... how is it that you're unable to get into recovery mode? Have you tried pulling ythe battery?
Click to expand...
Click to collapse
If you mess up the SPL you can't get into recovery. The only known method of messing up the SPL is with the "Hero" SPL (afaik, without manually trying to brick your phone).
If you get a bootloop, make sure you wiped AND completely cleared your ext2/ext3 partition with apps2sd. That always seems to cause a bootloop.
[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
UPDATE!!!
SO the CWM Ghost is back, once again. Still nothing out of the ordanary done on my part, just started getting random FC's and boom there it's ugly mug is when I go to CWM to fix permissions...
BUT, here is the problem, I'm trying to fix it how I did last time and when I go to flash the new recovery in Fastboot via ADB I get this error:
sending 'recovery' <4000 KB>... OKAY [15.390s]
writing 'recovery' ...FAILED <remote: image update error>
I have tried a few different CWM recovery downloads... any ideas?
dcwiker05 said:
[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
Click to expand...
Click to collapse
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....
faux123 said:
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....
Click to expand...
Click to collapse
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.
dcwiker05 said:
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.
Click to expand...
Click to collapse
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!
irrelephant said:
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!
Click to expand...
Click to collapse
I would say "lucky" as well. but i'm wondering if the 2.x recovery image might be the fix for this problem. If one could "brick" their phone with the same symptoms as this phone. Then flash the 2.x recovery and see if it fixes the problems.
Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!
dcwiker05 said:
Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!
Click to expand...
Click to collapse
Nice i'm going to remember this thread.
TOPSIDE for some new developments. See OP for update...
I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?
hello i need that recovery 2.___ for fix my problem same that! where i cant find_
vabeach454 said:
I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?
Click to expand...
Click to collapse
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.
dcwiker05 said:
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.
Click to expand...
Click to collapse
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.
victorx said:
hello i need that recovery 2.___ for fix my problem same that! where i cant find_
Click to expand...
Click to collapse
Download this navigate to this (C:\Users\YOURUSERNAME\Recovery_2.5.1.2_to_RomManager.zip\sdcard\clockworkmod\download\mirrorbrain.cyanogenmod.com\cm\recoveries\) extract the recovery 2.5.1.2. Rename it recovery.img and try to flash it via adb in hboot (fastboot flash recovery recovery I BELIEVE that is the command I can't honestly remember but a quick google search will yield you a adb guide no problem
TrueBlue_Drew said:
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.
Click to expand...
Click to collapse
I can't push to my device which is the COMMAND problem. Now when I try to push via ADB I get an error saying write---FAILED. I have tried a few other tricks I have been told as well about like repartitionion the cache via ADB and that doesn't work either. So I hope this works for the OP
Hi
I got Nexus S that currently is bricked for a couple of month now :-(....
the phone is I9020T (US phone).
I have a recovery image "recovery-clockwork-5.0.2.0-crespo.img"
But i cannot access the SDCARD whats so ever ..... to put the ROM, i also tried with ODIN in the past ( now i dont rememer...) and it fail as well it seems that when trying to flash the system it got stuck.
The current status of the phone is:
1.It can be boot into boootloader.
2.it can be boot into fastboot.
3.It can be boot into download mode.
But thats it... , when i try to power it regular it just stop in the blackscreen with Google name on it and the lock at the down and stop there.
What can i do ?
Thanks in advance.
Assuming you can get adb to work you should be able to flash the image to the phone straight from a pc. However that's the most help I can offer as I rarely use adb.
Actually just found this guide: http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Read it and modify to your needs, NOTE the part "Installing the ClockworkMod Recovery Image" as I think you could follow that but use your stock image instead.
In CWM did u try to /mount USB storage?
Then put some rom on it, then flash it.
I did try ...
kvaju said:
In CWM did u try to /mount USB storage?
Then put some rom on it, then flash it.
Click to expand...
Click to collapse
Thanks for the quick reply..
When i try to mount USB storage from the recovery i get the following error:
"Unable to write to ums lunfile ( No such file or directory)"
What i am doing wrong ?
Thank,
Tomcat383
Try to lock and unlock your boot loader via adb. Maybe try flashing original stock rom. The nexus s is hard to brick. I thought I bricked mine but turned out to be a hardware issue that was fixed by Samsung under my warranty.
Sent from my Nexus S using XDA App
smoka206 said:
Try to lock and unlock your boot loader via adb. Maybe try flashing original stock rom. The nexus s is hard to brick. I thought I bricked mine but turned out to be a hardware issue that was fixed by Samsung under my warranty.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
What do you mean Lock -->Unlock via ADB ?
And how can i flash the original stock rom with my problem ? ( BTW do you have a link for my Stock ROM ? ,I9020T I9020XXJK1 bootloader...)
Thanks
if you have recovery than u dont have a brick
Ok ...
b1337 said:
if you have recovery than u dont have a brick
Click to expand...
Click to collapse
But this is all I got I cannot flash the phone so I can boot it to any rom ... So maybe it's not a brick but in my case there isn't any diffrence ...
I tried with several ways and still didn't found the problem ..
I cannot mount the USB at all I cannot flash it via ODIN ..
Am I missing somthing ??
Do you have the right drivers installed? Also, is it the right recovery? Like for the i9020t, not the nexus s 4g (I made that mistake, me stupid! )
Sent from my Nexus S using XDA App
tomcat383 said:
What do you mean Lock -->Unlock via ADB ?
And how can i flash the original stock rom with my problem ? ( BTW do you have a link for my Stock ROM ? ,I9020T I9020XXJK1 bootloader...)
Thanks
Click to expand...
Click to collapse
He means to reboot into bootloader (not recovery), then lock the bootloader with "fastboot oem lock", then re-unlock it with "fastboot oem unlock".
There's sticky threads all over the boards with stock roms, radios, and bootloaders.
Sounds like a bad flash storage. It happens often on these phones. Nothing you can do but to send it to Samsung for warranty. They'll do it free of charge.
Unless you're missing something simple...
I tried Samsung without luck....
obsanity said:
Sounds like a bad flash storage. It happens often on these phones. Nothing you can do but to send it to Samsung for warranty. They'll do it free of charge.
Unless you're missing something simple...
Click to expand...
Click to collapse
This is what i think...
But my phone is already out of order for a few month and i got it from over seas and i tried to contact Samsung (UK). but they didn't want to assist.
And they told me to contact US the country that i bought it.
How can i be sure its an HW issue ?
Thanks for the help.
Tomcat383
i got the same problem... after flashing the rom i got stuck at the google image but thank god to nandroid back up and after updating to official image.. now everything working fine
How can I use the same way you did ?
cool_yking said:
i got the same problem... after flashing the rom i got stuck at the google image but thank god to nandroid back up and after updating to official image.. now everything working fine
Click to expand...
Click to collapse
Do you think it's possible for me to use the same procedure , I don't have any backup unfurtenetaly ..
Thanks,
Tom
Personally, I'd try reflashing the recovery as a first step. re-download it from cwm just in case of some weird corruption or something, grab the latest one and double or triple check whether you get the right one for your phone
Flash it, using fastboot, straight from the PC to the phone. Try the recovery again, see if that helps. If you still can't mount anything then, you've definitely got a hardware problem :/
If it does mount, use adb to push over a fresh ROM or a stock ROM and flash it after a full wipe (/system, /data, /cache, /boot and a factory reset)..
Good luck!
Been there try that ...
Erythnul said:
Personally, I'd try reflashing the recovery as a first step. re-download it from cwm just in case of some weird corruption or something, grab the latest one and double or triple check whether you get the right one for your phone
Flash it, using fastboot, straight from the PC to the phone. Try the recovery again, see if that helps. If you still can't mount anything then, you've definitely got a hardware problem :/
If it does mount, use adb to push over a fresh ROM or a stock ROM and flash it after a full wipe (/system, /data, /cache, /boot and a factory reset)..
Good luck!
Click to expand...
Click to collapse
Thanks for the info , but I allready tried this option a few times without any luck ...
So I think it's a HW issue , so my phone is dead ?
Thanks,
Ram
tomcat383 said:
Thanks for the info , but I allready tried this option a few times without any luck ...
So I think it's a HW issue , so my phone is dead ?
Thanks,
Ram
Click to expand...
Click to collapse
When my phone did this I was able to mount it after a few battery pulls. So try doing the procedure to mount USB storage and if it fails pull the battery again. I'd say give it about 100 tries. If it doesn't work it most likely will never mount. However if at one point it will, load and flash a rom. The only problem you will face is again after rebooting you'll have to keep trying to the same way to get pass the Google logo.
I know it sounds strange but this was my situation and that's how I got by until they replaced the unit for me.
obsanity said:
When my phone did this I was able to mount it after a few battery pulls. So try doing the procedure to mount USB storage and if it fails pull the battery again. I'd say give it about 100 tries. If it doesn't work it most likely will never mount. However if at one point it will, load and flash a rom. The only problem you will face is again after rebooting you'll have to keep trying to the same way to get pass the Google logo.
I know it sounds strange but this was my situation and that's how I got by until they replaced the unit for me.
Click to expand...
Click to collapse
OK , thanks i will try this .
By the way did you get the same error as mine when you tried to mount the USB ?
Thanks,
Tom
Nothing worked....
Well i tried everything from here and still nothing work ....
I also tried Lock\Unlock and after going back to Lock when i try to unlock again i see the Unlock choose screen but when i try to choose unlock the phone is stuck on this screen forever...
Is there something left for me to do ????
Thanks,
Tom
tomcat383 said:
Well i tried everything from here and still nothing work ....
I also tried Lock\Unlock and after going back to Lock when i try to unlock again i see the Unlock choose screen but when i try to choose unlock the phone is stuck on this screen forever...
Is there something left for me to do ????
Thanks,
Tom
Click to expand...
Click to collapse
you could always try beating it with a hammer
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys
I woke up and my phone was not turned on, when I did turn it on it turned right back off. So I wen't to recovery to reflash NexusV4from clsa but my /data and my /system could'nt be mounted so I fixed this by changing my file system from EXT4 to EXT2 and once again back to EXT4 on both the system and data, so after all of that I flashed Nexus and it booted up and then I decided to go back to the recovery and flash everything I had on there at once like Dolby Atmos and it would not boot after that it was stuck at the "your device is not trusted screen" so then I decided to flash B180 stock rooted Magisk from madvane20 and now my device with bootlooping and also the recovery splash screen pops up when I want to goto it and then it shuts off and then goes right back to boot
Can someone tell me or help me fix this, I currently don't have a computer for adb but I could use my fams computer. Thanks!!!
My suggestion would be to go back to https://forum.xda-developers.com/huawei-ascend-xt/development/rom-ascend-xt-nexusxt-b160-t3597766 and follow the instructions to get that working again like you had it. You may have to reinstall B160 firmware like instructions say.
Any idea what led to the phone getting corrupted? Be sure to make a full TWRP backup again once you get it working again and good luck
@InfinityXDA,
Were you not having problems with notifications not working with NexusV4 ROM like many reported in that thread? If you were having notification issues, maybe just flash and stick with the stock B160 ROM. Add Xposed, etc after installation.
Everything was fine for me bro @divineBliss
divineBliss said:
@InfinityXDA,
Were you not having problems with notifications not working with NexusV4 ROM like many reported in that thread? If you were having notification issues, maybe just flash and stick with the stock B160 ROM. Add Xposed, etc after installation.
Click to expand...
Click to collapse
I can't flash anything because the recovery does not work, like I said above it shows the splash screen and then reboots to the system and gets back in the bootloop.
Sounds like you need a PC to be able to do use bootloader to reflash recovery and maybe boot and system, then possibly have to flash the entire NexusV4 with TWRP depending on what happens after that.
InfinityXDA said:
I can't flash anything because the recovery does not work, like I said above it shows the splash screen and then reboots to the system and gets back in the bootloop.
Click to expand...
Click to collapse
divineBliss said:
Sounds like you need a PC to be able to do use bootloader to reflash recovery and maybe boot and system, then possibly have to flash the entire NexusV4 with TWRP depending on what happens after that.
Click to expand...
Click to collapse
Well crap I'll use my fams pc I guess
You're going to need to use fastboot at the very least.. I believe you can get to it via holding volume down and the power button. Then it's just a matter of hooking it up to a pc (only way otherwise would be usb otg or specialized equipment none of us have), and running the necessary commands to install twrp. I usually boot to new recovery first, though, to make sure everything works - file corruption is a lot rarer than the old days,but it still happens
-n0cturne- said:
You're going to need to use fastboot at the very least.. I believe you can get to it via holding volume down and the power button. Then it's just a matter of hooking it up to a pc (only way otherwise would be usb otg or specialized equipment none of us have), and running the necessary commands to install twrp. I usually boot to new recovery first, though, to make sure everything works - file corruption is a lot rarer than the old days,but it still happens
Click to expand...
Click to collapse
Do you think corruption happened??