Related
I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....
Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....
I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.
dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:
If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app
Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!
did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.
what step are you up to?
Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......
i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.
OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!
here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?
Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?
What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?
Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....
Great let us know what happens. I will be around for a while.
Hello co-A510 users,
I've been lurking for quite a while and I repeatedly see questions about "how to get the JB bootloader?". Followed by the answer "Go back to stock ICS, then get the OTA.". Usually followed by the follow-up question "B-b-but... how?"
This post attempts to answer that follow-up question, for most folks, in the easiest way possible.
The Six Steps to Stock:
Step 1: Download the Stock Acer OS (rom zip)
- Go to http://www.acer.com.au/ac/en/AU/content/drivers
- Select Tablet >> Iconia A >> A510 in the product list
- On the new web portion that will appear, select the "O.S." tab, and download your appropriate build (mine is WW.GEN 1)
Step 2: Flash the OS (rom zip)
- Save the zip in your SD card
- Enter your custom recovery, and flash it
- After the successful flash, reboot your system
- CWM will ask you if you want to keep your custom recovery, say NO. Remember, you want to go back to stock. So let the zip do it's job
Step 3: Check your System Date and Time
- Once booted, make sure that your date and time (time zone included) is correct.
Step 4: Check for System Updates
- Go to Settings >> About Tablet >> System Update >> Check now
Step 5: Wait
- If a pop-up is saying that you're on the latest version, try again at a later time.
- If there's no pop-up saying you're on the latest version, wait. It's a 252MB JB rom downloading in the background.
Step 6: OTA Update
- Once the JB zip is downloaded, a pop-up will say "Install Later, More details, Install Now"
- Select Install Now
- After a few familiar windows, you will now be on the JB recovery, and the JB rom. Ready for the adventure ahead.
This is nice, but a little info regarding why installing JB bootloader would be nice (if I remember correctly one of the things is to reduce the screen flicker, but that's what I THINK), and also how to root and get back in custom ROM road
Oh, and also, is there a way to know what verion of tab we have if we're already on custom ROM?
Lusanagi said:
This is nice, but a little info regarding why installing JB bootloader would be nice (if I remember correctly one of the things is to reduce the screen flicker, but that's what I THINK), and also how to root and get back in custom ROM road
Oh, and also, is there a way to know what verion of tab we have if we're already on custom ROM?
Click to expand...
Click to collapse
The main reason that you would want to have the JB bootloader, is to fix the audio stutter bug of the ICS bootloader.
(If you're on the ICS bootloader, play some music files, then turn your screen off. The CPU throttles down to the point of slowing down your music player.)
About how to root JB, I think it should deserve it's own thread. I simply follow the one here, it's pretty complete already (I rooted my stock JB just an hour ago):
http://forum.xda-developers.com/showthread.php?p=35907925#post35907925
And yes, whatever ROM you are on, you almost always have the settings >> about phone menu.
what I meant was get the appropriate build (either WW.GEN 1 or AAP.AU2); I did enter About Phone, but wasn't able to find any of that data (obviously)
Lusanagi said:
what I meant was get the appropriate build (either WW.GEN 1 or AAP.AU2); I did enter About Phone, but wasn't able to find any of that data (obviously)
Click to expand...
Click to collapse
Ah... good point. What I personally did was to restore my nandroid back-up from my stock image.
As an alternative, I would say flash NoThrills' optimized WW Gen1 rom. However, I do admit that it is something that I never tried as base. And it's a "do it at your own risk" thing.
Firmware version 1.073 A510 ICS
After flashing you will have stock firmware 1.73.00 WW GEN with closed bootloader.
Flash the fastboot mode (with unlock bootloader).
Run the restore.bat in the extracted archive folder.
After flashing tablet upgraded to firmware version AV051_A510_1.034.00_WW_GEN1 by OTA.
First post in 4PDA
Sorry for my english .. :cyclops:
salisbury_steak said:
Hello co-A510 users,
I've been lurking for quite a while and I repeatedly see questions about "how to get the JB bootloader?". Followed by the answer "Go back to stock ICS, then get the OTA.". Usually followed by the follow-up question "B-b-but... how?"
This post attempts to answer that follow-up question, for most folks, in the easiest way possible.
The Six Steps to Stock:
Step 1: Download the Stock Acer OS (rom zip)
- Go to http://www.acer.com.au/ac/en/AU/content/drivers
- Select Tablet >> Iconia A >> A510 in the product list
- On the new web portion that will appear, select the "O.S." tab, and download your appropriate build (mine is WW.GEN 1)
Step 2: Flash the OS (rom zip)
- Save the zip in your SD card
- Enter your custom recovery, and flash it
- After the successful flash, reboot your system
- CWM will ask you if you want to keep your custom recovery, say NO. Remember, you want to go back to stock. So let the zip do it's job
Step 3: Check your System Date and Time
- Once booted, make sure that your date and time (time zone included) is correct.
Step 4: Check for System Updates
- Go to Settings >> About Tablet >> System Update >> Check now
Step 5: Wait
- If a pop-up is saying that you're on the latest version, try again at a later time.
- If there's no pop-up saying you're on the latest version, wait. It's a 252MB JB rom downloading in the background.
Step 6: OTA Update
- Once the JB zip is downloaded, a pop-up will say "Install Later, More details, Install Now"
- Select Install Now
- After a few familiar windows, you will now be on the JB recovery, and the JB rom. Ready for the adventure ahead.
Click to expand...
Click to collapse
Hi,
I'm keen to update my bootloader, and have been trying to get it done for a while now.
However, i got stuck while following your instructions... at the beginning already!
At that url you quoted, there are only UPDATE files. They won't work, tried already. Those need you to have stock rom.
Where can you get a real stock rom zip?
Thanks!
.A.
Sent from my LG-D802 using XDA Free mobile app
Hi.
I am trying to get stock jb Rom on my 511 (sorry, i know 510 is in the threat).
Cwm 6.0.4.5, jb bootloader, cm11 and rooted. Full wiped and formated.
Downloaded 4.0 from Acer, edited update.zip 1. line ond got cwm error 7 device probably encrypred.
Tried same with 4.1 from Acer and got cwm error too.
Dont know what to do now?
Could anyone provide help?
Update.............
Now i am on ics, but ota updates could not be downloaded because of unstable network. Flashing update.zip via sd ends in red android logo (tried editing 1st line) after 1/3 progress?
DAMN...
I must search a little bit under my old account (because I've forgotten sometimes the username
Pls gave a look here
http://forum.xda-developers.com/showthread.php?t=2046832
Any idea how to solve this? http://i83.photobucket.com/albums/j293/socalrailroader/IMG_20120430_012752.jpg
x4x3 said:
Sent from my LG-D802 using XDA Free mobile app
Hi.
I am trying to get stock jb Rom on my 511 (sorry, i know 510 is in the threat).
Cwm 6.0.4.5, jb bootloader, cm11 and rooted. Full wiped and formated.
Downloaded 4.0 from Acer, edited update.zip 1. line ond got cwm error 7 device probably encrypred.
Tried same with 4.1 from Acer and got cwm error too.
Dont know what to do now?
Could anyone provide help?
Update.............
Now i am on ics, but ota updates could not be downloaded because of unstable network. Flashing update.zip via sd ends in red android logo (tried editing 1st line) after 1/3 progress?
DAMN...
Click to expand...
Click to collapse
monacoo said:
Any idea how to solve this? http://i83.photobucket.com/albums/j293/socalrailroader/IMG_20120430_012752.jpg
Click to expand...
Click to collapse
Hi both of you, I know I am terribly late, but I have basically the same problem.
I wanted to go back to the latest stock version because I am selling the tablet.
Before I had all kinds of CM and then NoThrills and wanted to go completely stock.
I managed to get 4.0/ICS with all Stock options, but I couldn't find a way to upgrade to JB with any "official" method.
The standard OTA search says "Unstable network connection" and the SD card update.zip ends with the red triangle robot.
Personally the journey is at an end for me, since I don't care, it will stay on ICS.
Maybe one has to fiddle with the bootloader lock/unlock, but I am tired of it.
Sorry for not being helpful, just saying I have the exact same problem.
I didn't see any guides for rooting/flashing roms for the motorola photon q. Is it easy? I am used to using odin for my Epic 4G. I want to be sure before I use my upgrade with Sprint, thanks.
So instead of Odin, you use RSD Lite and 'FXZ' files.
[05-08-2013] Photon Q FXZ
As for how to root, [CWM] 6.0.1.0 and how to root covers that nicely.
However, that version of CWM is a bit old, and won't flash KitKat ROM's - so go thru the unlock bootloader process and flash OpenRecovery or TWRP:
[recovery] TWRP 2.6.3.1
[25-11-2013] Photon Q Open Recovery 2.09
arrrghhh said:
So instead of Odin, you use RSD Lite and 'FXZ' files.
[05-08-2013] Photon Q FXZ
As for how to root, [CWM] 6.0.1.0 and how to root covers that nicely.
However, that version of CWM is a bit old, and won't flash KitKat ROM's - so go thru the unlock bootloader process and flash OpenRecovery or TWRP:
[recovery] TWRP 2.6.3.1
[25-11-2013] Photon Q Open Recovery 2.09
Click to expand...
Click to collapse
Thanks, but I'm still a bit confused. What are RSD Lite and 'FXZ' files? I clicked the first link that you posted,
"[05-08-2013] Photon Q FXZ" and clicked the "Download" hyperlink and downloaded Android 4.1.2
Blur_Version.98.10.5.XT897.Sprint.en.US. What is this? For rooting or unbricking? I tried the other links too, but I
didn't understand what they were about and got lost. Would you please explain it in more detail? Any idea when
CM11 Stable is going to be released?
Thanks.
EpicSaga said:
Thanks, but I'm still a bit confused. What are RSD Lite and 'FXZ' files? I clicked the first link that you posted,
"[05-08-2013] Photon Q FXZ" and clicked the "Download" hyperlink and downloaded Android 4.1.2
Blur_Version.98.10.5.XT897.Sprint.en.US. What is this? For rooting or unbricking? I tried the other links too, but I
didn't understand what they were about and got lost. Would you please explain it in more detail? Any idea when
CM11 Stable is going to be released?
Thanks.
Click to expand...
Click to collapse
You use Odin on a Samsung phone with a TAR file to return it to stock / unbrick.
You use RSD on a Motorola phone with a FXZ file to do the same.
CM usually releases their stable version when the next big Android version is released or is coming near. Thus, CM11 Stable is expected to be out in May~July (when the 4.4 cycle ends and Google announces next Android version + next Nexus devices).
Sent from Google Nexus 4 @ CM11
EpicSaga said:
Thanks, but I'm still a bit confused. What are RSD Lite and 'FXZ' files? I clicked the first link that you posted,
"[05-08-2013] Photon Q FXZ" and clicked the "Download" hyperlink and downloaded Android 4.1.2
Blur_Version.98.10.5.XT897.Sprint.en.US. What is this? For rooting or unbricking? I tried the other links too, but I
didn't understand what they were about and got lost. Would you please explain it in more detail? Any idea when
CM11 Stable is going to be released?
Thanks.
Click to expand...
Click to collapse
I said "instead of Odin"... I thought that would clue you in.
RSD Lite is like Odin. The FXZ files are complete stock backups - recovery, system, boot, everything completely stock. So yea, it's your way out if you do manage to do something wrong, or if you simply want to go back to a completely stock setup (again, including recovery).
CM11 is already pretty 'stable' although it's still in the "nightly" phase. I don't work for CM, nor do I dictate when they do their releases.
thanks for this
AndyYan said:
You use Odin on a Samsung phone with a TAR file to return it to stock / unbrick.
You use RSD on a Motorola phone with a FXZ file to do the same.
CM usually releases their stable version when the next big Android version is released or is coming near. Thus, CM11 Stable is expected to be out in May~July (when the 4.4 cycle ends and Google announces next Android version + next Nexus devices).
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Thank you for those details. I haven't heard anything of Sprint releasing any more androids with qwerty keyboards. Maybe I should order one soon. I want Cyanogen Mod on it though. Are there any other Cyanogen Mod stable versions out now for the Photon Q? I've tried the 10.2 links but get an error. I've never had to unlock a bootloader before. Some of the possible results seem concerning. I don't want to ruin the phone.
arrrghhh said:
I said "instead of Odin"... I thought that would clue you in.
RSD Lite is like Odin. The FXZ files are complete stock backups - recovery, system, boot, everything completely stock. So yea, it's your way out if you do manage to do something wrong, or if you simply want to go back to a completely stock setup (again, including recovery).
CM11 is already pretty 'stable' although it's still in the "nightly" phase. I don't work for CM, nor do I dictate when they do their releases.
Click to expand...
Click to collapse
Thanks for the update on RSD Lite. I didn't see RSD Lite in your links though. Maybe I missed it. Would you mind shooting me the link? I found RSDLite5.6.rar here on XDA. Is RDSLite5.6.rar the best to use to flash a Cyanogenmod ROM?
AndyYan updated me on the availability of Cyanogenmod, I didn't know that the next Stable version of CM is usually released unitl after the the next android operating system is released. Will the Photon Q be able to get more CM updates after CM11? I heard that the Samsung Epic 4G won't be able to.
What is the unlock bootloader process? I tried some of the links but got an access denied page. Then I got something where I would have to agree to legal terms. https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth Is this really necessary?
Thank you
EpicSaga said:
Thanks for the update on RSD Lite. I didn't see RSD Lite in your links though. Maybe I missed it. Would you mind shooting me the link? I found RSDLite5.6.rar here on XDA. Is RDSLite5.6.rar the best to use to flash a Cyanogenmod ROM?
AndyYan updated me on the availability of Cyanogenmod, I didn't know that the next Stable version of CM is usually released unitl after the the next android operating system is released. Will the Photon Q be able to get more CM updates after CM11? I heard that the Samsung Epic 4G won't be able to.
What is the unlock bootloader process? I tried some of the links but got an access denied page. Then I got something where I would have to agree to legal terms. https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth Is this really necessary?
Thank you
Click to expand...
Click to collapse
You still didn't get it... RSD is for getting back to stock. To flash a custom ROM you would have to load a custom recovery via fastboot. And to actually use fastboot you need an unlocked bootloader. If you don't see a "WARNING - BOOTLOADER UNLOCKED" message when you power on your phone, yours is NOT unlocked and it's necessary to unlock it before you proceed.
As for continued CM support, one particular good thing about Photon Q is that it uses a Qualcomm MSM8960 CPU which is strongly supported by Qualcomm (and maybe Google - most current Nexus devices use them). Basically, this means we can get newer CM builds faster than those with obsolete CPUs, like Epic 4G's Samsung S5PC110 (I once had an Epic 4G too!).
AndyYan said:
You still didn't get it... RSD is for getting back to stock. To flash a custom ROM you would have to load a custom recovery via fastboot. And to actually use fastboot you need an unlocked bootloader. If you don't see a "WARNING - BOOTLOADER UNLOCKED" message when you power on your phone, yours is NOT unlocked and it's necessary to unlock it before you proceed.
As for continued CM support, one particular good thing about Photon Q is that it uses a Qualcomm MSM8960 CPU which is strongly supported by Qualcomm (and maybe Google - most current Nexus devices use them). Basically, this means we can get newer CM builds faster than those with obsolete CPUs, like Epic 4G's Samsung S5PC110 (I once had an Epic 4G too!).
Click to expand...
Click to collapse
I downloaded the zip file "adb_fastboot_and_other_tools", then I ran "adb-setup-1.2". It is the 15 seconds ADB installer version 1.2.. At the prompt that says "Do you want to install ADB and Fastboot? [Y/N]" I selected Y. Then it prompted me "Do you want to install device drivers? [Y/N]" I selcted Y. It took me to the device installation wizard. I clicked next and "The drivers were successfully installed on this computer." Google, Inc. (WinUSB)Android Usb Device Class (01/27/2014 9.0.0000.00000)" I clicked finish It installed the 64-bit driver.
Is there anything else I need to do to install fastboot or was this just the drivers for it?
EpicSaga said:
I downloaded the zip file "adb_fastboot_and_other_tools", then I ran "adb-setup-1.2". It is the 15 seconds ADB installer version 1.2.. At the prompt that says "Do you want to install ADB and Fastboot? [Y/N]" I selected Y. Then it prompted me "Do you want to install device drivers? [Y/N]" I selcted Y. It took me to the device installation wizard. I clicked next and "The drivers were successfully installed on this computer." Google, Inc. (WinUSB)Android Usb Device Class (01/27/2014 9.0.0000.00000)" I clicked finish It installed the 64-bit driver.
Is there anything else I need to do to install fastboot or was this just the drivers for it?
Click to expand...
Click to collapse
I think instead of universal drivers like that, maybe you should go seek drivers specific drivers for Motorola phones or just for our model. I remembered installing a Motorola-specific driver before I could even do fastboot.
Of course I could be wrong - waiting on someone to proof or disproof that.
Sent from Google Nexus 4 @ CM11
Just ordered one
I ordered a Photon Q on Sunday and should have it by Wednesday. I need to have a hotspot on it so I can have internet. I currently use the
hotspot on my Samsung Epic 4G that I'll be replacing with my Photon Q for internet now. Are there any stable Cyanogenmod ROMS? If not what
is the most stable ROM? I'm used to using a guide and youtube videos from QBKing77 in order to root and flash CM on my Epic. Are there any
step by step guides and/or videos that anyone knows of? I need to flash a stable ROM, the most dependable, as soon as it comes in the mail.
Thanks
EpicSaga said:
I ordered a Photon Q on Sunday and should have it by Wednesday. I need to have a hotspot on it so I can have internet. I currently use the
hotspot on my Samsung Epic 4G that I'll be replacing with my Photon Q for internet now. Are there any stable Cyanogenmod ROMS? If not what
is the most stable ROM? I'm used to using a guide and youtube videos from QBKing77 in order to root and flash CM on my Epic. Are there any
step by step guides and/or videos that anyone knows of? I need to flash a stable ROM, the most dependable, as soon as it comes in the mail.
Thanks
Click to expand...
Click to collapse
Another former Epic 4G dude? Yeah :highfive:
Photon Q can initially be hard to deal with, but things will become very easy after you unlocked your bootloader. My Photon Q was bought unlocked so I don't know how to unlock it myself - just search it out - but after unlocking, just go to fastboot mode, flash in a custom recovery and you're ready to go for any custom ROMs you want. We have CM11, Carbon, many nice ROMs to try out. Personally, I always go for CM for the familiar layout/feeling.
AndyYan said:
Another former Epic 4G dude? Yeah :highfive:
Photon Q can initially be hard to deal with, but things will become very easy after you unlocked your bootloader. My Photon Q was bought unlocked so I don't know how to unlock it myself - just search it out - but after unlocking, just go to fastboot mode, flash in a custom recovery and you're ready to go for any custom ROMs you want. We have CM11, Carbon, many nice ROMs to try out. Personally, I always go for CM for the familiar layout/feeling.
Click to expand...
Click to collapse
I have to find out how to unlock it. Is fastboot mode on the Photon Q kind of like download mode on the Epic?
How do you unlock the bootloader? Is that what the ADT-bundle is for?
EpicSaga said:
I have to find out how to unlock it. Is fastboot mode on the Photon Q kind of like download mode on the Epic?
Click to expand...
Click to collapse
Different.
Photon Q also have a download mode, where you can use RSDLite to flash FXZ files, similar to how you use Odin to flash TAR files for Epic 4G.
EpicSaga said:
How do you unlock the bootloader? Is that what the ADT-bundle is for?
Click to expand...
Click to collapse
Dunno. I reckon ADT bundle gets you the fastboot drivers.
Sent from Google Nexus 4 @ CM11
Phone arrived
I got my Photon Q today in the mail, but I haven't activated it yet. I need to know how to unlock it first. Would someone please tell me how to unlock it? Can you brick the phone by making a mistake during the unlocking process?
just google "photon q bootloader unlock". there are some nice guides
Gesendet von meinem PHOTON Q mit Tapatalk
EpicSaga said:
I got my Photon Q today in the mail, but I haven't activated it yet. I need to know how to unlock it first. Would someone please tell me how to unlock it? Can you brick the phone by making a mistake during the unlocking process?
Click to expand...
Click to collapse
http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Is the one I used. I don't think you can brick the phone attempting this, assuming you follow the directions. The only thing people seem to complain about is the code not working properly to unlock - copy/paste works best.
Android SDK Managaer Log error
arrrghhh said:
http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Is the one I used. I don't think you can brick the phone attempting this, assuming you follow the directions. The only thing people seem to complain about is the code not working properly to unlock - copy/paste works best.
Click to expand...
Click to collapse
I opened the Android SDK Manager twice and the updates that it did said " failed to fetch" some files, then said that it was successful anyway. Does that mean that it downloaded what it needed and it is ok?
Fetching https://dl-ssl.google.com/android/repository/addons_list-2.xml
Fetched Add-ons List successfully
Fetching URL: https://dl-ssl.google.com/android/repository/repository-9.xml
Done loading packages.
Fetching https://dl-ssl.google.com/android/repository/addons_list-2.xml
Failed to fetch URL https://dl-ssl.google.com/android/repository/addons_list-2.xml, reason: Connection to https://dl-ssl.google.com refused
Fetched Add-ons List successfully
Fetching URL: https://dl-ssl.google.com/android/repository/repository-9.xml
Failed to fetch URL https://dl-ssl.google.com/android/repository/repository-9.xml, reason: HttpHostConnect Connection to https://dl-ssl.google.com refused
Done loading packages.
Thank you.
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!