Need help getting to sense 6 - HTC One Mini

So a few months ago I switched to CyanogenMod 11 while I was on sense 5. Well Cyan has started running really slow and not even the updates have fixed this. I have cwm installed, s-off, and my boatloader unlocked. Could someone tell me how exactly I go about flashing a sense 6 ROM? I'd greatly appreciate the help. Thanks !

Bump: anyone ?
Sent from my One Mini using XDA Free mobile app

Socrats said:
Bump: anyone ?
Sent from my One Mini using XDA Free mobile app
Click to expand...
Click to collapse
This is a good guide. You can probably start at step 3. Before you start, you should copy a sense 6 rom to your sd card. Also, in case your sd card gets wiped during the process, you should make sure you are able to push a rom to your phone from recovery (either ADB push or OTG device).
http://forum.xda-developers.com/showthread.php?t=2789272
Obviously, you should back everything up before you begin. If you're on older firmware your phone will probably be wiped completely.
Here are some good sense 6 ROMs:
http://forum.xda-developers.com/showthread.php?t=2753784
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
http://forum.xda-developers.com/htc-one-mini/development/rom-liberty-rom-sixth-sense-t2875292

Thanks bro ! I'll try this when I get home and let you know how it works.
Sent from my One Mini using XDA Free mobile app

jollywhitefoot said:
This is a good guide. You can probably start at step 3. Before you start, you should copy a sense 6 rom to your sd card. Also, in case your sd card gets wiped during the process, you should make sure you are able to push a rom to your phone from recovery (either ADB push or OTG device).
http://forum.xda-developers.com/showthread.php?t=2789272
Obviously, you should back everything up before you begin. If you're on older firmware your phone will probably be wiped completely.
Here are some good sense 6 ROMs:
http://forum.xda-developers.com/showthread.php?t=2753784
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
http://forum.xda-developers.com/htc-one-mini/development/rom-liberty-rom-sixth-sense-t2875292
Click to expand...
Click to collapse
Quick question, I'm going to flash the insert coin rom, but can I do this if my phone's boot loader is unlocked even without s-off? Also my phone currently has cwm installed for recovery, is it possible to just install twrp using the guide you posted even if I have cwm? Sorry for all of the questions lol. Thanks in advance.

Socrats said:
Quick question, I'm going to flash the insert coin rom, but can I do this if my phone's boot loader is unlocked even without s-off? Also my phone currently has cwm installed for recovery, is it possible to just install twrp using the guide you posted even if I have cwm? Sorry for all of the questions lol. Thanks in advance.
Click to expand...
Click to collapse
Boot loader unlocked is good.
You can't upgrade to sense 6 firmware unless you're s-off. But I thought you were already s-off? Have you ever been s-off? What firmware are you on now? Hboot and radio versions from boot loader.
Yes. Installing twrp 2.7.1.1 will replace the cwm recovery.
I can't stress enough...make a backup in recovery. And copy that backup and anything else you don't want to lose to your computer. It's very possible that your phone can be completely wiped during the process.
I'd also make sure that adb worked from recovery. In the event you can't boot your device into os (which means you won't be able to drag and drop the Rom to your device), you'll have to use adb commands to push the Rom to your device. You can test this by flashing twrp 2.7.1.1, then enter recovery. Then from your computer, in adb folder in a command prompt, type "adb devices". This should return your device serial number.

jollywhitefoot said:
Boot loader unlocked is good.
You can't upgrade to sense 6 firmware unless you're s-off. But I thought you were already s-off? Have you ever been s-off? What firmware are you on now? Hboot and radio versions from boot loader.
Yes. Installing twrp 2.7.1.1 will replace the cwm recovery.
I can't stress enough...make a backup in recovery. And copy that backup and anything else you don't want to lose to your computer. It's very possible that your phone can be completely wiped during the process.
I'd also make sure that adb worked from recovery. In the event you can't boot your device into os (which means you won't be able to drag and drop the Rom to your device), you'll have to use adb commands to push the Rom to your device. You can test this by flashing twrp 2.7.1.1, then enter recovery. Then from your computer, in adb folder in a command prompt, type "adb devices". This should return your device serial number.
Click to expand...
Click to collapse
No I'm not s-off, every method I've tried has failed. It's actually something I've been having trouble with. My phone is rooted, and every method has failed. I just tried firewater about 20 mins ago and it failed saying my phone isn't supported. This isn't my first time trying either.

Socrats said:
No I'm not s-off, every method I've tried has failed. It's actually something I've been having trouble with. My phone is rooted, and every method has failed. I just tried firewater about 20 mins ago and it failed saying my phone isn't supported. This isn't my first time trying either.
Click to expand...
Click to collapse
What firmware?

My firmware is 1.25.40g

Socrats said:
My firmware is 1.25.40g
Click to expand...
Click to collapse
That's just radio...what's hboot? 2.22?

jollywhitefoot said:
That's just radio...what's hboot? 2.22?
Click to expand...
Click to collapse
Oh lol, yes my hboot is 2.22

Socrats said:
Oh lol, yes my hboot is 2.22
Click to expand...
Click to collapse
You should be on the new partition layout, and should be able to flash a sense 6 rom without updating firmware.
Insert Coin might work, but i'm not positive about that. This stock one should definitely work: http://forum.xda-developers.com/showthread.php?t=2791725
I flashed this one when i was s-on, on hboot 2.22 and radio 1.25 without any problems. Once you're on that ROM, you can probably get s-off with Rumrunner if you want.
Here's the path I took when my device was in the state yours is in (S-On, hboot 2.22 & Radio 1.25)
- Flash TWRP 2.1.1.1 recovery
- make a full backup from TWRP
- test adb* from recovery (specifically: make sure "adb devices" returns your serial number, and that you can use "adb push <nameofROM.zip>" to your sdcard)**
- reboot into OS
- Copy the backup you just made (twrp folder on sdcard) and all other files that you don't want to lose to your computer (make sure to leave the TWRP backup on your sdcard in case you need to restore)
- Copy the sense 6 rom to your device
- Reboot into recovery
- Wipe your device*** (once you do this, your phone will not boot until you flash a working rom, or restore the backup you just made)
- Go to "Install" and find your rom's zip file on the sdcard, select it and swipe to flash ****
- After your ROM has flashed, if you don't get any errors, you can reboot your device
- That should be it...you will see a white screen with HTC on it for a little while while (sometimes as long a 5 or more minutes...or at least it seems that way sometimes) the installation finalizes (but there's no progress bar, so you just need to be patient here).
* here is more information on setting up adb if you need it: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
** this is not an essential step IF EVERYTHING GOES PERFECTLY, but, IF flashing a rom fails and you can't boot into OS and your sdcard gets wiped out and you your backup is no longer on the device, adb can save your bacon, because you can't drag and drop files from your computer to your device when the device is in recovery. Bottom line is, it's smart to make sure that you can transfer files to your device from recovery in case of disaster.
*** I prefer to wipe the device manually (wipe > advanced wipe > select DAVLIK CACHE, CACHE, DATA, & SYSTEM <do not select internal storage>
**** some ROMs use an installed called "Aroma" that steps through the installation process and lets you choose mods as you go. If the ROM you install has aroma, you will get wipe options. Make sure to select Do not wipe because you just wiped everything above. If your ROM doesn't have aroma, you will just see the installation log flashing in the terminal window).
That's all I can think of...hope this helps and everything goes smoothly.
EDIT: If all of this works and you're able to flash the stock sense 6 ROM i linked to above and want to try a newer stock rom or maybe even insert coin, just follow the steps above again. But i would probably start with the rom i linked to because i KNOW that one will work with your current config

jollywhitefoot said:
You should be on the new partition layout, and should be able to flash a sense 6 rom without updating firmware.
Insert Coin might work, but i'm not positive about that. This stock one should definitely work: http://forum.xda-developers.com/showthread.php?t=2791725
I flashed this one when i was s-on, on hboot 2.22 and radio 1.25 without any problems. Once you're on that ROM, you can probably get s-off with Rumrunner if you want.
Here's the path I took when my device was in the state yours is in (S-On, hboot 2.22 & Radio 1.25)
- Flash TWRP 2.1.1.1 recovery
- make a full backup from TWRP
- test adb* from recovery (specifically: make sure "adb devices" returns your serial number, and that you can use "adb push <nameofROM.zip>" to your sdcard)**
- reboot into OS
- Copy the backup you just made (twrp folder on sdcard) and all other files that you don't want to lose to your computer (make sure to leave the TWRP backup on your sdcard in case you need to restore)
- Copy the sense 6 rom to your device
- Reboot into recovery
- Wipe your device*** (once you do this, your phone will not boot until you flash a working rom, or restore the backup you just made)
- Go to "Install" and find your rom's zip file on the sdcard, select it and swipe to flash ****
- After your ROM has flashed, if you don't get any errors, you can reboot your device
- That should be it...you will see a white screen with HTC on it for a little while while (sometimes as long a 5 or more minutes...or at least it seems that way sometimes) the installation finalizes (but there's no progress bar, so you just need to be patient here).
* here is more information on setting up adb if you need it: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
** this is not an essential step IF EVERYTHING GOES PERFECTLY, but, IF flashing a rom fails and you can't boot into OS and your sdcard gets wiped out and you your backup is no longer on the device, adb can save your bacon, because you can't drag and drop files from your computer to your device when the device is in recovery. Bottom line is, it's smart to make sure that you can transfer files to your device from recovery in case of disaster.
*** I prefer to wipe the device manually (wipe > advanced wipe > select DAVLIK CACHE, CACHE, DATA, & SYSTEM <do not select internal storage>
**** some ROMs use an installed called "Aroma" that steps through the installation process and lets you choose mods as you go. If the ROM you install has aroma, you will get wipe options. Make sure to select Do not wipe because you just wiped everything above. If your ROM doesn't have aroma, you will just see the installation log flashing in the terminal window).
That's all I can think of...hope this helps and everything goes smoothly.
EDIT: If all of this works and you're able to flash the stock sense 6 ROM i linked to above and want to try a newer stock rom or maybe even insert coin, just follow the steps above again. But i would probably start with the rom i linked to because i KNOW that one will work with your current config
Click to expand...
Click to collapse
Ok I'm about to give it a shot, thanks!

Related

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

Virtuous ROM: SuperCID and Firmware upgrade NOT needed?

The thread [GUIDE] A must read for those noobs who want to enjoy ICS states that ALL ICS roms need a firmware upgrade.
However, the installation instructions for the Virtuous ROM doesn't say anything at all about upgrading the firmware: http://www.virtuousrom.com/p/documentation.html
Which one is right?
Also, just to be on the safe side, is SuperCID needed?
The documentation page you linked is installation instructions for all Virtuous ROMs, so it's pretty generic. If you look at the description page for Virtuous Inquisition, which is ICS-based, the page does mention firmware. That ROM is based on the most recent 3.32 firmware, which is probably what you want to use. AFAIK, all ICS ROMs require firmware version of 3.12 or greater.
As for SuperCID, I think there are firmware downloads on the forums now that don't require it but it's also pretty easy to do.
pyrilium said:
The documentation page you linked is installation instructions for all Virtuous ROMs
Click to expand...
Click to collapse
Ahhh. Ok. That was the missing link. Thanks.
I have a rooted S-OFF Sensation 4G with the stock ROM and ClockWork. So all I need to do is:
Flash the Firmware that doesn't require SuperCID
Nandroid Backup / Wipe
And then I can flash Virtuous.
Is that correct?
Also, does flashing Firmware alone cause a wipe?
That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.
pyrilium said:
That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.
Click to expand...
Click to collapse
Wow, this is extremely helpful, thank you. One other thing: does it matter what version of ClockWork I'm using? (I rooted/did S-Off a loooooong time ago.)
Glad I can help!
I don't know whether the version of CWM matters. I doubt it would, other than maybe making a nandroid backup in a format other than current, but it's not that hard to update the recovery either.
I actually started using 4ext recovery recently, and I like it a fair bit better than CWM. It's something like $2.00 on the market, but includes a userspace application that lets you do things like set up a series of recovery operations (i.e. make backup, wipe, flash a set of zips) and then reboot into recovery to run them.
Perfect, thanks. I'll give this a shot.
Every few weeks I look up how to move to ICS but then lose my enthusiasm once I see all the things I'd have to do to switch haha. But today I noticed that Virtuous doesn't need some of those steps
One more question: SuperWIPE is unnecessary for Virtuous Inquisition correct? I see that it is necessary for Android Revolution, but I just wanted to make sure.
I've always seen superwipe recommended as part of the upgrade process from GB to ICS. It might not be required for Virtuous, but I don't see why you'd want to avoid it. The flashing process *will* wipe your phone - you want to use something like Titanium Backup to backup/restore app states if that's a problem - and performing the superwipe takes almost no time.
Woohoo! Successfully upgraded from stock Gingerbread (rooted & S-Off) to Virtuous Inquisition ICS! I wrote down what I did, so if anyone is interested, below is how I did it. It took about 15 minutes in total (not including the backups). Hopefully it helps someone else out there!
Titanium Backup all apps
Nandroid Backup via ClockWork Recovery (1434 MB)
Get CID Version:
Download ADB/Fastboot files from attachment from Post #1 of the [Firmware][Mar 12] thread
Connect phone to PC -> adb reboot bootloader -> Then in bootloader:
fastboot getvar cid: T-MOB010
fastboot getvar mid: PG5810000
fastboot reboot
Download the appropriate Firmware from above thread (CTRL+F for T-MOB010/PG5810000) and the Virtuous ROM from Virtous Website
Copy both files to sdcard, check md5 on both
Flash Firmware:
Turn phone off -> Hold Volume-Down + Power to enter bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once completed successfully and asks you to reboot, pull the battery out. (Gingerbread & firmware are incompatible, causes bootloops)
With phone off and plugged into PC, do adb reboot recovery (Thanks pyrilium!)
Mount USB storage
Use PC to delete firmware file from sdcard
Wipe all data and cache -> Flash Virtuous -> Reboot
(Note that YES, flashing firmware causes bootloops -- as I found out! So firmware and ROM must both be flashed together.)
And thanks pyrilium for the note about using "adb reboot recovery" while the phone is off! I would have never figured that you could issue adb commands with your phone off. That tip isn't even in any of the guides, so thanks for that! Extremely helpful.
Anyway, hope that helps others out there. And thanks for helping me!

Going to root, am I doing it right?

I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.

[Q] Where Did I Mess Up?

This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
help
Hi,
I had a similar issue.. I followed a tutorial on YouTube and the guy forgot to mention that the ROM needs to be on the SD before rooting.
And my device was not reconised by my computer (win 7).
I messed around with a few recovery's.. turned out i was using a older version and after flashing about 3 recovery's my computer reconised my device when mounting SD card.
Hope this helps.
cfagan17 said:
This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
Click to expand...
Click to collapse
Okay First I don't whether you have an S3 version (VilleC2) or an S4 version (Ville).
Understand this, when you format SD card using TWRP recovery, you can't mount it. It is because only the Stock HTC recovery is able to format the SD correctly.
What you ought to do now is:
1. Download stock HTC recovery for your phone version, S3 or S4.
2. flash the recovery through Fastboot using the command:
Code:
fastboot flash recovery recovery.img
3. Go to bootloader and select the option to erase Storage; if it's not there, then you will have to select Factory Reset, wiping your data and apps too.
Regards
Just use this - http://forum.xda-developers.com/showthread.php?t=2471151
It will almost do all things for you, Unlock Bootloader, Flash recovery, Root ...
And remember, if abd console says "error: device not found" or when downloading and fail install "HTC MTP drivers" don't worry, it happened to me too.
Remember, you need flashed Recovery, to be able to Gain Root. And Unlocked Bootloader to flash Recovery.
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
cfagan17 said:
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
Click to expand...
Click to collapse
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
mjsheldon4 said:
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
Click to expand...
Click to collapse
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
cfagan17 said:
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
Click to expand...
Click to collapse
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
mjsheldon4 said:
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
Click to expand...
Click to collapse
I already flashed RUU. I can't flash a custom ROM.
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
mjsheldon4 said:
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
Click to expand...
Click to collapse
On

Android Revolution HD 7.3

Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.
Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr

Categories

Resources