Related
We've tested and can confirm this bootstrap recovery is working. Thank you to bane449 for testing. The recovery is a straight APK pull from the Droid X2. Worked thanks to the similarities between devices.
Instructions and download:
http://briefmobile.com/motorola-photon-4g-root-custom-recovery-now-available
Looks successful to me: DroidX2 Recovery GFAN.COM V2.5.1.8
And it booted back into Android properly, even
So what will this allow me to do? What are its advantages? What are the risks?
sub2k1 said:
So what will this allow me to do? What are its advantages? What are the risks?
Click to expand...
Click to collapse
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Forgive my ignorance but what is a "pseudo-Rom"?
kennethpenn said:
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
10 chars
I know what ROM's are, never heard anyone say psuedo-ROM.
Lokifish Marz said:
Custom ROMs (if available for the Photon) like MIUI, CM7 etc...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
I know what ROM's are, never heard anyone say psuedo-ROM.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Psuedo meaning "not really" a ROM. A locked bootloader will prevent true custom ROMs, but P-ROMs will be possible.
P-ROMs are based off of stock files and modifications. They don't replace the kernel or modem.
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
b-reezy said:
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
Click to expand...
Click to collapse
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
kennethpenn said:
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
Click to expand...
Click to collapse
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
brianez21 said:
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
Click to expand...
Click to collapse
Caveats:
This is not a *real* recovery. The way this recovery works is by hijacking portions of your boot process during system initialization and starting into recovery instead. So, if you hose your system *COMPLETELY* you will need to SBF. Specifically, if your logwrapper, logwrapper.bin, or hijack binary are missing from /system/bin, you will be screwed.
This is from koush himself concerning droid x/2 bootstrap. I would seriously wait til an sbf surfaces before flashing any of these "psuedo-ROMS" or even just deleting any system apk's. Just my opinion.
sub2k1 said:
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
Does the phone need to be rooted first in order to installl this recovery apk?
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
mediawiz said:
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
Click to expand...
Click to collapse
This is CWM bootstrap. Original one was on the Droid X, created by Koushik Dutta. Then it was ported to the Defy. Then to the Atrix. Next, the Droid X2. Now, the Photon 4G.
V2.5.1.8
Sbf is gonna be your friend when it comes to unrooting and restoring. It will pop up soon.
sub2k1 said:
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
beartrap said:
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
Click to expand...
Click to collapse
You can unplug.
Sent from the best phone yet!
I am S-ON, unlocked, and rooted. I made a backup in TWRP, and flashed the latest lenoob's CM9, then flashed gapps. Upon reboot, it hangs at the white HTC screen. So i read a little and see that i need to extract the boot.img from lenoob's image, and zip it on its own as PH98IMG.zip and place it on the root of the sd card. Great, so i did that, booted into HBOOT, it saw the PH98IMG.zip, said parsing, then never gave me an option to push UP to flash or reboot. Just puts me at the HBOOT menu.
Am i missing a step here?
Aha- i bet its because I'm still unlocked. fffffff i'm at work and can't relock :-/
I could be wrong because I'm still new, but being unlocked shouldn't have anything to do with it, I think you need to be unlocked to flash Roms. I don't have experience with TWRP but if your s-on you could also use fast boot to flash the boot.Img after flashing the rom itself
Sent from my Adrenalized Rezound
Extract the boot.img place it where you have adb on you computer then flash Rom gapps boot back to bootloader and use command fastboot flash boot boot.img, you have to be unlocked to flash roms if s-on.
Sent from my ADR6425LVW using xda app-developers app
Dogbone737 said:
I could be wrong because I'm still new, but being unlocked shouldn't have anything to do with it, I think you need to be unlocked to flash Roms. I don't have experience with TWRP but if your s-on you could also use fast boot to flash the boot.Img after flashing the rom itself
Sent from my Adrenalized Rezound
Click to expand...
Click to collapse
I could have sworn i read somewhere that i can flash stuff in TWRP, but not the boot image. Thought the boot image had to be flashed in HBOOT and for HBOOT to actually flash the image, the phone needs to be locked or relocked. I'm new too so i could have lots of bad information :fingers-crossed:
Also don't forget to wipe first.
Sent from my ADR6425LVW using xda app-developers app
molson8045 said:
Extract the boot.img place it where you have adb on you computer then flash Rom gapps boot back to bootloader and use command fastboot flash boot boot.img, you have to be unlocked to flash roms if s-on.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Gotcha. I will give this a go when i get home tonight. Thanks!
Aaaaaand success. LOVING CM9. This is what i want out of a phone. And google now is pretty slick too.
sshaar said:
Aaaaaand success. LOVING CM9. This is what i want out of a phone. And google now is pretty slick too.
Click to expand...
Click to collapse
And we just released a new build.
GrayTheWolf said:
And we just released a new build.
Click to expand...
Click to collapse
And so far, this build is impeccable, the only things I'm seeing problems with is some atypical choppiness.. which is to be expected. However, it's the battery life that I'm interested in, today will be the test for me. Lets see how it does.
xFonzie said:
And so far, this build is impeccable, the only things I'm seeing problems with is some atypical choppiness.. which is to be expected. However, it's the battery life that I'm interested in, today will be the test for me. Lets see how it does.
Click to expand...
Click to collapse
Read through the OP of the cm9 thread and you will see it says "enable GPU rendering in developer options to remove keyboard lag". This should help with overall lag.
you tizante
GrayTheWolf said:
Read through the OP of the cm9 thread and you will see it says "enable GPU rendering in developer options to remove keyboard lag". This should help with overall lag.
Click to expand...
Click to collapse
Oh, it's not keyboard lag, it's just some choppiness in some spots, not too big a deal. I am well aware of the enable GPU rendering deal.. all together, pretty darn good so far, I'm quite happy with the CM9 builds as it is.
GrayTheWolf said:
And we just released a new build.
Click to expand...
Click to collapse
GAH! After I got it all set up last night haha
So far I love everything on the 9/10 build, but i remember something closing or locking up. Obviously not a big deal since i can't even remember what it was now haha.
Wow... were at about 4 hours now.. and my battery is at 91% .. so far color me impressed..
Sent from my ADR6425LVW using xda app-developers app
I used my phone for about 2 hours this morning with some web browsing and playing around with google now, and text messaging, and i was down to 79%. So thats good enough for me on a stock battery.
sshaar said:
I am S-ON, unlocked, and rooted. I made a backup in TWRP, and flashed the latest lenoob's CM9, then flashed gapps. Upon reboot, it hangs at the white HTC screen. So i read a little and see that i need to extract the boot.img from lenoob's image, and zip it on its own as PH98IMG.zip and place it on the root of the sd card. Great, so i did that, booted into HBOOT, it saw the PH98IMG.zip, said parsing, then never gave me an option to push UP to flash or reboot. Just puts me at the HBOOT menu.
Am i missing a step here?
Click to expand...
Click to collapse
I have a question. phone is S-ON, unlocked, and rooted. I have never flashed a rom before. I am extreme newb at that.
I can understand the flashing of the PH98IMG.zip.
If you could help me understand what gapps is? Is this just some google apps? And if so when you say you flashed gapps, do you flash it in the same way you would the boot image?
Thanks in advance for help.
Gapps are simply Google apps.. play store... Gmail.. YouTube.. and so forth.
Sent from my ADR6425LVW using xda app-developers app
xFonzie said:
Gapps are simply Google apps.. play store... Gmail.. YouTube.. and so forth.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Do you flash them like you would the boot.img?
As in fastboot flash gapps?
Also do I need to worry about the kernel?
Sax1031 said:
Do you flash them like you would the boot.img?
As in fastboot flash gapps?
Also do I need to worry about the kernel?
Click to expand...
Click to collapse
Nope flash them as you would the rom
Sent from my ADR6425LVW using xda premium
Self explanatory.. this is daily use for me..
Sent from my ADR6425LVW using xda app-developers app
i just wonder....if there are semi unlock
coz i found that my phone has been locked back by flashing sbf and didnt brick
i brought my atrix back in 2012. and the time i was buy this phone the android version are 2.3.4 stock
so after get bored with stock rom,i decided to unlock my phone. and get the job done so my phone has been unlock
after month of experiment with the custom rom. i decided to return stock, i been google that since coz they said that you will brick if you flash sbf on unlocked phone until i find this thread http://forum.xda-developers.com/showthread.php?t=1014964
so i try to download full sbf and flash it and got it boot up without any damage. one i just notice that when my phone start there are no unlocked write on the top of red logo anymore
odystyle said:
i just wonder....if there are semi unlock
coz i found that my phone has been locked back by flashing sbf and didnt brick
i brought my atrix back in 2012. and the time i was buy this phone the android version are 2.3.4 stock
so after get bored with stock rom,i decided to unlock my phone. and get the job done so my phone has been unlock
after month of experiment with the custom rom. i decided to return stock, i been google that since coz they said that you will brick if you flash sbf on unlocked phone until i find this thread http://forum.xda-developers.com/showthread.php?t=1014964
so i try to download full sbf and flash it and got it boot up without any damage. one i just notice that when my phone start there are no unlocked write on the top of red logo anymore
Click to expand...
Click to collapse
Find a pudding sbf file, flash it via rsd, go through the steps to unlock, and you'll be good to go
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Find a pudding sbf file, flash it via rsd, go through the steps to unlock, and you'll be good to go
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
what i mean after i flash my phone with full sbf, my phone been locked back
i just wonder if somebody experience the same like i did....
coz people say it will brick your phone if you flash a full sbf
odystyle said:
what i mean after i flash my phone with full sbf, my phone been locked back
i just wonder if somebody experience the same like i did....
coz people say it will brick your phone if you flash a full sbf
Click to expand...
Click to collapse
I understood what you meant. Its not necessarily true that you will brick your device. If you have a device on 2.3.6, don't go flashing a 2.3.4 sbf. The pudding files are not full sbfs, and are designed to unlock the device, just follow the directions on the threads and you'll be fine. Myself, i've locked and unlocked mine several times since Oct 2012 when the ICS leak hit the internet. I've even done it on a replacement hardware (i had a lagging cpu and a cracked screen, thats why it was a replacement).
Sent from my MB860 using xda app-developers app
palmbeach05 said:
I understood what you meant. Its not necessarily true that you will brick your device. If you have a device on 2.3.6, don't go flashing a 2.3.4 sbf. The pudding files are not full sbfs, and are designed to unlock the device, just follow the directions on the threads and you'll be fine. Myself, i've locked and unlocked mine several times since Oct 2012 when the ICS leak hit the internet. I've even done it on a replacement hardware (i had a lagging cpu and a cracked screen, thats why it was a replacement).
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
so the fuse that keep our bootloader locked not really been blown away right
its just open the gate for us
By the way are u already try the new kernel 3.1
odystyle said:
so the fuse that keep our bootloader locked not really been blown away right
its just open the gate for us
By the way are u already try the new kernel 3.1
Click to expand...
Click to collapse
It is blown. To quote a dev who's name i forget at the moment, this is the best way to describe what happens. When you flash a full sbf, you cause the device to "forget" that the fuse is blown. When you re-flash the pudding sbf, you make the device remember that it is unlocked.
I've been trying it out here and there, but just because i've been dealing with errands and some personal drama, i haven't been able to fully sit down and take the new kernel for a spin. From what little i've seen so far, it does seem to be much better than the old kernel
Sent from my MB860 using xda app-developers app
palmbeach05 said:
It is blown. To quote a dev who's name i forget at the moment, this is the best way to describe what happens. When you flash a full sbf, you cause the device to "forget" that the fuse is blown. When you re-flash the pudding sbf, you make the device remember that it is unlocked.
I've been trying it out here and there, but just because i've been dealing with errands and some personal drama, i haven't been able to fully sit down and take the new kernel for a spin. From what little i've seen so far, it does seem to be much better than the old kernel
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
ok now that i fully understand with fuse thing thnks to you explanation about it...
yeah..... you were right about the new kernel , i have been try countless time to make my phone boot up with the new kernel, but it wont boot up
mybe my phone like to stay stable bulid lol
odystyle said:
coz people say it will brick your phone if you flash a full sbf
Click to expand...
Click to collapse
No they don't. Nobody said that. You will only brick the phone if you flash a wrong SBF. What you have (apparent relocking) is perfectly normal and expected and discussed before.
odystyle said:
ok now that i fully understand with fuse thing thnks to you explanation about it...
yeah..... you were right about the new kernel , i have been try countless time to make my phone boot up with the new kernel, but it wont boot up
mybe my phone like to stay stable bulid lol
Click to expand...
Click to collapse
Odd, might be a device issue.
Install steps should be like this
-Make nandroid backup of current rom
-Wipe system, data, cache, osh (webtop), and dalvik
-install rom
-install recommended gapps
-reboot and enjoy
Typically that is the norm, but there are some roms that change up the install instructions. I know that the beanstalk rom instructions are like that.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Odd, might be a device issue.
Install steps should be like this
-Make nandroid backup of current rom
-Wipe system, data, cache, osh (webtop), and dalvik
-install rom
-install recommended gapps
-reboot and enjoy
Typically that is the norm, but there are some roms that change up the install instructions. I know that the beanstalk rom instructions are like that.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
but i didn't have problem when boot up MROM ICS with leaked kernel
i always do a full wipe before flashing rom
odystyle said:
but i didn't have problem when boot up MROM ICS with leaked kernel
i always do a full wipe before flashing rom
Click to expand...
Click to collapse
Ok, well thats good. Which rom are you trying to use right now? Are you trying to use it with the old kernel or the new kernel?
Sent from my MB860 using xda app-developers app
right now i try to use the new rom with the new kernel.... made by krystianp
i have been try countless time to make it boot up but nothing work
Sent from my MB860 using xda app-developers app
odystyle said:
right now i try to use the new rom with the new kernel.... made by krystianp
i have been try countless time to make it boot up but nothing work
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Ok. I was able to get that to work for me. I wiped it down, flashed the rom, then rebooted and flashed gapps. Odd that its not working for you.
Sent from my MB860 using xda app-developers app
yeah....well its only me stay on GB forever
Sent from my MB860 using xda app-developers app
odystyle said:
yeah....well its only me stay on GB forever
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Did you try installing some other non GB rom but with old kernel?
Edit: I just read that you tried MROM ICS. Do you have sdcard inserted?
Edit2: Get this info from your phone:
- memory type:
- panel_size:
- sdcard present:
- atag revision:
- tegrapart:
- radio:
delete
krystianp said:
Did you try installing some other non GB rom but with old kernel?
Edit: I just read that you tried MROM ICS. Do you have sdcard inserted?
Edit2: Get this info from your phone:
- memory type:
- panel_size:
- sdcard present:
- atag revision:
- tegrapart:
- radio:
Click to expand...
Click to collapse
1.after i unlock my phone i only use MROM 7 AND MROM ICS with leaked kernel
2.when i try to get the new cm9 with 3.1 kernel. i put the rom,gapps and facelock on internel memory i didnt use memory card coz before flashing i always read instruction before flashing just to be clear what im doing.
3.phone info
memory type HYNIX
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR5: 0x0006 (0x0606)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR6: 0x0000 (0x0000)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR7: 0x0000 (0x0000)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR8: 0x0054 (0x5454)
Panel size
[ 0.000000] parse_tag_motorola: panel_size: 80000740
Sdcard present
16GB class 10
Atag revision
<4>[ 0.000000] mot_fixup: atag_revision=83f0
Tegrapart
tegrapart=mbr:d00:100:800,kpanic:2100:400:800
Title says it all.
Sent from my LWW. Cheers, Its Legend, wait for it, DARY!
alvster said:
Title says it all.
Sent from my LWW. Cheers, Its Legend, wait for it, DARY!
Click to expand...
Click to collapse
No!
Never!
It'll always be the same way through fastboot!
alvster said:
Title says it all.
Sent from my LWW. Cheers, Its Legend, wait for it, DARY!
Click to expand...
Click to collapse
Yes u can.but only in ur dream.not in the real life.
Sent from my WT19i using xda app-developers app
Probably, if someone could figure out the exact partition for kernel. The guys at p, u, sola and go have done that and they got similar situation as we do, no dedicated partition for recovery. But they managed to find their boot partition name and write cwm script to do raw kernel image write to the partition.
You cannot overwrite something you are using...so if you custom kernel, which includes CWM and then try to install another kernel....it will not work.
Someguyfromhell said:
You cannot overwrite something you are using...so if you custom kernel, which includes CWM and then try to install another kernel....it will not work.
Click to expand...
Click to collapse
Actually not coz the cwm gets loaded into the ram memory so we should be able to flash kernels but only if we know the correct partition block. Anonymous said it perfectly.
Sent from my LT26i using xda app-developers app
abcdjdj said:
Actually not coz the cwm gets loaded into the ram memory so we should be able to flash kernels but only if we know the correct partition block. Anonymous said it perfectly.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
The system is (at least should be) the same as on Windows. If you have a file open, you cannot replace it. Does not matter, that it is in use in RAM, you still can not replace it.
Someguyfromhell said:
The system is (at least should be) the same as on Windows. If you have a file open, you cannot replace it. Does not matter, that it is in use in RAM, you still can not replace it.
Click to expand...
Click to collapse
Well I installed cwm for locked boot loader on my /system partition and then booted into it. Then I formatted /system for flashing another ROM. The cwm was working even though I had formatted /system. After flashing the new ROM and rebooting, I tried entering cwm but could not as my new ROM did not have cwm inbuilt. So I guess it is possible.
Sent from my LT26i using xda app-developers app
abcdjdj said:
Well I installed cwm for locked boot loader on my /system partition and then booted into it. Then I formatted /system for flashing another ROM. The cwm was working even though I had formatted /system. After flashing the new ROM and rebooting, I tried entering cwm but could not as my new ROM did not have cwm inbuilt. So I guess it is possible.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
There does come an issue, where formatting /system causes problem when you try to start installing ROM. ROMs usually end up in bootloops or errors.
I recall a ROM, which required a custom kernel only because of that. If CWM was installed in /system partition, ROM installation would have messed up the whole system, ending up in a bootloop.
Now, to avoid going off-topic, the topic has been answered. Until a developer comes up with a solution, there is no such possibiltiy.
I have followed all instructions for flashing carefully. I have tried going back to TWRP 2.7.0.0b I have tried putting ROM zip on internal and external storage. I have rebooted recovery after wiping also tried without wiping. Tried to flash: Beanstalk, Paranoid, Carbon, PAC. All for new partition layout. I am S-off with firewater hboot 2.10.5555. The only ROM that has flashed successfully is Omni. I keep getting this error:
See picture.
Any help or info would be much appreciated.
Sent from my Nexus 5 using XDA Premium 4 mobile app
After wiping did you reboot to recovery before trying to flash again?
HTC Jewel
HBOOT 2.10 S-OFF (rumrunner)
Android 4.3 Sense 5.5 V3
Yes.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
naveen6252 said:
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
Click to expand...
Click to collapse
Thanks but I am sure I'm flashing the right ROM for my device. This just started happening recently. I just flashed the newest Omni just posted and that flashes too. Superuser flashes as well as gapps. I thought this might have been related to updating my TWRP to 2.7.0.4b which is why I flashed back to 2.7.0.0b and I got the same errors. Backups restore with out issue as well.
Sent from my EVO using XDA Premium 4 mobile app
Could this possibly be an issue with the firewater hboot?
EVOlved human
Evolution_Freak said:
Could this possibly be an issue with the firewater hboot?
EVOlved human
Click to expand...
Click to collapse
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
FinZ28 said:
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Fin! I will check on the signature checking. I did try going back to 2.7.0.0b but didn't try any older versions. As I said, this just started happening and is only with some ROMs.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Just checked and signature checking was disabled already. I will try your other recommendations next.
EVOlved human
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
aarsyl said:
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
Click to expand...
Click to collapse
New downloads.
EVOlved human
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
aarsyl said:
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
Click to expand...
Click to collapse
Yes, I'm sure. I just reverted back to TWRP 2.6.3.1b and I'm downloading Paranoid at the moment. Will update if it flashes.
Sent from my EVO using XDA Premium 4 mobile app
I'll be waiting for your response.
aarsyl said:
I'll be waiting for your response.
Click to expand...
Click to collapse
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Evolution_Freak said:
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Update:
I re-ran the RUU to bring my HBOOT back to 2.10.0000. I remained unlocked and S-off as is well known. I installed twrp 2.7.0.0b via bootloader and I'm now about to try flashing again. Will update again after trying.
Sent from my EVO using XDA Premium 4 mobile app
aarsyl said:
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Click to expand...
Click to collapse
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
FinZ28 said:
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
Click to expand...
Click to collapse
That's what I figured, but I'm at work, so my assistance is limited.
aarsyl said:
That's what I figured, but I'm at work, so my assistance is limited.
Click to expand...
Click to collapse
No worries. The biggest thing is to make sure you don't flash the wrong ROM on the wrong device when you edit out those parts of the updater script. Could spell trouble
Sent from my EVO LTE