Related
Hi all, my phone stats at present:
HTC Desire - originally on O2.
Rooted and S-off'd
Running Oxygen 2.1.6
I'm trying to flash this partition table:
Bravo Oxygen r2.
I have renamed PB99IMG_oxygenr2.zip to pb99img.zip and put it on the root of my SD.
When I boot into fastboot I get:
CID Incorrect
Update Fail
Do you want to reboot device?
Click to expand...
Click to collapse
Now I'm not adverse to a bit of dev work - I have the and. SDK up and running.
Code:
fastboot getvar all
shows:
(bootloader) cidnum: O2___001
I gather this is the problem.
How do I change the CID? Is there a quick and easy command line or shell fix?
Cheers
Flashing hboot via pb99img.zip does not work very often. Better do it with fastboot:
Code:
fastboot flash hboot C:\bravo_alphaspl-oxygenr2.img
fastboot reboot-bootloader
fastboot erase cache
Comment is for the case, your hboot.img is stored on partition C and you used the oxygen r2 hboot from http://alpharev.nl
MAKE SURE YOU CHECK MD5SUM BEFORE FLASHING HBOOT!!!
To avoid cid error, you need to create goldcard and put it in your desire:
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
Exactly, if you are comfy with the fastboot/adb there is no reason to use PB99IMG.
MatDrOiD - Danke!
I'm looking for a way to remove Revolutionary S-OFF...
I tried flashing several RUUs with different HBOOT versions but Revolutionary HBOOT is very persistant
I'd would love to return to HBOOT 0.93 since I have to return my device due to a possible hardware error.
anyone have a suggestion? tnx
Only to use RUU
name.vic said:
Only to use RUU
Click to expand...
Click to collapse
not sure what you mean exactly, but just flashing a stock RUU with NOT remove revolutionary HBOOT. I'll explain in next post.
SOLVED: just got THE answer from someone at #revolutionary
1. what: downgrade HBOOT using AlphaRev
how: go to http://alpharev.nl/, download (and always MD5-) check "bravo_downgrade.img", flash using fastboot
2. what: flash stock RUU
how:go to http://shipped-roms.com/index.php?category=android&model=Bravo and download RUU for your device and run the executable
(I chose "RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe " since it turned out to contain HBOOT 0.93 which I wanted)
3. done
Thank you thank you thank you thank you thank you !
Puff, i got a good scare after upgrading to GB.
I found out that after upgrading I cannot simply RRU my way back, installed revolutionary then I wanted to bring my Desire to service [reboots] and wanted to get rid of s-off and revolutionary hboot to make it "stock".
Once again, thanks to this great community !
hi.
Hope someone still watching these posts.
I tried your solution.
Flashed the hboot and it switched from Revolutionary to alpharev.
Then i flashed the phone with stock ruu RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
But still no luck.
The methods iv tried is:
All through command in windows, :
adb devices
adb reboot bootloader
fastboot devices
fastboot flash hboot bravo.img <-- i renamed the file i took from the ruu im using.
flash hboot - reboot to android os - stock ruu flash = no stock hboot
flash hboot 4 times - reboot to android os - stock ruu flash = no stock hboot
flashed hboot - still in hboot i ran stock ruu = no stock hboot.
am i missing any step?
My phone/hboot is:
Swedish unlocked HTC Desire.
Bravo pvt4 ship s-off
hboot 6.93.1002
radio 5.11.05.27
Why are you using adb? You must be on the fastboot screen not hboot screen
Sent from my HTC Desire using XDA App
rootSU said:
Why are you using adb? You must be on the fastboot screen not hboot screen
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hi and ty for your reply.
I think i have tried it in fastboot to.
Or on my phone it says fastboot usb marked in red collor.
Is that right or wrong?
could you give me a step by step?
I have the revolutionary drivers and uninstalled htc sync alredy.
The things iv tried so far is this list of commands in order:
cd c:\desire <--- where i have the files
adb devices
adb reboot bootloader
fastboot devices
fastboot flash hboot bravo.img
rootSU said:
Why are you using adb? You must be on the fastboot screen not hboot screen
Click to expand...
Click to collapse
how do you flash files in fastboot,if not with adb to my knowledge he was in the fastboot screen(when you adb reboot bootloader thats where it takes you)
we need more detail in step #2. after getting an "ok" flashing the downgrader image in step one,do you reboot to the OS,then run the executable from there? or do you run it while still in fastboot?
ive been helping him on another forum,and from what he describes,it looks like hes followed DXsl's steps,but it still hasnt worked.
thanks for any info
After flashing the downgrader, you cannot boot any rom, because the downgrader deletes all internal partitions. So after flashing the hboot downgrader successfully, just enter this
Code:
fastboot reboot-bootloader
When done, flash ruu. At the end you are on stock rom with stock hboot (s-on).
A little note at the end: If your phone is in fastmode mode, you cannot use adb (commands). If your phone is in hboot mode, you cannot use fastboot (commands). And fastboot can only be used if one is s-off. I know you are in this state, but this information is for the future.
MatDrOiD said:
After flashing the downgrader, you cannot boot any rom, because the downgrader deletes all internal partitions. So after flashing the hboot downgrader successfully, just enter this
Code:
fastboot reboot-bootloader
When done, flash ruu. At the end you are on stock rom with stock hboot (s-on).
A little note at the end: If your phone is in fastmode mode, you cannot use adb (commands). If your phone is in hboot mode, you cannot use fastboot (commands). And fastboot can only be used if one is s-off. I know you are in this state, but this information is for the future.
Click to expand...
Click to collapse
i see what you are getting at now. while you are in fastboot mode,you technically are using fastboot commands,not adb commands. kind of splitting hairs,but correct. when folks are in the CMD window and entering commands to the phone they broadly describe the experience as "using ADB".
while an engineering or patched hboot provides alot more functionality,there are limited commands for s-on in fastboot mode.
thanks for the info
This isn't working. RUU managed to flash HBOOT, Radio, Signature, but after that it gives error 140 and ends.
---------- Post added at 01:50 PM ---------- Previous post was at 01:29 PM ----------
So I tried to install it manually and the only component that failed to flash was system. Here is log:
Code:
********************************
###Calling fastboot with: flash system D:\Programy\Android\system\PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed\system.img###
sending 'system' (254219 KB)... FAILED (remote: data length is too large)
finished. total time: 0.004s
********************************
Is that with the downgrader flashed?
Sent from my HTC Desire using XDA App
Yes.
10char
How much total space do you have on system? (try a df -f on a terminal emulator)
Dunno, but I wiped entire phone and GB RUU runs fine.
Terepin said:
Dunno, but I wiped entire phone and GB RUU runs fine.
Click to expand...
Click to collapse
I think your partition size is somehow smaller than it should be. Did you flash the stock HBOOT after flashing downgrade HBOOT?
PS: also use command "fastboot erase cache" after flashing HBOOT and "fastboot reboot bootloader" too. Just to be sure
theGanymedes said:
I Did you flash the stock HBOOT after flashing downgrade HBOOT?
Click to expand...
Click to collapse
Nooo..If after the downgrader u flash the stock one, u are locked s-off again (downgrade protection)
the downgrader is already stock, and because this one has no protection, the ruu overwrite it before to flash the system partition
andQlimax said:
Nooo..If after the downgrader u flash the stock one, u are locked s-off again (downgrade protection)
the downgrader is already stock, and because this one has no protection, the ruu overwrite it before to flash the system partition
Click to expand...
Click to collapse
With custom MTD, we had to format system, cache and data so maybe it would be best practice to do that after flashing the downgrader if you still have recovery (i.e havent tried to run an RUU over CM7 hboot)
yes, u can't flash an ruu over the cm7 hboot, but u can over the downgrader
this damn downgrader is the stock hboot (with stock partitions size)with no protection..all the other hboots on alpharev have the downgrade protection (so an ruu can't overwrite it)
so for example, if u have the cm7 hboot, u dont need to flash the stock hboot and then the downgrader hboot (or viceversa)..only the downgrader is enough..the downgrader is an hboot with stock partition size
in addition, the first thing that the ruu does is to flash the hboot with stock size (only after the ruu flash the system)..but of course, it will successfully write the hboot only if u have the downgrader one
Hi guys,
A good friend of mine recently requested me to help with rooting her Wildfire S A510e (purchased from SingTel, CID HTC__044). I managed to change her Wildfire S from S-ON to S-OFF via HTCdev. As far as I know, HTCdev isn't supposed to give you S-OFF but only to remove the NAND write locks on certain partitions.
Users: This is NOT for you. This is NOT a tutorial.I will not be responsible for any bricked WFS.
Here's what happened, pretty long so I'm gonna break it down into multiple sections. Important points in red.
Replacing SingTel ROM with HTC EU ROM
The phone was originally running Android 2.3.3, ROM version 1.35.707.1, HBOOT 0.90.0000. This ROM version is not supported by HTCdev unlock yet.
Reboot to HBOOT on WFS. Choose FASTBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU for "hTC Asia India" from HTCdev. Attempted to install the RUU but got a CID error.
Disconnected WFS from computer.
Rebooted normally on WFS.
Connect WFS to computer via USB (Disk Drive).
Created a goldcard by using SimpleGoldCard while WFS is mounted as Disk Drive. (this wipes your SD card)
Disconnect WFS from computer and reboot.
Connect WFS to computer via USB (Disk Drive).
Downloaded RUU_Marvel_S_HTC_Europe_2.13.401.2
Ran the RUU. Went into %temp%, found the relevant directory and copied rom.zip to the goldcard as PG76IMG.zip.
Disconnect WFS from computer.
Turn off WFS and rebooted into HBOOT.
Went into HBOOT -> Fastboot. RUU_Marvel_S_HTC_Europe_2.13.401.2 was installed successfully (Android 2.3.5, ROM version 2.13.401.2, HBOOT 0.90.0000).
Installing HTCdev Unlock
Rebooted WFS into HBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU from HTCdev for "HTC EU".
Ran the HBOOT RUU. RUU installation gets stuck at 50% ("Flushing radio...") for about 20 minutes.
Decided that the RUU has hung so disconnected WFS from USB and did a battery pull
RUU offered to do a recovery but I clicked "Exit".
Turn on WFS in HBOOT mode.
S-OFF obtained!
I was pretty much at "dafuq?" at this stage. I didn't even need to upload the device identifier to HTCdev to get an unlock key. The device was already S-OFF (HBOOT shows it)!
HBOOT remained at 0.90.0000.
I verified the S-OFF by flashing ClockWorkMod which went without issues.
Possible theory of operation: (just my thoughts)
The HTCdev HBOOT RUU provides a temporary S-OFF in order to unlock the NAND
When the RUU is done, it is supposed to restore S-ON to the device.
However, since the process was hung, the RUU had no chance of restoring the device to S-ON.
Hence the WFS was left at S-OFF.
If there are any adventurous devs around who are willing to try to dissect the RUU, please do so, but standard disclaimer applies. Attempting to interrupt the HBOOT RUU flashing is pretty dangerous and WILL possibly brick your device! I will not be held responsible if you brick your WFS!
This seems to be a case of pure luck.
Addendum:
The HBOOT RUU contains 2 ZIP files: rom_01.zip, rom_02.zip
They are presumably flashed in-order.
rom_01.zip contains Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img
rom_02.zip contains hboot_1.08.0099_6e20b6fac09.nb0 and radio_47.23a.35.3035H_7.53.39.03M_MR.img
My friend has radio version 47.23b.35.3035_7.54.39.08M. From here, we can tell that rom_01.zip was successfully flashed but rom_02.zip wasn't. Also notice the "special" file name of the first radio image.
Addendum 2:
It appears that both radio ROMs have the same size but different md5sum. Can someone with S-ON try to flash Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img? (Again, standard disclaimer applies)
i like the very last sentence that you used ...
good job anyway mate !
how do you go about flashing a radio??
---------- Post added at 04:12 AM ---------- Previous post was at 04:09 AM ----------
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
stevie67 said:
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
Click to expand...
Click to collapse
If you look into the ZIP files, Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img and radio_47.23a.35.3035H_7.53.39.03M_MR.img are both the same size.
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
ok i tried to flash this radio i put the .img file on my sdcard went to fastboot then recovery,install from sdcard and there was nothing there so i put the rom1.zip folder on my sdcard went to fastboot,install from sdcard,rom1.zip and got this
CWM-based Recovery v5.0.2.6
-- Installing: /sdcard/rom_01.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom_01.zip
(bad)
Installation aborted
did i do something wrong??
You must flash the radio with fastboot command. But this wont work, bc the hboot will check if the file is signed. And that isn't.
But try, maybe i'm not right.
Sent from my HTC Wildfire S A510e using XDA App
and the fastboot command is??
and the file says its signed
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
Click to expand...
Click to collapse
He said it
Sent from my HTC Wildfire S A510e using XDA App
My phone wouldn't update using the HTC method so I extracted the two ROMs from the RUU and flashed them seperately. After the first one (radio) I noticed that the phone was S-OFF but when I'd flashed the second it was S-ON again and I couldn't go back.
WOW, you have S-OFF after flashing radio via
fastboot flash radio radio.img
???
And now you can't go back?
I extracted the htcdev ruu and tried to flash the radio image. but it is not possible, signature check fails. so if the bootloader is already unlocked, it is not possible to obtain s-off this way
Have u test it with
fastboot oem lock
first and then to flash the radio.img?
Or to try to downfrade hnoot with the tutorial here in forum and then flash the new radio.
not yet. Will try that and report again
did relock phone using oem lock.
*** RELOCKED ***
Tried flashing 1st radio from htcdev ruu
flashing successful, but still S-ON
Hmm, and can u try to downgrade to Hboot 0.9 or Hboot 1.08?
I'm a noob so it's possible I made a mistake but I'm pretty sure I was S-OFF after the first flash. I was on Hboot 0.09.0000. Unfortunately I didn't realise the significance at the time so proceeded anyway.
I will try
I will try too, but earliest tomorrow, then i have my windows pc
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
stevie67 said:
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
Click to expand...
Click to collapse
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
theq86 said:
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
Click to expand...
Click to collapse
so are you now s-off??
Hello,
I've encountered one stop point in my way to Jelly Bean. I'm playing with Desire HD, Android 2.3.5, HBOOT-2.00.0027. I've managed to get root by SuperOneClick, but I'm not able to flash the recovery. While I have root privs, I've downloaded "recovery-clockwork-touch-5.8.1.5-ace.img" and put it do sdcard as "recovery.img". Then I've tried to boot to hboot and through the fastboot run the following command:
fastboot flash recovery recovery.img
sending 'recovery' (3554 KB)...
OKAY [ 0.610s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.220s
As you can see without success. Second try was updating the recovery partition with shell root privs through adb shell:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
7108+0 records in
7108+0 records out
3639296 bytes transferred in 2.905 secs (1252769 bytes/sec)
I've got no error, but partition wasn't updated. It still contains the same data as I wouldn't run dd command at all. Is the partition in some kind of read only mode or ? I don't understand how it it possible. I thought that with the root I can do everything.
Is there any other way how I can move image data to recovery partition with the dd?
Are you S-Off or is your bootloader unlocked? If you don't know, paste the contents of hboot here.
The bootloader is locked with security on. Doesn't it matter actually? I thought that if you havethe root privileges, you can flash custom recovery with no problems. Apparently not.
I prefer not to use the htcdev unlocker. So what to do?
Root is software; it has nothing to do with flashing to hardware partitions. You flashed root somehow; did you unlock and then relock your bootloader? How did you root? At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
bananagranola said:
Root is software; it has nothing to do with flashing to hardware partitions. You flashed root somehow; did you unlock and then relock your bootloader? How did you root? At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
Click to expand...
Click to collapse
I know linux a little bit. Simply as I have written already I've got the root by running SuperOneClick application. Not sure what exploit it uses (perhaps ZergRush).
>did you unlock and then relock your bootloader?
No. As I said, I thought that I can simply move data to eMMC partition while I'm root by dd command. I dunno why I need to unlock and lock the bootloader again.
>How did you root?
Run the SuperOneClick application and clicked the "Shell root" button, then connect to phone through the adb connection, wrote "adb shell" and voila got "#".
>At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
Mmm, could tell me how the bootloader blocks the "dd" command from rewriting data on the eMMC partitions?
Can I download the S-Off tool somewhere, or unlock bootloader somehow else, why the root privileges are not enough here?
I'd like to know more about that.
I don't know anything about SuperOneClick. If it S-Offs your phone you should be fine just fastboot flashing a recovery. Can I see what your hboot says? If your phone in fastboot mode?
It helps that you know Linux. The closest Linux analogy is UEFI v. su rights. Root gives the ROM partition su rights in software. However, the bootloader won't let you flash other stuff to the partitions in hardware. They're separate issues.
EDIT: I just reread your OP. You need to have the recovery.img on your computer, not your phone. Then run fastboot from the folder where that recovery.img is saved.
SuperOneClick is here: http://forum.xda-developers.com/showthread.php?t=803682
Bootloader:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
etc...
Er, you are S-On and your bootloader is locked. Are you sure you have root?
SuperOneClick does nothing for HTC devices, AFAIK its simply designed for root and go Motorola and LG phones... same applies for Gingerbreak v1.20 or 1.5...i cant remember if its 1.2 or 1.5.... S-off is hard to obtain now that AAHK is retired, but there are advanced instructions on the developer of AAHK on his/her webpage
Sent from my Inspire 4G using xda premium
> Er, you are S-On and your bootloader is locked. Are you sure you have root?
Well, I have written already that I have security on and my bootloader is locked.
> SuperOneClick does nothing for HTC devices
why I got shell root with it then?
As I understand the issues:
Root - 'root' is linux super user that has all the privileges, if you are the root you are not limited by OS to do everything you want.
Bootloader lock - you can't flash custom ROMs in the fastboot mode, probably because of the fact that the custom ROM or the custom recovery are not signed
- what does it mean actually that the bootloader is unlocked? That it is rewrited by hacked version of bootloader where sign check is jumped? or I am wrong...
S-ON - hardware lock, probably you can't write to partitions ???
- probably that eMMC is set to be in read only mode by registry settings directly in eMMC chip? Am I right? And it is done in every boot when hw is initialized
As I said, I've got root privileges, so I am root in the Android and I can read from and write to everything in the Android. I've got it by some exploit (ZergRush / Gingerbreak). I'm not sure because it was set to "Auto" in the SuperOneclick app.
My situation:
Ok, I am able to obtain root privileges and I can rewrite eMMC partitions, but it has no effect probably because of S-ON (not sure here, nobody wants to tell me ).
I can't flash recovery through fastboot, probably because clockworkmod recovery is not signed by HTC.
As I understand, I can only follow the AAHK. It means downgrade to lower Android version where it is to possible get S-OFF and then it is possible to get root and rewrite eMMC.
I thought that obtaining the root is enough to rewrite the eMMC without S-OFF and/or unlocked bootloader, simply by rewriting block device in Linux.
AAHK is retired, but you can unlock your bootloader.
Ok.
I used AAHK to downgrade, S-OFF and root. Currently I'm running JellyTime 4.2...
hello
have flashed cynagonmod 10.2 endeavor to my htc one x -> all good , but after autoupdate to the suggested new version via download
my htc was in boot loop
-> so i flashed a recovery , i think the wrong one
now it shows:
relocked
hboot -1.72.0000
endeverou pvt ship s-on RL
radio 5.1204
can`t switch in recovery mode
which recovery should i flash via minimal adb and fastboot?
which command to unlock boot?
1000 thank`s for help
how can i get s-off to flash new recovery?
have downloaded recovery clockworktouch 5.8.4.0 endeavor for new flash
and
Ressurection Remixunoff20140622-endeavor for image
is this the wright one for me?
noobtotal said:
hello
have flashed cynagonmod 10.2 endeavor to my htc one x -> all good , but after autoupdate to the suggested new version via download
my htc was in boot loop
-> so i flashed a recovery , i think the wrong one
now it shows:
relocked
hboot -1.72.0000
endeverou pvt ship s-on RL
radio 5.1204
can`t switch in recovery mode
which recovery should i flash via minimal adb and fastboot?
which command to unlock boot?
1000 thank`s for help
how can i get s-off to flash new recovery?
have downloaded recovery clockworktouch 5.8.4.0 endeavor for new flash
and
Ressurection Remixunoff20140622-endeavor for image
is this the wright one for me?
Click to expand...
Click to collapse
Just go to HTCDEV.com unlock your bootloader via site and after this flash recovery philz 5.15.9 and after this new rom
thanks
Thant said:
Just go to HTCDEV.com unlock your bootloader via site and after this flash recovery philz 5.15.9 and after this new rom
Click to expand...
Click to collapse
Thanks for answer,
bootloader now unlocked,
now:
endeavoru pvt ship s-on RL
hboot -1.72.0000
cpld-none
microp-none
radio-5.1204.164d3.31
emmc dis
cpu dis
hw sec enabled
modem p off
now i can go to fastboot mode -> but after showing checking sd card: update P46IMG tries to install and failed
-> always i go into fastboot mode
-> now i have installed clockworkMod Recovery 5.8.4.0
can reach into recovery
can flash boot now also
but cant flash another os , always fails with 24 verifying android txt failed and aborted
-> i think the custom rom i have tried to install always tries to install after reboot
cid is vodap102
ty for help
noobtotal said:
Thanks for answer,
bootloader now unlocked,
now:
endeavoru pvt ship s-on RL
hboot -1.72.0000
cpld-none
microp-none
radio-5.1204.164d3.31
emmc dis
cpu dis
hw sec enabled
modem p off
now i can go to fastboot mode -> but after showing checking sd card: update P46IMG tries to install and failed
-> always i go into fastboot mode
-> now i have installed clockworkMod Recovery 5.8.4.0
can reach into recovery
can flash boot now also
but cant flash another os , always fails with 24 verifying android txt failed and aborted
-> i think the custom rom i have tried to install always tries to install after reboot
cid is vodap102
ty for help
Click to expand...
Click to collapse
install philz 5.15.9 recovery after this mount sd card and copy your custom rom to sd card after this flash boot.img from fastboot after this go in recovery and flash the rom if you want KK rom you must flash latest TWRP or CWM but ther have problem with mount sd card.
And sonmething else when you go to bootloader your phone must be disconnected from PC and when you are in bootloader conect to PC and you will see fastboot usb
problem solved!TY!
Thant said:
install philz 5.15.9 recovery after this mount sd card and copy your custom rom to sd card after this flash boot.img from fastboot after this go in recovery and flash the rom if you want KK rom you must flash latest TWRP or CWM but ther have problem with mount sd card.
And sonmething else when you go to bootloader your phone must be disconnected from PC and when you are in bootloader conect to PC and you will see fastboot usb
Click to expand...
Click to collapse
Thanks for help!
now on CM 10.2.1 endeavoru again tried philz and there i could see my sdcard , so i can push new rom to sd card;tried to flash the cm version, always failed code 23 or 7 ->
-> flash was possible after i haved deleted "asserts...............................; in the android-txt file (found here in xda forum) , i think there is proofed which version of rom and h-boot is on the phone . i deleted it (the first 4 lines up to :good: and saved it to the rom.zip-> then , no prob to flash the cm.zip via sd card; then flashed boot image from cm , deleted cache and factory reset , restart and now cm again
thanks for help !!!!!! great job! great forum here!