Related
I am receiving my new N1 Fri. Have been reading about rooting and all, does a new phone come with all the settings to the factory resets? Are there differences between my unlocked AT&T phone and others? If I choose to upgrade to new ROM's are my steps different? Been trying to figure it all out but unsure. Thanks
yes it comes with factory settings if its brand new.
upgrading to new roms won't be any different if you're on AT&T.
Link below is for nexus one in general, carrier doesn't matter.
http://forum.xda-developers.com/showthread.php?t=688000
Makes sense. If I do decide to install a rom I would only have to load the file onto the sd card and install? Are the advantages of the rom's better performance or features?Been spending a lot of time trying to get educated but too many ques.
erikclaw said:
Makes sense. If I do decide to install a rom I would only have to load the file onto the sd card and install? Are the advantages of the rom's better performance or features?Been spending a lot of time trying to get educated but too many ques.
Click to expand...
Click to collapse
better features and access for more customization.
mrandroid said:
Link below is for nexus one in general, carrier doesn't matter.
Saw your post after I replied. So after reading, I wouldn't have to root for the Froyo install? Just the steps you listed? Is the reason for rooting going from one rom to a newer or different one? Or do others have to do that because their phones are locked? Mine is unlocked cause with AT&T.
Click to expand...
Click to collapse
erikclaw said:
mrandroid said:
Link below is for nexus one in general, carrier doesn't matter.
Saw your post after I replied. So after reading, I wouldn't have to root for the Froyo install? Just the steps you listed? Is the reason for rooting going from one rom to a newer or different one? Or do others have to do that because their phones are locked? Mine is unlocked cause with AT&T.
Click to expand...
Click to collapse
all nexus ones are unlocked lol. and yes you do not need root for froyo and there are ways to downgrade to an official 2.1. an unlocked bootloader allows you to run unofficial roms cooked up by people and lets you flash anything you want.
Click to expand...
Click to collapse
mrandroid said:
Link below is for nexus one in general, carrier doesn't matter.
Saw your post after I replied. So after reading, I wouldn't have to root for the Froyo install? Just the steps you listed? Is the reason for rooting going from one rom to a newer or different one? Or do others have to do that because their phones are locked? Mine is unlocked cause with AT&T.
Click to expand...
Click to collapse
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.
just make sure you follow the 2 prerequisites first, then follow the instructions on that post. you'll be good to go.
dudebro said:
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.[
So I would have to root to make my phone able to run Froyo? Correcting the zip to flash is making it able to run flash? I know it is elementary but not sinking in.
Click to expand...
Click to collapse
dudebro said:
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.[
So I would have to root to make my phone able to run Froyo? Correcting the zip to flash is making it able to run flash? I know it is elementary but not sinking in.
Click to expand...
Click to collapse
no, you do not need root to run froyo.
miketlo said:
erikclaw said:
all nexus ones are unlocked lol. and yes you do not need root for froyo and there are ways to downgrade to an official 2.1. an unlocked bootloader allows you to run unofficial roms cooked up by people and lets you flash anything you want.
Click to expand...
Click to collapse
ok, thanks for the info.
Click to expand...
Click to collapse
So basically, Nexus reads and loads roms etc like a computer? For new programs etc sometimes you need to upgrade driver ie zip to flash
dudebro said:
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.
Click to expand...
Click to collapse
since I don't have to root then I have root access?
erikclaw said:
since I don't have to root then I have root access?
Click to expand...
Click to collapse
nope... I must be confusing you.
- you do not have root access after flashing froyo
- no you don't need root to flash it
- follow the steps in the thread and you will be fine
You do not have to root to run froyo. There are two flavors of Froyo floating around the net. They are the same OS version, but each can be used on a different setup.
One is a .zip signed by Google that can be flashed on an untouched/stock Nexus One, i.e. a locked bootloader. It's just a simple option selection in the bootloader to enter recovery mode. Recovery is where the updates are flashed.
The other version of Froyo that is out there is one that has root enabled, which is not signed by Google, and can only be flashed using a bootloader that is unlocked. Remember everything is flashed in recovery mode. By unlocking the bootloader you are able to replace the default recovery (which only allows the installation of signed files) with a custom one. The custom recovery allows you to flash unsigned files, many of which have root access.
In short, unlocking a bootloader does not give you root. It simply provides a mechanism by which you can flash an update that has root.
The signed file is only available for the T-Mobile 3G frequency phone thus far. It can still be flashed on an ATT one, but additional steps are required.
Well, I've been trying to use some custom roms and after all I restored the backup I made before, everything fine.
Today I wanted to try to use a custom rom again but it wouldn't work so I decided to wait for the official ICS release for the IncS. And here we get to my problem: When I restore the backup, and manually flash the boot.img (have to do this manually, got S-ON) and I boot my phone it gets to the HTC bootscreen, reboots and automatically gets to the CWM recovery.
Can anyone provide me an original boot.img (I haven't found it yet) or the whole standard android rom? If you have another solution, I would like to hear it!
Vaxx93 said:
Well, I've been trying to use some custom roms and after all I restored the backup I made before, everything fine.
Today I wanted to try to use a custom rom again but it wouldn't work so I decided to wait for the official ICS release for the IncS. And here we get to my problem: When I restore the backup, and manually flash the boot.img (have to do this manually, got S-ON) and I boot my phone it gets to the HTC bootscreen, reboots and automatically gets to the CWM recovery.
Can anyone provide me an original boot.img (I haven't found it yet) or the whole standard android rom? If you have another solution, I would like to hear it!
Click to expand...
Click to collapse
You can find the latest OTA in the Android Dev section. If you would use the search function ( yeah we really have a "search" function.. ) you would easily find it. If you want your boot.img we do need what for a Rom from which carrier you got.
Silversniper said:
You can find the latest OTA in the Android Dev section. If you would use the search function ( yeah we really have a "search" function.. ) you would easily find it. If you want your boot.img we do need what for a Rom from which carrier you got.
Click to expand...
Click to collapse
Actually I DID use the search, but I haven't found any stock roms for the IncS.. I would like a boot.img for T-Mobile carrier (that's what a 'carrier' is right?).
Vaxx93 said:
Actually I DID use the search, but I haven't found any stock roms for the IncS.. I would like a boot.img for T-Mobile carrier (that's what a 'carrier' is right?).
Click to expand...
Click to collapse
Here is the sticky thread in the Development section that contains official HTC Shipped RUU/ROMs for the IncS.
http://forum.xda-developers.com/showthread.php?t=1033922
tpbklake said:
Here is the sticky thread in the Development section that contains official HTC Shipped RUU/ROMs for the IncS.
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
Thàt is helpfull! Thanks! Now my, probably last, question: how do I know which version I need? I know I have a WWE version, but which one?
Vaxx93 said:
Thàt is helpfull! Thanks! Now my, probably last, question: how do I know which version I need? I know I have a WWE version, but which one?
Click to expand...
Click to collapse
I have just been reviewing your posts and you posted that you applied the OTA and received HBOOT 2.01.0001, correct?
Then the RUU/ROM you need is the 3.11.405.2 version.
You also stated that you were able to unlock HBOOT 2.01.0001 using the HTCDEV.com site, correct? Which custom recovery did you install after that?
tpbklake said:
I have just been reviewing your posts and you posted that you applied the OTA and received HBOOT 2.01.0001, correct?
Then the RUU/ROM you need is the 3.11.405.2 version.
You also stated that you were able to unlock HBOOT 2.01.0001 using the HTCDEV.com site, correct? Which custom recovery did you install after that?
Click to expand...
Click to collapse
That's all correct, I installed the CWM recovery after that, not sure which version, the most recent one if I'm sure. I notice that the RUU/ROMS are .exe, do I flash these the same way as a .zip rom?
Vaxx93 said:
That's all correct, I installed the CWM recovery after that, not sure which version, the most recent one if I'm sure. I notice that the RUU/ROMS are .exe, do I flash these the same way as a .zip rom?
Click to expand...
Click to collapse
No, you run the exe on a PC and follow the directions on the screens. The program will tell you when to connect your phone to the PC using the USB cable.
This will completely wipe your phone and reload the ROM. Your HBOOT screen will probably show RELOCKED and you will need to unlock it again. Please confirm.
tpbklake said:
No, you run the exe on a PC and follow the directions on the screens. The program will tell you when to connect your phone to the PC using the USB cable.
This will completely wipe your phone and reload the ROM. Your HBOOT screen will probably show RELOCKED and you will need to unlock it again. Please confirm.
Click to expand...
Click to collapse
If that's true, I LOVE YOU, that's what I've been looking for. Is there a way to save my data like contacts, whatsapp messages and settings and stuff or do I have to live with the fact that I get a completely "new" phone?
Vaxx93 said:
If that's true, I LOVE YOU, that's what I've been looking for. Is there a way to save my data like contacts, whatsapp messages and settings and stuff or do I have to live with the fact that I get a completely "new" phone?
Click to expand...
Click to collapse
You can sync your contacts to your Google/Gmail account or save them to your SD cards. You can use Titanium Backup to backup apps and some settings.
Well this sucks: The ROM Updatestff can't update the Android hpone. Get the right ROM Update program and try again.
Were you sure that this is the right one? ;p
Vaxx93 said:
Well this sucks: The ROM Updatestff can't update the Android hpone. Get the right ROM Update program and try again.
Were you sure that this is the right one? ;p
Click to expand...
Click to collapse
This is the only one that has HBOOT 2.01.0001. You will also need to relock your HBOOT before you run the RUU using the command:
fastboot oem lock
tpbklake said:
This is the only one that has HBOOT 2.01.0001. You will also need to relock your HBOOT before you run the RUU using the command:
fastboot oem lock
Click to expand...
Click to collapse
Okay I did that now, it said that it was succeeded and a line under that one it said that it failed. Trying to update now, curious what happens.
It seems that he's updating now!
He updated it to the original Android, dude, you're amazing! Thanks mennnn! Just forbid myself to ever try a custom rom again and just stick to waiting for official releases
Vaxx93 said:
He updated it to the original Android, dude, you're amazing! Thanks mennnn! Just forbid myself to ever try a custom rom again and just stick to waiting for official releases
Click to expand...
Click to collapse
Glad to help! Next time just use the "Thanks" button....
Ah ofcourse, I'm pretty new to the forum and didn't notice the thanksbutton before. Used it to thank you right away!
Please help I unlocked and loaded twrp. Then I flashed the latest Bad Boys Rom 4.4.3 and now I am stuck at the HTC screen. I can't get it to do anything. I have read and tried for hours to RUU or find some way to get a ROM to boot. I am lost...any help much appreciated!
kpahl1973 said:
Please help I unlocked and loaded twrp. Then I flashed the latest Bad Boys Rom 4.4.3 and now I am stuck at the HTC screen. I can't get it to do anything. I have read and tried for hours to RUU or find some way to get a ROM to boot. I am lost...any help much appreciated!
Click to expand...
Click to collapse
Did you fastboot flash the boot image?
What firmware are you on?
Which version of TWRP did you flash?
Captain_Throwback said:
Did you fastboot flash the boot image?
What firmware are you on?
Which version of TWRP did you flash?
Click to expand...
Click to collapse
I used the One_M8_ALL-in -One-Kit_v to get root and to flash trwp 2.7.0.2. I didn't mess with the firmware but I know I was on 4.4.2 and it wanted to take the update but I didn't allow it. I flashed Bad Boyz 4.4.3 latest version...And I do feel dumb for doing that. Wasnt thinking. NOw I am stuck on the white htc screen and cant even get it off by holding the power down button.
kpahl1973 said:
I used the One_M8_ALL-in -One-Kit_v to get root and to flash trwp 2.7.0.2. I didn't mess with the firmware but I know I was on 4.4.2 and it wanted to take the update but I didn't allow it. I flashed Bad Boyz 4.4.3 latest version...And I do feel dumb for doing that. Wasnt thinking. NOw I am stuck on the white htc screen and cant even get it off by holding the power down button.
Click to expand...
Click to collapse
Ok I was just able to get it back to the bootloader and recovery. Thats a positive step. So what do I need to run? I am not S OFF and dont have a rom loaded at the moment. Any help appreciated. I dont want to mess it up any more than I have.
kpahl1973 said:
Ok I was just able to get it back to the bootloader and recovery. Thats a positive step. So what do I need to run? I am not S OFF and dont have a rom loaded at the moment. Any help appreciated. I dont want to mess it up any more than I have.
Click to expand...
Click to collapse
Does anyone have an old 4.4.2 rom I can load to get me going? I know I need to s off and right now I need to get my phone up and running for work and need an older rom that works with current firmware. Thanks so much for any help. I am dead in the water at the moment.
kpahl1973 said:
Does anyone have an old 4.4.2 rom I can load to get me going? I know I need to s off and right now I need to get my phone up and running for work and need an older rom that works with current firmware. Thanks so much for any help. I am dead in the water at the moment.
Click to expand...
Click to collapse
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-2-16-651-4-(Android-4-4-3)
Don't forget to fastboot flash the boot image, and you'll need to download SuperSU and flash the zip after you flash the ROM for it to boot up completely.
Captain_Throwback said:
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-2-16-651-4-(Android-4-4-3)
Don't forget to fastboot flash the boot image, and you'll need to download SuperSU and flash the zip after you flash the ROM for it to boot up completely.
Click to expand...
Click to collapse
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
kpahl1973 said:
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
Click to expand...
Click to collapse
Click the second link in my sig & scroll down to the section on S-on kernel flashing.
As far as SuperSU, you'll find it in the link below.
http://forum.xda-developers.com/showthread.php?t=1538053
kpahl1973 said:
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
Click to expand...
Click to collapse
You don't need that zip file. Just extract to boot.img from the ROM zip. The zip file is specifically for MultiROM support.
Captain_Throwback said:
You don't need that zip file. Just extract to boot.img from the ROM zip. The zip file is specifically for MultiROM support.
Click to expand...
Click to collapse
Ok I flashed the boot.img from the rom I downloaded which was M8WHL 2.16.651.4 Stock Rooted - Deodex and then I flashed the rom. I then flashed the latest SuperSU and rebooted and I am still stuck at the htc screen...did I do something wrong? I was careful to follow step by step with the instructions.
kpahl1973 said:
Ok I flashed the boot.img from the rom I downloaded which was M8WHL 2.16.651.4 Stock Rooted - Deodex and then I flashed the rom. I then flashed the latest SuperSU and rebooted and I am still stuck at the htc screen...did I do something wrong? I was careful to follow step by step with the instructions.
Click to expand...
Click to collapse
I thought you wanted to flash an older base ROM? If so, you wanted to choose a 1.xx base ROM from the thread. Perhaps that's your issue.
Captain_Throwback said:
I thought you wanted to flash an older base ROM? If so, you wanted to choose a 1.xx base ROM from the thread. Perhaps that's your issue.
Click to expand...
Click to collapse
Yes I did to get it going. What would I have to do to get the 2.xx rom going? Or do I need to just get it running first on the old version? I really do appreciate all the help! I really just want my phone to work and its so frustrating. I am downloading the older version now and will try that with the boot.img and supersu as well.
kpahl1973 said:
Yes I did to get it going. What would I have to do to get the 2.xx rom going? Or do I need to just get it running first on the old version? I really do appreciate all the help! I really just want my phone to work and its so frustrating. I am downloading the older version now and will try that with the boot.img and supersu as well.
Click to expand...
Click to collapse
Flashing the 2.xx base ROM requires updating your firmware. You needed an older stock ROM so you could S-OFF and do update it, correct? I thought that was the original issue?
Captain_Throwback said:
Flashing the 2.xx base ROM requires updating your firmware. You needed an older stock ROM so you could S-OFF and do update it, correct? I thought that was the original issue?
Click to expand...
Click to collapse
Yes you are correct. I got ahead of myself. I am downloading the older stock now and hopefully can get that running and then will attempt to s off and put this behind me. Believe it or not I have rooted the evo, lte, one7 and now first time messed up with the m8. You would think I would know a little more and not have made these mistakes. Oh well...with luck this will work and I appreciate all the help!
kpahl1973 said:
Yes you are correct. I got ahead of myself. I am downloading the older stock now and hopefully can get that running and then will attempt to s off and put this behind me. Believe it or not I have rooted the evo, lte, one7 and now first time messed up with the m8. You would think I would know a little more and not have made these mistakes. Oh well...with luck this will work and I appreciate all the help!
Click to expand...
Click to collapse
Thanks for all the help! I am back up and running. I will S off and update.
CF-Auto-Root Peregrine by Chainfire
I asked chainfire to provide us with a supporting root programme to root the Moto G 4G edition XT1039/XT1040 Peregrine
This will root the Moto G XT1039/XT1040 on KitKat or Lollipop
Instructions
Copy file to pc
Connect phone to PC via USB
Put phone in fastboot mode
Unzip all the files in zip
Run the script depending on what
operating system you are using
Restart phone once done
Optional step
Open the supersu app and update the binary (normal method not recovery)
Download
Chainfires CF-Auto-Root site Here
Notes
You need an unlocked bootloader
You need to unlock your bootloader via the Motorola website before using this!
If you have already unlocked your bootloader in the past it will not format data
This version should do all Peregrine models but use at your own risk
All credit goes to chainfire for making the package
Main CF-Auto-Root XDA thread Here
Main CF-Auto-Root Site Here
Nice work, thanks!
mooms said:
Thanks you marcussmith2626 (and to Chainfire of course) I have seen the CF AutoRoot the other day and was thinking that the one for XT1003 would surely work for the XT1039/1040/1042/1045, but having one specially made for ours is better.
One thing to know: the recovery is not flashed, only booted (command used is fastboot boot), so no change is made to the (custom) recovery, which is good.
I have already rooted my XT1039 so I do not need to use this but I will use it next time I flash my phone.
I don't know if Chainfire will regularly update these images to update superSU binary, but updating it from Playstore is very easy anyway
Click to expand...
Click to collapse
Copying quote from the other thread I accidentally double posted to bring everything here
marcussmith2626 said:
Notes
You need an unlocked bootloader
If you havent previously unlocked your bootloader it will format data as it runs the unlock bootloader command
Click to expand...
Click to collapse
So this means, we do not need the motorola-website to get an unlock code? CF-Root will unlock
the bootloader on its own? Meaning Motorola can never know that the bootloader was unlocked,
if we lock it again?
Greetz
Mitsch79 said:
So this means, we do not need the motorola-website to get an unlock code? CF-Root will unlock
the bootloader on its own? Meaning Motorola can never know that the bootloader was unlocked,
if we lock it again?
Greetz
Click to expand...
Click to collapse
No you need to unlock the phone via the Motorola website if you have never unlocked the bootloader before
It means if you have relocked the bootloader since you unlocked it then it will unlock it again
WIll I be able to update OTA to Lollipop (when it comes available), with this applied?
/EDIT:
I think I have an answer to above question:
To be able to sideload the OTA I will:
1) download and extract the 5.0 factory image
2) fastboot flash boot boot.img
3) fastboot flash system system.img
4) adb sideload The5_0_1OTA.zip
Anyone can confirm this?
I know I will lose root again after following above steps.
bas-r said:
WIll I be able to update OTA to Lollipop (when it comes available), with this applied?
/EDIT:
I think I have an answer to above question:
To be able to sideload the OTA I will:
1) download and extract the 5.0 factory image
2) fastboot flash boot boot.img
3) fastboot flash system system.img
4) adb sideload The5_0_1OTA.zip
Anyone can confirm this?
I know I will lose root again after following above steps.
Click to expand...
Click to collapse
Only time will tell if you can update whilst rooted
If you change any apps in system it's unlikely you will be able to
It doesn't change the recovery so you will still have stock recovery
There is an unroot feature in the supersu app but I don't know if this is enough to fully unroot
If all else fails you can always flash stock 4.4.4 and then update
How to get pass < Waiting for device>
How do you get past the <waiting for device> screen on a mac. I can't seem to overcome that part.
UPDATE:
I've since move on to using a PC instead of a Mac. But now I get:
booting...
FAILED <remote failure>
I also tried unlocking through the motorola website and it tells me I cannot unlock device. Is this normal?
DKCN said:
How do you get past the <waiting for device> screen on a mac. I can't seem to overcome that part.
UPDATE:
I've since move on to using a PC instead of a Mac. But now I get:
booting...
FAILED <remote failure>
I also tried unlocking through the motorola website and it tells me I cannot unlock device. Is this normal?
Click to expand...
Click to collapse
You need to unlock your bootloader via the Motorola website before you can use this
Some models on certain carriers cannot be unlocked - see Motorola website for details on unlocking bootloader and if your device can be unlocked
Tested on official lollipop for XT1039 23.21.17.peregrine_retgb.retgball.en.GB.retgb and roots it fine
Apps optimize on restart and may restart twice - just wait till its finished booting
TheFixItMan said:
Tested on official lollipop for XT1039 23.21.17.peregrine_retgb.retgball.en.GB.retgb and roots it fine
Apps optimize on restart and may restart twice - just wait till its finished booting
Click to expand...
Click to collapse
Can I ask have you a copy of this original lollipop firmware... Or a link... Thanks??
dog121 said:
Can I ask have you a copy of this original lollipop firmware... Or a link... Thanks??
Click to expand...
Click to collapse
Firmware images have not been released yet
I have a copy of the old ota from the first build (there have been 3 in total) - The difference as far as I can tell is kernel changes and probably better multitasking but its probably best you wait until Motorola pushes it out to everyone
Just reporting that it works on XT1040 with lollipop - br version
raf.lozano said:
Just reporting that it works on XT1040 with lollipop - br version
Click to expand...
Click to collapse
Added to op
Just tested in a XT1040 (23.21.8.peregrine_retbr.retbr.en.BR amxbr) and it works fine. Should work with retbr too.
XT1039 received Lollipop last day, can I root my phone with this tool? Can anyone confirm that it will work? Thanks
DeX1009 said:
XT1039 received Lollipop last day, can I root my phone with this tool? Can anyone confirm that it will work? Thanks
Click to expand...
Click to collapse
Yes it works...no problems
do i need to unlock the bootloader before using this or does this unlock it?
shuli81 said:
do i need to unlock the bootloader before using this or does this unlock it?
Click to expand...
Click to collapse
Yes you need to unlock the boot loader...its written on the thread under NOTES...
dog121 said:
Yes you need to unlock the boot loader...its written on the thread under NOTES...
Click to expand...
Click to collapse
My bad. I totally missed that.
Thanks
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
shepppster said:
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
Click to expand...
Click to collapse
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
Ok the unbricking has worked so far....can someone confirm the fastboot commands in Linux are the same as on a windows CMD prompt please?
I dont want to get this far and not flash the firmware properly.
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
shepppster said:
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
Click to expand...
Click to collapse
Fastboot works just the same in Linux as in Windows with the exception of you must use "sudo"
So
Code:
fastboot devices
becomes
Code:
sudo fastboot devices
Code:
fastboot flash zip firmware.zip
becomes
Code:
sudo fastboot flash zip firmware.zip
and so on if you forget to use sudo you will just see "waiting for device" in which case press ctrl+c to cancel and do command again with sudo :good:
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
shepppster said:
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
Click to expand...
Click to collapse
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
shepppster said:
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
Click to expand...
Click to collapse
no firmware does not revert back .. where are you getting these files ?
clsA said:
no firmware does not revert back .. where are you getting these files ?
Click to expand...
Click to collapse
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
shepppster said:
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
Click to expand...
Click to collapse
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Danny201281 said:
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Click to expand...
Click to collapse
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
shepppster said:
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
Click to expand...
Click to collapse
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Danny201281 said:
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Click to expand...
Click to collapse
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
shepppster said:
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Danny201281 said:
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Click to expand...
Click to collapse
@Danny201281 and @clsA Thanks for all your help...successfully flashed up to the latest 6******** firmware and flashed a custom rom.
Perhaps minscule to u guys but massive step forward for me !
Few nailbiting moments anticipating a brick again..but it worked fine using Ubuntu which is much less finicky than windows to use and my weapon of choice from now on!
:good::good: