Related
[Tutorial] Root FRF91/FRF85B/FRF83/FRF72 (T-Mo/AT&T) Without Unlocking (100% Working)
Credits:
Booker-T
M9x3mos
th3fallen
juan413
_Sri_
Amon_RA
cyanogen
For your amazing works leading up to this guide
Notes:
- Donate if I've helped save your HTC warranty.
- This will work! If you can't figure something out, don't get discouraged. Ask here for help.
- After this process, you can flash whatever ROM you like in recovery. I just have the steps showing for CyanMod so you know you have a good, clean system to start off with.
[T-Mo & ATT] Prerequisites:
- Locked Nexus One flashed with FRF85B
(Stuck on FRF91? Use THIS to downgrade to EPE76. Then update back up to FRF85B.)
- Lastet SDK (Click)
- Working ADB (Info)
- The attached .zip "ROOT_FRF83.zip" (Attachment at bottom)
- Got Mac/Linux? (Click Thanks madj42)
Process:
1) Extract the files within "ROOT_FRF83.zip" into the "tools" directory of the extracted SDK package
2) Open a command prompt or terminal and change to the "tools" directory of the extracted SDK package
- Example: Type "cd C:\Users\Matt\Desktop\android-sdk-windows\tools" and hit Enter
3) Type "loop" and hit Enter
4) With phone attached through microUSB, enter Recovery with the battery cover OFF and the SDcard REMOVED.
- Tip: Be careful not to let the battery fall out during this process
- Tip: To enter recovery, boot while holding Volume down button. Then select the recovery option.
5) When you see the HTC devices attached in recovery mode, hit Ctrl+C, then "y", then Enter
6) Slide in SDcard (Make sure there is no update.zip on it at this point)
- Tip: It should slide in and click VERY easily if you trim the tab on the battery properly. A sharp razor blaze works well.
- Tip: I recommend this instead of other methods (paper slip) because it will work without error
- Tip: You only need to cut as far as the SDcard slot goes, you do not need to trim the entire tab
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) On your phone, press Power + Volume Up AFTER inserting SDcard
8) Choose "apply sdcard:update.zip"
- Tip: It will fail, but that is expected because there is no update.zip
- Tip: This is done to mount the SDcard after achieving adb while the SDcard was out
9) In your terminal type "adb push flash_image /sdcard/flash_image" and hit Enter
10) In your terminal type "adb push ota.zip /sdcard/update.zip" and hit Enter
11) In your terminal, type "adb push update.zip /sdcard/update.zip" and DO NOT yet hit Enter
12)Ready your finger near the Enter key of your keyboard so that you can quickly hit it once you complete the next step
13) Choose "apply sdcard:update.zip"
14) As soon as you see the yellow installation progress bar, hit Enter on your keyboard
- Tip: If completed properly, you should see a message about rooting adb
15) Choose "Reboot into system"
You now have root access(aka Admin rights) in your stock ROM, but with limited capabilities.
If you want to do any of the following, please continue:
- Flash a custom recovery
- Perform Nandroid backup
- Flash a Rooted Stock Froyo ROM with full capabilities
- Flash CyanogenMod
16) Download the following to the root of your SDcard
- recovery-RA-nexus-v1.7.0.1.img: http://rapidshare.com/files/393267368/recovery-RA-nexus-v1.7.0.1.img
- Note: UnMount your SDcard after copying these files, but keep your phone plugged in
17) In your terminal type "adb shell" and hit Enter
18) In your terminal type "su" and hit Enter
- Tip: At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- Tip: $ should now be replaced with #
19) In your terminal, type "mount -o rw,remount /dev/block/mtdblock4 /system" and hit Enter
20) In your terminal, type "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter
21) In your terminal, type "chmod 775 /system/bin/flash_image" and hit Enter
22) In your terminal, type "flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img" and hit Enter
23) In your terminal, type "rm /system/etc/install-recovery.sh" and hit Enter
24) In your terminal, type "rm /system/recovery-from-boot.p" and hit Enter
You can now boot into your new Recovery by turning off your phone and turning back on while holding Volume Down.
If you want the latest CyanogenMod, please continue.
25) Download the following to the root of your SDcard
- update-CM-5.0.8-N1-signed.zip: http://cyanogen-updater.googlecode.com/files/update-cm-5.0.8-N1-signed.zip
- gapps-passion-EPF30-signed.zip: http://www.mediafire.com/download.php?mjzwozjojkh
26) Nandroid backup
- Tip: In Recovery, choose "Backup/Restore" then "Nand backup"
- Tip: This will give you an exact copy of your system's current state which you can revert back to at any time
27) Wipe your phone
- Tip: In Recovery, Choose "Wipe" then "Wipe data/factory reset"
28) Apply zip "update-CM-5.0.8-N1-signed.zip"
- Tip: In Recovery, Choose "Flash zip from sdcard"
29) Apply zip "gapps-passion-EPF30-signed.zip"
30) Reboot into your newly rooted phone!
thanks! is there any specific reason why it has to be FRF83 or FRF72 if you know? for us AT&T Nexus User stuck on EPE54B, shouldn't we be able to do the same? or the ota.zip is different in that sense? Please give us some insight. thanks!
Sorry, where is The attached .zip "ROOT_FRF83.zip" ?
where is the attached .zip "ROOT_FRF83.zip"
Oops!! Added link to the top!
Constrabus said:
Oops!! Added link to the top!
Click to expand...
Click to collapse
the link wont work
Link updated
Constrabus said:
4) With phone attached through microUSB, enter Recovery with the battery cover OFF and the SDcard REMOVED.
- Tip: Be careful not to let the battery fall out during this process
5) When you see the HTC devices attached in recovery mode, hit Ctrl+C
6) Slide in SDcard (Make sure there is no update.zip on it at this point)
- Tip: It should slide in and click VERY easily if you trimmed the tab on the battery properly
7) On your phone, press Power + Volume Up
8) Choose "Apply update.zip from SDcard"
- Tip: It will fail, but that is expected.
9) In your terminal type "adb push flash_image /sdcard/flash_image" and hit Enter
Click to expand...
Click to collapse
Still getting either adb with no sd, or sd with no adb.
When I follow your exact process, apply "sdcard:update.zip" returns
"-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted."
and then "adb push flash_image /sdcard/flash_image" returns
"failed to copy 'ota.zip' to '/sdcard/flash_image'ermission denied".
These are the exact same returns I get when I tried the process without a card inserted, which is what leads me to believe the card is in but not mounted.
Is there a way to tell adb to (re)mount the SD card in recovery?
Or am I doing something wrong...
Can you walk me through just those particular steps? Like Cookbook-detailed instructions.
Make sure that you are inserting the sdcard BEFORE you press Power and Volume Up to reveal the recovery options and AFTER you get adb connected in recovery mode with loop.
Also make sure you can get adb working while in android to make sure the driver is installed properly.
lostinatlanta said:
Still getting either adb with no sd, or sd with no adb.
When I follow your exact process, apply "sdcard:update.zip" returns
"-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted."
and then "adb push flash_image /sdcard/flash_image" returns
"failed to copy 'ota.zip' to '/sdcard/flash_image'ermission denied".
These are the exact same returns I get when I tried the process without a card inserted, which is what leads me to believe the card is in but not mounted.
Is there a way to tell adb to (re)mount the SD card in recovery?
Click to expand...
Click to collapse
weird thing is adb devices do not see my phone even without SD card...
guess froyo is a must to get this working?
i am on EPE54B, still...
I now have an unlocked, newly unrooted FRF83. Will this tutorial still work for me?
t mobile usa 3g network, stock recovery image. I think I am unrooted because there was a warning in the tutorial and my adb shell denies super user permissions.
kaiser_tytnii said:
weird thing is adb devices do not see my phone even without SD card...
guess froyo is a must to get this working?
i am on EPE54B, still...
Click to expand...
Click to collapse
This guide is for people stuck on FRF83 because you can't revert to the older build where other guides worked.
adambenjamin said:
I now have an unlocked, newly unrooted FRF83. Will this tutorial still work for me?
t mobile usa 3g network, stock recovery image. I think I am unrooted because there was a warning in the tutorial and my adb shell denies super user permissions.
Click to expand...
Click to collapse
If you are unlocked, this guide would be redundant for you. The purpose of this guide is to root without having to unlock, thus preserving your warranty.
Shell script version of loop.bat:
I assume this will work...
Code:
while true; do adb devices; done
Constrabus said:
If you are unlocked, this guide would be redundant for you. The purpose of this guide is to root without having to unlock, thus preserving your warranty.
Click to expand...
Click to collapse
I still would like to get my root back. Will that part of this tutorial work to get the root back?
EDIT: Got it rooted. wow that was easy.
Based on you providing links for recovery-RA-nexus-v.1.7.0.1.img, update-CM-5.0.8-N1-signed.zip, google addon EPF30; will the steps involving these install Cyanogen on my phone?
I was hoping to do this process without wiping my phone's memory and keeping my stock FRF83.
what25 said:
Based on you providing links for recovery-RA-nexus-v.1.7.0.1.img, update-CM-5.0.8-N1-signed.zip, google addon EPF30; will the steps involving these install Cyanogen on my phone?
I was hoping to do this process without wiping my phone's memory and keeping my stock FRF83.
Click to expand...
Click to collapse
If you don't want the Cyanogen ROM or RA recovery just skip step #22 and stop with step #24. I didn't follow this tutorial as I did Booker-T's method with some tweaks but if you do what I said you should be fine.
madj42 said:
If you don't want the Cyanogen ROM or RA recovery just skip step #22 and stop with step #24. I didn't follow this tutorial as I did Booker-T's method with some tweaks but if you do what I said you should be fine.
Click to expand...
Click to collapse
You dont have to use that rom, you can flash any other rom as long as you have root. Paul obrien offeres a rooted FRF83 rom
I was able to do this without taking out / putting the SD card in (and thus avoided filing down my battery. I didn't run "loop.bat" until I was highlighting the Recovery icon, the ran it, when into Recovery, and adb picked it up.
Worked perfect!
Just, when flashing recovery, the better terminal emulator was giving me an error, i used Rom Manager to flash the recovery, and back to terminal to rm /system/etc/ blah blah ....GREAT Tutorial!
~DEVELOPMENT STOPPED, THEME NO LONGER BEING WORKED ON~
~ Here it is, Android 2.3 (Gingerbread) theme for X10 Mini/Pro (And 2.1 only)! ~
[For Build 2.0.A.0.504 without the zip file and 2.0.2.A.0.24 with the zip file]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(v1)
tested on the Mini works 100%
Need to have ROOT to apply this theme.
I'm not responsible if you brick your device, use at your own risk.
Added Reboot option, made the some icons clearer namely battery and fixed the bugs in settings.
..I find the xRecovery way of installation much easier & quicker
Install this theme via xRecovery (<-- click, if you want to know how to get recovery on your device)
1. Download the update.zip file: UPDATE.ZIP
2. Do not extract it, copy the update.zip file to the sdcard
3. Reboot your device into Recovery Mode
4. Go to install custom zip option
5. Click, Yes - Install /sdcard/update.zip, wait a little
6. Reboot your device and Enjoy
If you have any problems with any of the apks then re-install them manually.
I'll keep this TUT in here anyway:
How to manually replace the framework-res.apk (apply this theme) using Root Explorer:
1. Make a backup of the original framework-res.apk (found in /system)
2. Extract the framework from the rar file (link below) then Copy the framework-res.apk to the SD card
3. Mount /system in RootExplorer as "R/W"
4. Press the menu button and select the option 'Multi-select' then mark the framework file and Copy the framework-res.apk from the SD card to /system
5. Set the permissions of the framework-res.apk to 644:
In this part please Dont COPY the framework, but move it.
6. Move the framework-res.apk from /system to /system/framework and click ok to replace the existing file.
7. Finally, restart your phone.
and Enjoy
Big thanks to:
draco_ag (for his framework used as a base)
mr.megi @ se-nse (for the 2.3 icons)
To change icons in the dock (LauncherPro):
Keep hold of one of the icons and a menu will pop-up, you should see title 'Edit dock shortcut' then select 'Change icon' and then 'Custom icon' then select the icon
PS.. I'm not changing the download below to the latest until I know the update.zip file works perfectly
Guys! First Install the updated theme then Unzip this file: [2.0.2.A.0.24] Replace These Files to Make Theme Work.rar (below) then replace the extracted files with the ones in system/framework (root explorer method, remember to set permissions), the theme should now work properly (this is for 2.0.2.A.0.24 users only)
UPDATE: Has now got the old background which people requested for
Please don't forget to say
Good one Manny-!
oooh...cool!
downloading...
installing...
rebooting...
+1 for Gingerbread sexy...
works for Mini Pro via Root Explorer method.
nice work mate!
good one
very nice
downloading
Glad you like it
error =S
say "application not installed", i have a rooted X10 Mini Pro
Damn, I've been working on that too, and you were faster! Anyways, very nice
How can i put this beautiful theme work on my stone?
Sent from my U20i using XDA App
Added a how-to to the OP
thx.
works on my mini pro and looks very nice
When i change permissions and press 'ok' didn't save the permissions,and i try to move the file and it doesn't work...
Help plz
Sent from my U20i using XDA App
you have to mount r/w in /, /sd card and /system (look at the botton it should say Mount R/O in all folders), change the permissions of the file when the framework is in the /system folder then move it to /system/framework
When i copied the framework-res.apk to the framework in /system my phone rebooted and it can't start. I't stops on the sony ericsson text.
What should i do?
Do you have a mini or mini pro if you have the mini try this:
1. go to update service application
2. load it up to the x10 Mini update part
3. then connect your phone to the computer
4. keep hold of power + home (middle button) + back (hold all three)
5. you should see the green light come on, then quickly let go of power and home button only, whilst still holding down the back button, then seus should detect your phone
if you don't see the green light, or if it doesn't detect your phone: keep of hold of back button (don't let go), then press both power and home until the green light comes on wen it does let go of power & home
(this works for me all the time so i don't see why it shouldn't work for you)
if this doesn't work you will have to wait until your battery dies completely then put it on charge for a while (without switching it on) and once it charged, connect to SEUS (sony ericsson update service) as you would normally and re-install 2.1..
Manny- said:
Do you have a mini or mini pro if you have the mini try this:
1. go to update service application
2. load it up to the x10 Mini update part
3. then connect your phone to the computer
4. keep hold of power + home (middle button) + back (hold all three)
5. you should see the green light come on, then quickly let go of power and home button only, whilst still holding down the back button, then seus should detect your phone
if you don't see the green light, or if it doesn't detect your phone: keep of hold of back button (don't let go), then press both power and home until the green light comes on wen it does let go of power & home
(this works for me all the time so i don't see why it shouldn't work for you)
if this doesn't work you will have to wait until your battery dies completely then put it on charge for a while (without switching it on) and once it charged, connect to SEUS (sony ericsson update service) as you would normally and re-install 2.1..
Click to expand...
Click to collapse
Thank you
superb and the theme is funky
ThePerfectBitch said:
Thank you
Click to expand...
Click to collapse
Now when i tried again and deleted the framework-res.apk my the same thing happened again. What do i have to do to make it work?
Now it worked
What theme do you have? And can i get the green background?
I use LauncherPro (long-press on the dock icons to change), I've added the wallpaper and the dock icons to the original post
Hi, great looking theme! But i have found some of the original blue theme still left in there.
In the messaging app, if you open a conversation the name is shown on a blue bar. Also the recieved messages are still blue.
The standard t9 keyboard is also still blue.
Other than that it looks great!
This is ClockworkMod Recovery (v.3.2.0.0) ported to work on X10mini / X10mini pro / X8
Introduction
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain old xRecovery and uses Edify exclusively:
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
Despite the non-support for Amend scripts, it's the future of Recoveries and cooks should get used to this kind of scripting when making their zips.
Update:
CWM 3.2.0.0-r3 introduces two new features that validate and restore the currently installed recovery and it's deps before reboot / shutdown. If the current recovery doesn't appear to be correct, it will prompt for a recovery restore option that at least guarantees that the phone can boot into recovery. This is NOT:
- a way to make any ROM that you installed boot
- an idiot proof mechanism (e.g. if you are prompted and omit restoring, you are on your own)
Features
ADB root shell
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
backup (also backs up ext partition and installed apps to sdcard)
restore (also restores ext partition and installed apps to sdcard)
restore from xRecovery (Use this in case you want to restore backups done with xRecovery)
advanced restore
mounts and storage
mount / unmount /cache
mount / unmount /data
mount / unmount /sdcard
mount / unmount /system
mount / unmount /sd-ext
mount / unmount /cache
format /cache
format /data
format /sdcard
format /system
format /sd-ext
mount USB storage
advanced
reboot recovery
wipe Dalvik Cache
wipe Battery Stats
report Error
key Test
partition SD Card
Ext Size (formatting as ext4)
Swap Size (Set this to 0)
Rest Size is for vfat
fix permissions
validate recovery
restore recovery
power off
Usage
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Requirements
Stock 2.1 ROM
Busybox from the market
Root
Installation
EITHER:
If you have xRecovery: Flash the CWM recovery Amend zip
OR:
If you have a previous version of CWM Recovery: Flash the CWM recovery Edify zip
OR:
If you don't have a recovery installed, using Root explorer: manually extract any of the above CWM recovery zips and copy the contents of the system folder (system/bin and system/xbin) to /system, then give 755 permissions to those files, especially to /system/bin/chargemon, or you'll get bootloop.
Notes to everyone
Do NOT use this recovery if you are not in Stock 2.1 firmware. If you have a custom ROM, your cook should incorporate this to his ROM first
Notes to Devs/Cooks
To incorporate this to your ROM, extend the chargemon file to contain the needed part required in order to boot your ROM, the rest of the files need no changes.
Switch to Edify when giving updates for your ROMs. Search xda and google for that, there are plenty of resources out there. E.g: http://forum.xda-developers.com/showthread.php?t=936175
Also use the attached update-binary which is modified and tested to work correctly with this recovery.
Credits:
DaRk_dOg for his testing / support
koushd for writing the piece of software the first place
zdzihu for his rm -rf tip
Cyanogen for the obvious reasons...
Disclaimer:
I can't be held responsible if this Mod bricks your device or makes it explode in your hands! Use it at your own risk!
Changelog:
ClockworkMod Recovery v.3.2.0.0-r2:
- Added restore from xRecovery option
- Fixed letters cutoff at the bottom of the screen
ClockworkMod Recovery v.3.2.0.0-r1 for x10mini
- Ported default CM7 Recovery option
Thank you mate! Another great addition!
very cool but does this mean i cant install it when i am using your miniCM7 ??
freebordjunky said:
very cool but does this mean i cant install it when i am using your miniCM7 ??
Click to expand...
Click to collapse
That means you should bother the dev of your ROM.
....
And also check the MiniCM7 thread
Thanks a million! Will try on MiniCM6-1.0.1!
Sent from my X10mini using XDA Premium App
Great work. Thanks
o2gulo said:
Thanks a million! Will try on MiniCM6-1.0.1!
Sent from my X10mini using XDA Premium App
Click to expand...
Click to collapse
Uhm, you shouldn't.....
nobodyAtall said:
Notes to everyone
Do NOT use this recovery if you are not in Stock 2.1 firmware. If you have a custom ROM, your cook should incorporate this to his ROM first
Click to expand...
Click to collapse
Nobody.... I have one question. Though my phone gets stuck up in SE screen the CWM recovery works fine and shows up on repeated pressing of back button. Now once you upload the rectified ".zip" file can I not reflash it with CWM recovery and boot my device normally instead of going through the entire process of updating through SEUS?
This seems great as with all your work. May I bother you enough to make it work with MiniCM6, as the one you posted effed up my cellphone?
Keep up the great work, nAa
parthabhatta said:
Nobody.... I have one question. Though my phone gets stuck up in SE screen the CWM recovery works fine and shows up on repeated pressing of back button. Now once you upload the rectified ".zip" file can I not reflash it with CWM recovery and boot my device normally instead of going through the entire process of updating through SEUS?
Click to expand...
Click to collapse
Hi,
This thread is for Stock 2.1 ROMs only.
At the state you are, you need to reflash with SEUS and restore with xrecovery.
Good Thing I reverted Back to 2.1 ..
One question, If we use xRec and Flash it, will xRec be removed?
Is backward compatible with xRecovery? I mean themes updates and Backups made for xRecovery will work?
Sent from my X10mini using XDA App
It replaced xRecovery.. No problems at all... Works great... Thanks dude..
When want to replace my recovery i get:
E:Can't chown/mod /system/bin/charger
(No such file or directory)
E:Failure at line 4:
set_perm 0 0 0755 SYSTEM:bin/charger
Edit: well it seemed like it worked, well recovery is orange now
Now it is stuck on SE screen, i dit revert back to stock 2.1
nobodyAtall please help
a couple of questions,
1. i did a backup with the new cwm so the old backups from xrecovery wont work so can i delete them?
and
what is key test?
X10mini miniCM7 2.0.1 using XDA Premium App
This is really awesome, porting to mini pro right now! Thanks nAa, you're the man
cheers, d4.
EDIT:
@nAa Still some wrong on sizes, hope you can fix it, or upload sources, but awesome work, ported to mini pro, ofc all crdtis for you
EDIT2:
Can you please upload a modded version that says Mini pro? Thanks
I flashed the file zip, but the phone forces close..it doesn't work..i repaired the software with SE
Sent from my X10mini using XDA Premium App
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
bitmovel said:
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Click to expand...
Click to collapse
DJxSpeedy said:
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
Click to expand...
Click to collapse
Yeah, same here, btw, tried to make a edify script for flashing old xRecovery, and it gives me error ?, I used chumby's amend2edify tool
Hi.
This is the stock ROM I have flashed: French stock: G1XXKPQ
http://forum.xda-developers.com/showthread.php?t=1531850
I flashed the 2.3.6 stock ROM with Odin 1.85. And used Odin again to flash the TerraSilent 1.3.5 custom kernel. Then I have CWM custom recovery. And for the 2.3 GB ROM, I can see I have root (adb shell, su is okay).
Now I can't find out what to do as next step. I have looked at several AOSP ROMS' threads in the development forum, and still got no clue.
I tried the following:
1.
Download the following ROM: [ROM][YPG1][4.2.2] Paranoid-Android 3.60 - With HALO - 6/26/13
http://forum.xda-developers.com/showthread.php?t=2340544
And put it to the SDCARD. BTW, I have no external SDCARD installed.
In the CWM recovery, I chose to install this .ZIP file, the process is failed as follows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The on screen text is OCR'ed by human flesh as follows:
Code:
ClockWork Mod Recovery v5.0.2.7
-- Installing: /sdcard/ROM/pa_ypg1-3.60-26JUN2013-201457.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "ypg1" || getprop("ro.build.product") == "ypg1"
E:Error in /sdcard/ROM/pa_ypg1-3.60-26JUN2013-201457.zip
(Status 7)
Installation aborted.
As the message hints, I run similar commands in "adb shell" within the stock 2.3.6 ROM:
# getprop ro.product.device
getprop ro.product.device
YP-G1
# getprop ro.build.product
getprop ro.build.product
YP-G1
Click to expand...
Click to collapse
("adb shell" on Windows will have all commands echoed back, hence the stupid repeated command lines)
I don't know if this result is related to that assert performed in recovery. Just for the record. And I believe "YP-G1" is definitely "not equal" to "ypg1". But this is a safe assert. If this failed, probably there is something not expected by the ROM installer, so I understand cancelling installation is the correct thing. But how to pass the test and enable installation anyway?
2.
Then I downloaded this "preflash" zImage as mentioned in this most recent CM10.1 ROM thread:
http://forum.xda-developers.com/showthread.php?t=2333769
I have found several threads linking to this "preflash" zImage. It is somewhat quite mysterious. I don't know what does this "preflash" indicate: under what condition indeed does this "preflash" procedure to be performed?
I have come across the "MTD based ROM" jargon while searching everywhere. I have no idea of that. But I just want to get the AOSP likes to be installed onto the device. This "preflash" kernel seems to be just for such task.
Any way, I flashed it using TerraSilent's CWM recovery. The device is stuck at the samsung logo. So I reboot to Ubuntu to use heimdall to flash the zImage raw file.
By the way, can I pack zImage into .tar file and flash using Odin? heimdall tends to get messed up, and install its driver in Windows tends to mess even more, this tool definitely is not recommended to casual user).
So after flashing using heimdall, the device enters boot loop, the "samsung" logo did apear for three times, then the recovery screen just flashed away, even too fast to peek for the on screen message, I have to capture it by recording a video, and here is the frame extracted from the video:
Again the on screen text is OCR'ed by human flesh as follows:
Code:
CWM-based Recovery v6.0.1.2
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
Internal SD Card marker not found... continuing anyways.
-- Installing:
Finding update package...
E:unknown volume for path []
E:Can't mount
Installation aborted.
At last I'm still with that French stock 2.3.6... Any help would be appreciated and sorry for the lengthy gossips I have put here.
Well I figured out... It turns out after flashing the "preflash" zip, you MUST NOT reboot, but instead go on to flash the ROM itself.
And another important thing: you must restore /efs after flashing back to stock using Odin.
Initially I just can't get such hints from all those ROM threads in the development forum. Maybe it's too obvious. But it certainly is not so obvious for we Chinese people, as I searched in Chinese, I can find many have done exactly the same I did (lol). Anyway from the Chinese forums I finally get to it.
I have made a record of all the flashing procedures and put it here, hope it will help some avoid searching all over the world to get started from scratch.
Samsung Galaxy S Player WLAN 4.0, YP-G1 International (Intl.) version flashing notes
====================================================================================
I use Windows 7 X64 to perform the following operations.
Part 0: Backup /efs (to your computer)
I don't know what this really means, but it is REQUIRED for later flashing, so don't rush to the flashing.
I use adb shell to make backup:
# tar cf /sdcard/efs.tar /efs
And pull it to your PC and keep it safe:
C:\> adb pull /sdcard/efs.tar .
(This is just an example, your backup and restore approach can be different)
Part 1: Revert to stock Android 2.3 (Gingerbread)
I believe this can be performed as long as you have download mode available, and this should be a good start if you think you have totally messed up with your device.
Files you need:
a. Samsung mobile driver: http://forum.xda-developers.com/showthread.php?t=2038555
For the 1.5.25.0 driver installation, the install wizard says it some error occurred at the end. But it seems no harm.
b. Odin flashing tool: (download link is the same as a.) I use Odin 1.85 for the YP-G1 device.
c. The 2.3.6 stock ROM: http://forum.xda-developers.com/showthread.php?t=1531850
I picked G1XXKPQ, version 2.3.6. Since my device is bought from China, it is compatible.
Also download the "Pit" file, again for my YP-G1 from China, I choose the "Intl" version.
Steps:
1. Put your device into download mode:
a. Shutdown deivce entirely, and pull battery and re-install to be sure
b. Key combinations: PRESS and HOLD: HOME button and Volume Down button. Then additionally, press and hold POWER until "Download mode" appears on device screen.
2. Connect your device to PC, let the system recognize new devices and install drivers.
3. To further make sure, you can disconnect the device, pull out its battery. And enter download mode, then connect to PC again.
4. Open Odin tool, this needs Administrator privilege, if Odin detects your device, it will display some message like "<ID:0/008> Added!!", and there is a blank text field under the "ID:COM" label turning to yellow color and showing a COM port number.
Then on the Odin GUI, select two files:
a. Click "PIT" button, locate your downloaded ".pit" file. This will cause the "Re-Partition" option to be selected automatically.
b. Click "PDA" button, locate your ROM, which is a .tar.md5 file, like: YP-G1FullRestoreIntl2.3.6.tar.md5
c. Click "Start" and wait until the device reboots.
Sometimes Odin is stuck at "SetupConnection", then retry: find a better cable (should not be too long), find a better USB port on your PC (USB 2.0 possibly can be preferred over USB 3.0). Retry by restarting from Step 1.
5. After device reboots, it enters the Android recovery automatically, and you can see some RED text saying "mount failed" alike. Just choose "wipe data/factory reset" and then reboot.
Now you are stock.
Part 2: The TerraSilent custom kernel (with custom recovery ClockWork Mode, CWM)
The stock Android recovery cannot be used to flash custom stuff, so you need to flash a custom recovery first.
Steps:
1. Download TerraSilent custom kernel: http://forum.xda-developers.com/showthread.php?t=1643384
I choose 1.3.5, which comes with CWM v5.0.2.7
The odin flashable kernel file is: TerraSilent_intl-1.3.5.tar
2. Shutdown device, and enter download mode again, and connect it to the PC, open up Odin, DO NOT touch the "PIT" button, only the PDA button, and choose custom kernel file. Then punch "Start".
3. This should be quick, and device reboots automatically, but you will find nothing new in your stock Gingerbread ROM.
Part 3: Restore your /efs folder
Like part 0:
C:\> adb push efs.tar /sdcard/
Then "adb shell" to the device, and "su" if necessary:
# tar xf /sdcard/efs.tar -C /
(Again your restore approach can be different)
Part 4: Get 4.x AOSP ROM and flash:
This is the time you transform your Android 2.3 player into an AOSP based Android 4.x ROM, so it's a little tricky (in fact the tricky stuff includes above /efs backup & restore thing)
I'm taking this CM9 as an example: http://forum.xda-developers.com/showthread.php?t=2213152
Because in this thread it mentions you MUST restore /efs for this ROM install to succeed, otherwise it will fail. (I have attached a photo of the failed install for reference.)
1. From this thread, download two files:
a. cm-9-20130402-kernel-preflash.zip
b. cm-9-20130408-UNOFFICIAL-ypg1.zip
Put both to device's /sdcard. And REMOVE your external Micro SD card if any.
2. Shutdown your device. Addtionally pull and re-install the battery for sure. Then you need to enter the recovery.
The key combinatoins for entering recovery:
PRESS and HOLD: HOME button and VOLUME UP button.
Additionally, press and hold power button. When the screen lights up, release POWER button, but keep HOME and VOLUME UP pressed.
As you are in the CWM recovery, this is from the TerraSilent custom kernel, version is v5.0.2.7.
a. Perform some wiping:
- wipe data/factory reset
- wipe cache partition
- advanced, - Wipe Dalvik Cache
b. Then install:
- install zip from sdcard, - choose zip from sdcard, --> select the .zip ROM file and confirm.
Sometimes the /sdcard won't mount, i.e., after choosing "- choose zip from sdcard", nothing can be found there.
Then I pull the battery and repeat it. Probably the files will show up.
Flash in the following order, don't reboot after the first .zip is flashed:
a. cm-9-20130402-kernel-preflash.zip
b. cm-9-20130408-UNOFFICIAL-ypg1.zip
When flashing the second one, the device will reboot automatically. Wait patiently until the device stays at a "new" custom recovery, which shows its version as "CWM-based recovery v6.0.1.2". Then you have completed all. Here you can flash the GAPPS package, if you have put it at your /sdcard before.
PS. "GAPPS" packges download: http://goo.im/gapps/
Please match the version, e.g., CM10.1 is "Jelly Bean" 4.2 (JB), CM9 is "Ice Cream Sandwich" (ICS).
Part 5: Other AOSP based ROMS.
From now on, you don't need that "cm-9-20130402-kernel-preflash.zip" file when flashing other AOSP based ROMS.
Just put the .zip ROM file at /sdcard, and reboot into custom recovery, wipe as needed, and install.
Attached is a photo showing how it fails to install the CM9 ROM if /efs was not restored:
Wow this is a full fledged guide on how to flash cm9, cm10 and cm10.1. I will add this to the all-in-one when I'll get some time.
Envoyé depuis mon Nexus 7 avec Tapatalk
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
aromafm_galaxy5.zip (v1.91)
http://www.mediafire.com/?p5pdelpib6w8px
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
XDA:DevDB Information
PhilZ Touch Recovery : galaxy5, Tool/Utility for the Samsung Galaxy 5 I5500
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-07
Created 2014-07-12
Last Updated 2014-07-12
Very good recovery. :good:
Everyone should check it out.
I haven't found any bugs as of now.
UPDATE:
Changelog:
-Updated PhilZ sources to 6.23.8 (26.03.2014).
-Updated androidarmv6 sources. So, you'll be able to flash cm-ota without any Signature Verification error.
Below is the recovery.img file, flash using Terminal Emulator method:
recovery.img
Need feedback. If everything is fine, I'll add it to first post.
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
jpeps said:
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't try it until the developer says so!
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
RobsX2 said:
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
Click to expand...
Click to collapse
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Bhargav97 said:
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Click to expand...
Click to collapse
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
EDIT: Recovery has flashed and does work. Thanks!
RobsX2 said:
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
Click to expand...
Click to collapse
Then there is another simple solution.
-Install any CWM recovery (through ODIN).
-Now download any zip file of cwm recovery (use madteam.co if you don't find at xda).
-Open the zip and replace the recovery.img inside with this (PhilZ Recovery) one.
-Now, flash this modified zip file with the current cwm recovery (which you installed using odin).
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
RobsX2 said:
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
Click to expand...
Click to collapse
Have you done all the wipes?
Vagelis1608 said:
Have you done all the wipes?
Click to expand...
Click to collapse
Yessir
RobsX2 said:
Yessir
Click to expand...
Click to collapse
Did you pulled the battery to turn the device off when it hunged (at the "Android" screen)?
Have you tried booting up again?
Also, contact me via PM so that I will help you fix the issue. Let's not spam this thread .
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
deleted
Bhargav97 said:
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
Click to expand...
Click to collapse
ALL HARDKEYS WOORK FINE!
I just have one doubt.
When i reset to "Koush default" it gave me a netted grey background..
Whereas :"Philz default" gave a complete black background..
Is this supposed to happen.
Maybe I am too stupid
But where is on goo.im the PhilzTouch for this little jewel called galaxy5?
wrong post