Database Info

Does anyone have the proper file to get QuickBoot working?

I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?

The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.

What does this do? does it make recovery stick?

watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.

TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?

Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.

Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.

any update to this?
thanks

joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?

I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!

I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets

I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762

watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks

[How to] [Linux] Root Hboot 2.02

For anyone having issues with running this in linux.
I used zikronix guide and modified it for use in a linux support thread. The original thread can be found here:
http://forum.xda-developers.com/showthread.php?t=829045
This is my setup:
-I made sure to show my .bashrc profile and path to my tools folder if you needed help getting that setup as well... If not please ignore.
Code:
[email protected]:~$ cat .bashrc | grep adb
alias start-adb='sudo /usr/local/android-sdk/tools/./adb start-server'
alias kill-adb='sudo /usr/local/android-sdk/tools/./adb kill-server'
[email protected]:~$ cat .bashrc | grep android-sdk
export PATH="/usr/local/android-sdk/tools/:${PATH}"
[email protected]:~$ $PATH
bash: /usr/local/android-sdk/tools/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
Download: http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
Download (Mirror): http://sdx-downloads.com/EVO/devs/jerdog/fixes/hboot202-s_off-V6.2.zip
Now This might make things easier.
-I have this so that you are in the same enviroment that i was in so that the paths will be the same.
Code:
wget http://www.wackynoodle.com/hboot202-s_off-V6.2.zip
mkdir Evo-root
mv hboot202-s_off-V6.2.zip
cd Evo-root
unzip hboot202-s_off-V6.2.zip
- This step I just made sure that adb devices showed my device. If not get it working.
- Once adb devices showed my device properly, I simply ran the following commands.
Code:
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
adb push root/amon_ra.img /sdcard/
- Then this is just changing permissions. Pretty straight forward.
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
chmod 0755 /data/local/flash_image
- Running the script. Should kick you out of adb... If not after 5 min kill the adb server and restart.
Code:
adb shell
./data/local/tmp/rageagainstthecage
- Now you should see a "#", if you do proceed. If not then run the script above again till it works.
Code:
adb shell
- If you saw that "#" run this. This can only be ran as root "#" means root.
Code:
./data/local/flash_image misc /sdcard/mtd-eng.img
Now you are going to want to reboot into the bootloader. Make sure once you do that you selet bootloader and let the PC36IMG.zip load.
Code:
reboot bootloader
After that is done reboot into the new rooted rom. Then make sure adb works again. Then run the following commands. Make sure you terminal is in the same directory this entire time there is no reason to leave the direcory we went into earlier "cd Evo-root" You directory should always be Evo-root. Thanks. The part that I found out was the second command where the entire recovery/ needed the permissions changed to be executable. As you saw in my post on that forum board.
- This will remove the PC36IMG.zip to a different name so that the bootloader won't get confused again. Then the second commands makes the directory executable recursivly. Then the third will reboot you into recovery.
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-ENG.zip
chmod -R +x recovery/
adb reboot recovery
- Now this is going to be done at the recovery screen. As long as you followed the steps above it will work fine. Should only take you about 20 mins to root this phone. Though it took me about 2 hours since no one else has been rooting using linux. I am thinking about writing a script that will root everything and alls you have to do is follow a terminal guide.... But ill see.
- Just run these commands that will allow you to flash the unrevoked-forever.zip. Once you follow the onscreen instructions of the unrevoked-forever.zip you will be able to reboot into the recovery and see the S-Off. Once that is done reboot into the rom, now we need to flash a custom recovery!
Code:
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
- Again make sure your terminal was never closed and in the same folder. Then simply run these commands to flash the Amon_ra recovery. Since it has wimax capabilities I prefer it.
Code:
adb push root/flash_image /data/local/
adb shell
chmod 0755 /data/local/flash_image
./data/local/flash_image recovery /sdcard/amon_ra.img
reboot recovery
Now you should see the custom recovery and you should be able to flash any rom you desire!

reserved for later use

i see that they are same commands as the pc.., so would this also work with PC?

nickespi said:
i see that they are same commands as the pc.., so would this also work with PC?
Click to expand...
Click to collapse
I am guessing your talking about windows? Sure make sure adb is in your path. Though there are steps in here that are only for linux.

95% success
Well I want to thank you for this thread
It has worked for me I have root I have NAND unlocked
I can flash ROMs
The only issue I have is my radio/baseband and PRI version have been lowered
I have not been able to get thise back where they whould with either update or by using teh wimax.ADDRESS.tree.xml fix (there is no file with that)
If you have any ideas how to fix this would be much appreciated
I am unable to get higher tahn baseband 1.36.00.04.02 in ant rom
when I got teh phone it was 2.15.00.xx.xx
any help would be appreciated

100% Success
THANK YOU
My Evo
Hardware 004
Build 3.30
Hboot 2.02
Baseband 2.15.xx.xx
is now sucessfully rooted.
I did have some problems after being able to flash ROMs of not haveing PRI and Baseband updated.
On thread #787756 there are downloads that can be flashed to fix this problem if anyone else is in that boat.
zikronix sent me there for the fix...I believe he is adding it to the main thread but if it isn't there yet I wanted to add it now for anyone in my boat.
Again this method works and there is success.
Happy rooting

Hey thanx for this Linux guide. Does this steps work with the update 12.25.10 on the windows thread?
Will you update this guide?

[UPDATED]how to root 1.47.161.2 hboot 002 (and possibly others)

sorry about all the updates i am trying to remember as i go along with the help of the comments below, we will get this working as i know it does
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1178912
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions pressing enter at the end of each step
(big thanks to Jorgen2009 for cleaning up the instructions)
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. reboot the phone with the cable attached to the computer
6. adb shell (this gives a $-prompt)
7. /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (when everything is OK you'll go back to your own prompt, not the phones)
8. adb shell (you'll have a #-prompt now, cause the the is temp-rooted)
9. /data/local/tmp/misc_version -s 1.27.405.6
10. install the earliest RUU version you can find. I used RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed
11. after rebooting your phone has the old HBOOT (0.98.0000)
12. enable USB Debugging (Settings - Applications - Development) and reboot the phone again
13. Run the AlphaRevX binary and don't install the CWM recovery, we'll use 4EXTRecovery lateron
congratulations, your phone is now S-OFF!
download the latest EXT4Recovery from here
adb reboot bootloader
fastboot flash recovery [PATH TO recovery.img]
fastboot reboot-bootloader
go to the recovery and install any ROM you like
hope this helps everyone.
as usuall not my fault, brick yadda yadda
credit to sethario, the fre3vo dev team and Jorgen2009

davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
as usuall not my fault, brick yadda yadda
Click to expand...
Click to collapse
Brilliant and well done. .
could you please add exactly which 1.47 version that you achieved this on and from which country.
also get this useful thread added to the INDEX sticky thread that we have be either PM' ing threads OP or adding post in that Thread.
Sent from my HTC Desire S using XDA Premium App

ben_pyett said:
Brilliant and well done. .
could you please add exactly which 1.47 version that you achieved this on and from which country.
also get this useful thread added to the INDEX sticky thread that we have be either PM' ing threads OP or adding post in that Thread.
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
not sure exactly what 1.47 as its gone now but as i said in my post im on a vodafone uk if that helps
also just to make it clear, none of this is my own work guys a lot brighter than me figured all the hard stuff out, i just fitted the different bits together

davidreece said:
not sure exactly what 1.47 as its gone now but as i said in my post im on a vodafone uk if that helps
also just to make it clear, none of this is my own work guys a lot brighter than me figured all the hard stuff out, i just fitted the different bits together
Click to expand...
Click to collapse
All the same, Putting the bits together, writing the guide and having the balls to try all of these steps on your own device is worthy of thanks and just a little praise
Sent from my HTC Desire S using XDA Premium App

thanks ben just glad to put something back instead of leeching all the devs hard work all the time

Thanx davidreece, great find!
Unfortunately it's not working for me I get stuck at point 5 running the fre3vo binary. I waited 20 minutes for it to complete, but it's still saying "please wait" with a blinking cursor. For the record, I'm using this rom: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed. That could be the problem perhaps.
I also noticed that the the fre3vo link from your article is a bit older then the fre3vo version on the fre3vo thread. Of course i tried that one too, but it gives the same result for me
Any ideas?
Cheers

not a clue jorgen sorry i should maybe add the words "some"
just a thought when you ran the fre3vo command where you in adb shell or at the command prompt >, i seem to remember it happened to me the first time i tried it but i cant remember how i got it wrong, ithink you have to enter the adb shell command first then enter /data/local/tmp/fre3vo next or it may be enter them both together as one line i cant really remember, i was so surprised it worked if anyone else gets this to work could you please clarify the fre3vo steps and i will update the main post thanks, hope this helps, also i only used the link version not any newer one

davidreece said:
not a clue jorgen sorry i should maybe add the words "some"
just a thought when you ran the fre3vo command where you in adb shell or at the command prompt >, i seem to remember it happened to me the first time i tried it but i cant remember how i got it wrong, ithink you have to enter the adb shell command first then enter /data/local/tmp/fre3vo next or it may be enter them both together as one line i cant really remember, i was so surprised it worked if anyone else gets this to work could you please clarify the fre3vo steps and i will update the main post thanks, hope this helps, also i only used the link version not any newer one
Click to expand...
Click to collapse
I tried both methods, both with the same result. It's great to see however it worked for you. It means there is at least a possibility to get S-OFF on updated devices

jorgen2009 said:
I tried both methods, both with the same result. It's great to see however it worked for you. It means there is at least a possibility to get S-OFF on updated devices
Click to expand...
Click to collapse
really sorry i falsly got your hopes up, maybe ask in the fre3vo forum maybe im just getting it wrong, it was 4am here when i succeeded so its all a bit hazy

jorgen2009 said:
Thanx davidreece, great find!
Unfortunately it's not working for me I get stuck at point 5 running the fre3vo binary. I waited 20 minutes for it to complete, but it's still saying "please wait" with a blinking cursor. For the record, I'm using this rom: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed. That could be the problem perhaps.
I also noticed that the the fre3vo link from your article is a bit older then the fre3vo version on the fre3vo thread. Of course i tried that one too, but it gives the same result for me
Any ideas?
Cheers
Click to expand...
Click to collapse
Eureka i have updated the instructions jurgen also redownload my fre3vo link just in case it was different, i knew i had to do something else, please let me know if it works now

I remember seeing in the original fre3evo thread there was a series or range of hex addresses to try if the first default one didn't achieve root
Sent from my HTC Desire S using XDA Premium App

I am stuck on instructions step 5. it says unable to chmod -debug: No such file or directory. My Bootloader version is 0.98.0002. In my understanding instructions step 5 is confusing as first i wrote it with step 4 and then i realize that first write adb shell chmod 777 etc etc. Am i doing right?

maroof.saeed said:
I am stuck on instructions step 5. it says unable to chmod -debug: No such file or directory. My Bootloader version is 0.98.0002. In my understanding instructions step 5 is confusing as first i wrote it with step 4 and then i realize that first write adb shell chmod 777 etc etc. Am i doing right?
Click to expand...
Click to collapse
sorry maroof not sure whats wrong maybe ask in the original thread linked at the 1st post

maroof.saeed said:
I am stuck on instructions step 5. it says unable to chmod -debug: No such file or directory. My Bootloader version is 0.98.0002. In my understanding instructions step 5 is confusing as first i wrote it with step 4 and then i realize that first write adb shell chmod 777 etc etc. Am i doing right?
Click to expand...
Click to collapse
Hello, you're right there appears to is a slight mistake above, from my understanding of this the commands they should be entered as I've shown below from your PC within a command shell window with a <RETURN> at the end of every line.
Code:
C:\Program Files\Microsoft Support Tools> [B]adb shell [/B]
$ [B]chmod 777 /data/local/tmp/fre3vo[/B]
$ [B]chmod 777 /data/local/tmp/misc_version[/B]
$ [B]/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF[/B]

davidreece said:
sorry maroof not sure whats wrong maybe ask in the original thread linked at the 1st post
Click to expand...
Click to collapse
Thanks for the reply but the thing is that am i doing the right way as i wrote in my last thread that first i mix 4th step and fifth but then i realize and did the same as in 4th step? If its right then offcourse i 'll ask someone in the original thread.

davidreece said:
Eureka i have updated the instructions jurgen also redownload my fre3vo link just in case it was different, i knew i had to do something else, please let me know if it works now
Click to expand...
Click to collapse
That did the trick!! I'm running Saga LBC Mod as we speak!! The steps I followed after downloading the bits from the first post for this were the following:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
reboot the phone with the cable attached to the computer
adb shell (this gives a $-prompt)
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (when everything is OK you'll go back to your own prompt, not the phones)
adb shell (you'll have a #-prompt now, cause the the is temp-rooted)
/data/local/tmp/misc_version -s 1.27.405.6
install the earliest RUU version you can find. I used RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
after rebooting your phone has the old HBOOT (0.98.0000)
enable USB Debugging (Settings - Applications - Development) and reboot the phone again
Run the AlphaRevX binary and don't install the CWM recovery, we'll use 4EXTRecovery lateron
congratulations, your phone is now S-OFF!
download the latest EXT4Recovery from here
adb reboot bootloader
fastboot flash recovery [PATH TO recovery.img]
fastboot reboot-bootloader
go to the recovery and install any ROM you like
Big thanx again to David!

glad it worked, i knew it was in there somewhere is it ok if i add your instructions to the first post to save confusion

@david
Of course it is, let the S-OFF-ing begin (again)

jorgen2009 said:
That did the trick!! I'm running Saga LBC Mod as we speak!! The steps I followed after downloading the bits from the first post for this were the following:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
reboot the phone with the cable attached to the computer
adb shell (this gives a $-prompt)
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (when everything is OK you'll go back to your own prompt, not the phones)
adb shell (you'll have a #-prompt now, cause the the is temp-rooted)
/data/local/tmp/misc_version -s 1.27.405.6
install the earliest RUU version you can find. I used RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
after rebooting your phone has the old HBOOT (0.98.0000)
enable USB Debugging (Settings - Applications - Development) and reboot the phone again
Run the AlphaRevX binary and don't install the CWM recovery, we'll use 4EXTRecovery lateron
congratulations, your phone is now S-OFF!
download the latest EXT4Recovery from here
adb reboot bootloader
fastboot flash recovery [PATH TO recovery.img]
fastboot reboot-bootloader
go to the recovery and install any ROM you like
Big thanx again to David!
Click to expand...
Click to collapse
all worked well but while installing RUU_Saga_HTC_Europe_1.28.401.1. Its gives an error saying CUSTOMER ID Error. Now what

maroof.saeed said:
all worked well but while installing RUU_Saga_HTC_Europe_1.28.401.1. Its gives an error saying CUSTOMER ID Error. Now what
Click to expand...
Click to collapse
are you using the exe version of the ruu, if you are maybe try making your sdcard into a gold card

Slight problem unrooting

Hi all,
I've done a search and not found anything that has helped. Long story short I think I have flashed the wrong stock image to my Nexus S so that I can get a warranty repair done.
The problem I am having is that my bootloader seems to be frozen and I cannot use fastboot to flash cwm again to install the stock nandroid that I found in the FAQ. The phone can boot normally and I can use adb but cannot do anything in the bootloader. I've also tried using adb to push the recovery to data but get a permission denied error.
Any helps guys as its kinda urgent.

FirmShark said:
Hi all,
I've done a search and not found anything that has helped. Long story short I think I have flashed the wrong stock image to my Nexus S so that I can get a warranty repair done.
The problem I am having is that my bootloader seems to be frozen and I cannot use fastboot to flash cwm again to install the stock nandroid that I found in the FAQ. The phone can boot normally and I can use adb but cannot do anything in the bootloader. I've also tried using adb to push the recovery to data but get a permission denied error.
Any helps guys as its kinda urgent.
Click to expand...
Click to collapse
What error are you getting in fastboot? You're on the fastboot screen and not trying to access the recovery, right?
Make sure you clean your phone of CWM recovery too before sending to warranty.

polobunny said:
What error are you getting in fastboot? You're on the fastboot screen and not trying to access the recovery, right?
Make sure you clean your phone of CWM recovery too before sending to warranty.
Click to expand...
Click to collapse
I boot into the bootloader and I cannot select any options on the menu, it appears frozen. "Fastboot devices" brings up no devices at all. ADB works when the phone is booted normally. Also it is on the stock recovery so I cannot flash the stock nandroid image that is available. I have got myself into a proper dilemma with it. Believe it or not I have been quite successful with rooting and flashing in the past but this has me puzzled.
I think it is down to the stock image I flashed which was Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader for the i9020a. I was always under the impression I had the i9020a as that's the ota updates I had used since I got the phone.
If I can get fastboot working again then I can flash cwm and restore the nandroid and get myself back to stock. Then I can re-lock the bootloader.

FirmShark said:
I boot into the bootloader and I cannot select any options on the menu, it appears frozen. "Fastboot devices" brings up no devices at all. ADB works when the phone is booted normally. Also it is on the stock recovery so I cannot flash the stock nandroid image that is available. I have got myself into a proper dilemma with it. Believe it or not I have been quite successful with rooting and flashing in the past but this has me puzzled.
I think it is down to the stock image I flashed which was Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader for the i9020a. I was always under the impression I had the i9020a as that's the ota updates I had used since I got the phone.
If I can get fastboot working again then I can flash cwm and restore the nandroid and get myself back to stock. Then I can re-lock the bootloader.
Click to expand...
Click to collapse
So if I get this straight:
-Booting into fastboot you cannot move your cursor using vol + or vol - (?)
-You cannot access recovery, which is stock
-You can use your phone but cannot do anything requiring SU permissions (not rooted)
-You are on stock ROM
-Device is unlocked
Is everything right?

-Booting into fastboot you cannot move your cursor using vol + or vol - (?)
Yeah that's what happens.
-You cannot access recovery, which is stock
I can reboot using adb to get to it. Recovery is stock.
-You can use your phone but cannot do anything requiring SU permissions (not rooted)
I can use my phone but cannot make/recieve calls or send/recieve sms. Wifi works however.
-You are on stock ROM
I am on stock 2.3.6.
-Device is unlocked
Device is unlocked.
Hopefully that clear's it up a bit. Beginning to worry about my phone now

Hi!
If ADB work , you can root your devices then you can change stock recovery with CWM 5.0.2.0 or......

How so? I don't know of a way to change the recovery using adb. I only know how to using fastboot which isn't working.

FirmShark said:
How so? I don't know of a way to change the recovery using adb. I only know how to using fastboot which isn't working.
Click to expand...
Click to collapse
If ADB work it's very easy....
You can changed by installing Rom Manager with root acces and rerwrite recovery with CWR....after that you can install all what you want...

Can you tell me how then as I can't find how to do it???

FirmShark said:
Can you tell me how then as I can't find how to do it???
Click to expand...
Click to collapse
ok
You must do exactly as I say and you will see that it is not hard ... it will root your phone

Yes, what are the instructions?

you need that : http://www.4shared.com/file/7wJht93f/Root.html
unpack in your pc...and waitt me...for detail...
it's not virus...I can help you ....
waitt me 5 min .....

I have downloaded the file.

if you are ready....let's go...
connect your device and see if adb responding >adb devices
normal you will see your id device or un number...and tell me
---------- Post added at 11:52 PM ---------- Previous post was at 11:52 PM ----------
FirmShark said:
I have downloaded the file.
Click to expand...
Click to collapse
ok just unpack

adb is working fine and my device is present.

FirmShark said:
adb is working fine and my device is present.
Click to expand...
Click to collapse
click cmd
>adb push files\zergRush /data/local/tmp/
>adb shell
#chmod 777 /data/local/tmp/zergRush
#exit
---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------
>adb shell
#./data/local/tmp/zergRush
WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)

done that, now what?

>adb push files\busybox /data/local/tmp/
>adb shell
#chmod 755 /data/local/tmp/busybox
#exit
>adb shell
#/data/local/tmp/busybox mount -o remount,rw /system
#dd if=/data/local/tmp/busybox of=/system/xbin/busybox
#chown root.shell /system/xbin/busybox
#chmod 04755 /system/xbin/busybox
#/system/xbin/busybox --install -s /system/xbin
#rm -r /data/local/tmp/busybox
#exit
>adb push files\su /system/bin/su

done that now. what do i do now?

>adb shell
#chown root.shell /system/bin/su
#chmod 06755 /system/bin/su
#rm /system/xbin/su
#ln -s /system/bin/su /system/xbin/su
#exit
>adb push files\Superuser.apk /system/app/
>adb shell
#cd /data/local/tmp/
#rm *
#exit
>adb reboot
ALL DONE!!!
now instal ROM Manager for ClockWordMod Recovery

Ulefone Power Armor 13 Root

I want to root my phone and remove any bloatware. Can I do this with a stock A11 or custom Rom and still have the cameras and infrared range finder work properly? Does anyone know of any ROMs built specifically for the Power Armor 13?

Use the "temporary ROOT" method, will say put a matching SU-binary into phone's /data/local/tmp directory and then by means of ADB
make use of it:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
adb shell "chmod 0677 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<COMMAND-WHAT-REQUIRES-SUPERUSER-RIGHTS-HERE>'"

jwoegerbauer said:
Use the "temporary ROOT" method, will say put a matching SU-binary into phone's /data/local/tmp directory and then by means of ADB
make use of it:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
adb shell "chmod 0677 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<COMMAND-WHAT-REQUIRES-SUPERUSER-RIGHTS-HERE>'"
Click to expand...
Click to collapse
Thank you. I didn't know there was such a thing as a temp root. Do you have any advise on getting a ompatible rom for my hardware?

jwoegerbauer said:
Use the "temporary ROOT" method, will say put a matching SU-binary into phone's /data/local/tmp directory and then by means of ADB
make use of it:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
adb shell "chmod 0677 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c '<COMMAND-WHAT-REQUIRES-SUPERUSER-RIGHTS-HERE>'"
Click to expand...
Click to collapse
Hi,
Can you please give me a hand with the method you mentioned?
1. the SU binary should be the supersu binary as zip file or the folder from the zip file?
2. could you please give me an example of how this string would look like if the file was for example in partition C?
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp
I tried patching the boot image with Magisk and using ADB to install it but the phone is stuck on the start screen .
Thanks in advance!

I managed to root the phone permanently. However, I accidentally formatted the NVRAM partition. Could someone send me one?

Any updates?

FutureCrusader said:
Any updates?
Click to expand...
Click to collapse
I managed to do it quite easily. I will make a detailed tutorial this week.

denis9rafael said:
I managed to do it quite easily. I will make a detailed tutorial this week.
Click to expand...
Click to collapse
Thanks, appreciate it, mine is coming in this week so excellent timing lol

denis9rafael said:
I managed to root the phone permanently. However, I accidentally formatted the NVRAM partition. Could someone send me one?
Click to expand...
Click to collapse
Use the MauiMETA aka ModemMETA 10.2124.0
The software can restore your IMEIs but you need know How use that.

lopestom said:
Use the MauiMETA aka ModemMETA 10.2124.0
The software can restore your IMEIs but you need know How use that.
Click to expand...
Click to collapse
Because I messed up the first time I did it and had to format all with SP FlashTool, I had to restore the IMEI. I will post instructions on that too.
If you root with Magisk the boot image, it will put it in a reboot loop. I found on another forum a file that you have to flash first via adb.
It took me a week and reinstalling the software 5 times before I managed to find all I needed . Now it takes 10 minutes max to set it up.

FutureCrusader said:
Thanks, appreciate it, mine is coming in this week so excellent timing lol
Click to expand...
Click to collapse
I have created a complete guide on how to permanently root the phone using Magisk.
Please find it below:
How to root Ulefone Power Armor 13! Now with TRP recovery and Magisk included
Hello, Below is a guide on how to root Ulefone Power Armor 13 using Magisk, changing/restoring IMEI etc. Before you continue, I take no responsibility for any bricked devices. *Note: Before you begin, make sure you install the latest software...
forum.xda-developers.com