Related
i have installed insertcoin dataplus v3 with partition of fat32 =6.40gb
and ext3=1gb ...still the internal memory appears low all the time ...can any1 help me with this .....
Thanx
Are you S-off? Did you flashed the CM7 HBoot partition table?
YES M S-OFF ..... I DIDNT FLASH CM7 HBoot partition table ...WHAT IS IT ???
Next time READ!!!
from the Insertcoin data++ thread:
1st things 1st, you need to flash Bravo CM7 Hboot. either from fastboot or from hboot.- goto alpharev.nl site - is there together with all the info how to flash it
Click to expand...
Click to collapse
From alpharev.nl (here you can find also the required files).
If you are already S-OFF, you can get our newest patched HBOOTs from here. (without going through the entire procedure again).
Please read the entire table and pick the partition table with the correct sizes for your ROM. One easy way to switch partition tables, is to nandroid backup,
and verify that the sizes of your backup are indeed the ones listed in the table (or smaller), and restore after flashing hboot.
1) Nandroid backup in recovery.
1a) Download This file.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore.
Click to expand...
Click to collapse
More detailed instructions here:
http://forum.xda-developers.com/showpost.php?p=12699557&postcount=8
thanx davebugyi
gawwd .....i still cant get it still didnt understand the procedure wanted to use data++
1.Download the .img file from Alpharev's site. The BRAVO_CM7 one.
2. Download android SDK from official site, and run SDK Manager. When it is running, then install the platform-tools (revision 3 ATM), too.
3. Copy the CM7 file (.img) you downloaded into the android SDK folder, where fastboot.exe is located.
4. Reboot your phone into fastboot (holding down BACK+POWER keys when the phone is switched off) - it should show FASTBOOT USB.
4a. Make sure you have the USB drivers installed (for me HTC sync is not needed, i used the UNREVOKED USB drivers instead)
5. Fastboot flash. navigate to your android SDK directory in Command Promt (CMD.EXE) then run these commands:
a, fastboot flash hboot bravo_alphaspl.img (or whatever is the name of the file)
b, fastboot reboot-bootloader
c, fastboot erase cache
6. You have now the Partition table.
7. Just in case, go to the recovery, wipe EVERYTHING and Re-flash the ROM.
Alternative solution here: Did not try it myself, so don't ask, how to
http://forum.xda-developers.com/showthread.php?t=794638
finally did it .....
thanx alot davebugyi
i cannot update the latest radio 32.56.00.32U_5.17.05.08
i m using insercoin gingersense v2
i tried updating it shows update complete but the radio is still the same
any idea ????
Have the same problem,
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 5.11.05.27.
SPL/hboot version: 0.93.1000.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
Flashing "radio" - PLEASE WAIT.
"radio" flash FAILURE.
Whats the problem?
do you use a custom hboot? If yes, your cache partition is probably to small to hold a radio-flash (depends on which hboot exactly you are using), so you have to use fastboot to flash radios.
Are you flashing from Recovery? If so, are you using a custom Hboot that doesn't have a large enough cache partition?
Im using CM7 hboot, and i was tring to flash with festbootcomander 1.1
Try flashing it in fastboot with "fastboot flash radio radio.img". Making sure the radio.img is in the proper folder before hand.
or try Android Flasher...I think it does the radio...not 100% though. But again, I'm not sure if these utilities use the cache partition or not. If they do, CM7's Hboot is too small.
Step-by-step, if you need it. (Taken from www.oxygenrom.com)
Flash Radio (S-OFF fastboot method):
1.Fully charge your phone
2.Download the radio image from the link below and unzip the radio.img
3.Connect your phone to your computer.
4.Reboot your phone into the bootloader (fastboot mode).
5.At the command prompt on your computer type: fastboot devices
6.A value like HTXXXXXXXXXXX should be displayed with the word fastboot next to it.
7.Your phone screen should have FASTBOOT USB on it.
8.If all of the above is not exactly as described DO NOT PROCEED and resolve your fastboot problem.
9.At the command prompt type: fastboot flash radio "filename".img - you must type it correctly!
10.Now, observe the computer and be patient TOUCH NOTHING!!
11.The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
12.Watch the little indicator at the top of your phone screen.
13.Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
14.Then, and only then, reboot your phone.
Tnx but getting in the command prompt:
C>fastboot devices
'FASTBOOT' is not recognized as
operable program or batch file.
S O L V E D:
I unzipped the radio and and flashing only the radio.img with the fastboot commander 1.1
So I've just USB bricked my phone and I'm running through the steps to fix it but when I run 'fastboot oem boot' it says my INFOCID is Super CID and I can't find out what my CID is in order to generate the mtd0.img How can I find out my CID and ROM version?
jordan.harris01 said:
So I've just USB bricked my phone and I'm running through the steps to fix it but when I run 'fastboot oem boot' it says my INFOCID is Super CID and I can't find out what my CID is in order to generate the mtd0.img How can I find out my CID and ROM version?
Click to expand...
Click to collapse
Rom version in Settings>About Phone
CID from ASTRO file manager (download from market) via this tutorial:
http://www.mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/
How can I find out my ROM Version? I'm running a custom ROM and About Phone just says 2.3.4.
Did you try the fastboot oem enable command in the sd card fix section of the USB brick thread?
Yes, I did that. When I'm running the '/data/flash_image misc /data/mtd0.img' command in terminal will it tell me if it's successful or not? Because it's not telling me anything. Just jumping to the next line. I've tried rebooting after that and it's still saying damaged SD card.
Not sure if this has something to do with it but I flashed the new OxygenR2 Hboot...could that have something to do with it since they patched the SuperCID?
That was it. The new OxygenR2 Hboot has all CID's set to superCID (so you don't need a goldcard to run an RUU) I was using the backupCID which had my carrier in it. Once I generated the mtd0.img with superCID as the CID it went no problem.
Good news! Useful issues for others to read. Maybe add to the title and tag it [SOLVED]?
seriously, the USB-Brick thread MUST BE UPDATED !!!
if you are S-OFF (which you must be since running a custom hboot) you can fix usb-brick with:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and that is it, usb-brick fixed !
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
As you can see in the picture the phone boots up to this screen. A friend of mine bought an HTC One on ebay and he found out it was rooted/unlocked so he went to put it back to stock and may have bricked the device while doing so.
EDIT: so I am able to use fastboot, but not adb because I can't get into Windows. Flashing the stock Verizon RUU I found still doesn't get me anywhere though.
Is there any hope for this device? Thanks in advance!
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
cmlusco said:
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
Click to expand...
Click to collapse
Yea I saw that after messing around with it some more. It is Windows 7 x64.
I tried the one at the bottom of the page as I can't find one anywhere else. I also used the commands at the bottom to try and flash it.
http://www.htc1guru.com/downloads/ruu-zip-downloads/
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
cmlusco said:
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
Click to expand...
Click to collapse
OK cool I will try that once it downloads. It shows "My HTC" in the device manager. Also with the fastboot devices command it does give me the device ID.
EDIT: That worked! Thanks a lot for the RUU file, as I could not find that anywhere.
Hello. A friend of mine has the same problem. She tried to flash this RUU: "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted" but the phone doesn't boot. Here is more info about the problem: http://forum.xda-developers.com/showthread.php?t=2688936
Can she flash the RUU posted here?
This is what the hboot says:
Unlocked
m7_wlv pvt ship s-off rh
cid-11111111
hboot 1.54.0000
radio 1.12.42.0906
opendsp v31.120.274.0617
os 1.10.605.10
Thank you very much.
She can, but since she is s-off, its better to flash the decrypted one. http://vzw1files.dyndns.org/RUUs/2.10.605.1/PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip
cmlusco said:
She can, but since she is s-off, its better to flash the decrypted one.
Click to expand...
Click to collapse
First, thank you very much. She changed the CID to VZW__001. That's not a problem, right?
Does the CID and MID have to be compatible with the RUU? She has this MID: PN0731000.
Downloading this RUU, will report back.
Again, thank you.
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
cmlusco said:
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
Click to expand...
Click to collapse
Hello again. Before we try to flash the RUU, I would like to ask you the steps to do it. This is what we gonna do:
1. Download RUU
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
And that's it? Nothing else is needed, right?
EDIT: we flashed the RUU. Now the phone boots always in fastboot. No matter what option we choose, the phone does nothing and goes back to fastboot. On the bottom of hboot there is a new line in red: "Active cmdline overflow! (1073 Bytes)"
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
cmlusco said:
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
Click to expand...
Click to collapse
Hello. We just did it, and still the same problem. We were reading that some people solved this by doing a downgrade to hboot 1.44. But I don't want to make this problem worse.
You can try it, its worth a shot. Just flash an older ruu. http://vzw1files.dyndns.org/RUUs/. Dont remember which one goes with 1.44
cmlusco said:
You can try it, its worth a shot. Just flash an older ruu. Dont remember which one goes with 1.44
Click to expand...
Click to collapse
You can't be more kind. We made a downgrade, and now we can use CWM again. (We did the downgrade before reading your post, so we didn't use an older RUU) Now thinking hwat should be the next step: flashing a ROM (custom or stock, mounting a pendrive) or flashing an older RUU or anything else. Again, dude, you're awesome.
I'm stuck in a similar situation and any help would be appreciated so I don't screw this up. I can get into the bootloader but not into recovery (gets to the first TWRP screen then reboots). Safe mode works fine too.
Win7 64bit
S-off
Rooted
Stock ROM
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW-001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OS-1.10.605.8
I can get into ADB. Would just like to know if I need to flash a new RUU or should I flash updated TWRP first? And the proper commands so I don't botch this.
Any help would be greatly appreciated.
Thanks
I would try reflashing twrp first. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
fastboot erase cache
fastboot flash recovery recovery.img
cmlusco said:
I would try reflashing twrp first.
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Didn't work. Got to the TWRP splash screen and back into the bootloop again.
Ok then i would do an ruu. http://vzw1files.dyndns.org/RUUs/
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip (may fail with flush error, just do the cmd again)
fastboot reboot
Hi,
Similar problem here.
This is my situation:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
CID: VZW__001
MID: PN0731000
Only fastboot. Can't access to recovey (CWM). Can't access to OS, so no adb.
Every time I try to RUU it gives the "Signature verify fail" message.
So, I tried encrypted ROMs (those at vzw1files. dyndns. org), and I could go a step forward; but the flashing hungs up after giving this messages:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
Thanks in advance, I hope I didn't screw it up.
The problem is nicouy that you are s-on, and on the newest kk firmware. An s-on phone will not allow you to "downgrade" firmware, and we do not yet have the latest ruu available, at least to my knowledge. So your kind of screwed right now untill we get our hands on a kk ruu.