Database Info

[23/05] rooting the "Magic" - we have a root! [MODS?]

MODS - can you please move this thread to the sapphire development forum and stick it? thanks
_______________________________________________________________
WE HAVE A ROOT NOW
haykuro said:
GOT ROOT?
http://droiddeveloper.com/hrbuilds/boot-new.img.zip
1. download this, extract boot-new.img to your computer.
2. place your device into bootloader mode (BACK+POWER, or VOLUME DOWN+POWER)
3. fastboot boot boot-new.img
4. wait for device to boot
5. adb push boot-new.img /sdcard/boot-new.img
6. adb shell flash_image boot /sdcard/boot-new.img
that's it!
your device now has root via adb shell.
i'm making the rooted recovery.img now for magic
Click to expand...
Click to collapse

It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.

maxisma said:
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
Click to expand...
Click to collapse
Well, you see what I meant? all the expert are here!
Let's wait for Viper comment and/or ideas.

But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )

maxisma said:
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
Click to expand...
Click to collapse
I am far from being an expert but even if RC29 works and the DREAM test recovery works (which I doubt), it has no support for virtual keyboard, so right after he gets root he will need a hacked rooted ROM for the Magic. Isn't it safe to assume that until someone cook a special ROM for the Magic he is stuck with a rooted but unusable device?

A much bigger problem: how in the hell can you telnet in the Magic with no keyboard? Or even get past the setup wizard? In other words, even with RC29 there'll be no way to get root or even use the phone. This is gonna be a hell of a lot more difficult than it was for the G1(and it was pretty damn difficult for that)

Well, I guess HTC created this function for their reasons (tests etc.) and now it's only a matter of time until someone will find the way to do it too.
that's the reasone I posted the request, I seen things in XDA that i could never believe before, let's hope it'll happen again ...

Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.

chuazy said:
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
Click to expand...
Click to collapse
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.

[email protected] said:
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
Click to expand...
Click to collapse
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...

avimak said:
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
Click to expand...
Click to collapse
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.

[email protected] said:
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
Click to expand...
Click to collapse
Well, if external USB keyboard is the only thing it takes to root my device - I'll buy one, and root the rest of the Magic Israeli users for free

You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.

maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
I got it:
$ (I can write stuff)...
what next?

@avimak:
You mean, you've connected your magic with installed rc29?

maxisma said:
@avimak:
You mean, you've connected your magic with installed rc29?
Click to expand...
Click to collapse
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.

avimak said:
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
Click to expand...
Click to collapse
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.

maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.

[email protected] said:
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
Click to expand...
Click to collapse
Can you please write it again in simple words?
It's a bit "pro only" talking. I got my Android yesterday...

maxisma said:
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
Click to expand...
Click to collapse
There is an option to go back to the orig. version after the downgrade? can I "dump" my OS somewhere and Install it again from SPL if it failed the rc29?
I'm coming from WM - I'm speaking they lang...

[Q] HTC Sensation SIM restrictions / bootloader

Hello.
I know that it's very difficult to help other person is such complicated problems but I beg you for help, because I really need it.
So..
I rooted my HTC Sensation this way:
http://theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000/
I unlocked my device aswell.
And now I want to delete sim card restrictions and I simply can't!
My phone is S-ON.
The thing is - I was following this instruction:
http://forum.xda-developers.com/showthread.php?t=1232107
Method 1
When I'm entering "SU" command in Terminal Emulator I have error : /system /bin/SH Su not found.
(I installed SU! I have even root acces, what the?)
Method 2
I'm in Bootloader menu and after 2 seconds I have info that security bla bla bla and I can only reboot my device.
Help me, I have been doing this for 5 hours.
P.S
HBOOT 1.27.0000

Furionpl said:
Hello.
I know that it's very difficult to help other person is such complicated problems but I beg you for help, because I really need it.
So..
I rooted my HTC Sensation this way:
http://theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000/
I unlocked my device aswell.
And now I want to delete sim card restrictions and I simply can't!
My phone is S-ON.
The thing is - I was following this instruction:
http://forum.xda-developers.com/showthread.php?t=1232107
Method 1
When I'm entering "SU" command in Terminal Emulator I have error : /system /bin/SH Su not found.
(I installed SU! I have even root acces, what the?)
Method 2
I'm in Bootloader menu and after 2 seconds I have info that security bla bla bla and I can only reboot my device.
Help me, I have been doing this for 5 hours.
P.S
HBOOT 1.27.0000
Click to expand...
Click to collapse
Hi,
If your are hboot 1.27,you have to follow THIS

malybru said:
Hi,
If your are hboot 1.27,you have to follow THIS
Click to expand...
Click to collapse
Thank you sir I owe you.
But I can't do this, it has to be S-OFF.

Furionpl said:
Thank you sir I owe you.
But I can't do this, it has to be S-OFF.
Click to expand...
Click to collapse
Hi,
S-off is HERE and HERE

Furionpl said:
Thank you sir I owe you.
But I can't do this, it has to be S-OFF.
Click to expand...
Click to collapse
if you really want to do it then to S-OFF see here
http://forum.xda-developers.com/showthread.php?t=1614617

I simply cannot do this S-OFF.
Wire method made me angry, I was trying to do this for 2 hours, mostly 3.
Is there any other way to disable SIM card restrictions?
Without S-OFF.

Furionpl said:
I simply cannot do this S-OFF.
Wire method made me angry, I was trying to do this for 2 hours, mostly 3.
Is there any other way to disable SIM card restrictions?
Without S-OFF.
Click to expand...
Click to collapse
Check the sim unlock thread. Some people have been able to find the sim unlock code in the system its self. But if you cannot find it you will have to s-off.

I'm really sorry for bothering you, but about what method are you talking?
Can you link something?
I'm using search engine but I cannot find anything.

Furionpl said:
I'm really sorry for bothering you, but about what method are you talking?
Can you link something?
I'm using search engine but I cannot find anything.
Click to expand...
Click to collapse
i assume he is talking about this
http://forum.xda-developers.com/showthread.php?t=1232107

rzr86 said:
i assume he is talking about this
http://forum.xda-developers.com/showthread.php?t=1232107
Click to expand...
Click to collapse
Yes, thank you!
As I wrote in the first post I tried this method, but I have strange problem with it.
Method 1
(Using windows commands)
system/bin/sh: SU: Not found.
But my phone is rooted!
I'm sorry for spamming here, but I cannot write in that topic, I'm begging for your help.
And thanks for your support.

Furionpl said:
Yes, thank you!
As I wrote in the first post I tried this method, but I have strange problem with it.
Method 1
(Using windows commands)
system/bin/sh: SU: Not found.
But my phone is rooted!
I'm sorry for spamming here, but I cannot write in that topic, I'm begging for your help.
And thanks for your support.
Click to expand...
Click to collapse
maybe your su binary needs update check it
i can't think somethng else.i don't have any experience on this one

rzr86 said:
maybe your su binary needs update check it
i can't think somethng else.i don't have any experience on this one
Click to expand...
Click to collapse
I'm really confused right now, because I have latest SU....
Older one is not working with my HBOOT. 1.27.

Furionpl said:
I'm really confused right now, because I have latest SU....
Older one is not working with my HBOOT. 1.27.
Click to expand...
Click to collapse
hmm,
go to system/bin/sh
and check if you have that file(sh file)

rzr86 said:
hmm,
go to system/bin/sh
and check if you have that file(sh file)
Click to expand...
Click to collapse
I'm new on android, sorry for stupid question.
Where's the file explorer?
Or do you mean files on my SD card? (there is no folder called system on my SD)

Furionpl said:
I'm new on android, sorry for stupid question.
Where's the file explorer?
Or do you mean files on my SD card? (there is no folder called system on my SD)
Click to expand...
Click to collapse
no on sdcrad memory
go to internal memory
then system/bin/sh
use any file manager to access to internal storage

rzr86 said:
no on sdcrad memory
go to internal memory
then system/bin/sh
use any file manager to access to internal storage
Click to expand...
Click to collapse
Yes - I have this file.

Furionpl said:
Yes - I have this file.
Click to expand...
Click to collapse
open su app and see if terminal has root access

rzr86 said:
open su app and see if terminal has root access
Click to expand...
Click to collapse
I was trying this already but the only app that has root acces is Superuser...
I don't see any option to add terminal.

Furionpl said:
I was trying this already but the only app that has root acces is Superuser...
I don't see any option to add terminal.
Click to expand...
Click to collapse
if terminal is not listed for root access then probably it hasn't root access
try this
clean cache and data of terminal app and then delete it
then install it again
open it and enter su
see how it goes

rzr86 said:
if terminal is not listed for root access then probably it hasn't root access
try this
clean cache and data of terminal app and then delete it
then install it again
open it and enter su
see how it goes
Click to expand...
Click to collapse
Thank you, I did it.
But terminal method won't work for me, it shows date instead of unlocking code, I guess it's over for me.

[Q] Nexus 4 Toolkit - Error - rooting+busybox - File not found while choosing SuperSU

So here's the Problem: Using Nexus 4 Toolkit 2.3.8 I get an error when I try to root my phone and am at the point where the superuser method is chosen.
When I choose "2. SuperSU 1.69 by ChainFire [recommended]" I get the error: "Das System kann die angegebene Datei nicht finden. An Error Occured. Returning to Main Menu.." (The system wasn't able to find/locate the wanted file)
See the Screenshot here or in the attachment
hxxp://i.imgur.com/93G1H82.jpg
The UPDATE-SuperSU-v1.69.zip file is located at C:\Google_Nexus_4_ToolKit\root so that should be ok.
Any ideas?
Thanks in advance
(Maybe this Problem is too special or my translation is too bad (Using the German version) either way I couldn't manage to find a solution.)

I can't reply to the original Toolkit Developer Thread maybe someone can forward the question?
Otherwise it might get overlooked here.

[ROM][Deprecated]Lenovo Vibe Z - Rooted + Google Apps

Well, some of you might have had the same urge to buy one of these little wonder with almost the same data sheet than a LG G2 but with a Dual SIM functionality and at a much smaller price. If you are one of these crazy people that ordered their in China just like me, you might have the same disappointment that I felt when I finally received mine: the advertised SD Card slot is just a fantasy and all Google apps have been replaced by their Baidu counterparts. If the English language is indeed present in the Operating System, none of the installed application seems to understand this language. If you just don't speak Chinese just like me, you might end up wondering why on earth you bought a smartphone destined to Chinese people.
So I decided to turn this frustration into something positive and succeeded so I'm happy to bring you my home cooked ROM for the Lenovo K910. But first of all, the usual disclaimer:
Disclaimer
Don't hold me responsible if you brick your phone. This method have been successfully tested on mine but this is no guarantee for yours. You should obviously always have a backup of your data at all time if you're willing to install this ROM (or any other).
Safety measures
Like most Android phones, the Lenovo Vibe Z have many possibilities of recovery. I would advise you to be ready to apply at least this one:
Download the QSB file of your ROM (for example, mine is K910_SS_S_2_040_0039_131101.qsb). Google will point you to a Baidu site where it is downloadable
Put it in the folder /sdcard/SDFUSE/
Shut down your phone
Hold Volume Down and Power button for a few seconds
You end up in a menu with a "SD Card Update" entry. Move down to this entry using the Volume Down button then press ENTER or power button.
Make sure your ROM is available in the list
Cancel and reboot
If your QSB file is visible in the list, you should be pretty safe. If anything goes wrong, use the same method but apply the upgrade this time. Note that this method overwrite everything included your applications, SD Card, ...
What it is
The ROM I'm offering is:
An extract from K910_SS_S_2_040_0039_131101.qsb
Applying only to your system partition (your applications and data should be safe)
Rooted
Busybox-ed
Grossly freed from most vendor applications
Replaced by Google applications
What it is NOT
This was already some work to figure out how to reach that goal so it is not:
Bug free (I have at least observed a strange display glitch for the network icons which turn standard blue instead of Lenovo's white one)
A multi-language ROM
A ROM build from scratch like MIUI, Cyanogenmod, ...
A custom recovery (though this might come in a later stage)
...
Prerequisite
You should have installed:
K910 ADB Driver (available on the CD that appear when you connect the device)
ADB
Fastboot
Just check that your USB debug mode is enabled (in the USB Access Mode menu).
In any of these prerequisite is an issue for you, I'm ready to explain you further but you should also wonder if you are ready to go further because if anything goes wrong, you won't be able to properly act.
The installation
OK, enough talking, now some action. It is pretty simple actually:
Download the ROM and un-7zip it (mirroring in progress)
Reboot your phone in bootloader mode. Therefore, open a command prompt (no matter which OS you're using) and type:
Code:
adb reboot-bootloader
Now your phone is displaying the Lenovo logo
Check that you can access the system
Code:
fastboot devices
If fastboot just return displaying nothing, you might have to run in Administrator/root mode. Under Linux, I had to use sudo.
Unlock the bootloader (this should wipe all your data if it wasn't unlocked previously):
Code:
fastboot oem unlock
Flash the system:
Code:
fastboot flash system <path-to-file>system.img
Reboot:
Code:
fastboot reboot
That's all folks ! After your phone restarts, you should be able to use Google applications (though not all of them are there, at least the Play Store is allowing you to install the others).
What's next ?
I hope to be able to free some time to achieve these next steps:
Publish the script I wrote to extract content from Lenovo QSB files
Apply the same method to the last upgrade (K910_SS_S_2_040_0078_131203 ?). If you are lucky enough to have this version please contact me to see if you can provide the QSB file.
See if I can cook a custom recovery.
This is probably my very first participation to the community so I'll accept any comments as long as they are constructive :good:

Thanks!!!!!
Thank you so much, I'm crazy because I get the phone and to try, where is the link to download please??
Thanks again, you can post pictures?
---------- Post added at 04:44 PM ---------- Previous post was at 04:35 PM ----------
Another important question ... How did you rooteado?
What program did you use?
Thanks.
All need you help please.

I'll need just a few more hours since my upload just missed (I'm not sure why it only uploaded 437 Mb on the 659 Mb)
It will be for the first hours of 2014 (at least for me).

csu333 said:
I'll need just a few more hours since my upload just missed (I'm not sure why it only uploaded 437 Mb on the 659 Mb)
It will be for the first hours of 2014 (at least for me).
Click to expand...
Click to collapse
Thank you very much for your work, but you can tell us how you got to be root??

sakilxda said:
Thank you very much for your work, but you can tell us how you got to be root??
Click to expand...
Click to collapse
Probably in the most complicated way possible: I extracted the system partition from the upgrade file, mounted it in my Linux, put all the needed files and authorization then flashed it on my device.
I confirm that the file is now available but I need a few more messages before I can add the link. In the meanwhile, I can send it privately.

csu333 said:
Probably in the most complicated way possible: I extracted the system partition from the upgrade file, mounted it in my Linux, put all the needed files and authorization then flashed it on my device.
I confirm that the file is now available but I need a few more messages before I can add the link. In the meanwhile, I can send it privately.
Click to expand...
Click to collapse
Sure I get it, I also took little time here and leaves add links.
You could pass it private?
With your permission I'll share it on other sites of course directing people to this thread so they can see their creator and comment.
In several HTCMania we are waiting to receive the phone and while we're compiling everything.
Root on many threads where people are wanting to get and so far you're the only one.

I await your email with the link partner, and with your permission I'll share. A greeting.

sakilxda said:
Sure I get it, I also took little time here and leaves add links.
You could pass it private?
With your permission I'll share it on other sites of course directing people to this thread so they can see their creator and comment.
In several HTCMania we are waiting to receive the phone and while we're compiling everything.
Root on many threads where people are wanting to get and so far you're the only one.
Click to expand...
Click to collapse
As long as you don't ask money for it, feel free to share this as much as you want. My goal is sharing !
You should have received the link in the meanwhile. I'm also busy trying to mirror it on AndroidFileHost but it failed last time so just wait and see.

Latest ROM version release notes
By the way, here are the release notes of the next ROM (K910_SS_S_2_040_0078_131203).
What Google translate by:
Recommend
* Expand the system partition, a number of bug fixes
Update log
System
* Expand the system partition to 1.5G
* Boot and recovery signature added to the system
Show
* Fixed shutdown problem dialog scene mode switching
* Modify profile English translation error
* Adjust section shows the layout
Camera
* Pre-correction first picture black beauty
Click to expand...
Click to collapse
This means that next upgrade will most probably erase all the content of your phone (again) included your data and internal SD Card. This also means that flashing the first version of my custom ROM will make you "lose" 500 Mb, at least until a release based on the latest version of Lenovo's original ROM.
This also mean that:
Next Custom ROM upgrade won't be applicable to the not upgraded phone (you would be certain of bricking your phone)
You will lost 500 Mb worth of storage on your non expandable device
This isn't all good news ...

csu333 said:
As long as you don't ask money for it, feel free to share this as much as you want. My goal is sharing !
You should have received the link in the meanwhile. I'm also busy trying to mirror it on AndroidFileHost but it failed last time so just wait and see.
Click to expand...
Click to collapse
Thank you very much for sharing, of course I will not ask for money and in forums where I am at all costs to visit this thread.
csu333 said:
By the way, here are the release notes of the last ROM (K910_SS_S_2_040_0078_131203):
What Google translate by:
This means that next upgrade will most probably erase all the content of your phone (again) included your data and internal SD Card. This also means that flashing the first version of my custom ROM will make you "lose" 500 Mb, at least until a release based on the latest version of Lenovo's original ROM.
This also mean that:
Next Custom ROM upgrade won't be applicable to the not upgraded phone (you would be certain of bricking your phone)
You will lost 500 Mb worth of storage on your non expandable device
This isn't all good news ...
Click to expand...
Click to collapse
They are not good news. but I honestly what I need are 3 things:
1 Language Spanish, but we already you can not imagine not doing anything?
2 Root, to be able to use apps like Titanium Backup, Root Explorer, etc..
3 Very importantly, GAPPS (Play Store, Gmail), but of course in Spanish or English.
Your Rom has 2 I need and it is very important to me and very many users, it is a great job and the first to do so was you.
I do not mind losing 500mb, but I worry that the next official update is dangerous for us.
Thank you very much for sharing the link. If you write more answers in this thread at XDA have permission to put the link publicly, I think the requirement is 10 responses and almost have them.
---------- Post added at 12:28 PM ---------- Previous post was at 12:11 PM ----------
Apply the same method to the last upgrade (K910_SS_S_2_040_0078_131203). If you are lucky enough to have this version please contact me to see if you can Provide the QSB file.
You control by private (Because here I can not yet) a link to the version you want, I found on google, as I said I have not tested, I hope that this can do wonders lol
I also hope that I root Gapps and either Spanish or English: D

sakilxda said:
They are not good news. but I honestly what I need are 3 things:
1 Language Spanish, but we already you can not imagine not doing anything?
2 Root, to be able to use apps like Titanium Backup, Root Explorer, etc..
3 Very importantly, GAPPS (Play Store, Gmail), but of course in Spanish or English.
Click to expand...
Click to collapse
The few post I read about this are telling that it is close to impossible but I installed morelocale 2 on mine and it does add my language in the application that supports it.
Root is probably my top priority so it will stay available in the future releases
Play Store and GMail are present in the ROM and if you install morelocale 2, it will be in Spanish
sakilxda said:
You control by private (Because here I can not yet) a link to the version you want, I found on google, as I said I have not tested, I hope that this can do wonders lol
I also hope that I root Gapps and either Spanish or English: D
Click to expand...
Click to collapse
This is the link on Baidu I also found but for some reason, I can't flash it on my device so I can't cook it properly. I have to be able to flash it first

csu333 said:
The few post I read about this are telling that it is close to impossible but I installed morelocale 2 on mine and it does add my language in the application that supports it.
Root is probably my top priority so it will stay available in the future releases
Play Store and GMail are present in the ROM and if you install morelocale 2, it will be in Spanish
This is the link on Baidu I also found but for some reason, I can't flash it on my device so I can't cook it properly. I have to be able to flash it first
Click to expand...
Click to collapse
Of course, the priority is Root.
About the Gapps in Spanish or Englis, the could include a patch?
If not, do not worry that you use MoreLocale2.
I'll try to find more links ... it's a shame it does not work ...

The good news with root access is that you can do a lot of crazy things. For example, I'm starting to understand why it is so hard to get this upgrade thanks to a network dump:
Code:
POST /reaper/server/config2 HTTP/1.1
Host: fsr.lenovomm.com
Content-Length: 131
Content-Type: text/plain; charset=ISO-8859-1
Connection: Keep-Alive
User-Agent: Apache-HttpClient/UNAVAILABLE (java 1.4)
Config.2.1.2.imei.8628720201xxxxxxxxxxxxx
HTTP/1.1 503 Service Unavailable: [B][COLOR="Red"]Back-end server is at capacity[/COLOR][/B]
Content-Length: 0
Connection: keep-alive
That said, I'm sick of coming close to the end and receiving a connection time out

Patience friend, I do not really understand how you could do, but I'm sure you will. Good luck ...

sakilxda said:
Patience friend, I do not really understand how you could do, but I'm sure you will. Good luck ...
Click to expand...
Click to collapse
If I have latest version K910_SS_S_2_040_0109_131226 installed via ota update and push this system.img from previous version it's ok?
Really apreciate your work and hoping to be able to support you anyway. Keep working ! Respect.

katalinscrob said:
If I have latest version K910_SS_S_2_040_0109_131226 installed via ota update and push this system.img from previous version it's ok?
Really apreciate your work and hoping to be able to support you anyway. Keep working ! Respect.
Click to expand...
Click to collapse
This should work since the system it pretty much self contained but since I haven't tested it, I really can't be sure. Furthermore, this is a downgrade of your system.
If you have this version, could you check if you still have the image on your sdcard? This could be in folder /sdcard/lenovoota.

csu333 said:
This should work since the system it pretty much self contained but since I haven't tested it, I really can't be sure. Furthermore, this is a downgrade of your system.
If you have this version, could you check if you still have the image on your sdcard? This could be in folder /sdcard/lenovoota.
Click to expand...
Click to collapse
ok, here's the deal:
1. I tried to push system.img but no working, adb respond "failed: targed locked".
2. I don't have the ota file anymore BUT I have the K910_SS_S_2_040_0109_131226.qsb file. I poot this one in sdfuse folder and updated already before starting procedure with adb from above as you described, no problem just flashed it, btw it wipes everything.
So, my opinions:
1. Locked target issue could be determined by the bootloader beeing locked? Don't we need to unlock it somehow?
2. Can you reinsert root and gapps in this newer version K910_SS_S_2_040_0109_131226.qsb file?
3. How do you decompiled .qsbfile ?
Waiting for your feedback asap.
Respect.
Obs:
- we can use android-aio-flasher just to substitute from working with cmd commands... just sayin', works for me.
- reboot in recovery command doesn't work, just adb reboot bootloader, then lenovo logo appears.
- correct command for pushing system.img is adb fastboot flash system path to system.img.

katalinscrob said:
ok, here's the deal:
1. I tried to push system.img but no working, adb respond "failed: targed locked".
Click to expand...
Click to collapse
Just to be sure, is it an answer from adb or fastboot?
katalinscrob said:
2. I don't have the ota file anymore BUT I have the K910_SS_S_2_040_0109_131226.qsb file. I poot this one in sdfuse folder and updated already before starting procedure with adb from above as you described, no problem just flashed it, btw it wipes everything.
Click to expand...
Click to collapse
This is great news! Do you have any way of posting ithe QSB somewhere?
katalinscrob said:
So, my opinions:
1. Locked target issue could be determined by the bootloader beeing locked? Don't we need to unlock it somehow?
Click to expand...
Click to collapse
I had nothing to do but I did restart a few time with a custom boot.img that I never actually flashed. Maybe this helped?
katalinscrob said:
2. Can you reinsert root and gapps in this newer version K910_SS_S_2_040_0109_131226.qsb file?
Click to expand...
Click to collapse
I sure will!
katalinscrob said:
3. How do you decompiled .qsbfile ?
Click to expand...
Click to collapse
I wrote a script for that purpose. I have to clean it a bit before I can publish it but I'll definitely do it.
katalinscrob said:
Obs:
- we can use android-aio-flasher just to substitute from working with cmd commands... just sayin', works for me.
- reboot in recovery command doesn't work, just adb reboot bootloader, then lenovo logo appears.
- correct command for pushing system.img is adb fastboot flash system path to system.img.
Click to expand...
Click to collapse
You are right. I didn't know about android-auto-flasher, probably because I'm running Linux (which made my task easier to cook the ROM since the system partition can be mourned like any other).
I edited my first post with your correction and the link since I have now 10 messages on the board !

Well who are finding out that important things. Hopefully soon have new developments. I keep watching your work. I hope that more and more we are, I have put in all the sites I've found this link for more developers to come.

csu33 said:
This is great news! Do you have any way of posting ithe QSB somewhere?
Click to expand...
Click to collapse
I have it. please contact me in PM

[Q] Device Encryption of Huawei G750 and alternatives

Hey Guys,
I have a Huawei G750 and really LOVE it!
As I am using it for business as well, I have a connection to an exchange server.
By now my Administrator told me to enable device encryption or else I'll loose access to the exchange server and can#t use my phone for business purposes anymore.
As I had to notice, the G750 currently does not include encryption settings...
I had a call regarding that topic with Huawei support and they were wondering as well.
Now I am looking for an app oign exactly the same, Android does with device encrption.
Does anyone of you have ever heard about such an app?
File- or Appencryption is not enough!
Thank you all in advance!
Alex

Enkhiel said:
Now I am looking for an app oign exactly the same, Android does with device encryption.
Click to expand...
Click to collapse
Hi Alex!
I think this is not trivial as Android encrypts the whole /data partition. You have to make really deep changes to the system to do exactly the same and you would certainly end up with the same implementation.
I think you first have to find out if there is really no encryption feature in your ROM. From the Huawei support I would expect that they can tell you if this is actually the case! Maybe someone in the forum has also some more experience with the absence of the encryption feature in manufacturer-ROMs?
Some more points that come into my mind:
- Do you even see the option to activate encryption in the settings?
- You have to choose PIN or password as unlocking method for your phone. Otherwise encryption can't be enabled.
- Did you root your phone? Can you try to activate encryption via terminal or ADB? Here is the command you have to execute as root:
Code:
/system/bin/vdc cryptfs enablecrypto inplace YOURPASSWORD

bastei said:
Hi Alex!
I think this is not trivial as Android encrypts the whole /data partition. You have to make really deep changes to the system to do exactly the same and you would certainly end up with the same implementation.
I think you first have to find out if there is really no encryption feature in your ROM. From the Huawei support I would expect that they can tell you if this is actually the case! Maybe someone in the forum has also some more experience with the absence of the encryption feature in manufacturer-ROMs?
Some more points that come into my mind:
- Do you even see the option to activate encryption in the settings?
- You have to choose PIN or password as unlocking method for your phone. Otherwise encryption can't be enabled.
- Did you root your phone? Can you try to activate encryption via terminal or ADB? Here is the command you have to execute as root:
Code:
/system/bin/vdc cryptfs enablecrypto inplace YOURPASSWORD
Click to expand...
Click to collapse
Hey bastei,
thank you for all your work!
Yep, I had some phone calls with Huawei and those option really does not exist.
As I have a connection to exchange already, I use a screen lock with PIN.
I checked Storage and Security screen several times to really be sure not overseeing anything :victory:
Regarding ADB I only have a Windows 8 Client from my employer where USB connection does not really work with ADB-drivers.
Can I run
a) that command in something like a dry-run to clearify if this option exists without really encrypting
b) that command from root terminal directly on my phone?
BTW: Yep, it's rooted.
Attached have a look at the mail from Huawei:
[...] Die Telefonverschlüsselung ist aktuell leider nicht in die Software des Huawei Ascend G750 implementiert. Natürlich gehen wir davon aus, dass diese in Kürze durch ein Performance Update nachgereicht wird. [...]
Click to expand...
Click to collapse
[...]Sadly the mobile-phone-encryption currently is not implemented within G750 software. Of course we expect to have a ???Performance Update??? delivered to fix that issue
Click to expand...
Click to collapse
Best regards,
Alex

Enkhiel said:
Yep, I had some phone calls with Huawei and those option really does not exist.
Click to expand...
Click to collapse
Yeah, I think you have no chance then... Maybe sometime Huawei will deliver their "Performance Update" or someone will build a custom ROM for your phone...
Enkhiel said:
a) that command in something like a dry-run to clearify if this option exists without really encrypting
Click to expand...
Click to collapse
Execute
Code:
/system/bin/vdc cryptfs enablecrypto
It should respond with
Code:
cryptfs enablecrypto <wipe|inplace> <passwd>
Enkhiel said:
b) that command from root terminal directly on my phone?
Click to expand...
Click to collapse
Yes, you can execute it on the phone. Make shure to run it as root (execute "su" beforehand).

imagefoxy.com/2Yh
Click to expand...
Click to collapse
Looks good, eh?
Seems like they just forgot to add a GUI-Button :cyclops:
Will that encrypt Internal AND external storage?
Cheers,
Alex

Enkhiel said:
Looks good, eh?
Click to expand...
Click to collapse
So far, yes. But I don't know what exactly they "didn't implement". So you have to try if that will do the trick.
Enkhiel said:
Will that encrypt Internal AND external storage?
Click to expand...
Click to collapse
The standard Android encryption feature will only encrypt /data (internal storage).
Do you have a custom recovery installed? Use it to make a backup before you try to encrypt.

bastei said:
So far, yes. But I don't know what exactly they "didn't implement". So you have to try if that will do the trick.
The standard Android encryption feature will only encrypt /data (internal storage).
Do you have a custom recovery installed? Use it to make a backup before you try to encrypt.
Click to expand...
Click to collapse
Tried to encrypt today but sadly it doesnt work..
Running /system/bin/vdc cryptfs enablecrypto inplace *** as root leads into a new line "200 0 -1"
To bad it's not working as I can't connect to exchange anymore :crying::crying:

Tried MailWise Mail-Client and Xposed do trick out Exchange, without any success as well...
Seems like a lost battefield