Related
Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???
Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.
matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!
Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2
gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium
Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.
xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2
wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2
Hi all,
Apology if this questions may already been ask millions of time but I am really stucked at the moment and hoping that someone may guide me to the correct direction.
I have got HTC One X-LTE (Evita)
I managed to get S-OFF and also CID - 111111
It has TWRP 2.6
The last time I got it working was on the STOCK 4.2.2 I downloaded from the XDA - then I got into the issues of rebooting and loosing signal from time to time. so I went into my TWRP backup I had and reflashed it using my old backup made from my TWRP.
the reflashed failed and now I can only boot up to the HTC logo and then black screen.
I can get to the TWRP recovery and I have got fastboot and ADB on my PC.
When I run the fastboot devices command --> it shows device connected BUT when i try ADB command ---> no device is found.
It will be much appreciated if someone can guide me to the right direction as I am really stucked at the moment not sure where to start.
I tried searching in the forum but I don't think I went to the correct area/tutorial.
Please help
Thank you
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
ImagioX1 said:
When you made your twrp backup did you select system,data, and boot? If it's hanging at the HTC screen it seems there is not boot.img installed or one that is incompatible with your backup. Open whatever Rom your backup is made from and copy the boot.img to your fastboot directory. Then reboot the phone into fastboot mode and flash the boot.img using this command.
Fastboot flash boot boot.img
Then reboot the phone and see what happens
Sent from my HTC One XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
ardabelati said:
Thanks for the reply.
When looking at the TWRP backup I copied into my PC - does not have the .img - the one I can find is MD5
Can I use the existing ROM I donwload from XDA like : EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip
when I extracted EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.zip - I can see the "boot.img" can I use this one?
Thanks
Click to expand...
Click to collapse
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
sandys1 said:
I had a somewhat similar experience with Viper 4.0 ROM - I managed to get Cyanogenmod installed correctly (particularly this one). Take a shot and see if it works - atleast your phone will be up and working.
Click to expand...
Click to collapse
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
hmm - Im on ROM dated 09/13, which is not present now. Your best bet would be http://get.cm/get/aOM
Also remember to flash Google Apps (play store, etc.) which is packaged separately here - http://goo.im/gapps/gapps-jb-20130813-signed.zip
ardabelati said:
Hi Sandy,
I tried the link but I think it is broken link.
Can you please let me know which one is the link .
Cheers
Click to expand...
Click to collapse
Did it work finally ?
sandys1 said:
Did it work finally ?
Click to expand...
Click to collapse
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
It sounds like it might be a bad download or something. I noticed u never mentioned wiping the phone before flashing, Are u clean wiping? And also what hboot are you on?
Sent from my HTC One X using xda app-developers app
ardabelati said:
Hi Sandy
Thank you again for your help
I finally got my phone at least booting again.
What i did was I went to the fastboot and then correct to the PC and when it was asking for format the drive, I did format it (fingers crossed) and luckily it let me see the ROm I downloaded from the Stock 4.2.2 Turge version.
Now my problem is that the phone keeps rebooting.
I don;t know how to flash the kernel as suggested on the front page of the thread.
What is the most stable ROM at the moment?
I want to learn how to flash and fix this - I have kept reading post after post but I still can not get myself to where I want it to be which is fixing the reboot issue from the STOCK 4.2.2 Turge version.
I am a real newbie so I am not too familar with some of the fancy terms people use.
Any help is greatly appreciated.
Thanks again
Click to expand...
Click to collapse
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
timmaaa said:
You can either flash the kernel, which can be found in the Android Development section, flashing the kernel is just like flashing a ROM, just install in Beastmode. Or you can upgrade your firmware to 2.15, the instructions are I'm the first post of the ROM thread.
Asking which ROM is best/favorite/most stable is against the rules so we can't answer that question.
When you say the phone keeps rebooting, does it ever make it into the OS or is it boot looping (showing the boot animation then starting over)?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply
When you said that flashing kernel is the same as flashing ROM, I did it By going to TWRP and the press install and locate the zip file. Is this what should be done?
What is beast mode?
Sorry for the basic questions
Thanks
Yeah that's how you install the kernel. It must be done after you install the ROM. I kinda worded my reply a bit weird, sorry about that. Beastmode is the name of the kernel, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2165880
Sent from my Evita
I did try to flash it through recovery but it always failed. Not sure why. I copied the kernel zip file into my phone sd and then I went to recovery and press the install and located the kernel zip file but still failed.
Sent from my HTC One XL using Tapatalk 2
Which recovery version are you using?
Sent from my Evita
Recovery is 2.6.3.
The process failed on not able to fine the MD5 file or something like that. We don't need to extract the Zip file do we?
Cheers
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
timmaaa said:
Disable md5 checking in settings. You never need to extract a kernel or ROM zip.
Sent from my Evita
Click to expand...
Click to collapse
I have checked the setting in TWRP and nothing is ticked.
When I flash the zip, it is still saying "failed due to md5 does not exists".
I am not sure which should be address first but I now noticed that there is an error : "unable to locate storage device"
also came out.
When I plug my phone to PC I can see the storage but why it is saying "storage device not found" in TWRP?
Thanks