Related
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
razorseal said:
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
Click to expand...
Click to collapse
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Are you unlocked??
Sent from my MB860 using XDA App
Paschalis said:
Are you unlocked??
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
As long as he's on 1.8.3. that shouldn't matter.
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Paschalis said:
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Refer to the link I sent him...
Unlocked as in rooted?
I'm running gingerblur, so yes, I'm rooted so i have access to cwm...
Can I just flash that? And yes I'm on 1.8.3
Flashing via sbf?
Sent from my MB860 using XDA App
mpalatsi said:
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
razorseal said:
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA. Edit: actually, that one is modified with the unlocked bootloader.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Edit2: If it makes you feel any better, I personally used the method you described in the OP to upgrade. Wasn't that hard or "complicated".
feisty_noodle said:
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Click to expand...
Click to collapse
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
I'm in the same boat. I'm on ginger blur and 1.83 and I just want to update, unlock and root.I would like to revert back if need be.
Sent from my MB860 using XDA App
razorseal said:
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
Click to expand...
Click to collapse
This link was exactly what I used.
As far as upgrading in the future, you can use the resources found here, on XDA. People will be dissecting new updates to remove the nasty bits (bootloaders and such).
If you decide that you want to play with custom ROMs, you can do that, too.
You will NOT be able to use OTA's unless you backtrack to a fully stock ROM via official OTA's or SBF's. This can be done, but will require some careful work on your part.
For the bootloader unlocking--go read the Pudding thread here. It is very a straightforward procedure.
Edit: if your first Motorola boot screen has the word "Unlocked" in the upper left corner, then you are unlocked. If not, then ...
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Paschalis said:
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Click to expand...
Click to collapse
well then I should stay from that link that was provided here considering it's an sbf file...
Paschalis said:
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
feisty_noodle said:
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
Click to expand...
Click to collapse
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
razorseal said:
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
Click to expand...
Click to collapse
Yes, zomgunlock-lite.sbf is the contents of "pudding".
That is your bootloader that has the unlock code. Just follow Ken's instructions from the page you linked to.
Also, here is the link for an easy root method after you are done.
If you are still scared, watch the videos of the process here. I didn't have time to look too carefully, but it clearly shows what the bootloader screen should look like when you've successfully unlocked.
Good luck, I have to sleep now.
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
razorseal said:
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
Click to expand...
Click to collapse
You are not in a bricking situation! Take a deep breath.
I have not seen this, but others have ...
http://forum.xda-developers.com/showthread.php?t=1062727
Do some homework.
I am really going now.
I just reflashed.... I guess something got corrupted it works now
alright, off to unlocking, and doing the radio tweak along with battery % and att logo removal
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
lightningdude said:
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
Click to expand...
Click to collapse
I am messing with the files now trying to see if it can uncompressed if it is. And the font is so big because someone already thanked me for the post, and I dont think its right I get the thanks as you were the one who brought them out... I'm just a messenger. So big font to get peoples attention to thank you not me
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
My Mom was just saying today how she wants to sue Verizon in a class action for raising fees and what not. Maybe we should all get together and start that badn wagon. Haha.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
I dislike VZjust as much as the next guy, but VZ feels that if you are a subsidized phone with a plan then the phone is not yours until the contract is up. For me i bought my phone off ebay to replace the total crap that is Motorola Droid 2 Global (loved the keyboard, hated the Motorblur and locked BL)
But I agree, VZ is raping everyone who has a wirelss plan with them, but no news here all Carriers do that.
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
droidjunkie said:
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
Click to expand...
Click to collapse
Free with a 2 year contract or free from someone you knew? If its free from a contract of 2 years to them they own the device for the length of the contract. I am not trying to support VZ, just saying that I have seen attempts (not firsthand) of people trying to sue VZ or other carriers for the same thing and they are always squashed
jgregoryj1 said:
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Click to expand...
Click to collapse
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
Can you PM me a Nandroid backup of this?
Did a baseband update come with this?
Leraeniesh said:
Can you PM me a Nandroid backup of this?
Click to expand...
Click to collapse
oohh, that would be awesome...... net.... got lucky. But in a good way.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
kelvenha55 said:
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
jgregoryj1 said:
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
Click to expand...
Click to collapse
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Leraeniesh said:
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Click to expand...
Click to collapse
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Edit: Dident work. Just as expected
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Leraeniesh said:
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Click to expand...
Click to collapse
Just a reminder, now that I am thinking on it I am not so sure it will work.... not 100% sure, so you might relcok and find you cannot unlock.....
poo-tang said:
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Click to expand...
Click to collapse
Oh yeah that right! We have the custom recovery app from google play store.... sweet, that will help..
https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.
Phone was working great until it just froze, I did a battery pull and now it won't go past the HTC white logo screen.
It boots into recovery, but only as safe mode.
Cannot access internal memory or external memory.
Haven't tried wiping the system since I can't really access the storage space to flash anything, or even restore a backup.
It's not dead. Simone else just posted the same exact problem.
Download the latest ruu. Pull your external sdcard.
Put sdcard in the computer.
Copy the ph85img.zip to it.
Put sdcard in phone.
Boot to bootloader.
Follow the on screen instructions.
That'll get you back to square one.
Also look for Odysseus' post in the other threads. He has some good information on this subject.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
It's not dead. Simone else just posted the same exact problem.
Download the latest ruu. Pull your external sdcard.
Put sdcard in the computer.
Copy the ph85img.zip to it.
Put sdcard in phone.
Boot to bootloader.
Follow the on screen instructions.
That'll get you back to square one.
Also look for Odysseus' post in the other threads. He has some good information on this subject.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice. I was thinking about putting the ruu but I wasn't sure. I needed confirmation on this issue.
I will keep you posted about what happens.
Darin_Ram said:
Thank you for the advice. I was thinking about putting the ruu but I wasn't sure. I needed confirmation on this issue.
I will keep you posted about what happens.
Click to expand...
Click to collapse
As Chevy said, someone else posted with this exact same problem a day or two ago. Since you're S-off and unlocked the procedure is to download the latest factory image for your device. You can't flash one from another carrier or you'll brick it. There are links in one of the "pinned" threads at the top of the forums.
Once you have it downloaded rename it to "PH85IMG.zip" (note the capitalization must be exactly the same) and place it in the root of your external SD card. Now comes the fun part. It won't flash on an unlocked bootloader, so you must relock it using ADB commands or with the Amaze toolkit (don't worry you won't loose S-off). BTW I hope you saved the HTC unlock blob from when you first unlocked as you'll need it again to unlock later.
Flash the image from the bootloader hboot. When it's finished then go to settings / about phone /software information and accept any HTC updates. With a T-Mobile phone there will be at least three OTA's depending on which image you installed. Two of them are 30MB and require rebooting in between. The last one just updates a couple of .apks and doesn't need a reboot. You need these to get the latest radio.
Once all of the updating is finished you'll be back to factory with the latest radio. Now all you have to do is unlock, install a recovery, reroot, SuperCID, and you'll be ready to play again.
I hope this helps
Thanks again for the help, the phone is functional again. Does anybody have any idea why this happens?
Odysseus1962 said:
As Chevy said, someone else posted with this exact same problem a day or two ago. Since you're S-off and unlocked the procedure is to download the latest factory image for your device. You can't flash one from another carrier or you'll brick it. There are links in one of the "pinned" threads at the top of the forums.
Once you have it downloaded rename it to "PH85IMG.zip" (note the capitalization must be exactly the same) and place it in the root of your external SD card. Now comes the fun part. It won't flash on an unlocked bootloader, so you must relock it using ADB commands or with the Amaze toolkit (don't worry you won't loose S-off). BTW I hope you saved the HTC unlock blob from when you first unlocked as you'll need it again to unlock later.
Flash the image from the bootloader hboot. When it's finished then go to settings / about phone /software information and accept any HTC updates. With a T-Mobile phone there will be at least three OTA's depending on which image you installed. Two of them are 30MB and require rebooting in between. The last one just updates a couple of .apks and doesn't need a reboot. You need these to get the latest radio.
Once all of the updating is finished you'll be back to factory with the latest radio. Now all you have to do is unlock, install a recovery, reroot, SuperCID, and you'll be ready to play again.
I hope this helps
Click to expand...
Click to collapse
Holy crap I did none of the above. The ruu flashed on the unlocked bootloader, I didn't even capitalize it.
The bootloader stayed unlocked, I didn't check the supercid on it................................................................ I just re-installed the recovery
It booted fine though, so I have no idea what's going on
Darin_Ram said:
Thanks again for the help, the phone is functional again. Does anybody have any idea why this happens?
Click to expand...
Click to collapse
I'm as careful as they come. but it happened to me a few weeks back too. Sometimes you just get a bad flash, other times NAND memory cells get stuck (they wear out over time) or are slow to accept data. All it takes is an important part of the file system flashed onto a bad data block and the whole thing can get stuck in a loop. For me I had been trying out a bunch of ROMS and somehow a kernel failed to flash. I ended up with a kernel mismatch (kernel modules don't match the kernel) which resulted in a bootloop.
As a precaution I just keep an old 2GB SD-card handy that only has the Amaze image on it, so in case of an emergency all I have to do is relock the bootloader, stick in the SD card and I'm back in action within 15 mins.
Odysseus1962 said:
I'm as careful as they come. but it happened to me a few weeks back too. Sometimes you just get a bad flash, other times NAND memory cells get stuck (they wear out over time) or are slow to accept data. All it takes is an important part of the file system flashed onto a bad data block and the whole thing can get stuck in a loop. For me I had been trying out a bunch of ROMS and somehow a kernel failed to flash. I ended up with a kernel mismatch (kernel modules don't match the kernel) which resulted in a bootloop.
As a precaution I just keep an old 2GB SD-card handy that only has the Amaze image on it, so in case of an emergency all I have to do is relock the bootloader, stick in the SD card and I'm back in action within 15 mins.
Click to expand...
Click to collapse
That's a good idea, but is it really necessary for me right now? You know, since the bootloader is still unlocked, SuperCID is still 1's and I'm still S-OFF?
If it happens again, I'll re-lock, reload, and re-flash
Darin_Ram said:
Holy crap I did none of the above. The ruu flashed on the unlocked bootloader, I didn't even capitalize it.
The bootloader stayed unlocked, I didn't check the supercid on it................................................................ I just re-installed the recovery
It booted fine though, so I have no idea what's going on
Click to expand...
Click to collapse
Did you flash from your SD card or push the ruu with ADB? Usually it will only accept the zip image from the bootloader, but the ruu can be pushed with ADB.
What ever the case I'm just glad things worked out.
Odysseus1962 said:
Did you flash from your SD card or push the ruu with ADB? Usually it will only accept the zip image from the bootloader, but the ruu can be pushed with ADB.
What ever the case I'm just glad things worked out.
Click to expand...
Click to collapse
Flashed via SD card.
By the way, can we dual boot this phone?
I know, it's risky booting it to two os, but I'm just wondering cause making backups and restoring nandroids are becoming a pain every time I want to take good photos. :/ So I was wondering if we could dual boot.
I dual booted my old defy that only had about half the ram, and half the processing speed lmao so why not this device?
Darin_Ram said:
Flashed via SD card.
By the way, can we dual boot this phone?
I know, it's risky booting it to two os, but I'm just wondering cause making backups and restoring nandroids are becoming a pain every time I want to take good photos. :/ So I was wondering if we could dual boot.
I dual booted my old defy that only had about half the ram, and half the processing speed lmao so why not this device?
Click to expand...
Click to collapse
I could dual boot on my old HD2 as well. I don't believe any devs here have written a bootloader with that capability for the Amaze, but you could always just do a search and find out for yourself. It might be just a matter of porting an existing app to this device. Good luck!!!!
Odysseus1962 said:
I could dual boot on my old HD2 as well. I don't believe any devs here have written a bootloader with that capability for the Amaze, but you could always just do a search and find out for yourself. It might be just a matter of porting an existing app to this device. Good luck!!!!
Click to expand...
Click to collapse
I googled it, the only thing that came up was an old thread about someone asking for the system/cache/boot sizes.
Looks like no one really wanted it for this device.
I wish they did though, the Sense camera is amazing
Darin_Ram said:
I googled it, the only thing that came up was an old thread about someone asking for the system/cache/boot sizes.
Looks like no one really wanted it for this device.
I wish they did though, the Sense camera is amazing
Click to expand...
Click to collapse
I know what you mean. One reason I keep coming back to NRG is because of camera and video. I can't find a replacement that comes close.
Odysseus1962 said:
I know what you mean. One reason I keep coming back to NRG is because of camera and video. I can't find a replacement that comes close.
Click to expand...
Click to collapse
I've actually never flashed that one lol
But I was reading up and apparently there's a HD camera mod (can't remember if it was the desire or sensation) that was supposed to take better 1080p videos and superb photos.
I saw it floating the forums a while ago, but it was a sense cam so I couldn't flash it. I had Pac 4.3 at the time.
Now I'm on 4.4 Evervolv, so far so good. Lowest ram usage I've ever had with a lot of apps installed, so I'm happy with it.
I may or may not try Cyanogenmod 11 but I'm in no hurry.
Darin_Ram said:
Thanks again for the help, the phone is functional again. Does anybody have any idea why this happens?
Click to expand...
Click to collapse
No idea why it happens but I had the same symptoms - wouldn't get past the HTC logo but this happened after I had simply powered the phone off and removed the battery after I wasn't going to use it for a while [playing with the Lumia 920].
It seemed like the partition map gets wiped out or something causing the problem.
The hdd camera is in the aroma installer I'm my viper Rom.
Well also be the camera default in the upcoming release of jellybean sense and other future releases.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
The hdd camera is in the aroma installer I'm my viper Rom.
Well also be the camera default in the upcoming release of jellybean sense and other future releases.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Sounds good, but no kit kat?
One Rom at a time... Lol
Ravike and I have been working on this for a while now. Can't progress until we get the next level finished, then the next version will be hopefully easier. We are getting closer. Ravike has a lot of building from scratch to do.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
One Rom at a time... Lol
Ravike and I have been working on this for a while now. Can't progress until we get the next level finished, then the next version will be hopefully easier. We are getting closer. Ravike has a lot of building from scratch to do.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Ooooh
I used your rom, I love the full gpu rendering. Haven't tried the camera yet, but looking forward to that HD mod that's on there.
Nenamark2 gets 50.5 fps!!!!!!!!!! That's the most I've ever seen this device go up to!!!!
Damn! Awesome lol
Antutu shows that the graphics goes over the 4000 mark. Definitely love it.
Darin_Ram said:
Ooooh
I used your rom, I love the full gpu rendering. Haven't tried the camera yet, but looking forward to that HD mod that's on there.
Nenamark2 gets 50.5 fps!!!!!!!!!! That's the most I've ever seen this device go up to!!!!
Damn! Awesome lol
Antutu shows that the graphics goes over the 4000 mark. Definitely love it.
Click to expand...
Click to collapse
ViperAmaze was one of the first ROMs I tried when I got mine. I loved everything about it except I had Bluetooth pairing and WiFi tethering issues. Since I'm a truck driver, I need hands free on my daily driver. Unfortunately, it seems most if not all of the builds that are not derived directly from the OEM HTC Amaze, have some type of Bluetooth or WiFi issue that's not easily overcome.
I have a vzw max and i recently reverted everything back to stock and unrooted; or so i believed. The kernel still says 3.4.10 etc. and the phone has no signal nor can it find my location. It keeps rebooting every 30 secs or so and no matter what mode I put the device into, it isn't recognized by my PC. the bootloader is locked and I am S-Off. This all happened after I tried to flash CWM's HTC M7 recovery because the Max isn't listed and I couldn't figure out how to flash TWRP. Help please because this is getting crazy and I can't figure out what to do...
bump
nobody at all eh...
LocBox said:
nobody at all eh...
Click to expand...
Click to collapse
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
dude i feel for you.
why did you put m7 cwm on there. clearly not for this device.
can you still get to bootloader? if you can flash the correct recovery! then find a backup someone has done and restore. or flash the correct boot.img
dude here's the correct recovery
http://forum.xda-developers.com/showthread.php?t=2498749
Well the only problem is my any pc won't even detect that it's connected when I plug it into it. So I can't use any fastboot or adb methods and even when I put the phone into fastboot mode it doesn't connect either. I'm able to put it into bootloader mode and it doesn't reset but still no connection; just charges. I've tried flashing through stock recovery manually and it aborts every attempt I'm assuming because my BL is locked..
No it doesn't
dottat said:
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
no it doesnt'
LocBox said:
no it doesnt'
Click to expand...
Click to collapse
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Thanks
Dottat has helped me and not a moment too soon, I was seconds from printing out the return label for HTC and sending it in for a refurb exchange. smbh. thanks man.:good:
dottat said:
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
pradeepvizz said:
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
Click to expand...
Click to collapse
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
pradeepvizz said:
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
Click to expand...
Click to collapse
That is correct, full flash from bootloader. 0P3PIMG.zip on root of sd. and boom with some pow.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
dottat said:
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
Click to expand...
Click to collapse
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
JBS976 said:
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
Click to expand...
Click to collapse
Check your pm shortly. S-off later today ?
Sent from my HTC6600LVW using Tapatalk