Warning! There is a huge risk that you will permanently loose root with no way to regain root. Do not flash s-on before you flash this RUU. You will permanently loose root if you do!!!
Incredible_C_GB_S_VERIZON_WWE_4.06.605.2_Radio_2.1 5.10.07.07_NV.zip - 180.6 MB
MD5 Sum: 096d841530dd2f223ef4a1b701c7d429
Install Instructions:
•Rename the file to PB31IMG.zip
•Drop it on the root of the SD Card
•Boot into the bootloader
•Flash as usual
Next go here* to learn how to get root back. Your phone must still be s-off in order to regain full root.
*Sorry guys link is down. I'll add in the instructions here tomorrow.
Want to contact unrEVOked on IRC about the root situation and how you can help?You can speak to the unrEVOked team live.
Go to: unrEVOked IRC
IRC Instructions:
1. Type in a nickname into the nickname box. This is your name that will be displayed during the chat.
2. Type in the captcha.
3. Press connect.
Once connected the page will load and give some brief info. The page will fully load and you will notice a list of usernames on the right. These are all the people currently in the IRC chat. You will also notice a text box at the very bottom of the page. Just type what you want to ask or say there and press [enter] on your keyboard to send your message. Just wait after you send your message. Someone will soon reply. The IRC is similar to an instant messenger, its just web based.
Hopefully this will help some of you to know where to go to get the info you need for this issue.
Disclaimer Please do not abuse this IRC channel. I'm sure unrEVOked is very busy trying to keep up with all these demands for new root patches. Lets not spoil this line of communication while we have it. Keep your questions clear and to the point. Also try to include only important information during your chat. Most importantly, be respectful and professional.
Click to expand...
Click to collapse
now someone pull the radio from this and post it.
k.electron said:
now someone pull the radio from this and post it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1227215
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
tiny4579 said:
So I pulled the RUU today, extracted system.img via yaffsexpert app from the market. Transferred to my PC for inspection. build.prop is exactly the same as the other leak using diff. I don't see any significant difference but we'll wait to hear from one of the official devs if there is a difference.
Click to expand...
Click to collapse
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
So everybody who did this is unrooted now or what
Ignore: I'm goofy and flashed the old zip instead of the new.
evilstewie23 said:
So everybody who did this is unrooted now or what
Click to expand...
Click to collapse
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
tiny4579 said:
Also, the boot.img from the RUU broke adb for me. Maybe I have to do something special with it.
Click to expand...
Click to collapse
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.
evilstewie23 said:
So everybody who did this is unrooted now or what
Click to expand...
Click to collapse
Yes if you flash this as is you are now unrooted.
I got the nag on first boot but havent after that
tiny4579 said:
If you flashed the zip file in the OP then it will return you to stock recovery and you will be unrooted yes. I don't know about S-OFF though, I'm not sure if it reverts it. It will install the bootloader but I thought S-OFF was deeper in the system than that. Maybe someone who installed this can tell us. If you're still S-OFF you should be able to flash a custom recovery. It will say S-ON or S-OFF at the top of the bootloader.
Click to expand...
Click to collapse
K thanks guess ill just wait to get this when I unroot for the official ota as soon as it cones out and someone discovers another rooting method for 2.3
davwman said:
I got the nag on first boot but havent after that
Click to expand...
Click to collapse
I rebooted a few times and got it every time. Hmm... I wonder if it's just me. I think I've figured out how to stop it though. Testing to make sure.
EDIT: LOL! I may have flashed the original one I had. Let me double check.
I'm pretty sure I flashed the original instead of the new. I had them named to close to the same. Sorry.
wildstang83 said:
Check the build.prop for sdk level and make sure your sdk is updated to what is required by this rom. Your Android drivers may be out of date? I'm just talking to hear myself talk, but it sounds good enough to check our bases here.
Yes if you flash this as is you are now unrooted.
Click to expand...
Click to collapse
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
tiny4579 said:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
Click to expand...
Click to collapse
+1 just tried it and ADB is disabled.
jermaine151 said:
+1 just tried it and ADB is disabled.
Click to expand...
Click to collapse
Do you know how to edit and repack boot.img files?
If so all you have to do is to unpack and change default.prop to this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
davwman said:
I got the nag on first boot but havent after that
Click to expand...
Click to collapse
Okay, after enough reboots I can say the following about the location nag:
1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.
2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag after every reboot. I guess we'll have to hack it to get rid of that.
3) If "Fast Boot" is disabled and you power down, then boot up, you get nagged.
I still see no reason why they delayed the OTA since nothing seems to be changed.
tiny4579 said:
I actually compared the build.prop in this to the build.prop in the rooted zip released earlier this week using diff and they're identical. It was the first thing I did as soon as I extracted the system.img from the RUU.
When I reverted to the earlier boot.img from the rooted zip or the boot.img from the leak a few months ago I got adb back. I don't think it's a change to the kernel but I bet they modified the ramdisk to disable adb.
Yep, confirmed it was disabled in the ramdisk. If you want/need adb access don't use the boot.img from the RUU today.
Click to expand...
Click to collapse
jermaine151 said:
+1 just tried it and ADB is disabled.
Click to expand...
Click to collapse
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
jermaine151 said:
Okay, after enough reboots I can say the following about the location nag:
1) If "Standalone GPS" is enabled, you get the nag on every reboot. If you disable that, you don't.
2) If "Fast Boot" is enabled and you power down, then boot up, you won't get it. Reboot doesn't use "Fast Boot" so you get the nag again. I guess we'll have to hack it to get rid of that.
I still see no reason why they delayed the OTA since nothing seems to be changed.
Click to expand...
Click to collapse
Maybe because of the wifi issue. Has anybody checked to see if we have wifi back now?
wildstang83 said:
Hmm, thats nice to know. I wonder if you guys remembered to go check the adb check box? If so and it isn't working and is disabled how hard it would be to enable it.
Click to expand...
Click to collapse
Yep, that's with USB debugging enabled.
tiny4579 said:
Do you know how to edit and repack boot.img files?
If so all you have to do is to unpack and change default.prop to this:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Try attached. It should work with adb and I believe have module compatibility with my OTA modules zip.
Click to expand...
Click to collapse
Are you saying you got adb to be enabled?
Related
I finally found a way to unlock the HBOOT! A patch is applied to the bootloader and then you can flash Unrevoked and get all the custom ROMS!!!
But be careful! It's not my fault if this tool will break your phone, so you're doing it on your own responsibility!! Also please read the instructions carefully! And don't remove power or unplug the USB cable while the unlock is running, otherwise you will brick your phone!!!
Instructions:
1. make a backup of all your apps and data on your phone just to be sure
2. download unlockhboot.zip and extract it somewhere. there is only one binary file unlockhboot
3. if you don't have adb then download it somewhere and make sure it's running
4. make sure you have USB debugging mode enabled
5. on your PC open a command line (Start --> Run --> then enter cmd)
6. change to the directory that contains the downloaded unlockhboot
7. type in the following commands:
adb push unlockhboot /data/local
adb shell
cd /data/local
chmod 744 unlockhboot
Click to expand...
Click to collapse
8. now to start flashing the patch.... just type in:
./unlockhboot
Click to expand...
Click to collapse
I made the process as simple as possible. The tool will get itself a root shell, extract your bootloader, patch it, and then flash it back. After this it will automatically boot into recovery mode and from there you should be able to flash Unrevoked!
HAVE FUN WITH YOUR NEW PHONE!!!
1st of April
Wrong date, eh?
Screenshots and test reports needed or its an aprils fool!!!!
Sent from my HTC Wildfire using XDA App
Lol!
Sent from my HTC Wildfire using Tapatalk
any confirmations??
edit :- tried... it actually april fool's day!!! LOL!!!! was still worth a try though!!
also, second time it gave me permission denied!!
ahahahahahahahaaa lolol
I should've waited till today to change my sig and then left it like that tomorrow - that would've been fun
Omg it worked!!!! Thanks a lot!!! finally got s-off
pyroblazer said:
any confirmations??
edit :- tried... it actually april fool's day!!! LOL!!!! was still worth a try though!!
also, second time it gave me permission denied!!
Click to expand...
Click to collapse
On your screenshot it seems the file is not on the phone. did you actually push the file? maybe your forgot the adb push command.
Just flashed Froyo RUU to try this out. It works great! Thanks a lot.
Edit: Tested ROM Manager, flashed new recovery fine.
I have error: Wrong date?
How to solve??? Help me
dungquoc said:
I have error: Wrong date?
How to solve??? Help me
Click to expand...
Click to collapse
I Also have this msg:
""error161: wrong date""
whats the problem??
ata63 said:
I Also have this msg:
""error161: wrong date""
whats the problem??
Click to expand...
Click to collapse
Basic scripts just work for one day. You need to buy a licence to let it work forever.
So you need to wait for an updated script. Maybe donating would speed up the process.
fifarunnerr said:
Basic scripts just work for one day. You need to buy a licence to let it work forever.
So you need to wait for an updated script. Maybe donating would speed up the process.
Click to expand...
Click to collapse
I see, I'm lucky :d
but my having error. "wrong date"
fifarunnerr said:
Basic scripts just work for one day. You need to buy a licence to let it work forever.
So you need to wait for an updated script. Maybe donating would speed up the process.
Click to expand...
Click to collapse
OR maybe it'll work tomorrow, you never know.
i can't believe this actually worked, im sooo happy now
Does it actually work or is this just a stupid jode?
nhnt11 said:
OR maybe it'll work tomorrow, you never know.
Click to expand...
Click to collapse
Ña, same problem.... we just have to wait? days? week?years?
Miyagi said:
Ña, same problem.... we just have to wait? days? week?years?
Click to expand...
Click to collapse
seriously... try tomorrow. he released it early, it activates only tomorrow. guess there's a bug which lets it work for some people... like the signal bug that happened only for a few. i'll upload a pic soon if you want.
nhnt11 said:
seriously... try tomorrow. he released it early, it activates only tomorrow. guess there's a bug which lets it work for some people... like the signal bug that happened only for a few. i'll upload a pic soon if you want.
Click to expand...
Click to collapse
that's pretty weird
Here is the OTA update zip.
http://www.androidfilehost.com/?fid=22946563261203148
d0c70dc593bdd729b14688a1be473102
http://tinyw.in/RwRh
d0c70dc593bdd729b14688a1be473102
Dammit, beat me to the punch lol. Thanks bud!
Sent from my SPH-L720 using Tapatalk 2
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
shabbypenguin said:
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
Click to expand...
Click to collapse
Will do. Running a backup right now and will install after that.
Putting stock back on.
Wiping Data
Installing update
Yep it is blocked.
crawrj said:
Yep it is blocked.
Click to expand...
Click to collapse
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
shabbypenguin said:
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
Click to expand...
Click to collapse
Yeah I plan on it. Attached the gz.
Pulling source now to run a diff and see what has changed in kernel beyond the obvious.
Be interested to see if they left that in the defconfig since they know someone will probably flip it back.
anyone check to see if kies would update em? would be a nice thing to have the tar for it as well
Just to confirm the obvious rooting did not work.
Installing the stock MDC kernel allows rooting.
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Well, that diff was actually productive.
They have made the change in the common defconfig for all i9505 variants.
So expect this to be coming to the rest of them soon.
Looks like on the kernel side a majority of the changes are to 3 files:
firmware/ssp_rev03.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1_fac.fw.ihex
Beyond those 3, many of the changes pertain to ATT and EUR variants.
Attaching a zip of the diff file for reference as I'll be spreading the word.
Guess I'll get with Agat to make an MDL kernel with that flipped off...
*Update 2* As Shabby mentioned, only Tmo and Sprint have seen this so far... so AT&T results can be ignored.
www.shabbypenguin.com/OUDstuff/Sams...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
sorry for teh delay, had to make breakfast for my daughter this is a MDL source built kernel, but with MDC ramdisk until i can get MDL ramdisk. it will allow root however
shabbypenguin said:
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Click to expand...
Click to collapse
The boot.img is in the update.zip already. Or do you still need it DD?
crawrj said:
The boot.img is in the update.zip already. Or do you still need it DD?
Click to expand...
Click to collapse
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
I haven't looked at the at&t threads but I would say they are wrong. You can install root but the kernel kills it. So it won't run. I have tried all three methods of install and it doesn't work.
1. Installing custom recovery and flashing supersu
2. Oding CFAutoRoot
3. Moto
shabbypenguin said:
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Click to expand...
Click to collapse
So you have the new kernel working? Where is that same old link again And thanks!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
crawrj is correct, its not a matte rof re-rooting its the binary is being killed as it tries to launch. att didnt get it in an update yet, only tmo and sprint for the us carriers.
crawrj said:
So you have the new kernel working? Where is that same old link again And thanks!
Click to expand...
Click to collapse
http://www.shabbypenguin.com/OUDstu...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
I have not rooted yet and im trying to push the OTA update now. once it goes through, you want me to try one of the rooting methods???
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
bd1212 said:
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
jonnythan said:
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
Click to expand...
Click to collapse
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
bd1212 said:
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
Click to expand...
Click to collapse
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
meant2live218 said:
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
Click to expand...
Click to collapse
I was under the impression that we cannot do a factory reset or we won't get the soak test OTA pushed to our phones. That's what the soak test post said atleast. Something along the lines of "DO NOT FACTORY RESET or you will not receive the OTA"... don't want to quote it directly since I'm under an NDA, but it was something like that. Did I misunderstand? If I use the Moto X toolkit or RSDLite to revert back to stock is that different than a factory reset?
jonnythan said:
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
Click to expand...
Click to collapse
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file. I'm still reading all of the links so I might not have gotten to the part where it explains what to do, so forgive me for that.
bd1212 said:
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file.
Click to expand...
Click to collapse
Right from my third link:
Next, you need to put the phone into "fastboot mode" as described above, also make sure usb debugging is enabled in the developer menu settings. Then download the FW for your phone found (follow what i said in regards to the other persons post below), then unzip that, put the system and recovery image in the same directory that your fastboot and adb is in, then run these commands from the cmd prompt
fastboot flash system system.img
fastboot flash recovery recovery.img
then your done, you can type
fastboot reboot
Click to expand...
Click to collapse
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Yep, just got to that part lol. Having some trouble downloading the VZW file. My current download just stopped with a network error and the website that is hosting the files keeps saying service unavailable and to contact the website administrator. Weird. I'm blaming it on my college's ****ty wireless network.
Edit: Yup, for some reason the wifi at the school decided it need me to input my credentials to re-login for the 6th time today to verify who I am and allow me internet access.
Edit 2: The things I'd do to have a stable connection... Once again, the download failed halfway through because the damn connection at this college sucks. This is infuriating.
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
bd1212 said:
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
Click to expand...
Click to collapse
Uploading now, but it'll take a bit. Big file.
jonnythan said:
Uploading now, but it'll take a bit. Big file.
Click to expand...
Click to collapse
Thanks man. You don't even know how much I appreciate this.
Which one of the two is the camera update for vzw?
Where do you get stock recovery?
EDIT: Sorry, Nevermind. I probably extract it from the zip.
Sent from my XT1060 using xda app-developers app
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
FireMedic1234 said:
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
Click to expand...
Click to collapse
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
simms22 said:
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
Click to expand...
Click to collapse
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
FireMedic1234 said:
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
Click to expand...
Click to collapse
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
simms22 said:
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
Click to expand...
Click to collapse
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
FireMedic1234 said:
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
Click to expand...
Click to collapse
ok, boot into the bootloader, connwct via usb to your computer, the type fastboot devices. at that point, it should list your phone via a number. if it does, then its all connected right. then you can flash the factory image, but do not use the flash-all script, flash them all individually.
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
FireMedic1234 said:
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
Click to expand...
Click to collapse
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
I concur. I have used "the" toolkit to see what happens. Have had multiple failures using toolkit and always had to revert to fastboot to fix. Might as well use fastboot up front. Saves a lot of time and headaches.
simms22 said:
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
Click to expand...
Click to collapse
Gotcha thanks again!
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You can drag and drop or copy/paste the image into the command line.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
are you flashing with flash-all or are you flashing each image individually. dont use flash-all, flash them individually.
Share a screen print of the command prompt, with the command you executed, and the error message?
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
FireMedic1234 said:
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
Click to expand...
Click to collapse
Yes.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You don't need to put the system.img there. Please do read general > sticky roll-up thread > adb and fastboot...
...some time.
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
FireMedic1234 said:
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
Click to expand...
Click to collapse
Yes the flash-all.bat can't break up the image. Has something to do with how it sees the partition. Have heard that fastboot in SDK 23+ has fixed this problem. Have not confirmed as I do each individually anyway depending on what I want to do.
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Only way you're gonna possibly brick is flash wrong image to wrong partition. Not sure that even that can be corrected with fastboot as long as the one you bork isn't the bootloader.
Can you flash ROMs without root?
What twrp version is best for this device? Thanks
Tmobilefan906 said:
Can you flash ROMs without root?
Click to expand...
Click to collapse
Yes. You do have to have your bootloader unlocked though. Most custom ROMs come rooted once you flash them.
Tmobilefan906 said:
What twrp version is best for this device? Thanks
Click to expand...
Click to collapse
I'm using 2.8.7.0 and haven't had any issues.
coal686 said:
Yes. You do have to have your bootloader unlocked though. Most custom ROMs come rooted once you flash them.
I'm using 2.8.7.0 and haven't had any issues.
Click to expand...
Click to collapse
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Tmobilefan906 said:
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
Click to expand...
Click to collapse
And is facepalm still working for s off? I heard they stopped deving for it. Thanks again.
Tmobilefan906 said:
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
And is facepalm still working for s off? I heard they stopped deving for it. Thanks again.
Click to expand...
Click to collapse
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Sloth said:
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Click to expand...
Click to collapse
OK. Every time I tried that, it kept saying error. All drivers were installed..drivers for while in BL, normal mode and recovery were installed on my PC. Maybe I typed it wrong. After .zip, there is a space then /sdcard/...right?
coal686 said:
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
Click to expand...
Click to collapse
Yea, the phone has 2.6.4 twrp already on it. I bought it with no o.s
coal686 said:
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
Click to expand...
Click to collapse
I hear rumrunner and firewater still work...true?
Tmobilefan906 said:
Yea, the phone has 2.6.4 twrp already on it. I bought it with no o.s
Click to expand...
Click to collapse
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
Tmobilefan906 said:
I hear rumrunner and firewater still work...true?
Click to expand...
Click to collapse
@Sloth might have kept up with this better. AFAIK, those Rumrunner will still work if you are on an older firmware, but I'm not sure.
EDIT: Fixed due to Sloth's answer below.
coal686 said:
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
@Sloth might have kept up with this better. AFAIK, those will still work if you are on an older firmware, but I'm not sure.
Click to expand...
Click to collapse
Update what? My twrp? I was thinking flashing 3.8.7 like u suggested. Its been a while since I tinkered with htcs. I've hacked quite a few in my days. Thanks again!!
coal686 said:
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
@Sloth might have kept up with this better. AFAIK, those will still work if you are on an older firmware, but I'm not sure.
Click to expand...
Click to collapse
RumRunner might work if it is still on one of the earlier updates, Firewater has been discontinued, if RR does not work you will have to use SunShine to s-off.
Tmobilefan906 said:
Update what? My twrp? I was thinking flashing 3.8.7 like u suggested. Its been a while since I tinkered with htcs. I've hacked quite a few in my days. Thanks again!!
Click to expand...
Click to collapse
Yeah, TWRP. 2.6.x is pretty old. Since you've hacked a few HTC devices in the past, this device isn't much different except without an SD card, you can't use a specially named zip (like PGxxxx.zip) to flash firmware. It must be done with fastboot.
coal686 said:
Yeah, TWRP. 2.6.x is pretty old. Since you've hacked a few HTC devices in the past, this device isn't much different except without an SD card, you can't use a specially named zip (like PGxxxx.zip) to flash firmware. It must be done with fastboot.
Click to expand...
Click to collapse
Why is recovery m7lw and roms zips are m7spr?
Sloth said:
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Click to expand...
Click to collapse
It says no such directory
Tmobilefan906 said:
It says no such directory
Click to expand...
Click to collapse
I had to put .zip in the cmd prompt. Thanks.
Tmobilefan906 said:
It says no such directory
Click to expand...
Click to collapse
Ugh. Stuck at 5%
Every time I flash recovery, it won't stick. I've tried button combos, multiple flashing recoveries. I need help
I think my bootloader is locked. Ugh
On my bootloader it says m7wls. Where can I find ROMs for that? I need to adb push it..I tried the RR ROM named m7spr, and it won't work. Please help!! Lol
Tmobilefan906 said:
Why is recovery m7lw and roms zips are m7spr?
Click to expand...
Click to collapse
Does ".zip" have to be in ROM name to flash? This is my first sprint HTC. Ugh.