Database Info

Signature error for ADP1

I am now on JF1.3 on my ADP1. I tried to flash this 'leaked' image:-
http://andblogs.net/2009/01/new-adp1-images-leaked/
I renamed the file as update.zip and reboot with Power+Home. Then did the ALT+W and ALT+S.
The Flashing failed because of errors in Signature(5 files). I tried the following to remedy:-
1) Reformatted the card
2) Renamed the Update.zip to 'Update'
Even after these I am keeping on getting the Signature errors. Please help solve this issue. Thanks.
* I tried to install Cupcake and it works. Though returned to jf1.3 because of the radio issues.

vinodis said:
I am now on JF1.3 on my ADP1. I tried to flash this 'leaked' image:-
http://andblogs.net/2009/01/new-adp1-images-leaked/
I renamed the file as update.zip and reboot with Power+Home. Then did the ALT+W and ALT+S.
The Flashing failed because of errors in Signature(5 files). I tried the following to remedy:-
1) Reformatted the card
2) Renamed the Update.zip to 'Update'
Even after these I am keeping on getting the Signature errors. Please help solve this issue. Thanks.
* I tried to install Cupcake and it works. Though returned to jf1.3 because of the radio issues.
Click to expand...
Click to collapse
You have to use fastboot as this is not an update.zip.
You can either flash each img or you can try out the full system update...
Code:
fastboot update update.zip
I have *not* tried this approach yet but it is documented so I assume it works?
Also, you will notice that there is no misc partition; you can ignore that error and flash the rest (skip splash1/splash2 if you already have custom splash screens).
Added nice-ities:
-The ability to skip signing-in to your google account
-System updater
-...it's new?

Thank you !. Fastboot worked.

Getting Roms Working With Rogers Magic?

So thanks to the hard work of the techies here, it has finally been shown that Rogers likes screwing with what works. With the memory offsets and tweaked radio, it seems that very few of the current roms work with the Rogers Magic. This got me wondering if there was a way to make the current roms work with the Rogers Magic, maybe through patching the boot.img or something along those lines? Maybe a tutorial on how to do this, or some kinda patch tool?
I believe that Amon_RA has already done this for nk02's ION rom (which works beautifully btw), but this taste of freedom has left me craving more!

Can you give me a link to that ROM?

Sure. It was a bit buried in the thread:
Amon_RA said:
I quickly repacked "R4 full" with the HTC offsets and replaced the kernel just to prove that it CAN work on HTC branded Magic's like the Nordic Magic and even the ROGERS one!
This is just to show that it works on HTC branded Magic's, some kernel added features might not work, up to Nk02 to fix his ROM and make it available for ALL HTC Magic devices
How to proceed :
1. Download this repacked version of the R4 full, rename it to update.zip, and copy it to your SD-card.
2. Download RAv1.0H rooted recovery here.
3. Boot the device in fastboot mode.
4. Connect the device to your machine over USB.
5. $fastboot boot recovery-RAv1.0H.img
wait a few minutes and unplug your device from USB
6. Choose option "Wipe data/factory reset" from the menu
wait for the datawipe to complete
7. Choose option "Apply sdcard:update.zip" from the menu
8. Choose option "Reboot system" from the menu
Enjoy.
Click to expand...
Click to collapse
Also, to get wifi working:
Amon_RA said:
If you want to get wlan working on the HTC branded repack :
1. Download this wlan.ko.
2. adb remount
3. adb push wlan.ko /system/lib/modules/wlan.ko
+> I think it's better if nk02 continues his work, I feel like I'm stealing his work
Click to expand...
Click to collapse

skittleguy said:
Sure. It was a bit buried in the thread:
Also, to get wifi working:
Click to expand...
Click to collapse
Hmmm, every time I try to run sudo adb remount I get error: device not found. Any ideas? I'm running Ubuntu Jaunty.

Amon_RA also mentioned what we should prepare and read up on, which I did. Linux + SDK. Extracted and unpacked the images, even the boot images. Opened two boot images up to compare and found different offsets. But I'm lost until they drop us some more hints....

parrot5 said:
Amon_RA also mentioned what we should prepare and read up on, which I did. Linux + SDK. Extracted and unpacked the images, even the boot images. Opened two boot images up to compare and found different offsets. But I'm lost until they drop us some more hints....
Click to expand...
Click to collapse
Thank's to Amon_Ra I can use nk02's ION Multi5 ROM. Unfortunately HSDPA does not work for me when using that ROM.

hotweiss said:
Thank's to Amon_Ra I can use nk02's ION Multi5 ROM. Unfortunately HSDPA does not work for me when using that ROM.
Click to expand...
Click to collapse
Only rogers ROMs show H when its on HSDPA. all other still have HSDPA but continues to show 3G.

skittleguy said:
So thanks to the hard work of the techies here, it has finally been shown that Rogers likes screwing with what works. With the memory offsets and tweaked radio, it seems that very few of the current roms work with the Rogers Magic. This got me wondering if there was a way to make the current roms work with the Rogers Magic, maybe through patching the boot.img or something along those lines? Maybe a tutorial on how to do this, or some kinda patch tool?
I believe that Amon_RA has already done this for nk02's ION rom (which works beautifully btw), but this taste of freedom has left me craving more!
Click to expand...
Click to collapse
You can get any custom ROM working on your Rogers Magic and basically on every HTC branded Magic around. If you like to "port" a custom Google-branded ROM to a HTC-branded ROM follow these steps :
- I assume that you have basic Linux knowledge and that you know how to set up your own environment and tools, unpack gz files and cpio them etc...
- Download these tools. They contain the JesusFreke's SignApp, William Enck's splitboot using my recompiled mkbootimg-H binary (including the HTC branded offsets), and a repack pearl script.
Now the actually work :
1. Get the boot.img and recovery.img from your original HTC branded Magic (fastboot my recovery image and use nandroid for this).
2. unpack the boot.img and recovery.img using unpack-H.pl.
3. move both kernels somewhere save, you'll need them later.
4. Download the google branded custom ROM you want to port, most of the custom ROMs come in the form of a update.zip file.
5. Extract the boot.img and recovery.img (if there is one) from the update.zip.
6. unpack the boot.img and recovery.img (same as step 2).
7. replace both kernels with the ones you saved previously in step 3.
8. repack boot boot.img and recovery.img using repack-H.pl
9. copy both boot.img and recovery.img in the update.zip package making sure you overwrite the existing ones inside with the new ones.
10. Sign the update.zip file with SignApp (see readme inside rar).
11. Copy the update.zip file to your SDcard.
12. fastboot my recovery image and choose data wipe and then update.
13. reboot
Good luck

Thanks so much for the step by step.
Question for you : If i port the SuperHero v2 which has working wifi to a "Rogers version" following your instructions, will the wifi work or will it not (since it doesnt on Killadude's rogers port of the Superhero 2) ?
My point is - does something need to be done that he didnt do or forgot to do or will it just not work ?

Thanks alot Amon_Ra..
Redbull is comming your way.. Just what I needed..
Now the experimenting starts, lets see If I can cook something nice..
Thanks again, you live up to you name..

Awesome! Setting up Ubuntu as we speak.

Okay I repacked the nk02 f4 LITE version as instructed..... now to flash it to my own Magic.... the moment of truth...... LOL

So so ? Keep us updated lol !

ranxoren said:
So so ? Keep us updated lol !
Click to expand...
Click to collapse
BRICKED
Second try: Got the T-Mobile logo and Rogers logo in a loop

parrot5 said:
BRICKED
Second try: Got the T-Mobile logo and Rogers logo in a loop
Click to expand...
Click to collapse
Forgot to data wipe?
A logcat / ddms trace while booting can help too

Amon_RA said:
Forgot to data wipe?
A logcat / ddms trace while booting can help too
Click to expand...
Click to collapse
Did the data wipe.
The device doesn't come online long enough for adb to see it... DDMS fails to see the device while the device is in the booting loop, and logcat simply says "waiting for device".

Amon_RA said:
Forgot to data wipe?
A logcat / ddms trace while booting can help too
Click to expand...
Click to collapse
I have the same problem, it doesn't matter if you do a wipe or not.

OK I flashed my original boot.img back in. Now the device is stuck on the original "HTC Magic" logo, but at least DDMS picked it up and here are the errors:
Code:
06-28 20:13:36.063: ERROR/flash_image(37): error opening /system/recovery.img: No such file or directory
06-28 20:13:36.963: ERROR/RIL Acoustic(32): can't open /dev/htc-acoustic -1
06-28 20:13:38.703: ERROR/AndroidRuntime(33): JNI_CreateJavaVM failed
06-28 20:13:39.063: ERROR/HTC Acoustic(34): Fail to open /system/etc/AudioPara_Rogers.csv -1.
06-28 20:13:39.133: ERROR/A2DP(34): bt_audio_service_open failed
06-28 20:13:39.133: ERROR/A2dpAudioInterface(34): a2dp_init failed err: -111
06-28 20:13:39.133: ERROR/AudioFlinger(34): mA2dpDisableCount is already zero
06-28 20:13:41.103: ERROR/AndroidRuntime(54): JNI_CreateJavaVM failed
06-28 20:13:46.503: ERROR/AndroidRuntime(55): JNI_CreateJavaVM failed
06-28 20:13:50.863: ERROR/AndroidRuntime(58): JNI_CreateJavaVM failed
06-28 20:13:56.593: ERROR/AndroidRuntime(71): JNI_CreateJavaVM failed
06-28 20:14:01.673: ERROR/AndroidRuntime(72): JNI_CreateJavaVM failed
06-28 20:14:06.083: ERROR/AndroidRuntime(73): JNI_CreateJavaVM failed
06-28 20:14:11.493: ERROR/AndroidRuntime(74): JNI_CreateJavaVM failed
06-28 20:14:15.913: ERROR/AndroidRuntime(75): JNI_CreateJavaVM failed
06-28 20:14:21.333: ERROR/AndroidRuntime(76): JNI_CreateJavaVM failed
06-28 20:14:26.743: ERROR/AndroidRuntime(77): JNI_CreateJavaVM failed
06-28 20:14:31.153: ERROR/AndroidRuntime(78): JNI_CreateJavaVM failed
06-28 20:14:36.563: ERROR/AndroidRuntime(79): JNI_CreateJavaVM failed
06-28 20:14:40.973: ERROR/AndroidRuntime(80): JNI_CreateJavaVM failed
06-28 20:14:46.383: ERROR/AndroidRuntime(81): JNI_CreateJavaVM failed
06-28 20:14:50.803: ERROR/AndroidRuntime(82): JNI_CreateJavaVM failed
EDIT:
I restored everything, and the following lines exist in the error log (so we can ignore them, I think)
Code:
ERROR/RIL Acoustic(32): can't open /dev/htc-acoustic -1
ERROR/HTC Acoustic(34): Fail to open /system/etc/AudioPara_Rogers.csv -1.
ERROR/A2DP(34): bt_audio_service_open failed
ERROR/A2dpAudioInterface(34): a2dp_init failed err: -111
So really the only errors are:
Code:
ERROR/flash_image(37): error opening /system/recovery.img: No such file or directory
ERROR/AndroidRuntime(33): JNI_CreateJavaVM failed
But note that I had to flash the original boot.img back to get these, else DDMS doesn't even pick up the device

Amon_RA said:
You can get any custom ROM working on your Rogers Magic and basically on every HTC branded Magic around. If you like to "port" a custom Google-branded ROM to a HTC-branded ROM follow these steps :
- I assume that you have basic Linux knowledge and that you know how to set up your own environment and tools, unpack gz files and cpio them etc...
- Download these tools. They contain the JesusFreke's SignApp, William Enck's splitboot using my recompiled mkbootimg-H binary (including the HTC branded offsets), and a repack pearl script.
Now the actually work :
1. Get the boot.img and recovery.img from your original HTC branded Magic (fastboot my recovery image and use nandroid for this).
2. unpack the boot.img and recovery.img using unpack-H.pl.
3. move both kernels somewhere save, you'll need them later.
4. Download the google branded custom ROM you want to port, most of the custom ROMs come in the form of a update.zip file.
5. Extract the boot.img and recovery.img (if there is one) from the update.zip.
6. unpack the boot.img and recovery.img (same as step 2).
7. replace both kernels with the ones you saved previously in step 3.
8. repack boot boot.img and recovery.img using repack-H.pl
9. copy both boot.img and recovery.img in the update.zip package making sure you overwrite the existing ones inside with the new ones.
10. Sign the update.zip file with SignApp (see readme inside rar).
11. Copy the update.zip file to your SDcard.
12. fastboot my recovery image and choose data wipe and then update.
13. reboot
Good luck
Click to expand...
Click to collapse
I got this error when repacking (Step 7):
sudo sh ./repack-H.pl boot.img-kernel /home/paul/Booty boot.img
./repack-H.pl: 3: use: not found
./repack-H.pl: 4: use: not found
./repack-H.pl: 7: my: not found
./repack-H.pl: 9: my: not found
./repack-H.pl: 11: die: not found
chdir: 13: can't cd to [1]
./repack-H.pl: 15: Syntax error: word unexpected (expecting ")")
Click to expand...
Click to collapse
Any ideas? I'm actually confused about setting the path of my ramdisk...

hotweiss said:
I got this error when repacking (Step 7):
Any ideas? I'm actually confused about setting the path of my ramdisk...
Click to expand...
Click to collapse
I think you need to extract that ramdisk.gz, mount the file within, and copy the contents to another directory, which becomes the "path of ramdisk".
(Or, whatever method you like to extract those files... )

[Recovery] [09-Feb-2011] RA-supersonic-v2.3

[ Description ]
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
[ Features ]
Detailed description of every menu item
[ Known Issues ]
v2.3.3 has some screen tearing/color weirdness going on. This is just a graphical bug in the recovery kernel, nothing to worry about. I'll try to fix it in a next version.
[ Download ] - ALWAYS check the md5sum to make sure the file isn't corrupted!
recovery-RA-supersonic-v2.3.img - MD5Sum: c00243750cc79e4a1dd4888db175b19f
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Mirror to all my recoveries (Click a few adds to keep it up and running - Thanks DrMacinyasha ^^)
[ Install ] - There are several ways to install a custom recovery, feel free to pick the one that suits you best :
- the Bootloader way - - Thanks Tiffany84 ^^
Place PC36IMG.zip on the root of your sd card.
Boot the phone into the bootloader by powering the phone down, then press the power and the volume down buttons at the same time.
Once the phone boots into the bootloader the phone will automatically recognize the zip file. It will ask if you would like to update, select yes and let it do it's thing and you will be good to go
- via Rom Manager - - STILL NEEDS TO UPDATED TO v2.3!!
Download "Rom Manager" from the Android market
Start "Rom Manager"
Select "Flash ClockworkMod Recovery" and wait for it to finish
Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
- via terminal app or adb - (Make sure your rom contains flash_image!!)
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
[ Important notes ]
Don't restore wimax nandroids between different phones! If you still plan to do it make sure to remove the wimax image from the nandroid backup before restoring!!
I'll only answer to posts with a real problem description and a pastebin log. All other "issues" will be skipped/ignored.
Make sure have enough free space available on your sdcard when making a nandroid backup!!
Always check recovery.log before posting your issues!
You can do this by doing :
"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
[ Special Thanks ]
http://www.androidspin.com for hosting ^^
Tiffany84 for the PC36IMG's ^^
DrMacinyasha for the mirror ^^
jhansche for the initial port of the evo recovery and his menu navigation and verification code.
joncfoo for the menu loop code.
toastcfh for testing and all his awesome work on the Evo (root, unlocked nand, ..) Thanks ^^ Buy him a coffee!!
flipzmode for testing, screenshots and feedback, Thanks ^^
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for his awesome work on recoveries and ROM manager ^^
Cyanogen for his dedicated work! , buy him a beer!
Chris Soyars for the new Apps2SD method ^^
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
rikupw for the ideas and toggle_ums script.

Change-log
v2.3
Nandroid will skip sd-ext backup when it's not present.
Nandroid will not check the battery percentage anymore.
Switched off signature check by default (Stop asking now, ok?).
Cache is not selected as part of a default Nandroid backup anymore.
Added wipe Boot, System and sdcard to the wipe menu.
Re-ordered some items in the wipe menu.
Switched to a CM android-msm-2.6.35-unified kernel (should stop the endless dots).
v2.2.1
Fixed Nandroid ext backup/restore. It now backups/restore the entire ext.
v2.2
Nandroid backup is now selective, boot/system/cache/data are selected by default.
Nandroid checks if there's at least 500MB free on SDcard before starting a backup.
Kernel min freq is set to max freq to speed up things (tip of toastcfh).
Added/updated error/warning messages.
v2.1.1
Updated kernel to 2.6.32.17 , this should fix the partition issues on newer hboots
Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.
Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.
Re-ordered the wipe menu.
Added SDEXT support for update scripts.
Added "filebrowser" support when you select a zip to flash.
Added "/.." support to the filebrowser so you can navigate up.
Added a mount menu so you can manually (u)mount stuff.
Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases...
Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options.
Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default.
Added a few new Google apps to the Google app backup script.
v1.8.0
updated Nandroid so it also backups and restores the wimax partition.
made the recovery 400kb smaller so it fits most recovery partitions with bad blocks.
added a return option (instead of pressing vol-up+down) to the menu (by jhansche).
completely ignore verification (by jhansche).
added menu loop (by joncfoo).
v1.7.0.2
Reduced the overall size so it can still be flashed when having lots of bad blocks.
v1.7.0.1
Initial release (port from my Nexus One recovery)

awesome I was waiting for this i was tired of having to go home to change roms!

Nice, i'm going to try this out right now and report back if there are any problems.

It works nicely. I don't like having to press both volume-keys to go back to the previous menu, but it's not a deal breaker. Good job Amon_RA. =]

trying to flash the image its telling me not found when i tried every which way to flash it any ideas? Ugh sorry maybe i need to read...a little more next time sorry!

Arthur101 said:
trying to flash the image its telling me not found when i tried every which way to flash it any ideas? Ugh sorry maybe i need to read...a little more next time sorry!
Click to expand...
Click to collapse
How are you flashing it? the fastboot method worked fine for me
Edit:
1) Get fastboot.exe here
2) Place recovery-RA-evo-v1.7.0.1.img in the same dir as fastboot
3) boot your phone into fastboot (Volume Dwn+ Power) Select fast boot
Then follow
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.7.0.1.img(press enter)

I keep getting a error opening /sdcard/recovery-RA.img no such file or directory.

Fixter said:
I keep getting a error opening /sdcard/recovery-RA.img no such file or directory.
Click to expand...
Click to collapse
It's recovery-RA-evo-v1.7.0.1.img , not recovery-RA.img ...

Amon_RA said:
It's recovery-RA-evo-v1.7.0.1.img , not recovery-RA.img ...
Click to expand...
Click to collapse
I got the error with both names. I renamed the file to see if I was making mistakes with the file name since it was so long.

Hey, Ra, you do realize we ARE going to need Care Bears on our Evo recoveries just like you spoiled us with on our MT3G's... I'm just saying!

I've tried downloading the file a couple of times to make sure it wasn't corrupted but I keep getting "sending 'recovery' (5032 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)"
Also thanks for the new recovery, was hoping you'd release one for our Evo's

And I know I have flash_image because I did Toasts Nand Unlock yesterday. And I checked and the file is on the root of the SD Card.

Fixter said:
And I know I have flash_image because I did Toasts Nand Unlock yesterday. And I checked and the file is on the root of the SD Card.
Click to expand...
Click to collapse
it should be in /data
once you restore a rom that didn't have it, it's no longer on the phone where it should be. if you put it back in /data and chmod 755 it you should have no problem.

Cordy said:
it should be in /data
once you restore a rom that didn't have it, it's no longer on the phone where it should be. if you put it back in /data and chmod 755 it you should have no problem.
Click to expand...
Click to collapse
Yup. I just did. I was thinking about this and went ahead. Thanks for the information though.
PS: I get a Build Not Set on the End of the Recovery.

Amon_RA said:
Features
Fix apk uid mismatches :: Does extacly that
Click to expand...
Click to collapse
thanks for this great recovery! im excited to try it!
two quick questions:
does the fix apk uid mismatches uses the common fix_permissions.sh script?
do you have a github or location where the source code is viewable?
thanks again!

Fixter said:
I got the error with both names. I renamed the file to see if I was making mistakes with the file name since it was so long.
Click to expand...
Click to collapse
How are you flashing? Fastboot, flash_image? Are you sure you mounted /sdcard? Do an "ls /sdcard/recovery*" to make sure the sdcard is mounted and that the recovery image can be found.
Cordy said:
I've tried downloading the file a couple of times to make sure it wasn't corrupted but I keep getting "sending 'recovery' (5032 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)"
Click to expand...
Click to collapse
Did you unlock NAND?
joeykrim said:
thanks for this great recovery! im excited to try it!
two quick questions:
does the fix apk uid mismatches uses the common fix_permissions.sh script?
do you have a github or location where the source code is viewable?
thanks again!
Click to expand...
Click to collapse
Erm, I'm using the same fix_permissions.sh script as in my other recoveries, check github :
Scripts : http://github.com/packetlss/amonra_recovery_scripts
Recovery : http://github.com/packetlss/amonra_bootable_recovery
Still need to push the evo recovery.

Amon_RA said:
Did you unlock NAND?
Click to expand...
Click to collapse
Yes, I'm able to flash toasts recovery.img through fastboot no problem.

How do I check if I loaded the recovery correct? I get a Build : Not Set when I entered the recovery on the lower end where its suppose to say the build number.

You should work together with Koush and make one great recovery. He has some features such as the ability to flash a zip from ANYWHERE on the SD Card. The two of you should be able to work some miracles.
Ceger

[NIGHTLY][ROM][FRG83] CyanogenMod 6 for vendor Bravo (HTC Desire GSM)

This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire GSM (cdma version here)
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. Update your radio if needed (720p require 5.x radio)
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://mirror.teamdouche.net/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
thank's to gatsu_1981 and imfloflo for inspiration

Rooting Guide
http://forum.xda-developers.com/showthread.php?t=788044
Google Addon: latest HDPI-20101114
Other release http://goo-inside.me/google-apps/
Radio Firmware: 5.x radio required (GSM ONLY)
Desire GSM radio thread
Read/Write Access System Partition (S-OFF)?
Thank's to AlphaRev [site] [xda]
Low storage for apps?
Flash the AlphaRev HBOOT Bravo N1Table (Require S-OFF)
Follow this instrunction for update without data lost (aka no data wipe)
Still low storage for apps?
Install an A2SD solution: Firerat or Darktremor
i recommend the Firerat solution: CM specific, less space usage 25kb vs 6mb, bind mount, no boot loop, auto restore after cm rom update (from 1.35b)

Fantastic, thanks Kali!

bemymonkey said:
Fantastic, thanks Kali!
Click to expand...
Click to collapse
+1
And don't post questions before reading the 300+ pages of this thread: http://forum.xda-developers.com/showthread.php?t=719544
Just kidding. But I thought a reference to the old thread could be useful.

yuo should add a link to alpharevs s-off and modified partition table

deleted .

the developt is in 6.1 cyanomod nightly updated right?

Latest nigthlies have been rock solid for me. My only complaint is the annoying credential storage password, which I must enter every time I reboot the phone if I want to connect to 802.1x wifi networks. Other than that, 16x have been flawless.

*cheers kali on*
Finally an up to date thread. Reading your post I learned something. I didn't know firerat a2sd now works with cyanogen.
Anyone got experience migrating from dta2sd to firerat?
Swyped with my S-OFF'd brain using teh internetz

Is there a patched Amon Ra recovery image that allows you to use the N1 partition table ?

why woud you patch it?? just use n1 table and default amon ra

madman_cro said:
why woud you patch it?? just use n1 table and default amon ra
Click to expand...
Click to collapse
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.

ganjamu said:
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.
Click to expand...
Click to collapse
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom

madman_cro said:
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom
Click to expand...
Click to collapse
Thanks! I will give it a shot tonight and let you know how it goes.

Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore

stingerpl said:
Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore
Click to expand...
Click to collapse
Yes! Absolutely no problem... (but if you already have recovery, then there is no need to flash a new one)

Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.

dipje said:
Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.
Click to expand...
Click to collapse
Have you tried diasabling signature verification?

vnvman said:
Have you tried diasabling signature verification?
Click to expand...
Click to collapse
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
EDIT: Solved it. Apparently there is a bug in my recovery. If I use the recovery the mount my sdcard over USB, afterwards /sdcard can get unmounted. So it couldn't find the .zip file I was choosing because /sdcard was not mounted. Why it was still possible to list the contents on the sdcard is a mystery to me. That must mean the recovery mounts /sdcard, lists the contents and then unmounts it again, and _then_ tries to start the update?!?
Anyway, going into the 'mounts and storage' menu and choosing 'mount /sdcard' suddenly made sure things worked again.
Really stumped how this happened.

dipje said:
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
Click to expand...
Click to collapse
What recovery image are you using? If you have amonRA you might try to fix this launching clockworkmod via fake flash and using that one to install the update. Otherwise if you already have clockwork you might try flashing amonRA via hboot and use that one...at times i can't perform something with one of the two recoveries, and using the other one often solves every issue for me

My Phone just rebooted and now loops at the android loading logo CM13

Hello I have the latest version of this rom http://forum.xda-developers.com/oneplus-one/development/rom-cm-12-builds-t3045053
and it was working great! I had no problems and then one day while playing an audio file (smart voice recorder), my phone froze for lke 30 seconds and then just rebooted by itself and started looping the android logo. Worried I booted into TWRP (3.0.2-0) and found out that in the logs I get these messages:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Unable to mount storage
What the hell, does this happen to anyone? Using their phone all ok and then bam reboot and now my internal storage is gone! Was it because I was using a 25 watt apple charger because I was recording video at the time and needed the juice. Oh man I really need those videos they mean everything to me!
system shows a size but very small like 1.3 gigs or something
data shows 0 mb for all stats
cache shows 0 mb for all stats
Internal Storage shows "invalid partition selection"
I have no idea what happened, I have such important data on this phone! How can I recover this? Please!!! I tried using the repairing data option and i got this error message
/sbin/efsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair data
Will offer a bounty if someone can help me recover my data! I am knocking my own ass for not having a backup ugh

I will offer a bounty if someone with experience can help me through this. The memories of my mother's passing means a lot to me and I would hate to lose it because some stupid app crashed on me and the phone rebooted.

vap3 said:
Hello I have the latest version of this rom http://forum.xda-developers.com/oneplus-one/development/rom-cm-12-builds-t3045053
and it was working great! I had no problems and then one day while playing an audio file (smart voice recorder), my phone froze for lke 30 seconds and then just rebooted by itself and started looping the android logo. Worried I booted into TWRP (3.0.2-0) and found out that in the logs I get these messages:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Unable to mount storage
What the hell, does this happen to anyone? Using their phone all ok and then bam reboot and now my internal storage is gone! Was it because I was using a 25 watt apple charger because I was recording video at the time and needed the juice. Oh man I really need those videos they mean everything to me!
system shows a size but very small like 1.3 gigs or something
data shows 0 mb for all stats
cache shows 0 mb for all stats
Internal Storage shows "invalid partition selection"
I have no idea what happened, I have such important data on this phone! How can I recover this? Please!!! I tried using the repairing data option and i got this error message
/sbin/efsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair data
Will offer a bounty if someone can help me recover my data! I am knocking my own ass for not having a backup ugh
Click to expand...
Click to collapse
In twrp if you go to advance then file manager click on sdcard can you see your files?
If not did you try to mount in twrp?
If so then you can pull the whole sdcard or select files via adb.

Durso81 said:
In twrp if you go to advance then file manager click on sdcard can you see your files?
If not did you try to mount in twrp?
If so then you can pull the whole sdcard or select files via adb.
Click to expand...
Click to collapse
for question #1 yes I do see my files. But certain folders like DCIM (pictures) or other apps such as whatapp is not showing.
when i try to mount in TWRP only firmware and system is checkable.... data/cache/usb-otg is not selectable (meaning check marks won't show up if I try to click it)
when I hit "select storage" i see the select storage options and both options (internal storage and usb-otg) says 0 MB
for your last suggestion im going to try it and see if I can access my files
Thank you for your help! Let me know how else I can continue the diagnostic and I will keep my word

vap3 said:
for question #1 yes I do see my files. But certain folders like DCIM (pictures) or other apps such as whatapp is not showing.
when i try to mount in TWRP only firmware and system is checkable.... data/cache/usb-otg is not selectable (meaning check marks won't show up if I try to click it)
when I hit "select storage" i see the select storage options and both options (internal storage and usb-otg) says 0 MB
for your last suggestion im going to try it and see if I can access my files
Thank you for your help! Let me know how else I can continue the diagnostic and I will keep my word
Click to expand...
Click to collapse
Yeah I would try pulling the whole sdcard to your computer via adb and see if it pulls the files you want.
If that doesn't work all I got is you can dirty flash that same ROM you had installed before. When you dirty flash you don't wipe data or anything since its the same ROM you had before. Its the same thing you do when you update to a new version of that developers ROM and you don't loose your data.
Just curious did you change over to f2fs the developer recommended it for installing his ROM, not sure if that's what caused the initial problem if you did not change to f2fs.

Durso81 said:
Yeah I would try pulling the whole sdcard to your computer via adb and see if it pulls the files you want.
If that doesn't work all I got is you can dirty flash that same ROM you had installed before. When you dirty flash you don't wipe data or anything since its the same ROM you had before. Its the same thing you do when you update to a new version of that developers ROM and you don't loose your data.
Just curious did you change over to f2fs the developer recommended it for installing his ROM, not sure if that's what caused the initial problem if you did not change to f2fs.
Click to expand...
Click to collapse
interesting i will try the adb method and see if that i can pull the files despite not seeing everything in the file manager
unfortunately i have never changed to the f2fs file system due to me being a noob at the time. But i never had a problem with his early builds and dirty flashing all the way to September. Ironically every time I dirty flashed i did a nandroid backup on the phone. lol... i can't even access that file right now because i don't see it in the file manager as the data cannot be accessed at the moment.

vap3 said:
interesting i will try the adb method and see if that i can pull the files despite not seeing everything in the file manager
unfortunately i have never changed to the f2fs file system due to me being a noob at the time. But i never had a problem with his early builds and dirty flashing all the way to September. Ironically every time I dirty flashed i did a nandroid backup on the phone. lol... i can't even access that file right now because i don't see it in the file manager as the data cannot be accessed at the moment.
Click to expand...
Click to collapse
Just to interject, not being on f2fs is wise, I don't believe it to be as stable, and is not very useful..
I'd like to also recommend using TWRP 2.8.6 (there's a link in my signature).. I've read more recovery related issues since it was updated..
Good luck

I know you said you are new if your having issues figuring out how to pull files via adb there is a all in one toolkit that has a pull/push file fearure. http://www.wugfresh.com/brt/
It will be under advance utilities.

should i downgrade to twrp 2.8.6 before proceeding to try the adb dirty flash upgrade?
Durso81 you are so awesome! Gonna try this tonight (PRAYING) and Setting.Out thank you!

damn I got this error message triying to flash twrp 2.8.6.0
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.351s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.399s
uh oh... is the thing totally bricked? i also tried to flash the oct 15th build of jpgapps and it didn't work got this screenshot for you! That Bacon tool is cool though!

vap3 said:
damn I got this error message triying to flash twrp 2.8.6.0
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.351s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.399s
uh oh... is the thing totally bricked? i also tried to flash the oct 15th build of jpgapps and it didn't work got this screenshot for you! That Bacon tool is cool though!
Click to expand...
Click to collapse
Looks like your firmware isn't correct, finish switching to 2.8.6 before fixing this.. As per recovery, flash the image in TWRP.. Select 'instal' and there's an option for 'IMG' select it and find the recovery image and then select the option for recovery, swipe to flash and upon success reboot the recovery.. Now update the firmware as per the ROM's OP and the ROM will flash..

Setting.Out said:
Looks like your firmware isn't correct, finish switching to 2.8.6 before fixing this.. As per recovery, flash the image in TWRP.. Select 'instal' and there's an option for 'IMG' select it and find the recovery image and then select the option for recovery, swipe to flash and upon success reboot the recovery.. Now update the firmware as per the ROM's OP and the ROM will flash..
Click to expand...
Click to collapse
I tried that and when i rebooted the TWRP is still 3.02.0 what's the next step?

vap3 said:
I tried that and when i rebooted the TWRP is still 3.02.0 what's the next step?
Click to expand...
Click to collapse
You still had 3.02 after flashing the 2.8.6 recovery.img and rebooting twrp? And fastboot flashing recovery failed?..
Try flashing this normally..
https://www.androidfilehost.com/?fid=95916177934548751

Setting.Out said:
You still had 3.02 after flashing the 2.8.6 recovery.img and rebooting twrp? And fastboot flashing recovery failed?..
Try flashing this normally..
https://www.androidfilehost.com/?fid=95916177934548751
Click to expand...
Click to collapse
exactly! Its like nothing wants to work I got the same error message trying to flash that url you gave me too
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.406s
man now I know its one of those things I can't recover no matter how much money I throw at it T_T not even about the value of the phone but the data I appreicate your help though so if you have any other ideas please let me know i'm all ears

vap3 said:
exactly! Its like nothing wants to work I got the same error message trying to flash that url you gave me too
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.406s
man now I know its one of those things I can't recover no matter how much money I throw at it T_T not even about the value of the phone but the data I appreicate your help though so if you have any other ideas please let me know i'm all ears
Click to expand...
Click to collapse
Don't fastboot flash a .zip... Flash it through recovery using twrp..
Fastboot is for recovery.IMG
Let's see if that helps..

Setting.Out said:
Don't fastboot flash a .zip... Flash it through recovery using twrp..
Fastboot is for recovery.IMG
Let's see if that helps..
Click to expand...
Click to collapse
what i would do is unzip the twrp and the default file name is recovery.img so I would unzip it to my SDK android folder that contains the adb.exe
so I tried flashing in TWRP again but this time selecting the zip file instead of the img file and I got the same error and it after rebooting it still boots into TWRP 3.0.2.0

vap3 said:
what i would do is unzip the twrp and the default file name is recovery.img so I would unzip it to my SDK android folder that contains the adb.exe
so I tried flashing in TWRP again but this time selecting the zip file instead of the img file and I got the same error and it after rebooting it still boots into TWRP 3.0.2.0
Click to expand...
Click to collapse
Are you encrypted?

Setting.Out said:
Are you encrypted?
Click to expand...
Click to collapse
like through TWRP or through android? I don't remember... if I am how do I unencrypt? But I'm wondering how I got here in the first place.

vap3 said:
like through TWRP or through android? I don't remember... if I am how do I unencrypt? But I'm wondering how I got here in the first place.
Click to expand...
Click to collapse
You'd know, it requires many steps to encrypt, so I'll guess no.. Have you ever been able to flash anything through that recovery?
I'd copy your SD to your computer and return to stock, then try again with customs from there...

Setting.Out said:
You'd know, it requires many steps to encrypt, so I'll guess no.. Have you ever been able to flash anything through that recovery?
I'd copy your SD to your computer and return to stock, then try again with customs from there...
Click to expand...
Click to collapse
nope when I try to flash the oct 15th of the rom I get simliar error messages like trying to flash the twrp 2.8.6
im wondering how am I suppose to recover certain files like my bitcoin app, google authenticator passcodes, smart audio recorder files, photos and videos as when i peek into the file structure nowhere is to be found!
can the bacon tool do all the backup for me? what's the easiest way to do this? damn im super sleepy so i'll try again tomorrow thanks for the help