Related
please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
im trying to install this ROM on my Sensation: http://forum.xda-developers.com/showthread.php?t=1098849 (ARHD) - the ICS version.
So im following the instructions it points to here:http://forum.xda-developers.com/showthread.php?t=1192300
So my phone was running stock gingerbread. So i follow the instructions.
I successfully S-off the phone.
Then i did the PG58IMG.zip thing --- successfully updates --- but now the phone is in boot loop?? it says there it should reboot to home screen? I can still get to the bootloader menu but recovery or any of those options dont work?
I have tried googling but all those threads get so technical. I AM A COMPLETE UTTER AND DISGUSTING NOOB.
Please can someone give me a step by step easy to understand directions to fix my phone? please please?
To be honest the same thing happened to me when i first flashed an ICS rom.
What i did was that i connected the memory card to my PC using an adapter and deleted the PG851MG file.
Then i moved on to flashing my ICS rom (Virtuous inquisiton) and it worked out quite good.
But traditionally it should boot back after flashing the firmware.It has never happened to me again.
Thats my experience. I dont thnk tat nething should go wrong, but still the phones at your own risk. Do go thru other posts in the forum b4 u do nething.
debarox said:
To be honest the same thing happened to me when i first flashed an ICS rom.
What i did was that i connected the memory card to my PC using an adapter and deleted the PG851MG file.
Then i moved on to flashing my ICS rom (Virtuous inquisiton) and it worked out quite good.
But traditionally it should boot back after flashing the firmware.It has never happened to me again.
Thats my experience. I dont thnk tat nething should go wrong, but still the phones at your own risk. Do go thru other posts in the forum b4 u do nething.
Click to expand...
Click to collapse
I deleted the file after and it still boot loops.
How do i flash my ICS ROM? the guide says to put the ROM and the "superwipe" zip into the root of the SD card and boot load then select "install from ZIP on SD"...but nothing comes up???
Ohk here are the steps u need to follow.
1-Turn Off ur phone
2-Boot into boot loader (by holding volume down + power button)
3-Select Recovery
4-select instal zip from sd card
5-Select SuperWipe.zip
For flashing the rom follow the above steps again and just select the rom u want to flash at the end
debarox said:
Ohk here are the steps u need to follow.
1-Turn Off ur phone
2-Boot into boot loader (by holding volume down + power button)
3-Select Recovery
4-select instal zip from sd card
5-Select SuperWipe.zip
For flashing the rom follow the above steps again and just select the rom u want to flash at the end
Click to expand...
Click to collapse
When i select Recovery the HTC logo comes up then a logo of my phone with arrows and then my phone with a red triangle and a exclamation mark....thats it...nothing else happens?
HELP!
I think you dnt have CWM or 4ext on ur phone.
Did you install it first or not?
Even if you did. try Flashing the CWM again
debarox said:
I think you dnt have CWM or 4ext on ur phone.
Did you install it first or not?
Even if you did. try Flashing the CWM again
Click to expand...
Click to collapse
whats CWM???? What must i do?
and i cant install 4ext as i cant download it cause phone is in boot loop
CWM means clockwork recovery mod.
download the attachment. place it in your sd card.
Bootloader will automatically detect the file and update it.
I believe you have ur phone S-OFF b4 u are attempting this
debarox said:
CWM means clockwork recovery mod.
download the attachment. place it in your sd card.
Bootloader will automatically detect the file and update it.
I believe you have ur phone S-OFF b4 u are attempting this
Click to expand...
Click to collapse
its saying battery level too low now...im going to leave it off and charge it then try again.
make sure you
Have correct firmware for ics. Its 3.32. If your comming from GB, you need to flash the firmware because ics uses different firmware than GB. Hope this helps!
Sent from my HTC Sensation Z710e using xda premium
Stop everything. I'll give you a simple solution.
Follow this step by step.
WRITE SUPER CID [YOU ONLY NEED TO DO THIS ONCE]-
1. Download adb tools here: download for WINDOWS or download for LINUX or from the attachments below
2. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
3. Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting
Manually put the phone in the bootloader/hboot mode
Navigate to fastboot by pressing volume down and pressing power button to select (power off > vol down + power on)
It will take you to the fastboot bootloader screen on your phone
Connect your phone via USB
Your Screen should now read fastboot USB
1. enter the command "fastboot oem writecid 11111111"
2. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
3. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
4. enter the command "fastboot reboot"
5. You can now flash any ROM you like.
Quoted from here.
Click to expand...
Click to collapse
Updating the firmware
This step is MANDATORY otherwise you ROM will not boot. Please take a look at the firmware thread so you can understand what you are about to do.
After updating the firmware you will have the 3.32 firmware with unlocked bootloader. Which basically means that you can use advanced fastboot commands, such as: flash new radios and splashscreens
Download any firmware from here.
Copy the PG58IMG.zip file you've downloaded to the root of the sdcard. Root of the sd card mean that you can't put the file inside any folder. Also, you can't rename the file. Please keep the PG58IMG otherwise the bootloader won't recognize it.
Power off your phone or remove the batt and put it back again.
Hold volume-down + power button to boot into the bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once it completed successfully and prompted you to reboot, pull the battery out.
Connect your SD card to the PC and remove the PG58IMG.zip file.
Quoted from here
.
Click to expand...
Click to collapse
Download the zips for SuperWipe & your ROM and put them on your memory card.
Hold volume-down + tap the power button once to boot into the bootloader.
Press vol down to highlight Recovery and press the power button to select it.
Next, select Install zip from SDcard and touch to navigate to the location of the Super Wipe zip and select it.
Once it is done, you will be rebooted to Recovery. Again choose Install from SD card and this time navigate to the ROM and select it.
After the install is finished, go back to main recovery menu and select reboot.
That's it, you're good to go.
This will work, I'm a 100% positive on that.
Hey guys.
Basically:
My brother has a Motorola Xoom 32GB MZ604. He tried to root it but it was unsuccessful. After reboot of the failed root, it will now get stuck on the M boot screen and not move, there's no loop as such, it will literally stay on until it runs out of battery or is turned off by pressing buttons.
Any ideas what's happened and how we can fix it?
He took it back and they want £46 to put new software on.
Thanks
Oli
Can you still enter recovery??
Sent from my Xoom using XDA Premium App
I believe he can but he said he's already wiped it? I'll try again though when he gets home tonight from work.
I had the same issue when I first tried to root my xoom. Here is what you do:
1) take out the external sd card. And thru pc , put on it the new recovery image and put it back into xoom.
2) search my posts on how to root mz601. I know yours is mz604. But it is the same procedure. I will post steps for you soon.
Sent from my MZ601 using Tapatalk 2
There you go. Step by step.
First, download the below and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: get the latest release for mz604 from here. http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot adb
reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Sent from my MZ601 using Tapatalk 2
if it's getting to the splash screen then just as you turn it on, whack it into fastboot then you'll be able to flash new recovery or flash back to stock.
matt4321 said:
if it's getting to the splash screen then just as you turn it on, whack it into fastboot then you'll be able to flash new recovery or flash back to stock.
Click to expand...
Click to collapse
Go here: http://developer.motorola.com/products/software/ to get the stock images to flash in fastboot to get the xoom back to factory conditions. It's normally the last resort, but the most successful. You may need to sign up for an account, but it is free.
Right guys basically i want my xoom to be complete stock what is the best way to do this. can i still use the above steps but by using the default motorola software.. it looked like it was using differnt firmware, and one of the links didnt work. sorry i really dont have a clue what to do and need my xoom back its been away for 3 weeks now
yes you can.. just flash the stock OS for it and you are good to go again.
and whats the best way to do this. sorry im not too sure about rooting on the xooms etc i used that poxy one click root which by the looks of things lots of people have had problems with it.
Rooting is pretty straight forward steps. Use the steps I provided you above if you want. If you are looking to flash stock rom, you still need recovery and stock rom to be flashed.
Sent from my MZ601 using Tapatalk 2
My mz601 is stuck at booting it keeps going off and booting again
My steps to a factory reset Xoom Wingray
My Xoom Wingray also crashed and was stuck in the boot animation. I still use my Xoom as my alarm clock and music player with multimedia dock. I had to put the Xoom in the drawer as there was no way to turn it off, it would just reboot back to the flashing animation. I was surprised that it wasn't dead by morning and it was still in the boot loop. So I wanted to revert back to the stock ROMs so this is what I just did. This is assuming you have nothing installed on your PC so from scratch. I actually just went through this a hour ago so I am still in the very last step.
First download and install the following:
-Minimal Android SDK from http://forum.xda-developers.com/showthread.php?t=2317790
-Motorola drivers from http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Now you need the original images:
You can try to get it from the source here, https://motorola-global-portal.custhelp.com/app/standalone/rom-images , but I had to request access to the files and was impatient.
I found the original images here instead, http://forum.xda-developers.com/showpost.php?p=64412362&postcount=10
You will need to find the original images for your device, the source in the first link should be able to help you.
Flashing Instructions
I would recommend having the power cord attached throughout this, but if your Xoom is fully charged it should be ok.
Assuming you installed the minimal SDK in the default folder, C:\Program Files (x86)\ Minimal ADB and Fastboot, unzip the individual images (boot.img, recovery.img, system.img and userdata.img) into this folder. If you installed into some other folder unzip there instead.
Now you need to put the Xoom into fastboot mode. Press the VOL-UP and Power to reboot, but then keep holding the VOL-UP. You should end up in fastboot mode.
Plug the Xoom into your PC.
Open a CMD window into the fastboot directory. If you installed the Minimal Fastboot from above you can simply go Start>Minimal ADB and Fastboot>Minimal ADB and Fastboot.
Type "fastboot devices"
Type "fastboot flash boot boot.img"
Type "fastboot flash system system.img"
Type "fastboot flash recovery recovery.img"
Type "fastboot flash userdata userdata.img"
Type "fastboot erase cache"
Type "fastboot oem lock"
You can see the responses I got in the attached image. Once complete the Xoom rebooted with the original Honeycomb OS and then I had to wait for all of the OTA updates to be pushed. This has taken several hours and now it is updating all of the stock Google apps.
Help with my MZ601
Please, I need help with my MZ601.
A friend who recently passed willed his MZ601 GSM/Wifi to me. I do not know a thing about it; however, I have read a couple of posts. I gathered from these posts that the MZ601 would need to be flashed with a new ROM, especially as when I powered it on, it stopped at the big 'M' logo.
I have checked so many posts online here and found links to many Roms and Gapps, but none is working.
Please, I would be glad if anyone could help me with the following:
(a) MZ601 GSM/Wifi ROM - whether Stock or Custom ROM.
(b) Also remember that I am a idiot; hence, I will need a step-by-step guide on what to do.
Thank you very much.
oyeniyib
Hello,
So I have a rooted HTC Desire S with Hboot 2.00.0002, unlocked bootloader and 4ext touch recovery. After a couple of failed attempts of flashing the MIUI rom and nandroid restoring it, I lost the ability to connect to 3G after the fourth attempt. So, I tried to flash a new kernel on it to see if it would solve anything. It didn't, whenever I boot up my phone it hangs on the HTC logo, then reboots a little while in 4ext recovery mode.
From here I again tried to nandroid restore, but with no luck.
How do I get my phone back to working? (what I had before was rooted stock rom)
I have tried these two kernels: http://bit.ly/ozxbWr (HTC-Kernel-2.6.35.10) and the Reaper 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1433816).
Thanks.
Alright, found the problem. For future Googlers here is how I fixed it.
So, first I downloaded a custom rom for my phone, MIUI. I placed the zip on my micro-SD card (I have a converter so it will fit into my laptop) and booted into 4EXT recovery. I guess you can use ClockworkMod Recorvery aswell.
In here I picked "choose from SD-card" and picked my .zip file and installed it.
After installation you boot into the bootloader (Volume Down + Power button) and go into fastboot. While in fastboot you plugin your USB-cable.
Set up ADB and Fastboot with this guide http://forum.xda-developers.com/showthread.php?t=1272595
Now go back to where you downloaded the custom rom to and extract the boot.img file to the folder where adb.exe and fastboot.exe is.
Upon up a cmd in your folder where adb.exe and fastboot.exe is in (Use Shift+Right click, pick "Open cmd here").
Now write exactly the following
Code:
fastboot flash boot boot.img
.
Press Enter and let it do it's job. When it's done you can unplug the USB cable and restart the phone as normally. The phone will now function again.
Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.
SimonTS said:
Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.
Click to expand...
Click to collapse
And even more so now
Impressed that someone actually resolved their own issue, let this hopefully be a lesson to the crowd
Swyped from my DesireS
The guide for doing this is here: http://forum.xda-developers.com/showthread.php?t=1525100
Thread closed
hey guys i have a question.. i made a total n00b mistake and now i am not sure what to do..
I have a htc one s
-i rooted the phone and put twrp 2.8 the newest one then i tried to load a custom rom.. i read somewhere on line that you did not need s off to do this so i tried and now everytime the phone boots it loads the htc screen but goes to a black screen which is kind of dim .. anyway my bootloader is unlocked its version 2.15 and i can get back in to my recovery and mount it i tried several roms but none work.. i was wondering if someone here has a stock rom or something that can get my phone to boot in to a os.. i have tried using fastboot to try and s off but everywhere i read it says u need debugging on my drivers are installed correctly but when u do adb devices it shows empty space.. ive tried many drivers even the google generic i cannot get it to work for the life of me... any help will be appriciated
cheers
Sam
Well let's take it easy. There were some things you've missed when reading so that's why you run into problems.
First thing you missed is that YOU MUST FLASH THE KERNEL IN FASTBOOT if you're S-On. That is EVERYTIME you flash a ROM.
Second, when you're in fastboot, you won't have "ADB devices" command working, you'll have to use "fastboot devices" command instead, ADB does not work while in fastboot.
What you'll have to do is like this:
1. Take any ROM you'd like to flash, place it on your sdcard (while you're in recovery you can mount sdcard to be accessible from pc)
2. Extract from the rom and save it on your pc (in the same folder where adb/fastboot commands are, usually /android-sdk/platform-tools) the "boot.img" file that's in the root of the ROM zip. That'll be called generic "the kernel".
3. Flash the ROM in recovery
4. Reboot to bootloader then while still connected to pc via USB, select fastboot mode. On your screen the "fastboot USB" will be shown.
5. Check if fastboot drivers are installed and fastboot commands are working by issuing "fastboot devices" command. If it'll not return your device then check if drivers are installed properly and you are not using an USB 3.0 port on windows 8.1 (were reported some issues with this configuration).
6. Having fastboot working, open command prompt in the location where fastboot is (and where you have saved the boot.img file) and issue the command: "fastboot flash boot boot.img"
7. Reboot
Now your new ROM should boot and work. Pay attention to choose the right ROM for your hboot and don't forget to do these steps EVERYTIME you're flashing a ROM.
If you're still looking for a stock ROM to flash, there's a thread with all RUUs linked, choose the one for your carrier or model type and run that one but I guess you won't need that
Good luck
Sent from nowhere over the air...