Hello everyone.... i really think i bricked my device and i would love for someone to help me... i Have been searching the forum since yesterday morning and i cant seem to find anything that works... well first off i am rooted (s-off) i used the gfree method because setting up adb wasnt going to well for some reason... but im stuck in bootloop mode or whatever and when i hold down power and the vol down button it recognizes the pd15dimg.zip file but when i do the update i get an error check out the first pic below... then when i put it in recovery mode i get another error check out 2nd pic... then when i to to load the pd15dimg.zip manually from the choose zip file directly from the root of the sd card i get another error check out third pic... as u can see im on cwm 3.0.2.4 and the rom i was originally using i dont remember the name but it was gingerbread...can someone plz help?? any help will be appreciated. thnx
I had this same issue 3 weeks ago. But I wasnt getting those partition errors with the PD15dimg.zip. I would first suggest downloading another one to make sure the one you got wasnt corrupted. But before I figured out to do the pd15dimg trick, the nice fellas over on Cyanogenmods Shoutbox were helping me out with a different method. You have the engineering bootloader, which is great news for you. I did not. Do you have a nandroid backup on your SD that you can copy over to your computer?
i didnt do a nandroid back up but i did a back up threw the rom manager i had... is that useful?
curlz187 said:
i didnt do a nandroid back up but i did a back up threw the rom manager i had... is that useful?
Click to expand...
Click to collapse
Hmm. Maybe, I'm not sure what that backs up, do you know what folder that went into? Find it and post whats in there
the folder is on the root of my sd card... its call clockworkmod... i click that then i see two folders one of which is named back ups. i click that and it has tsome some files in it such as android_secure.img boot.img cache.img data.img nandroid.md5 recovery.img and system.img
curlz187 said:
the folder is on the root of my sd card... its call clockworkmod... i click that then i see two folders one of which is named back ups. i click that and it has tsome some files in it such as android_secure.img boot.img cache.img data.img nandroid.md5 recovery.img and system.img
Click to expand...
Click to collapse
Perfect! Alright, PM now and I'll help you with the rest alright?
Ok just did it
does anyone else have any insight on this subject?
Once you get fail-pu you can't do anything as you need to send it back they have to replace the motherboard. Fail PU means failed partition update at this point once its corrupted you can't reformat it since we are using SLC-EUDA low level format which is 1 time.
TmpUsr said:
Once you get fail-pu you can't do anything as you need to send it back they have to replace the motherboard. Fail PU means failed partition update at this point once its corrupted you can't reformat it since we are using SLC-EUDA low level format which is 1 time.
Click to expand...
Click to collapse
the original file i used was corruted JDV28 sent me another file and it starts the update but idk how long its suppose to take because its been updating for bout 15 mins now
Well PD15IMG.zip can be corrupted and even if you get a good radio/rom image and verify it the problem you will run in to is when you try to write to the partition. Fail PU means failed partition update where you can't write radio, recovery and system. I was leaning on to gfree but I need another phone to fully hack it as I was massing with the emmc block last time but atm I don't have any other phones. Best solution is soon as you see the errors on recovery you should push and manually flash recovery partition and replace it.
TmpUsr said:
Well PD15IMG.zip can be corrupted and even if you get a good radio/rom image and verify it the problem you will run in to is when you try to write to the partition. Fail PU means failed partition update where you can't write radio, recovery and system. I was leaning on to gfree but I need another phone to fully hack it as I was massing with the emmc block last time but atm I don't have any other phones. Best solution is soon as you see the errors on recovery you should push and manually flash recovery partition and replace it.
Click to expand...
Click to collapse
how do i do that?
Terminal said:
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
flash_image recovery /sdcard/recovery.img [hit enter]
Click to expand...
Click to collapse
adb said:
adb devices [hit enter]
adb push boot.img /data/local/boot.img [hit enter]
adb shell [hit enter]
su [hit enter]
flash_image boot /data/local/boot.img [hit enter]
rm rm /data/local/boot.img [hit enter]
Click to expand...
Click to collapse
Like I said depends on how deep the issue is you can't revert it. But try it anyways. You will need image which you can get from dev section.
im not connected threw adb had problems setting it up b4... but after i did the update now my screen only turns black? idk what happened it was updating i leave for a min now it seems unusable
I had the same issue, couldn't recover it so I sent it back.
Sent from my HTC Glacier using XDA Premium App
partitioning issues most likely = game over unless your running the engineering boot. thats the bottom line i think with everyone thats running into these issues..
Related
i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.
Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581
so phone will be stock again right? have to re dload apps and sync contacts and **** again right?
hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.
volume up + end button = Recovery
ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?
yes its suppose to be on the root of the sdcard too
still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...
can u link me to the tut u are using?
http://forum.xda-developers.com/showthread.php?t=647707
QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??
Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.
Ok I got A Problem. Went to flash a new rom after backing my current one up with rom manager everything went fine till I went to flash it and now it says
E: Failure at line 7 symlink dumpstate SYSTEM:bin/dumpcrash
I dont have a working phone. Tried several different roms and nothing.
what do I need to do??
can u boot in to recovery mode " vol up + power button " ? and dont use Clockworkmod recovery as its known to have issues with the eris.
use the other recovery.
Thanks T.A.
Yes I can Boot into recovery thats it.
How do I go about Flashing a New Recovery Manager
Topaz is right.... Amon_RA FTW !
How do I install that now though. I have been searching through forums looking cant find a step by step
Forgot to say I was a Leaker before they found the method.
would this work
http://forum.xda-developers.com/showthread.php?t=725096&highlight=Flash+Amon's+recovery
metzy75 said:
How do I install that now though. I have been searching through forums looking cant find a step by step
Forgot to say I was a Leaker before they found the method.
would this work
http://forum.xda-developers.com/showthread.php?t=725096&highlight=Flash+Amon's+recovery
Click to expand...
Click to collapse
might work, I imagine you could also try this....
http://forum.xda-developers.com/showthread.php?t=725047
this gives you the S-OFF bootloader and Amon_RA for recovery
you might wait to see if others weight in on the best approach here.
Already turned S-OFF the only reason I have clock work is because my noobie ass used rom manager for convience
metzy75 said:
Already turned S-OFF the only reason I have clock work is because my noobie ass used rom manager for convience
Click to expand...
Click to collapse
"noobie ass" is funny.
jcase's approach in your link is probably all you need then
Phones about to get thrown at the wall. Nothing is working, do the adb push moves file fine then couple commands down it says not there
metzy75 said:
Phones about to get thrown at the wall. Nothing is working, do the adb push moves file fine then couple commands down it says not there
Click to expand...
Click to collapse
if you do
adb devices
does its show a device HTCxxxxxxxxxx (some alphanumeric)?
Do this
Code:
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
try this in fastboot ( SEND + POWER )
not sure u can push files into /data/local/
hopefully it will work and if not and all fails.
put a rom on sd card and boot into recovery and hopefully clockworkmod recovery will flash it.
Yep, really have no idea what to do. I run the commands in what you gave me and the stupid thing says file its there when i use root command to navigate there its right there. idk whats going on.
TopazAaron said:
Do this
Code:
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
try this in fastboot ( SEND + POWER )
not sure u can push files into /data/local/
hopefully it will work and if not and all fails.
put a rom on sd card and boot into recovery and hopefully clockworkmod recovery will flash it.
Click to expand...
Click to collapse
doesn't show its connected, I have fastboot USB showing on the eris
tried flashing many roms no good same error
http://forum.xda-developers.com/showthread.php?t=651669
May help in that it includes the Amon_RA file and offers a different approach...
good luck
have you ever heard of the jitterbug?
Sjflowerhorn said:
have you ever heard of the jitterbug?
Click to expand...
Click to collapse
Idk what a jitter bug has to do with this. But I got the recovery changed but nothing still flashes.
Got to line 8 instead of line 7
says cant chown/mod /system/bin
(no such file or directory
E: failure at line 8
set_perm_recursive 0 2000 07550
Sjflowerhorn said:
have you ever heard of the jitterbug?
Click to expand...
Click to collapse
holy crap... i almost fell outta my chair!!!! LOL (i used to tell this lady at work all the time.... you NEED a jitterbug!!!).
------------------------------------------------------------------------------------------------------------
in any case...
metzy75... you said you backed up (a NAND backup i'm assuming)... are you able to restore your backup? or same failure? different message?
metzy75 said:
Idk what a jitter bug has to do with this. But I got the recovery changed but nothing still flashes.
Got to line 8 instead of line 7
says cant chown/mod /system/bin
(no such file or directory
E: failure at line 8
set_perm_recursive 0 2000 07550
Click to expand...
Click to collapse
what ROM are you trying to flash?
zach.xtr said:
what ROM are you trying to flash?
Click to expand...
Click to collapse
Just Official eris one that came with that all in one zip. and plain jane as wwell
Plain Jane fails at line 7 and offical eris line 8
tenzomonk said:
holy crap... i almost fell outta my chair!!!! LOL (i used to tell this lady at work all the time.... you NEED a jitterbug!!!).
------------------------------------------------------------------------------------------------------------
in any case...
metzy75... you said you backed up (a NAND backup i'm assuming)... are you able to restore your backup? or same failure? different message?
Click to expand...
Click to collapse
Backups all failed.
Hi everyone,
A few days ago I got the OTA 2.2.1 on my MT3G and then rooted it using the SuperOneClick tool. I was able to remove all useless apps, pushed others to /system/app with Root Explorer, etc., there is only one to do, and I am clueless: how to replace the stock Android System Recovery <3e> with a custom recovery image, so I can do Nandroid backups, flash .zip files, etc?
I used the ROM Manager app to flash Clockwork, got an "Installation successful" confirmation, but then on reboot into recovery mode my phone got stuck on the MT3G logo. I had to remove the battery, then in second attempt the phone booted into the <3e> image. Restarted again, opened the ROM Manager, according to it Clockwork was installed. Total craziness! Then I tried to flash it using Better Terminal Emulator (su, flash_image recovery /sdcard/Clockwork.img) but I got a "flash_image: not found" message, though I had the image on my sd card.
Any good ideas, folks?
All useful suggestions much appreciated, thanks!
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
It's kinda relative to the topic. I'm stuck on clockworkmod and would like to get back to stock recovery as the new HBOOT doesn't let me flash roms. Is there any way I can do so?
Look in my guide... all the files, steps and binaries are included...
Check out my signature!
Thanks, Asadullah. One more question: Are there different versions of flash_image for different android versions, because I saw in another forum a user complaining he/she didn't use the right binary.
Edit: I've extracted a flash_image binary from CM 6, hope it will work
Edit2: It worked, thanks a lot, man!
I think that flash_image from different devices is different someone correct me if I'm wrong. Glad it worked
Sent from my HERO200 using XDA App
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
lgtsanev said:
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
Click to expand...
Click to collapse
I know it's been a while and you didn't get a reply, and while I found this thread because I too am having enormous trouble rooting this whatever it is cheap chinese android 2.2.1 momo 2 thing covered completely in chinese language apps that I simply cannot use even for the low price it cost me - I thought I'd offer an answer, most likely wrong, but one that may help the next person who may fall into your position.
adb root is an option to start the adb service in root mode, and I can only assume that means for the device.
As I have not been able to get this thing sorted, not knowing what it is really - no phone, no camera, no buttons on the case apart from power/sleep - Home/Esc which do nothing on booting apart from alert the PC to detect a new USB device, no market access, but otherwise exactly what I required - I dont know if it'll help.
But I hate threads left in a question, because I always find them. And this circle of frustration seriously should not be real, it just cannot be this damn hard to do something...
yikes!
help please
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
sky rider said:
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
Click to expand...
Click to collapse
root your phone
install terminal emulator on your phone
type in everything that you quoted except for adb shell
Confused in differences
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Jkhim said:
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Click to expand...
Click to collapse
Honestly it's been so long I forgot ?? I don't think you need too use flash image anymore
rm failed????
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sh: ./flash_image: not found how to fix this sir? im so new about this, sorry about that
---------- Post added at 05:22 AM ---------- Previous post was at 04:43 AM ----------
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sir is this CM.12 cyanogenmod fakelollipop is an example of flash_image even its in a zip file? because i cant get it at all, im stuck at flash_image not found
Hi expert,
Has anyone successfully JB PS3 using the following link?
http://psfreedom.com/wiki/HTC_Droid_Eris
I cannot get it to work, just curious if anyone successfully done it would like to share how you accomplish this. There are 2 steps that I have question on, they are:
Fastboot should say < waiting for device >, I don't get this message, I only received boot image loaded OK
insmod /sdcard/psfreedom.ko returns error message "cannot insert psfreedom.ko file exists"
I've been reading the last 3 days and still unable to get this loaded, is there a more up to date instruction for eris? TIA.
psfreedom.ko
Did you copy psfreedom.ko file to your sdcard
sangweb said:
Hi expert,
Has anyone successfully JB PS3 using the following link?
http://psfreedom.com/wiki/HTC_Droid_Eris
I cannot get it to work, just curious if anyone successfully done it would like to share how you accomplish this. There are 2 steps that I have question on, they are:
Fastboot should say < waiting for device >, I don't get this message, I only received boot image loaded OK
insmod /sdcard/psfreedom.ko returns error message "cannot insert psfreedom.ko file exists"
I've been reading the last 3 days and still unable to get this loaded, is there a more up to date instruction for eris? TIA.
Click to expand...
Click to collapse
do you have fastboot on? make sure you have the right root
wonder if having clockwork or RA recovery makes a difference...
Why not just use psfSM from www.klutsh.com
Works on my Eris.
Sent from my Droid Eris using XDA App
Retrogress said:
do you have fastboot on? make sure you have the right root
wonder if having clockwork or RA recovery makes a difference...
Click to expand...
Click to collapse
Yes, I have the psfreedom.ko on my root of sd card and I think I do have fastboot on because the command fastboot devices return my phone id.
Chevelle1768 said:
Why not just use psfSM from www.klutsh.com
Works on my Eris.
Sent from my Droid Eris using XDA App
Click to expand...
Click to collapse
I went to the site but not sure what am I suppose to look for, I've downloaded the img file for eris, what am I suppose to do with it? TIA.
For what it's worth, very soon you won't be needing any device to jailbreak the PS3, the master key was discovered and most if not all future developments will be signed code making the jailbreak method obsolete.
There's already a working 3.55 custom firmware, though many homebrews still need to update to use it.
Its a recovery img just like Clockwork and Amon_Ra's. Its actually based off of Clockwork. So just flash it to your recovery.
Chevelle1768 said:
Its a recovery img just like Clockwork and Amon_Ra's. Its actually based off of Clockwork. So just flash it to your recovery.
Click to expand...
Click to collapse
To verify, I have to run the following commands except replace the recover-ra with the image I've just downloaded:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
Am I right? Thx.
sangweb said:
To verify, I have to run the following commands except replace the recover-ra with the image I've just downloaded:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
Am I right? Thx.
Click to expand...
Click to collapse
Just these
adb push recovery-ra-eris.img /sdcard
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
Click to expand...
Click to collapse
Thanks Chev, looks like I can see it on the recovery menu. I'll test it out once I get home. The only thing I see is I get the following error when I flash the image:
mtd: read error at 0x00000000 (Out of memory)
Are you running Vista or Windows7? If so, run the command prompt with Admin rights.
Otherwise do this:
adb push recovery-ra-eris.img /sdcard
adb shell
cd sdcard
flash_image recovery /sdcard/recovery-ra-eris.img
Click to expand...
Click to collapse
Chevelle1768 said:
Are you running Vista or Windows7? If so, run the command prompt with Admin rights.
Otherwise do this:
Click to expand...
Click to collapse
No, I ran it on XP but I can see the PS3 jailbreak option now, there are 3 JB option right? PL3, PSFreedom, or Hermes, so I can just select any to boot my ps3 in JB mode, do you know if these payloads has spoof on them?
sangweb said:
No, I ran it on XP but I can see the PS3 jailbreak option now, there are 3 JB option right? PL3, PSFreedom, or Hermes, so I can just select any to boot my ps3 in JB mode, do you know if these payloads has spoof on them?
Click to expand...
Click to collapse
I don't believe any of them do. But you can download the other PL3 payloads from the same site also. Then just extract them to you sdcard.
Hi Chev, thanks for all your help, I think I got enough information to go home and mess around with my ps3, I hope it'll work.
Marisa said:
For what it's worth, very soon you won't be needing any device to jailbreak the PS3, the master key was discovered and most if not all future developments will be signed code making the jailbreak method obsolete.
There's already a working 3.55 custom firmware, though many homebrews still need to update to use it.
Click to expand...
Click to collapse
anywhere we can read up on this?
FYI, I was able to run the JB last night and it works great, test out some games and got GT5 working so far but it does take a long time to load my GT5 to the HD. I am happy now that I don't have to switch games out for my kids any more .
Retrogress said:
anywhere we can read up on this?
Click to expand...
Click to collapse
The place is psx-scene, psxnews, psgroove, or best is google it, many useful sites out there. Good Luck.
My internal SD partition won't let me add or delete any contents on it. Anyone have a solution?
Could you please type "mount" in the terminal and copy it here?
It should be RW, you can try typing in the terminal: mount -o remount,rw /sdcard
Never mind. Got it working by rebooting to recovery, going through ADB, and chmod 777.
blackknightavalon said:
Never mind. Got it working by rebooting to recovery, going through ADB, and chmod 777.
Click to expand...
Click to collapse
Yes, I saw last nigh I was able to see your mount dump. You moved your /data and /sdcard partitions to f2fs. I have been trying to reproduce your issue and I have found the origin of it. It seems that you performed the backup of your internal sdcard using adb when switching to f2fs. In such case you indeed need chmod -R 777 /sdcard
I will update the guide accordingly.
Thanks for bringing this issue up.
Oki said:
Yes, I saw you had moved your /data and /sdcard partitions to f2fs. I have been trying to reproduce your issue and I have found the origin of it. It seems that you performed the backup of your internal sdcard using adb. In such case you indeed need chmod -R 777 /sdcard
I will update the guide accordingly.
Thanks for bringing this issue up.
Click to expand...
Click to collapse
It's not that I'm afraid of bricking a phone, it's that I want to keep it usable. That's probably why I won't ever buy another HTC phone until they get rid of CID and MID. And I was one of the guys who cracked the location of the ringtones/notifications on the original Galaxy Gear when it went to Tizen.
Anyway, I let it sit for 12 hours and, sure enough, the chmod fix stuck.
blackknightavalon said:
It's not that I'm afraid of bricking a phone, it's that I want to keep it usable. That's probably why I won't ever buy another HTC phone until they get rid of CID and MID. And I was one of the guys who cracked the location of the ringtones/notifications on the original Galaxy Gear when it went to Tizen.
Anyway, I let it sit for 12 hours and, sure enough, the chmod fix stuck.
Click to expand...
Click to collapse
Your sdcard dump was very useful. At least I was able to see it before you deleted it. It led me to the origin of this issue. We are lucky with the 2017U, it doesn't have the DFU mode of the 2017G. Ours at least is unbrickable due to the EDL mode. When doing testing or trying new things, a safe backup is all you need.