Database Info

[HOW-TO] downgrade HBOOT 0.93 to 0.80 again

After my new Desire updated by OTA to 2.2, my HBoot upgraded to 0.93.001
As a result, I am no longer to root it again or flashing any cooked rom.... It is such a nightmare for me. So I decided went to HTC service center and asking for a factory restore to Android 2.1, unfortunately the guy stated that due to my personal's fault - to hack the bootloader, there is no way to downgrade the software anymore. I need to pay extra money for a circuit board replacement. I am so angry with the replied, my phone actaully working fine with OTA 2.2 version (it is official release for Taiwan), all I want to do is requested for downgrade to official 2.1, why I need to replace a circuit board????
Anyway after a few hours, I figure out a solution and now working fine with Hboot 0.8 and then re-flashed to customized cooked FroYo rom
Here is the steps: (be careful, I am not responisable for any demage due to these procedures, also you need to have basic knowledge on using Android adb tools)
0.) Download this good program: http://evo4g.me/downloads/evo-root.zip (Credit goes to djR3Z)
Download this file to "PB99IMG.zip" http://shipped-roms.com/shipped/Bra...8U_4.06.00.02_2_release_126984_signed_txt.zip
1.) Make a NEW Goldcard (best using FAT32 format micro SD 4GB or 2GB)
http://www.klutsh.com/dlfiles/GoldCardTool-0.0.5.rar
2.) Find your CID ==> e.g HTC__622 (someone said all 11111111 also worked, but if you can query, why not to input your own?)
fastboot oem boot <--- run this command, will show your own CID
3.) http://ks33673.kimsufi.com/misc/
and Create your own "mtd0.img"
>adb push flash_image /data/local/
>adb push rageagainstthecage-arm5.bin /data/local/tmp/
>adb push mtd0.img /sdcard/
>adb push PB99IMG.zip /sdcard/
>adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
If you see:
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3319, 3319}
[*] Searching for adb ...
[+] Found adb as PID 74
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
> adb shell
# <---- you will see this good prompt
cd /data/local
./flash_image misc /sdcard/mtd0.img <---- make sure your connected to PC not in Disk drive mode
5.Shutdown your device
6.Hold volume DOWN and press power button
7.Wait until PB99IMG.ZIP was found and verfied. If that fails, check if you named the file the right way and it’s located in the root of your SD.
8.Press volume UP to start the update.
9.Wait until all steps are done. DON’T POWER OFF YOUR DEVICE!
10.After the downgrade progress has finished press volume UP to reboot.
Now you back to 2.1 with HBoot 0.80
(Please remember to delete the file PB99IMG.zip from your SDcard / folder)
If you want root again:
Navigate to http://www.unrevoked.com for rooted as usual

Interesting, a root exploit for froyo has been found? Though any downgrade of hboot is unnecessary. The rooting allows you to fix the misc partition which will let you flash any RUU you want.

My Desire show : Main Version is older! Update Fail!

setupspeed said:
My Desire show : Main Version is older! Update Fail!
Click to expand...
Click to collapse
what is the issue?
tell me what steps being failed...

hkfriends said:
what is the issue?
tell me what steps being failed...
Click to expand...
Click to collapse
read PB99IMG.ZIP finish , then checking PB99IMG.ZIP => fail

setupspeed said:
read PB99IMG.ZIP finish , then checking PB99IMG.ZIP => fail
Click to expand...
Click to collapse
Have u flashed Mtd0.img ok?

hkfriends said:
Have u flashed Mtd0.img ok?
Click to expand...
Click to collapse
Mtd0.img ok , pursuant step => still fail

better add some screenshoot bro

I have got hboot 0.93 with vodafone froyo and an amoled-display (no slcd).
Do the method of
android-tutorials.org/dev/?page_id=78
work (sorry, can't post the hole link because I an new registered, add www)?
Or do I have to use the method from post #1 in this thread?

cordezz said:
I have got hboot 0.93 with vodafone froyo and an amoled-display (no slcd).
Do the method of
android-tutorials.org/dev/?page_id=78
work (sorry, can't post the hole link because I an new registered, add www)?
Or do I have to use the method from post #1 in this thread?
Click to expand...
Click to collapse
Try teppic74's tool, i think it will be more easy and the same as mine too!
http://forum.xda-developers.com/showthread.php?t=768256

C:\adb>adb push flash_image /data/local/
adb server is out of date. killing...
* daemon started successfully *
774 KB/s (26172 bytes in 0.033s)
C:\adb>adb push rageagainstthecage-arm5.bin /data/local/tmp/
478 KB/s (5392 bytes in 0.011s)
C:\adb>adb push mtd0.img /sdcard/
1807 KB/s (655360 bytes in 0.354s)
C:\adb>adb push PB99IMG.zip /sdcard/
1550 KB/s (144169877 bytes in 90.807s)
C:\adb>adb shell
$ chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
$ chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3319, 3319}
[*] Searching for adb ...
[+] Found adb as PID 671
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
# cd /data/local
cd /data/local
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
# exit
exit
C:\adb>
-------------------------------------------------------------
my step , correct?

Yes, seems corrected..
have you made gold card?
what is your phone? OEM or branded?
what is the original Hboot version?
setupspeed said:
C:\adb>adb push flash_image /data/local/
adb server is out of date. killing...
* daemon started successfully *
774 KB/s (26172 bytes in 0.033s)
C:\adb>adb push rageagainstthecage-arm5.bin /data/local/tmp/
478 KB/s (5392 bytes in 0.011s)
C:\adb>adb push mtd0.img /sdcard/
1807 KB/s (655360 bytes in 0.354s)
C:\adb>adb push PB99IMG.zip /sdcard/
1550 KB/s (144169877 bytes in 90.807s)
C:\adb>adb shell
$ chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
$ chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3319, 3319}
[*] Searching for adb ...
[+] Found adb as PID 671
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
# cd /data/local
cd /data/local
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
# exit
exit
C:\adb>
-------------------------------------------------------------
my step , correct?
Click to expand...
Click to collapse

hkfriends said:
Yes, seems corrected..
have you made gold card?
what is your phone? OEM or branded?
what is the original Hboot version?
Click to expand...
Click to collapse
gold card => yes
My phone => HTC Desire
Hboot version => 0.93.0001

i have this error "error writing misc: Permission denied"
in this step: "./flash_image misc /sdcard/mtd0.img"

Noob question
Using your method wont brick my phone right? My phone details are below:
Unit: HTC Desire
ROM: FroYo OTA (Unbranded)
BOOTLoader: 0.93
Software:2.13.707.1
Kernel:2.6.32.15

Just use my tool instead, it's much easier.

Doesn't Unrevoked3, the tool that is used to root phones, support hboot 0.93 on unbranded / unlocked phones? So this step is un-necessary on unbranded / unlocked phones?

Did it work at all?
Hi,
I too want to downgrade my HTC Desire from 2.2 to 2.1 because after the upgrade to 2.2 with hboot 0.93 my desire has stopped connecting to the H or 3g network.
Did this guide work for anyone at all?

HI
CAN SOME HELP ME TO GET THE ROM IMAGE VERSION 2.13.707.1 I NEED THE EXE. FILE THATS THE ONLY WAY I KNOW TO INSTALL THE ROM!!!!
MY PHONE TRIED TO UPGRADE FROM THE PHONE SOMETHING WENT WRONG AND IT SWITCH ON AND GET STUCK IN WHITE SCREEN WITH htc GREEN LOGO . . . I TRIED TO INSTALL THE ROM FROM MY COMPUTER THE LATEST BUT THE IMAGE ON THAT IS 2.10.405.2 . I REALLY APPRECIATE IF SOMEONE CAN HELP ME

black screen
I got a black screen after downgrade. Also after restart the phone
Desire

[Q] trouble with MT4G downgrade

when i try to set the version it says permission denied.. i have successfully done the previous steps and when i try to put in the line in red it just doesnt give me permission even though i have # i am using http://forum.xda-developers.com/showthread.php?t=1178912
please refer to the Changing Version Number to Allow Downgrade section.
what am i doing wrong? what do i have too do?
P.S. I am asking in a new thread because the downgrade walktrough is in developers and i am new. any help will be apreciated
C:\AndroidSDK\platform-tools>adb shell
# /data/local/tmp/misc_version_01/misc_version -s 1.00.000.0
\/data/local/tmp/misc_version_01/misc_version -s 1.00.000.0
/data/local/tmp/misc_version_01/misc_version: permission denied
# sync
\sync
# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
2.19.531.110+0 records in
10+0 records out
10 bytes transferred in 0.003 secs (3333 bytes/sec)
#

Are you gaining temp root first?

um you didnt link to anything

I am seeing different commands than what you have posted...
> adb push misc_version /data/local/tmp/misc_version
> adb shell chmod 777 /data/local/tmp/misc_version
> adb shell
# /data/local/tmp/misc_version -s 1.00.000.0

they are different because the file name was different(it was misc_version_01 folder but had same misc_version file inside) and i pushed folder and not just the file so i had to get to the file

oh and i did get temp root...
that make adb shell make a # right

eddy14777 said:
they are different because the file name was different(it was misc_version_01 folder but had same misc_version file inside) and i pushed folder and not just the file so i had to get to the file
Click to expand...
Click to collapse
That shouldn't be the case, you are supposed to unzip the folder in your platform-tools directory, so you shouldn't have the folder name in the command...just the file.

thanks! i will try this and se if that goes smoother

you sir are a genious! thankyou soo much.. i probably wouldnt have gotten past this if it werent for you... thankyou

eddy14777 said:
you sir are a genious! thankyou soo much.. i probably wouldnt have gotten past this if it werent for you... thankyou
Click to expand...
Click to collapse
No problem...glad I could help

[Q] Cant change version number to allow downgrade htc g2 root

I have an HTC G2 - running android version 2.3.4. I followed all the steps correctly, once I got to downgrading the version I got stuck.
____________________________________________
> adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/*
> adb shell
> cd /data/local/tmp
# ./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
________________________________________
Once I do adb shell it takes me into adb shell and I cant run "cd /data/local/tmp"

Please use the Q&A Forum for questions Thanks
Moving to Q&A

Having problems with ADB and pushing files.

Hey everybody
I currently have a mytouch 4g on 2.3.4, and i want to downgrade so i can root my device. To get you up to speed, I have SDK with all the necessary downloads (except to google drivers, it says not supported on mac after download).
I have fre3vo, misc_version, and PD15IMG.zip all in the platform-tools folder.
Heres my issue,
when i type the commands:
> adb push fre3vo /data/local/tmp
> adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
It tells me that the file is not there. Ive tried re-downloading the files and still not working. Also, i have tried just pushing the misc_version and it takes me straight to the ADB command list.
-debugging is on
-SD Unmounted
-> adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length (good to go)
-it recognizes my device and serial number
can anybody help with this? what gives?
Thank you all!!
PS. IM ON A MAC COMPUTER

Did you add platform tools folder to your PATH?
Give me the result of this command:
echo $PATH
Sent from my HTC Panache / CM7 using xda premium.

see attached picture. I did the same thing with misc_version and got the same response.

Can anyone help me with this ptoblem? I would really appreciate it!
Sent from my HTC Glacier using XDA App

You're not running it from the directory where you have both of those files. This is why adb doesn't find them.
Just cd into correct directory where you have them before executing the command.
The guide clearly says:
1. Download the attached files, unzip them, and place the files in your platform-tools folder.
...
5. Run the following commands from your platform-tools directory
Click to expand...
Click to collapse

Hey Jack R1,
Thank you for the response. Please bare with me throught his problem, for i am not really good at this. I was under the impression that it is IN the platform tools folder. I have it all unzipped and ready to go. Maybe i am typing the commands wrong? Could you also tell me how to CD them to the right directory? I thought it was in the right place but i guess i just dont understand.
Thank you!
i attached another picture of my problem, if it helps.

Hello,
cd is used to change directory. Please google it because this is a basic command you must know.
So what you must do:
cd /home/USER/PATH_TO_ADB_FOLDER
You must replace USER and PATHZTO...
Please provide the result of the command I ask in my first response(echo $PATH)
Just copy paste the result here. Image are not easy to read from my phone.
Sent from my HTC Panache / CM7 using xda premium.

The files are in the correct directory. You aren't (your shell is open on default location, which is /User, I think). You're calling adb by full path, while you shouldn't be - your shell should be in the same subdirectory.
Instead of writing /User/blah/blah/platform-tools/adb, write:
cd /User/blah/blah/platform-tools
Click to expand...
Click to collapse
And from there, write:
adb push blah-blah wherever_you_want_it
Click to expand...
Click to collapse

SprigganMaster, Jack R1
Thank you both for helping me through this, im getting closer and closer .
I spent almost all night researching adb and cd and got more familiar with it. I guess the problem im having is writing it in the terminal the correct way.
SprigganMaster-
When i type echo ($path) this is what i get. (i have a feeling that im typing it in wrong)
jordan-browns-macbook:android-sdk-macosx jordanbrownlute2$ echo ($path)
-bash: syntax error near unexpected token `$path'
jordan-browns-macbook:android-sdk-macosx jordanbrownlute2$
Jack R1,
after reading what you posted, the articles on use of cd more more sense now, and i feel like a complete idiot. (I know that if this kinda stuff is not up my alley then i should probably just wait for a root, or ICS to be released, but after tinkering with this phone and sdk/adb, i am hooked! ). Anyways, back to the problem at hand....
after cd it to the directory, then typing the commands, i get a command not found for alot of commands..
jordan-browns-macbook:~ jordanbrownlute2$ cd /Users/jordanbrownlute2/Desktop/android-sdk-macosx/platform-tools
jordan-browns-macbooklatform-tools jordanbrownlute2$ /Users/jordanbrownlute2/Desktop/android-sdk-macosx/platform-tools
-bash: /Users/jordanbrownlute2/Desktop/android-sdk-macosx/platform-tools: is a directory
jordan-browns-macbooklatform-tools jordanbrownlute2$ cd /Users/jordanbrownlute2/Desktop/android-sdk-macosx/platform-tools
jordan-browns-macbooklatform-tools jordanbrownlute2$ adb root
-bash: adb: command not found
jordan-browns-macbooklatform-tools jordanbrownlute2$ adb devices
-bash: adb: command not found
jordan-browns-macbooklatform-tools jordanbrownlute2$ adb push fre3vo /data/local/tmp
-bash: adb: command not found
jordan-browns-macbooklatform-tools jordanbrownlute2$ adb push fre3vo /data/local/tmp
-bash: adb: command not found
jordan-browns-macbooklatform-tools jordanbrownlute2$ adb push fre3vo /data/local/tmpadb push fre3vo /data/local/tmp
-bash: adb: command not found
jordan-browns-macbooklatform-tools jordanbrownlute2$ adb push misc_version /data/local/tmp/
-bash: adb: command not found
jordan-browns-macbooklatform-tools jordanbrownlute2$
what am i doing wrong now?
i think this part is ok:
Last login: Thu Jan 12 14:05:06 on ttys001
jordan-browns-macbook:~ jordanbrownlute2$ cd /Users/jordanbrownlute2/Desktop/android-sdk-macosx/platform-tools
jordan-browns-macbooklatform-tools jordanbrownlute2$ (<-this is what it responds with, which means i am in the directory i need to be running the commands with right?)

Yes, you're changing to the correct directory.
You need to run "./adb" and not just "adb", I guess, when running from the same folder where ADB executable resides.

finnaly success
Jack R1,
I guess i am an idiot after all, a simple "./" is what was stoping me from pushing those files...
Heres the response:
Last login: Thu Jan 12 15:03:44 on ttys001
jordan-browns-macbook:~ jordanbrownlute2$ cd /Users/jordanbrownlute2/Desktop/android-sdk-macosx/platform-tools
jordan-browns-macbooklatform-tools jordanbrownlute2$ ./adb push fre3vo /data/local/tmp
217 KB/s (9796 bytes in 0.044s)
jordan-browns-macbooklatform-tools jordanbrownlute2$ ./adb push misc_version /data/local/tmp/
139 KB/s (15837 bytes in 0.110s)
jordan-browns-macbooklatform-tools jordanbrownlute2$ chmod 777 /data/local/tmp/fre3vo
chmod: /data/local/tmp/fre3vo: No such file or directory
jordan-browns-macbooklatform-tools jordanbrownlute2$
Its supposed to like like that right!?

Almost.
You forgot 1 thing: to actually enter ADB shell before executing chmod.
adb shell
Click to expand...
Click to collapse
(you get $ prompt, keep working from it)
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo with_the_parameters_from_the_guide
Execute_the_rest_of_the_guide
exit
Click to expand...
Click to collapse

you sir, are a genius. and i highly appreciate you sticking with me through this process. i now understand more of adb and its commands/functions. THANK YOU!!!
./adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 2fd00000
smem_len: 300000
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Frame Buffer handle: 4
Buffer offset: 002ee000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb57a00:600.
Exploiting device...
jordan-browns-macbooklatform-tools jordanbrownlute2$ ./adb shell
# exit
jordan-browns-macbooklatform-tools jordanbrownlute2$

SAMPDX said:
Exploiting device...
jordan-browns-macbooklatform-tools jordanbrownlute2$ ./adb shell
# exit
jordan-browns-macbooklatform-tools jordanbrownlute2$
Click to expand...
Click to collapse
The # mean you gain root access. Congrat
If I can offer some advices :
- Linux / Mac shell command are case sensitive. It means HELLO and hello are 2 differents things.
When I asked to execute echo $PATH, PATH must be in upper case and the $ is important.
It's why you got
-bash: syntax error near unexpected token `$path'
Example on my computer :
$:>echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/usr/share/java/apache-ant/bin:/opt/java/bin:/opt/java/db/bin:/opt/java/jre/bin:/opt/kde/bin:/usr/bin/core_perl:/opt/qt/bin
Click to expand...
Click to collapse
The MyTouch / Panache / Glacier is not easy to root. You need to downgrade and it's very important to follow the tuto closely to be sure you don't brick your phone. Feel free to copy paste the command to be sure you are not doing any error.
Regards

adb is a program i have never used before and i am very thankful that you are giving me advice. I am eager to learn more and tinker with my device!
-as for the commands being sensitive. It was my issue 90% of the time .
After all was said and done, i typed the command
>adb reboot bootloader
and it said something like, wrong image, main version is older. I repeated the whole process again and now it worked!!!!
I am officially back to 2.2.1! You have no idea how relieved i am.
Thank you for everything SprigganMaster and Jack_R1!

similar problem with adb push
Hello,
I am having a similar problem, I am unable to perform the "adb push fre3vo /data/local/tmp"
I am using a windows computer, and trying to downgrade the os on my mytouch 4g so I can install CyanogenMod I have tried it with and without the "./"
Here are the responces:
C:\android-sdk-windows\platform-tools> ./adb push fre3vo /data/local/tmp
'.' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk-windows\platform-tools> adb push fre3vo /data/local/tmp
When I do not use the "./" nothing happens, and I do not get another command prompt.
Is it different because it is a windows machine? or what are the other possibilities?
Thanks
_rob

may help
rla150 said:
Hello,
I am having a similar problem, I am unable to perform the "adb push fre3vo /data/local/tmp"
I am using a windows computer, and trying to downgrade the os on my mytouch 4g so I can install CyanogenMod I have tried it with and without the "./"
Here are the responces:
C:\android-sdk-windows\platform-tools> ./adb push fre3vo /data/local/tmp
'.' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk-windows\platform-tools> adb push fre3vo /data/local/tmp
When I do not use the "./" nothing happens, and I do not get another command prompt.
Is it different because it is a windows machine? or what are the other possibilities?
Thanks
_rob
Click to expand...
Click to collapse
yes it is different.... read this and it may help.
http://forum.xda-developers.com/showthread.php?t=1178912

Panasonic Eluga Power P-07D

Greetings,
I have received my shiny new Eluga Power and I am wondering if anybody else has this device and if anybody has rooted there's?
Sent from my P-07D using xda premium

Edit: moved to Q&A, lets see if you can get some help but do search for your device.
First welcome...
Next time post in the Q&A section for questions. To better serve you do a search for your device and look in the Dev section for your model device...also you will find a Q&A section there, Thank you.
Btw ensure you read the forum rules.
Sent from a closet, at Arkham Asylum using Forum Runner.

ianford10 said:
Greetings,
I have received my shiny new Eluga Power and I am wondering if anybody else has this device and if anybody has rooted there's?
Sent from my P-07D using xda premium
Click to expand...
Click to collapse
Where did you get it from?HOw much? How's it first impression?

mixmaster said:
Where did you get it from?HOw much? How's it first impression?
Click to expand...
Click to collapse
Had to import it from a Japanese eBay store with a cost of £560 with delivery. First impressions of the phone are very good, nice big clear screen, batter life is okay considering the screen size, calls are crisp and clear, feels good in the hand to hold. Will have more info as I use it over the next couple of weeks
Sent from my P-07D using xda premium

Rooting P-07D success...
I was able to root my Panasonic Eluga Power (P-07D) you can check the screenshot below. As of the moment I am re-writing the steps for others so they can easily follow the instructions as this was written in Japanese (Thanks to http://sithxi.blog49.fc2.com/blog-entry-51.html and goroh_kun. Hopefully this would help others root there device just like me. The only main problem for me now is SIM unlock the device.

Panasonic Eluga Power rooting instructions...
As promised here are the steps: (This seems to look like a temporary root, as you will loose it once the device rebooted) But still it's a good primary step. For the source code it can be downloaded from here. Panasonic Eluga Power Source Code
goroh_kun
2012/10/18
root privileges acquisition & tomoyo released experimental version in
the p-07d
things to do
Run:
1. >adb restore p-07d.ab
I press OK authentication
After the restore is finished
2. Open another command prompt and type the following:
>adb shell
$cd /data/data/com.android.settings/a/
$ls -l -d
drwxrwxrwx system system a
- check directory called A exists, it is world readable, writable as
show above
3. $ ls -l
⇒ file00 〜 file99 check if files exists
Delete all file from file00 ~ file99
run the command below
4. >adb shell
$cd /data/data/com.android.settings/
$rm -r a/*
change permissions to 777 /persist
This is the tricky part as you need to to do this using two command prompt, one running the adb restore p-07d.ab while the other on the shell command running ln -s /persist a/file99 command.
5. First run: >adb restore p-07d.ab while it is restoring on the other command prompt run in shell $ ln-s / persist a/file99
6. Now lets check the permission to folder /persist by typing on the command prompt that is already in shell.
$ ls -l -d /persist
drwxrwxrwx system system persist <--(you should see this)
Now move on your other command prompt window and run the following commands. (you can download the needed file at this link
Then run the command below to push the files needed for rooting:
>adb push init.cne.rc /data/local/tmp
>adb push p07dgetroot /data/local/tmp
>adb push xsh /data/local/tmp/
>adb push libQ.so /persist
>adb shell rm /persist/init.cne.rc
>adb shell ln -s /data/local/tmp/init.cne.rc /persist/init.cne.rc
>adb reboot
The next step is kinda hard to understand and I qoute: "/persist at Startup directory of the recovery process because it will not be restored and persist the only symbolic links should be a basic /data/local/tmp to keep the change."
After re-move environment variable is changed to check (LD_PRELOAD= /presist/libQ.so and be sure it is).
7. > adb shell
$echo $LD_PRELOAD
/persist/libQ.so <--(you should see this)
8. To Unlock Tomoyo, follow this steps:
> adb shell
$ cat /data/local/tmp/p07dgetroot > /tmp/xsh
$ ls -l /tmp/xsh
-rw-rw-rw- shell shell xsh <--(you should see this)
Make sure that wirelss LAN is ON before doing the command below:
9. WLAN ON / TURN OFF WLAN / TURN ON WLAN (wait to be connected before typing the below command or you will have to do it again)
$ ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
$ /tmp/xsh
/tmp/xsh
/tmp/.mem fd=3
read ret = 256
write ret = 256
At this stage, Tomoyo is now unlocked
10.
$rm /tmp/xsh
$cat /data/local/tmp/xsh > /tmp/xsh
11. WLAN ON / TURN OFF WLAN / TURN ON WLAN (wait to be connected before typing the below command or you will have to do it again)
$ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
12. $/tmp/xsh
$(precmd)[email protected]$HOSTNAME:${PWD:-?} $ <--(you should see
this)
Here is a shell with root privileges, so stand up and be able to work a variety. You can also install the su
13. $(precmd)[email protected]$HOSTNAME:${PWD:-?} $
$ mount -o remount,rw /system /system
$ chmod 777 /system/app/
$ chmod 777 /system/bin/
$ chmod 777 /system/xbin/
Open another command prompt:
adb push Superuser.apk /system/app/
adb push su /system/bin/
adb push busybox /system/xbin/
Go back to ($(precmd)[email protected]$HOSTNAME:${PWD:-?} $) window:
chown root.root /system/bin/su
chmod 6755 /system/bin/su
chmod 644 /system/app/Superuser.apk
chown root.shell /system/xbin/busybox
chmod 755 /system/xbin/busybox
chmod 755 /system/app/
chmod 755 /system/bin/
chmod 755 /system/xbin/
Verify root access by installing "Root Checker".
Note: each time you reboot your device you will need to run Tomoyo Unlock script to regain root access (Step 8 - 12) which I re-wrote below:
8. Tomoyo Unlock
> adb shell
$ cat /data/local/tmp/p07dgetroot > /tmp/xsh
$ ls -l /tmp/xsh
-rw-rw-rw- shell shell xsh <--(you should see this)
WLAN ON / OFF / ON
$ ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
$ /tmp/xsh
/tmp/xsh
/tmp/.mem fd=3
read ret = 256
write ret = 256
At this stage, tomoyo is released
$rm /tmp/xsh
$cat /data/local/tmp/xsh > /tmp/xsh
WLAN ON / OFF / ON
$ls -l /tmp/xsh
-rwsr-sr-x root root xsh <--(you should see this)
$/tmp/xsh
$(precmd)[email protected]$HOSTNAME:${PWD:-?} $ <---(you should end up here to regain root access, if not redo it again)
Proof:

ask questions
hi,
If it unlocked the device of sim by docomo, when i root it, the condition of unlock sim whether will cancel????
---------- Post added at 12:10 AM ---------- Previous post was at 12:06 AM ----------
dear zyper95,
Can you make the picture to show the process of root??
thank a lot

Panasonic P-07D
Hello, Someone tell me how to reset to factory settings "Android system recovery -> wipe data / factory reset -> Yes-delete all user data -> Please input password". What is the password to be entered? Help please.

Panasonic Eluga Power P-07D hard reset plz:crying::crying::crying: