Hello.
I hope I post in the good forum.
I've searched a lot, but I'm stuck, so I need your help
I've received a new chinese phone (a sample, from a partner), it's a G'Five A68, it comes with Froyo 2.2.2.
This one :
http://product.pcpop.com/000331820/Index.html
As it is a chinese phone and as it is pretty new, I've found nothing about this phone on the net.
I was able to root it pretty simply, thanks to the zergRush hack, I've removed a lot of Chinese apps thanks to Titanium Backup, I've done a dump af all '/dev/mtd/*', but now, I cannot go further without a custom recovery (among other things, I would like to change Settings.apk in order to include french translations that they have removed).
With a recovery, it will be more safe to customize this phone.
So the question is : how I can build a custom Clockwork recovery for this phone ?
Where I can get the sources ? What are the steps to follow ?
I'm pretty confortable in development and with linux command lines, so I think I'm capable to do it, but I need some clues to start.
Thanks for your help.
If you still want to do this, this might help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Awesome !
I will try this tonight.
Thanks a lot for sharing this link (and to have took time to reply to this 'old' thread).
Well ... I was able to build a custom recovery.img (if it works I will write a tuto because it was not so easy) but now I'm stuck because I cannot write this img into the mtd
Erasing the recovery partition seems to work:
# cat /dev/zero > /dev/mtd/mtd10
write: No space left on device
Click to expand...
Click to collapse
But when I try to write the img, I get this :
dd if=/sdcard/recovery.img of=/dev/mtd/mtd10
/dev/mtd/mtd10: write error: I/O error
1+0 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
Click to expand...
Click to collapse
and with flash_image, I get ECC errors
# flash_image recovery /sdcard/recovery.img
mtd: read error at 0x00000000 (Out of memory)
mtd: ECC errors (0 soft, 115 hard) at 0x00020000
mtd: ECC errors (0 soft, 208 hard) at 0x00040000
mtd: ECC errors (0 soft, 308 hard) at 0x00060000
mtd: ECC errors (0 soft, 409 hard) at 0x00080000
mtd: ECC errors (0 soft, 498 hard) at 0x000a0000
mtd: ECC errors (0 soft, 590 hard) at 0x000c0000
mtd: ECC errors (0 soft, 683 hard) at 0x000e0000
mtd: ECC errors (0 soft, 775 hard) at 0x00100000
mtd: ECC errors (0 soft, 871 hard) at 0x00120000
mtd: ECC errors (0 soft, 985 hard) at 0x00140000
mtd: ECC errors (0 soft, 1080 hard) at 0x00160000
mtd: ECC errors (0 soft, 1173 hard) at 0x00180000
mtd: ECC errors (0 soft, 1266 hard) at 0x001a0000
mtd: ECC errors (0 soft, 1358 hard) at 0x001c0000
mtd: ECC errors (0 soft, 1466 hard) at 0x001e0000
mtd: ECC errors (0 soft, 1562 hard) at 0x00200000
mtd: ECC errors (0 soft, 1654 hard) at 0x00220000
mtd: ECC errors (0 soft, 1745 hard) at 0x00240000
mtd: ECC errors (0 soft, 1852 hard) at 0x00260000
mtd: ECC errors (0 soft, 1952 hard) at 0x00280000
mtd: ECC errors (0 soft, 2055 hard) at 0x002a0000
mtd: ECC errors (0 soft, 2148 hard) at 0x002c0000
mtd: ECC errors (0 soft, 2241 hard) at 0x002e0000
mtd: ECC errors (0 soft, 2333 hard) at 0x00300000
mtd: ECC errors (0 soft, 2420 hard) at 0x00320000
mtd: ECC errors (0 soft, 2519 hard) at 0x00340000
mtd: ECC errors (0 soft, 2624 hard) at 0x00360000
mtd: ECC errors (0 soft, 2712 hard) at 0x00380000
mtd: ECC errors (0 soft, 2775 hard) at 0x003a0000
mtd: ECC errors (0 soft, 2775 hard) at 0x003c0000
mtd: ECC errors (0 soft, 2775 hard) at 0x003e0000
mtd: ECC errors (0 soft, 2775 hard) at 0x00400000
mtd: ECC errors (0 soft, 2775 hard) at 0x00420000
mtd: ECC errors (0 soft, 2775 hard) at 0x00440000
mtd: ECC errors (0 soft, 2775 hard) at 0x00460000
mtd: ECC errors (0 soft, 2775 hard) at 0x00480000
mtd: ECC errors (0 soft, 2775 hard) at 0x004a0000
Click to expand...
Click to collapse
So I don't know.
I don't thing the bootloader is locked as the mtd10 was well erased with cat /dev/zero > /dev/mtd/mtd10.
Maybe I've missed something ?
Anyway, now I'm a little afraid to restart the phone
I'm sorry, I can't help you further on this. The only way I have ever installed a recovery is via fastboot, which would require restarting your device in fastboot mode, which you say you are hesitant to restart your device (understandably).
Did you su before the flash_image command? Dunno if that's something obvious, or if it'd make a difference, just trying to think of anything that might help.
EDIT: Noticed the #, apparently you did su first.
SifJar said:
Did you su before the flash_image command?
EDIT: Noticed the #, apparently you did su first.
Click to expand...
Click to collapse
Yep
So, I'm still stuck.
I didn't find any solution and no one seems to have this issue with flash_image.
What is strange is that I can erase mtd10 (with /dev/zero) but I cannot write it back
I'm not sure that I can boot in fastboot mode with this phone.
Is there a way to be sure of this, when the phone is on ?
I think I can restart the phone, I've "only" erased the recovery, not the boot, so the phone should normally start ... I guess.
EDIT: hum, strange but it seems that my recovery as well been written anyway.
I've done a dump of mtd10, unpacked it, and I can see my build ... well, I think I've just to restart and cross my finger now ...
EDIT2: I did it !
I'm into Clockwork Recovery 2.5.1.8 ... but it doesn't work very well. I can navigate into the menu but I get a blank screen entering an item.
Anyway, it's a good start
EDIT3: the other good news is that the phone has a fast boot mode ... it can be useful
Well, it's a good start at least. All the best with getting it fully working.
Hi,
Did you get it works?
Can you make tut I want CWM for my PD10 tablet.
Thx!
masterross said:
Did you get it works?
Click to expand...
Click to collapse
Unfortunately, not
And I've bricked the phone playing too much with the /system partition, so ...
masterross said:
Can you make tut I want CWM for my PD10 tablet.
Click to expand...
Click to collapse
I'm afraid that it's not so simple.
There are a lot of requirement to achieve this kind of thing and it is better to have the device in order to test in realtime.
Good luck.
need help on how to root GFive A68
Hello. u mentioned that u rooted GFive A68 simply... but it took me about a week just to find driver for GFive A68. can u help me on how to root this android phone
reagards
I can help you
I have a A68
I can make a custom recovery for it
I don't make it I port it from zte blade
Every things work well
I try to port a rom but always I can't
Maybe we(I and you) can do it
I can upload it
If you want ...
:crying:
hamed... said:
I have a A68
I can make a custom recovery for it
I don't make it I port it from zte blade
Every things work well
Click to expand...
Click to collapse
Glad to hear that, it is a good start, congratulations.
hamed... said:
I try to port a rom but always I can't
Maybe we(I and you) can do it
I can upload it
If you want ...
Click to expand...
Click to collapse
Well, I will be very happy to help you in this adventure but I've a little tiny problem: I've bricked my A68 lol
I've played too much with the ROM without any security so ... my bad
But if you send me your recovery and a Nandroid of your phone, I will be (maybe) able to get it back to work and so, build a custom rom for it.
Can you do that ? I can send you an FTP access to upload the files if you want.
Thanks
Finaly I was able to resurect my A68 (don't ask how ...).
So now I'm really curious to know which recovery did you use ?
I've tried with the recovery for the ZTE Racer II as it uses the same chipset as the A68, but doesn't work.
Did you take a recovery and modify it yourself to include the kernel of the A68 ?
Plz Give Drivers For This Device
My uncle also own this device. Plz give the link of driver so i can root it and remove bloatware
gfive a68
Hello. u mentioned that u rooted GFive
A68 simply... but it took me about a
week just to find driver for GFive A68.
can u help me on how to root this
android phone plz upload its usb drivers if u have any senior who have this bomb help us
reagards
Related
can someone help me with it?
white screen and freeze if I turn on
log from mtty:
boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Card inserted
SDHW_EnablePowerOn
SDHW_ConfigGPIO
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
SDFATChkConf: RhOpenFile() failed NIKECONF.txt
OSSIPreLoad ++
OSSIPreLoad failed, CE is NONE
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
FMD_ReadSector+, bad block no=0xEE40, status:0x0
FMD_ReadSector+, bad block no=0xEE40, status:0x0
FMD_ReadSector+, bad block no=0xEE40, status:0x0
IPLMSG:0x2:ERROR: Failed to open storage partition.
A week ago un update went bad (stopped in the middle). My device was (not sure if after so many test it still is) cid unlocked and with hardspl (tried so many roms in one year).
Now my niki100 hangs at smart mobility screen. Tried to flash roms both from RUU (original roms stops with invalid vender id), others (including the ITA original one) stops with 262 error.
Also tried to flash from the SD card but cell hangs in "Loading..." screen.
From MTTY, output of the info commands are:
Code:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 1081 (0x439) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0xAA00
Partition[3], type=0x4, start=0xB740, total=0xFB80
CE Total Length(with sector info) = 0x5BFBA00
CE CheckSum Length(without sector info) = 0x5BA0000
and
Code:
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Nike, Bootloader Version : 1.16.0000
Built at: Oct 8 2007 18:27:27
Copyright (c) 1998-2007 High Tech Computer Corporation
Board ID=0x4
CPLD ID=0x4
gCurrentPanel=0x4
Searched a lot and read tons of posts but nothing.
Can anyone helps?
Thanks a lot!
Okay, try this:
MTTY -> use command boot -> you are stay in OS -> start SSPL -> Flash your ORIGINAL Rom ...
Goodluck
Tried that... but with the boot command, cell hangs at "smart mobility" screen...
Okay, are you sure you disabled active-sync maybe that causes the trubble.
About flashing, I flash my Niki 6 times a day (learn to cook) so I don't think that is the problem.
I had almost the same issue with an Elfin and I flashed it over and over again and after 9 or 10 times the phone accepted the rom and flashed it complety.
Not sure it was the right procedure to do (or just luck) but it worked.
Or read this http://forum.xda-developers.com/showthread.php?t=390606
Goodluck again
Hi devs,
Are you aware of any work (for other Android phones, for instance), where an altered mtd kernel driver was used to allow (raw) root access anyplace within flash memory? (For example, maybe a raw pseudo-partition which overlaps all the other partitions?) The stock mtd driver creates devices in the kernel device tree only for specific partition slices (boot, system, recovery, data, cache) - for obvious safety and security reasons.
After all these months, I stumbled across this tonight
Code:
C:\foo>fastboot oem listpartition
...
INFO[radio]:(OTHER) block start=0, size=332 (42496 KB)
INFO[hboot]:(RAW) block start=333, size=6 (768 KB)
INFO[misc3]:(RAW) block start=339, size=2 (256 KB)
INFO[mfg]:(RAW) block start=341, size=2 (256 KB)
INFO[sp1]:(RAW) block start=343, size=6 (768 KB)
INFO[misc2]:(RAW) block start=349, size=3 (384 KB)
INFO[mfg2]:(RAW) block start=352, size=3 (384 KB)
INFO[recovery]:(RAW) block start=355, size=40 (5120 KB)
INFO[boot]:(RAW) block start=395, size=20 (2560 KB)
INFO[system]:(YAFFS) block start=415, size=1360 (179520 KB)
INFO[cache]:(YAFFS) block start=1775, size=1040 (137280 KB)
INFO[userdata]:(YAFFS) block start=2815, size=1276 (168432 KB)
INFO[misc]:(RAW) block start=4091, size=5 (640 KB)
INFO[microp]:(OTHER) block start=0, size=0 (0 KB)
INFO[nv]:(OTHER) block start=0, size=0 (0 KB)
INFO[tp-melfas]:(OTHER) block start=0, size=0 (0 KB)
OKAY [ 0.071s]
finished. total time: 0.071s
I had never seen references in the Eris forums to the misc3, mfg, sp1, misc2, or mfg2 partitions - I suppose one or more are for boot images. Maybe interesting to boot a kernel image that had access to them, and have a peek at them?
bftb0
You are venturing into an area that is slightly beyond my current level of understanding. (Although we can all learn more.)
Is this even close to what you are looking for?
http://forum.xda-developers.com/showthread.php?t=754805
I'm thinking not, since they appear to be resizing the existing partitions, which doesn't seem to be quite what you are looking for.
I was asking about this a while back to see if anyone was able to get read access to the splash1 (i'm guessing sp1) partition so we could dump the REAL original splash screen for people that needed to go back to full stock. This was basically the only thing that is left out of going to stock since the "original" boot image that I had used for the android skateboards in my post about changing the boot logo was just a resized version I found online somewhere which is slightly bigger than the original if you look closely. I had some info laying around somewhere but it was definitely something about people modifying the mtd drivers in the kernel to get this done.
Without the modified drivers there is no way to do a FULL nand dump at this point.
gnarlyc said:
You are venturing into an area that is slightly beyond my current level of understanding. (Although we can all learn more.)
Is this even close to what you are looking for?
http://forum.xda-developers.com/showthread.php?t=754805
I'm thinking not, since they appear to be resizing the existing partitions, which doesn't seem to be quite what you are looking for.
Click to expand...
Click to collapse
Well, I'd seen that before - but THANK YOU - your post encouraged me to do a better job of searching, and I came up with this:
http://forum.xda-developers.com/showthread.php?t=542688
[SIZE=+2]Awesome![/SIZE] It appears that no mtd kernel hack is needed - as long the Eris kernels we are using accept those parameters (obviously, a little additional work is needed to get the offsets correct for the Eris).
I knew that partitions could be resized - but I wasn't aware that you could add new partition definitions. If it works for the Eris, then cool. (I have to say - the G1/G2/Hero devs surely have turned over a lot of stones that have helped us.)
bftb0
Mohahahhahahahaaha (rubbing hands together deviously). I smell either some interesting development or at least some interesting information coming out of this.
It's working.
More details later.
Flash Memory Map for the Eris:
Code:
PARTITION START END SIZE(1KB) SIZE(128KB) NOTES
radio 0x00000000 - 0x02980000 42,496 332 (3)
- gap! - 0x02980000 - 0x029a0000 128 1 (3)
hboot 0x029a0000 - 0x02a60000 768 6 (2)
misc3 0x02a60000 - 0x02aa0000 256 2 (5)
mfg 0x02aa0000 - 0x02ae0000 256 2 (6)
sp1 0x02ae0000 - 0x02ba0000 768 6 (4)
misc2 0x02ba0000 - 0x02c00000 384 3 (4)
mfg2 0x02c00000 - 0x02c60000 384 3 (4)
recovery 0x02c60000 - 0x03160000 5,120 40
boot 0x03160000 - 0x033e0000 2,560 20
system 0x033e0000 - 0x0dde0000 174,080 1360
cache 0x0dde0000 - 0x15fe0000 133,120 1040
userdata 0x15fe0000 - 0x1ff60000 163,328 1276
misc 0x1ff60000 - 0x20000000 640 5
( You can verify the above on your own phone with a combination of examining /proc/mtd, "dmesg" output immediately after the boot, and output of "fastboot oem listpartition" )
(1) Note all partitions are aligned to a 128-KB boundary (0x20000 - 18 bits)
Presumably this is why "fastboot oem listpartition" reports sizes in this unit
(2) Hboot images from HTC for the Eris have always been exactly 512 KB. Slack space is here,
but I found nothing but 0xFF's in the slack area.
(3) Attempting to dump the from this partition produces many, many error messages of the form:
mtd: MEMGETBADBLOCK returned -1 at 0x02940000 (errno=5)
mtd: MEMGETBADBLOCK returned -1 at 0x02960000 (errno=5)
(4) On my phone, dumps of partitions "sp1", "mfg2" and "misc2" produced un-interesting data blobs: all 0xFF's
Note that I have never flashed a custom boot splashscreen.
(5) Nearly "empty" - bytes not 0x00 or 0xFF are all string data (including CID)
(6) Contains "interesting" string data (including handset ID, manufacturing date, etc) and other binary data. Performing interesting handset operations and then recapturing a partition dump (before/after) and performing a binary diff could reveal strategic locations.
[SIZE=+1]HOW-TO[/SIZE]
Most people have absolutely no business doing this - you have been warned.
Under no circumstances should you hand-type any of these addresses; a simple typo could lead to disaster.
Code:
fastboot -c " mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata) " boot recovery-RA-Eris-v1.6.2.img
will produce the standard kernel partition mappings. Note the leading and trailing spaces in the quoted string - and that the order of appearance is critically important
You may append one or more** of the following, separated with commas as shown in the above (standard mapping) command.
[email protected](radio)
[email protected](hboot)
[email protected](misc3)
[email protected](mfg)
[email protected](sp1)
[email protected](misc2)
[email protected](mfg2)
** I performed individual boots adding only one non-standard partition, and can not guarantee that a disaster will not result if you try to append more than one - or all of them - in one boot.
You can verify the additional partitions have been kanged into the kernel's device tree with
adb shell cat /proc/mtd
and may dump individual partitions via the command "dump_image" (provided by Amon_RA in /sbin), as in the following example:
mount /sdcard
dump_image mfg /sdcard/part.mfg.img
bftb0
If you just want to dump a specific Eris flash memory partition(s) off your phone, there is an even easier method. (Doh!)
Prerequisites:
- 1.49.2000 S-OFF bootloader is installed on your Eris.
- working device drivers on PC and fastboot utility
Steps:
1) Connect via USB to your PC and put phone in FASTBOOT mode (Power up with Send+End)
2) Get the partition names listing using
Code:
fastboot oem listpartition
3) Using the following fastboot syntax, plug in the desired partition name (PNAME):
Code:
fastboot oem saveprt2sd PNAME -n PNAME.bin -a
for example, the "sp1" partition:
Code:
$ fastboot oem saveprt2sd sp1 -n sp1.bin -a
... INFOSaveImageToSD partition file name:sp1
INFOSaveImageToSD output file name:sp1.bin
INFOCmd5 CMD_TIMEOUT
INFOsdcc_poll_status(): i=21
INFOCmd5 polling status timed out
INFOSD: CMD5 fail, rc=2 ..
INFOSD 2.0
INFOHC card
INFO Searching free data sectors....
INFO [SAVE2SD] 131072 bytes saved.
INFO [SAVE2SD] 262144 bytes saved.
INFO [SAVE2SD] 393216 bytes saved.
INFO [SAVE2SD] 524288 bytes saved.
INFO [SAVE2SD] 655360 bytes saved.
INFO [SAVE2SD] 786432 bytes saved.
INFO [SAVE2SD] Done.
OKAY [ 1.728s]
finished. total time: 1.728s
Yep, it really is that simple.
bftb0
Hi All.
I have put winamp on my Aria, and now if I try to use the Bluetooth media button it asks if I want to use winamp or the defult player.
Unlike a normal dialogue for this it doesn’t have a make default option.
Does anyone know how I can make winamp my default player?
FALCON-LORD said:
it asks if I want to use winamp or the default player.
Click to expand...
Click to collapse
What do you see under the question? Is there a yes/no option?
It could be because you're launching the player through a strange concept.
Try SEARCH > name of random music file.
Should probably work.
EDIT: Meant to say context instead of concept. Damn you autocorrect.
Sent from my HTC Legend using XDA App
Thank for the replies.
Nope there is no box to allow you to set the default, and yep I have tried to just open a music file to see if it is the same dialogue, and it is.
FALCON-LORD said:
Hi All.
I have put winamp on my Aria, and now if I try to use the Bluetooth media button it asks if I want to use winamp or the defult player.
Unlike a normal dialogue for this it doesn’t have a make default option.
Does anyone know how I can make winamp my default player?
Click to expand...
Click to collapse
One solution I can think of is Tasker. It can automate the process for you. Its not free, but its worth it. They have a trial on their website. Its fully functional but is only good for a few days...enough for you test it out.
Sent from my Liberty using Tapatalk
Hi CMA, I am actually running Tasker which is the key reason I want the functionality (The symptoms are the same as with the headset button)
So for example I have this code which Pauses and attempts to un-pause the music, and it brings up the dialog
Any thoughts on how to get tasker to help?
<class cl="TaskerData" sr="">
<class cl="Task" sr="task18">
<nme>Pause & Read SMS</nme>
<id>18</id>
<class cl="Action" sr="act1">
<class cl="IntArg" sr="arg5">
</class>
<class cl="IntArg" sr="arg4">
<val>5</val>
</class>
<class cl="IntArg" sr="arg3">
<val>5</val>
</class>
<class cl="IntArg" sr="arg2">
<val>3</val>
</class>
<class cl="StringArg" sr="arg1" ve="2">
<val>com.svox.classic:eng-GBR</val>
</class>
<class cl="StringArg" sr="arg0" ve="2">
<val>%SMSRF Sent the following SMS %SMSRB</val>
</class>
<code>559</code>
</class>
<class cl="Action" sr="act0">
<code>443</code>
<class cl="IntArg" sr="arg1">
<val>1</val>
</class>
<class cl="IntArg" sr="arg0">
<val>3</val>
</class>
</class>
<class cl="Action" sr="act2">
<code>443</code>
<class cl="IntArg" sr="arg1">
<val>1</val>
</class>
<class cl="IntArg" sr="arg0">
<val>3</val>
</class>
</class>
</class>
<class cl="Profile" sr="prof17">
<nme>Bluetooth Read SMS With Pause</nme>
<id>9999</id>
<mid0>18</mid0>
<cdate>1316735989983</cdate>
<class cl="StateContext" sr="con0">
<class cl="StringArg" sr="a1" ve="2">
<val></val>
</class>
<code>3</code>
<class cl="StringArg" sr="a0" ve="2">
<val></val>
</class>
</class>
<class cl="EventContext" sr="con1">
<class cl="StringArg" sr="arg3" ve="2">
<val></val>
</class>
<class cl="StringArg" sr="arg2" ve="2">
<val></val>
</class>
<code>7</code>
<class cl="IntArg" sr="arg1">
</class>
</class>
</class>
<tv>1.1u2m</tv>
</class>
Click to expand...
Click to collapse
So...
I take it no one is using winamp and a BT Headset then?
FALCON-LORD said:
So...
I take it no one is using winamp and a BT Headset then?
Click to expand...
Click to collapse
Are you on a stock or custom ROM?
I use a different media player (not stock) on CM7 with BT all the time. I just delete the stock "music.apk" file from the "system/app" folder and then install one of my own choice.
Hey Charley
I am using the Stock International ROM (Not the AT&T One) So rooting and removing the package is your recommendation?
FALCON-LORD said:
Hey Charley
I am using the Stock International ROM (Not the AT&T One) So rooting and removing the package is your recommendation?
Click to expand...
Click to collapse
Well, rooting does open up a lot of flexibility and possibilities, not to mention getting rid of the ATT bloatware....
cHarley04 said:
Well, rooting does open up a lot of flexibility and possibilities, not to mention getting rid of the ATT bloatware....
Click to expand...
Click to collapse
As I said, I don't have the Bloated AT&T Build. It seems I am now going to be going back to the question of how to get root, without dropping a whole new ROM on the device, so that i can just clean it up as by my requirements.
Interestingly... This is where my questions started on these forums.
FALCON-LORD said:
As I said, I don't have the Bloated AT&T Build. It seems I am now going to be going back to the question of how to get root, without dropping a whole new ROM on the device, so that i can just clean it up as by my requirements.
Interestingly... This is where my questions started on these forums.
Click to expand...
Click to collapse
Which HBOOT do you have right now?
drumist said:
Which HBOOT do you have right now?
Click to expand...
Click to collapse
Still have 1.02.000
Haven't done anything since purchase.
FALCON-LORD said:
Still have 1.02.000
Haven't done anything since purchase.
Click to expand...
Click to collapse
If you want to get root without modifying your ROM at all (i.e. you like sticking with what you've got now), then you need to do these steps:
1) Use Revolutionary tool to S-OFF the device.
2) Normally, Revolutionary will attempt to install Clockworkmod Recovery to your device. If it fails for any reason (it happens sometimes), then you can manually install it by following the steps in this thread (just the first 6 steps).
3) Once you have Clockworkmod Recovery installed, I recommend taking a Nandroid backup of your current ROM. This creates a backup of your current ROM so that you can undo any changes later.
4) Root the ROM by following the steps under "To root" in the same thread I linked to in step 2.
The idea of Rooting the phone is good...
Well right up until it returns the following and my research indicates that there is no solution.
Oh well, Looks like I'll have to wait till the next revolution release
Root acquired!
Sending in Caroline...
Retrieving Caroline from certain doom...
Retrying Caroline...
Caroline failed, but had this to say: An error occurred while reading the partit
ion.
Errors (if any):-
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
Press (almost) any key to exit.
Click to expand...
Click to collapse
PS... Who is Caroline?
I don't know what is causing that error. I'd recommend going to the Revolutionary IRC channel and asking them directly:
http://webchat.freenode.net/?channels=revolutionary
FALCON-LORD said:
So...
I take it no one is using winamp and a BT Headset then?
Click to expand...
Click to collapse
I have now had this problem since the Winamp update to 1.2.1.
Every time I update the app the BT control is set back to the default android player.
http://download.nullsoft.com/winamp/android/Winamp-1.1.1.apk
On the new Winamp you just need to have the app open and then the BT controls will work. But I would rather stick with the old version where it was working properly.
Hello!
I think this post may be of more relevance to Development. But unfortunately, I do not have enough posts to do so. I usually don't have to post at all, thanks to searching.
This time I can't seem to find an answer to my problem, so here it goes;
I have an Eris that I'm using at the moment. I rooted it(or so I thought) back in the day. It seemed to work fine back then, and everything was dandy.
Never went about installing a custom ROM though, so I attempted. After I started it up, I realized I had made the worst mistake of them all. I didn't make a nandroid backup of the stock ROM. After a couple boot loops of the Cyanogen logo, I powered it into the bootloader to find that "S-ON" was showing. I cried a little at that moment.
If I try to install any other ROM(stock, EvilEris, etc.), it does not work. And after a couple of attempts of trying to install CM again, now only getting to the skateboarding androids, I have no idea what to do.
Does anyone possibly have a solution to this? I'm at a complete loss not being able to actually boot the phone into the ROM.
Also, everytime I try to just throw a PB00IMG.ZIP on the root of the SD card, it says there's "No image!"
Thank you for any help,
-Kickore
kickore said:
Hello!
I think this post may be of more relevance to Development. But unfortunately, I do not have enough posts to do so. I usually don't have to post at all, thanks to searching.
This time I can't seem to find an answer to my problem, so here it goes;
I have an Eris that I'm using at the moment. I rooted it(or so I thought) back in the day. It seemed to work fine back then, and everything was dandy.
Never went about installing a custom ROM though, so I attempted. After I started it up, I realized I had made the worst mistake of them all. I didn't make a nandroid backup of the stock ROM. After a couple boot loops of the Cyanogen logo, I powered it into the bootloader to find that "S-ON" was showing. I cried a little at that moment.
If I try to install any other ROM(stock, EvilEris, etc.), it does not work. And after a couple of attempts of trying to install CM again, now only getting to the skateboarding androids, I have no idea what to do.
Does anyone possibly have a solution to this? I'm at a complete loss not being able to actually boot the phone into the ROM.
Also, everytime I try to just throw a PB00IMG.ZIP on the root of the SD card, it says there's "No image!"
Thank you for any help,
-Kickore
Click to expand...
Click to collapse
Before you try the PB00IMG.zip, are you going into the Wipe menu and choosing the option "Wipe data/factory reset" before restarting the phone? If not, try starting in Recovery, do just that, and then try to restart. (Depending on the CM ROM you are installing, you may need to install a Google apps zip as well, if you have not already done so. However, it will boot without Google apps - you just will not have the market.)
This is what happens when I go to wipe/factory reset the phone.
I'm sorry I wasn't a bit more descriptive in my first post.
I have clockwork mod recovery 2.5.0.1.
...With S-On...
This picture shows why I can't love anything.
Since you have clockwork recovery, definitely do not try a PB00IMG.zip. There have been bricked phones from this.
See this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9
This may be a good idea. That line "Can't read MISC" - I wonder if you have some bad blocks on that partition (or others)? Anyway, read through that post I listed above, flash that zip file, and it will create a file on the SD card called "MTD_Inspect.txt". Let's see what that shows.
(I think that once we determine the state of flash storage, the best bet may be to flash the Flashback_21v2, which will return the phone to stock, unrooted, and then you can re-root using ScaryAlien's modified version of JCase's 1-click root app to get Amon_RA recovery on the phone. Getting S-OFF going forward may not be such a bad idea, but one step at a time.)
Listen to doogald, he's giving you some good advice!
doogald said:
Since you have clockwork recovery, definitely do not try a PB00IMG.zip. There have been bricked phones from this.
See this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9
This may be a good idea. That line "Can't read MISC" - I wonder if you have some bad blocks on that partition (or others)? Anyway, read through that post I listed above, flash that zip file, and it will create a file on the SD card called "MTD_Inspect.txt". Let's see what that shows.
(I think that once we determine the state of flash storage, the best bet may be to flash the Flashback_21v2, which will return the phone to stock, unrooted, and then you can re-root using ScaryAlien's modified version of JCase's 1-click root app to get Amon_RA recovery on the phone. Getting S-OFF going forward may not be such a bad idea, but one step at a time.)
Click to expand...
Click to collapse
Sorry it took a minute.
Here's what the MTD inspect gave me.
Code:
Eris MTD Partition Status Report Generated on Fri May 18 22:11:36 UTC 2012
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 20 20 0 0 0
system /dev/mtd/mtd3 178257920 1350 1360 0 0 0
cache /dev/mtd/mtd4 136314880 9 1040 18 0 0
userdata /dev/mtd/mtd5 167247872 1 1276 0 0 0
#################################### misc PARTITION ###################################
Partition Symbolic Name: misc
Partition (character-special) Device: /dev/mtd/mtd0
Partition Total Size: 655360
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
#################################### recovery PARTITION ###################################
Partition Symbolic Name: recovery
Partition (character-special) Device: /dev/mtd/mtd1
Partition Total Size: 5242880
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
#################################### boot PARTITION ###################################
Partition Symbolic Name: boot
Partition (character-special) Device: /dev/mtd/mtd2
Partition Total Size: 2621440
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 20
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### system PARTITION ###################################
Partition Symbolic Name: system
Partition (character-special) Device: /dev/mtd/mtd3
Partition Total Size: 178257920
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1350
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### cache PARTITION ###################################
Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 18
ECC corrected: 0
Number of bad blocks: 9
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### userdata PARTITION ###################################
Partition Symbolic Name: userdata
Partition (character-special) Device: /dev/mtd/mtd5
Partition Total Size: 167247872
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
Apparently, I have a few.
Ok, the next step is probably to try what is in this post: http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
That post mentions that you should download a decent ROM, but I think that you are already there.
Just a quick note: you should also read the warning in bright red here: http://forum.xda-developers.com/showpost.php?p=11652502&postcount=40
Never mind, I'll quote it:
ErisMTDNuke_v0.9.zip IS EXTREMELY DANGEROUS AND SHOULD NOT BE USED WILLY-NILLY. IT'S ONLY USE IS FOR DESPERATE, LAST-RESORT MEASURES - CLOCKWORK "SOFT BRICKINGS" WHERE PARTITION CORRUPTION IS EVIDENT.
Click to expand...
Click to collapse
At this point, please understand that your phone is bricked and it may not come back. Let's see what the ErisMTDNuke does, though.
I mentioned earlier the thought of unrooting by flashing Flashback and then re-rooting with JCase's 1-click app. That's still a possibility, too. That will at least replace the Clockwork Recovery with stock Recovery. However, the other way is to flash the CM7 ROM that you were going to flash anyway and replace the recovery using the app GScript Lite.
Flashback can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=792026
You can download the one without the radio, if that's what you want to do.
Anyway, let's see what ErisMTDNuke does. Good luck.
Dear doogald,
You are the coolest person on the internet. You have saved my phone by referencing forum posts made years ago that I totally couldn't figure out by myself.
Thank you very much.
I'm happy to announce that my phone has completed it's boot into stock, and I can now drag down my lock screen and activate my phone on the Verizon network.
I'll take to Jcase's one-click app tomorrow.
Thank you again,
-Kickore
P.s. Seriously, the coolest person on the internet ever.
Wow, that's awesome. Thanks redirected to bftb0, who did all of that work.
The way to install Amon_RA is here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
You should be able to use Scenario 5 in the first post (the JCase 1-click app method) that ScaryAlien mentions that it works with stock or stock-based ROMs like xtrSENSE. Just remember that 1-click works like this:
- allow third party app installs in settings->applications
- install the app (you may need the free app Astro File Manager to actually install by opening the .apk file in that app and choosing to install the app)
- run the 1-click app
- shut down and restart the phone - don't restart in recovery; restart as if you were going to make a phone call
- shut down and restart in Recovery by holding VolUp while booting
At some point I'll also post what you'd need to do to get the S-OFF engineering bootloader on, which will allow you to fastboot flash to recover any future problems (which, knock wood, will not happen...)
I attempted Jcase's app. It did give me Amon_RA's Recovery. It did not give me S-Off though, which I'm assuming is why you mentioned the engineering bootloader in your last post.
On a side note, I decided to experiment with something that wasn't clockwork mod, and found that I can flash custom ROMs with this Recovery. I also backed up my stock one this time, JUST IN CASE!
Well, it worked and I'm running GSB v4.5!
Still, I really appreciate it regardless of who originally found/wrote the documentation on how to do it. I'm a user with like 5 posts due to everything being figured out usually, and you're still helping instead of "GOOGLE IT."
So thank you.
kickore said:
I attempted Jcase's app. It did give me Amon_RA's Recovery. It did not give me S-Off though, which I'm assuming is why you mentioned the engineering bootloader in your last post.
Click to expand...
Click to collapse
Which version of the bootloader do you have? It will either be 1.46.0000, 1.47.0000, or 1.49.0000. (The method to get the 1.49.2000 S-OFF depends on which you have now, IIRC.)
I currently have the 1.47.0000.
kickore said:
I currently have the 1.47.0000.
Click to expand...
Click to collapse
Ok. I am away for the weekend, but will try to get some detailed instructions ASAP. The generalized instructions, though (and it's quite a few steps, sorry to say):
- get a copy of the root PB00IMG.zip file onto the SD card
- get a copy of Flashback (with radio) onto the SD card
- get a copy of ScaryAlien's version of JCase's 1-click root app on the SD card (which I belive you have)
- Nandroid backup when you have now
- start in HBOOT and let the phone run the root PB00IMG.zip (it should detect and ask you to flash it automatically). This gives you 1.49.2000 S-OFF with an old version of the Eris ROM
- * Run the JCase root app (this gets you Amon_RA Recovery back)
- Flash Flashback with radio (this gets you the updated radio back - the root PB00IMG.zip file will flash an older version of the radio)
- Run the JCase root app again to root the phone
- Restart in Recovery and Nandroid Restore GSB
- restart and you'll be back where you were with S-OFF
- (Important) Erase the PB00IMG.zip file from the SD card (or rename it or move it into a folder).
(I may have missed a step - this is off the top of my head. Also, the step with * may be wrong - I think that the root ROM is Android 1.5 and JCase's root app may not run. I don't recall - I'll need to check on that one...)
There is no need! I figured it out from what you said. I'm not really that new at this whole rooting process... But I'm not a programmer and would not have been able to do anything otherwise. I really do appreciate your help.
Thank you so very much!
-Kickore
Edit:
As a suggestion, perhaps making a new guide for anyone who comes to this forum can easily get the files which are now dead links. As well as follow a comprehensive guide on the rooting process.