Hi There!
There is a distinct lack of a place where owners of the T790 can discuss mods/technical problems/roms/etc anywhere on the web. So I have set up this thread for some discussion around this phone. I'll update this thread with links to Nandroid Backups and verified working roms when they become available :laugh: .
Root Access: http://www.kingoapp.com/
Working CWM: http://v790.blogspot.com.au/2013/06/recovery-for-zte-v790.html
Working TWRP: https://docs.google.com/file/d/0BwY7fOHbQ0_FVmx6VzlOSHQwaWc/edit
Stock Nandroid Backup (Un-Verified) (Credit to @piersoar/brick007123): Here
Stock TWRP Backup (Credit to @piersoar): Here
^ None of the above works are mine, they are links to the creator's external sites for instructions and downloads.
Thanks :silly:
Keep up the work!
Great post. Cheers fellow OzBargainer. :good:
Chipotleez said:
Hi There!
There is a distinct lack of a place where owners of the T790 can discuss mods/technical problems/roms/etc anywhere on the web. So I have set up this thread for some discussion around this phone. I'll update this thread with links to Nandroid Backups and verified working roms when they become available :laugh: .
Click to expand...
Click to collapse
Custom Recoveries & Stock NANDroid
Thanks Chipotleez for this thread. We have much to learn about the T790 (Telstra Pulse) / B790 (Boost Tango) device!
The link to the NANDroid dump above contains a carriage return & doesn't work. I'm too new to post the correct one or upload it here on XDA. Will PM updated link to Chipotleez.
It was made on a rooted but otherwise unchanged ZTE T790 using Online Nandroid Backup.
Note: this has been compressed (7-zip) to save space and will need to un7zipped before use.
In my experience both the Custom Recoveries from the V790 fail to mount DATA (MTD6) and SDCARD partitions on the T790. This means they cannot generate a complete NANDroid backup, and will probably also fail to restore one. Keen to be proven wrong.
Haven't been able to open up the recovery images (yet) to see why they're failing, but suspect different partition sizes &/or locations than the V790 which must be a close cousin, but not identical.
Keep sharing! Cheers.
piersoar said:
Thanks Chipotleez for this thread. We have much to learn about the T790 (Telstra Pulse) / B790 (Boost Tango) device!
The link to the NANDroid dump above contains a carriage return & doesn't work. I'm too new to post the correct one or upload it here on XDA. Will PM updated link to Chipotleez.
It was made on a rooted but otherwise unchanged ZTE T790 using Online Nandroid Backup.
Note: this has been compressed (7-zip) to save space and will need to un7zipped before use.
In my experience both the Custom Recoveries from the V790 fail to mount DATA (MTD6) and SDCARD partitions on the T790. This means they cannot generate a complete NANDroid backup, and will probably also fail to restore one. Keen to be proven wrong.
Haven't been able to open up the recovery images (yet) to see why they're failing, but suspect different partition sizes &/or locations than the V790 which must be a close cousin, but not identical.
Keep sharing! Cheers.
Click to expand...
Click to collapse
Hmmm, perhaps we could make a port of CM or sorts based on the material in the Nandroid Backup. However I doubt ZTE release any kind of kernel or OS sources....
Root is worth it alone to get rid of the bloatware Also getting Xposed framework and BusyBox is great!
Had to send my ZTE off with my HTC Desire X to Fonebiz for repair. I've sent my broken stuff to them tonnes in the past, but I'll let you all know how well they repaired a ZTE device.
Thanks
Chipotleez said:
...So I have set up this thread.....
Click to expand...
Click to collapse
You Sir, Are a gentleman and a scholar :good:
---------- Post added at 08:13 PM ---------- Previous post was at 08:07 PM ----------
Can confirm working Root with Cydia Impactor: http://www.cydiaimpactor.com/
I've got some playing around with rooting & stripping bloat from the T790 documented here: http://www.techthreads.com.au/2014/04/titanium-backup-make-your-device-useful.html
deathbypizza said:
You Sir, Are a gentleman and a scholar :good:
---------- Post added at 08:13 PM ---------- Previous post was at 08:07 PM ----------
Can confirm working Root with Cydia Impactor: http://www.cydiaimpactor.com/
I've got some playing around with rooting & stripping bloat from the T790 documented here: http://www.techthreads.com.au/2014/04/titanium-backup-make-your-device-useful.html
Click to expand...
Click to collapse
On an unrelated note, I have got to say, this phone makes a brilliant Chromecast companion...
I just use it by my TV to stream stuff to the big screen
Chipotleez said:
Had to send my ZTE off with my HTC Desire X to Fonebiz for repair. I've sent my broken stuff to them tonnes in the past, but I'll let you all know how well they repaired a ZTE device.
Thanks
Click to expand...
Click to collapse
hiya mate! any news on the repair? i'm stuck with the stock recovery, can't do a thing with it.
Much Apreciated. However...
So basically I came across these 2 ZTE T790's in a Cash Converters for $30 and its a half hobby to unlock them and half so I can sell them/give to family
Now so far I managed to Root it (cydia impactor), then install recovery and finally install a custom Rom form the ztev790support.wordpress.com website. (Also were I got the recovery).
I managed to install the recovery after downloading terminal emulator and running it as admin.
"su" then
"flash_image recovery /sdcard/recovery.img"
That was almost too easy.
However. The problem is with the ROM. You see the ZTE V790 Rom is built for a Dual SIM phone and not on the T790 Network's wont register. Everything else is fine as far as I can tell.
Please let me know if you can find a "stock" rom of the (T)790 preferably unlocked or unlockable. Or does anyone know of a Modded ROM?
Also, Does anyone need some help with this Phone? If so please let me know I came across many different things.
Firefox OS Running on a ZTE T790 (Telstra Pulse)
Details here:
http://forum.xda-developers.com/firefox-os/general/firefox-os-running-zte-t790-telstra-t2987108
elkedra said:
Details here:
http://forum.xda-developers.com/firefox-os/general/firefox-os-running-zte-t790-telstra-t2987108
Click to expand...
Click to collapse
Hi guys. I am the owner of ZTE V790 dual-sim phone 512Mb-RAM, 512Mb-ROM. I looked up FireFoxOS, which works on your phone and i can say that it is exactly the same works for me. T790 and V790 share the same platform-ROAMER2, and it looks like the ROMs for my phone should also work on your. I managed to build the CyanogenMod11 for my phone but there are a few small bugs. I certainly can't guarantee that everything will work fine, but if anyone wants to, you can try this out for yourself. For registration to Network: Menu Settings > > SIM cards > OperatorSettings > "and tap the radio-button"
It may well be that many will not work at your device, then you can try to replace the files in the CM11 archive to files from your phone from this list except Adreno200 blobs, and then flash it again. Sorry for my English.
I don't quite understand what you are saying
manfromnn said:
Hi guys. I am the owner of ZTE V790 dual-sim phone 512Mb-RAM, 512Mb-ROM. I looked up FireFoxOS, which works on your phone and i can say that it is exactly the same works for me. T790 and V790 share the same platform-ROAMER2, and it looks like the ROMs for my phone should also work on your. I managed to build the [] for my phone but there are a few small bugs. I certainly can't guarantee that everything will work fine, but if anyone wants to, you can try this out for yourself. For registration to Network: Menu Settings > > SIM cards > OperatorSettings > "and tap the radio-button"
It may well be that many will not work at your device, then you can try to replace the files in the CM11 archive to files from your phone from [] except Adreno200 blobs, and then flash it again. Sorry for my English.
Click to expand...
Click to collapse
0
Hi there, I don't quite understand your post, are you saying you installed the Mod (unofficial) and it worked fin on your ZTE (T)790? because I flashed it on one of mine and I still could not pickup a Sim/Reception
I had the same problem with V790 rom's on my T790. SIM wouldn't register (although I didn't do the Settings thing that manfromnn posted).
phillipdi said:
0
Hi there, I don't quite understand your post, are you saying you installed the Mod (unofficial) and it worked fin on your ZTE (T)790? because I flashed it on one of mine and I still could not pickup a Sim/Reception
Click to expand...
Click to collapse
elkedra said:
I had the same problem with V790 rom's on my T790. SIM wouldn't register (although I didn't do the Settings thing that manfromnn posted).
Click to expand...
Click to collapse
No, at me V790, and this ROM worked for me fine, but only first sim.
If I'm not mistaken, the T790 is also dual-sim phone?
Try to replacing this files:
Code:
# RIL & misc
system/bin/bridgemgrd
system/bin/port-bridge
system/bin/qmiproxy
system/bin/sapd
system/bin/netmgrd
system/bin/ATFWD-daemon
system/bin/qmuxd
system/bin/radish
system/bin/rild
system/bin/rmt_storage
system/lib/libauth.so
system/lib/libaudioeq.so
system/lib/libcm.so
system/lib/libdiag.so
system/lib/libdsi_netctrl.so
system/lib/libdsm.so
system/lib/libdss.so
system/lib/libdsutils.so
system/lib/libgsdi_exp.so
system/lib/libgstk_exp.so
system/lib/libidl.so
system/lib/libmmgsdilib.so
system/lib/libnetmgr.so
system/lib/libpbmlib.so
system/lib/libqc-opt.so
system/lib/libqdi.so
system/lib/libqdp.so
system/lib/libqmiservices.so
system/lib/libqmi.so
system/lib/libqueue.so
system/lib/libril-qc-1.so
system/lib/libril-qc-qmi-1.so
system/lib/libril-qcril-hook-oem.so
system/lib/libril.so
system/lib/libSimCardAuth.so
system/lib/libwms.so
system/lib/libwmsts.so
From your phone into the zip with CM.
And flash it again.
It has one SIM only
It has only one sim, which Is what makes it cheaper, and I suggest is giving me these issues.
What do I replace those files in the zip with?
phillipdi said:
It has only one sim, which Is what makes it cheaper, and I suggest is giving me these issues.
What do I replace those files in the zip with?
Click to expand...
Click to collapse
Oh, if so, first you need to fix the lines in the system/build.prop:
Code:
persist.radio.multisim.config = dsds
persist.dsds.enabled = true
in this way:
Code:
# persist.radio.multisim.config = dsds
# persist.dsds.enabled = true
Maybe that will be enough
Okay, I will give it a shot
manfromnn said:
Oh, if so, first you need to fix the lines in the system/build.prop:
Code:
persist.radio.multisim.config = dsds
persist.dsds.enabled = true
in this way:
Code:
# persist.radio.multisim.config = dsds
# persist.dsds.enabled = true
Maybe that will be enough
Click to expand...
Click to collapse
Okay I will give it a shot, thanks
This is the line's I have in the build.prop
"#persist.radio.multisim.config=dsds
#persist.radio.dont_use_dsd=true"
What do they need to be changed to??
phillipdi said:
This is the line's I have in the build.prop
"#persist.radio.multisim.config=dsds
#persist.radio.dont_use_dsd=true"
What do they need to be changed to??
Click to expand...
Click to collapse
You need to write the # in front lines:
persist.radio.multisim.config = dsds and
persist.dsds.enabled = true
In the file manager editor, save and restart the phone
If it will not help, then you need to take files, which I wrote above, from your phone, and put them instead of the files inside of archive with ROM (do not need extract the archive), and at the same time you can fix those lines in the file build.prop Then try to flash again.
Alas no avail
I have tried and tried but still no respite, I have the feeling I am doing wrong.
I eventually paid to get the phones unlocked, I was wondering if there was a way to find out the Algorithm by using the IMEI number
and the code given?
Would it be possible?
Now on the one I got unlocked the 3G data works but when someone calls me it goes straight to voicemail.
I reset the phone multiple times but nothing.
I am thinking the OS is stuffed.
In my attempts to unlock the phone on the cheap I used a universal sim card unlocker, it worked on both phone for only one day before the registration failed, they have always been a bit 50/50 on these matters. Weird.
My brother just bricked his T790 (Telstra Pulse) and he did not backup... I got him into CWM but nandroid backup link in OP no longer works, anyone have or can make me a stock nandroid backup so i can recover his phone?
Thanks,
Kriogenic
Sent from my SM-G130H using XDA Free mobile app
Related
There is now a super thread over here with this root information and some more recoveries. I plan on expanding as more things are developed for the Rugby Pro.
I have added other hacks to this thread below the root download links. Enjoy.
The below guide outlines how to gain root on the Samsung Galaxy Rugby Pro (SGH-I547 ATT / Bell (Yes, Canada works!) / commanche). Please read through the full guide before attempting to root your device.
You will need ODIN v3.04 in order to gain root on the Rugby Pro (comanche), I will not post a link due to the nature of the package. Google has plenty of links for it.
BIG thanks to utkanos for all the help and making this a reality
Install instructions -- goldenlederhosen has provided some further information and detail about the below procedure here
Please read his post as well as the instructions before attempting this procedure
Install drivers from link below
Download necessary packages (clockwork recovery, root update) from the links below
Copy root update to your devices sdcard(s) -- Copy to both if external SD card is present
Charge phone to at least 80%
Power off the phone
Unplug from USB / Charger
Boot into download mode (Home + Volume Down + Power)
When asked if you want to continue, press Volume Up to enter download mode
Plugin phone and
Launch ODIN
Check the checkbox next to "PDA"
Click the PDA button
Select the comanche_cwr_6015_utkanos.tar.md5 file
Make sure only "Auto Reboot" and "F. Reset Time" are selected
Click start
Your phone will reboot one the flash is complete
You now have Clockwork Recovery, continue with the steps to get root
Power off your phone
Unplug from USB / Charger
Boot into Clockwork Recovery (Home + Volume Up + Power -- Release when Samsung logo appears)
Select "Install zip from sd card"
Select "Choose zip from sd card"
Navigate to zip
Select zip
Confirm
Reboot
You should now have root
I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous, may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met with a dead device. Consider yourself warned
I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix, or have information that should be added let me know and I will update the necessary information.
Download Links
Head over to the super thread here (link) for links.
CWR Touch / ODIN
Courtesy of childrenofthehorn there is a now a Clockwork Recovery Touch and ODIN images for the ATT varient. The thread is: http://forum.xda-developers.com/showthread.php?t=1990519
Rootz Wiki Forum
childrenofthehorn has gotten a dedicated forum setup over at Rootz Wiki. Check it out: http://rootzwiki.com/forum/556-galax...o-development/
Works like a charm!
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
dweide9 said:
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
Click to expand...
Click to collapse
Thank you much for the donation
Would you be willing to pull an image of the stock boot partition (dd if=/dev/block/mmcblk0p7) and PM me a link?
Also: check the OP, I've added some info on how to get tethering (after rooting) without the need for a dedicated ATT tethering plan.
re: post-root stuff
>Would you be willing to pull an image of the stock boot partition (dd >if=/dev/block/mmcblk0p7) and PM me a link?
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
>Also: check the OP, I've added some info on how to get tethering (after rooting) without >the need for a dedicated ATT tethering plan.
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
dweide9 said:
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
Click to expand...
Click to collapse
You can copy the contents of boot by:
Install a terminal emulator from the market
Launch terminal
su
Accept request for root
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/mmcblk0p7_boot.img
Transfer mmcblk0p7_boot.img to your favorite cloud storage provider
Share link
If you run into trouble or have any questions let me know.
dweide9 said:
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
Click to expand...
Click to collapse
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2
boot partition image
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
So what fun stuff can you do with this file & how would my image be any different then yours? Or is it another issue, like uploading being restricted because you're a developer?
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
kemonine96 said:
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Click to expand...
Click to collapse
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
dweide9 said:
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
Click to expand...
Click to collapse
Thanks for the file. I just finished pulling it.
dweide9 said:
So what fun stuff can you do with this file
Click to expand...
Click to collapse
I plan on using a stock boot image so I can put together an ODIN image that will flash the phone back to a stock state. If you root your phone or have a custom recovery / system / boot OTA updates will generally fail to apply. The best way to get an OTA update applied is to rollback to stock and install the OTA.
dweide9 said:
how would my image be any different then yours?
Or is it another issue, like uploading being restricted because you're a developer?
Click to expand...
Click to collapse
The boot partition should be the same across devices unless you make modifications.
I had to blindly update the boot partition on my device to get root, so I do not have an un-changed copy of it. In order to get an OTA update applied and to work with some Cyanogen / Clockwork Recovery stuff I will need a clean boot partition image.
dweide9 said:
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
Click to expand...
Click to collapse
I worked with a few people to get help putting together an ODIN image that allowed me to get custom recovery and the clockwork recovery update.zip. There is no general guide on the steps necessary.
If you are interested in diving into the custom rom / recovery stuff I will be doing some work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully working on a Cyanogenmod 10 (JellyBean) port in the future. I am working on some items for the Rugby Smart (apache) at present, as soon as that stuff is taken care of I'll be focusing more on the Rugby Pro (commanche). If you are interested in taking a shot at updating the clockwork recovery for the commanche let me know and I can maybe point you in a few directions to get you going.
stuff
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
dweide9 said:
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
Click to expand...
Click to collapse
I pulled that package as well. Unfortunately it is only the GPL components they are required to release, not the full ROM sources. It does contain the kernel sources which will be very helpful down the line.
dweide9 said:
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Click to expand...
Click to collapse
There is a lot of testing work and guess/check for the ROM building stuff. I was thinking of setting up an IRC channel on FreeNode for discussing work on the device. Would you be interested / willing to move some of the interactive discussion over there once I have a channel setup?
dweide9 said:
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
Click to expand...
Click to collapse
Keep me in the loop. I tend to only tether for the purpose of my tablet when I'm not near a WiFi AP. I wanted to point it out just in case, better to have it working before it's necessary.
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
IRC channel on FreeNode is setup: #rugby-pro-dev for those that are interested.
Motorhead1991 said:
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
Click to expand...
Click to collapse
I think we should be covered at the moment. The first priority will likely be getting a recovery nailed down and 100% before working on a customized kernel. I'm hoping to get recovery nailed sooner than later so we can do things like nandroid and similar before starting in on CM10 or another ROM.
I am also working on the Rugby Smart (apache) CM9/3.0 Kernel/CM10 stuff as well so my time with the Pro is limited at the moment. Hopefully the Smart stuff moves quickly so I can loop back around to the Pro quickly.
>I pulled that package as well. Unfortunately it is only the GPL components they are >required to release, not the full ROM sources.
Ah, learn something new every day.
>I was thinking of setting up an IRC channel on FreeNode for discussing work on the >device. Would you be interested / willing to move some of the interactive discussion >over there once I have a channel setup?
Sure, I already monitor #opennic on freenode, so I can just open another channel.
kemonine96 said:
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
Click to expand...
Click to collapse
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
MCKINLEC said:
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
Click to expand...
Click to collapse
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
kemonine96 said:
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
Click to expand...
Click to collapse
Thanks, but I made a backup copy, Think the issue could be because it was deleted instead of frozen?
ETA, help, donation etc
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
@kemonine96 et.al.:
When do you think a beta CM port will be ready?
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
goldenlederhosen said:
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
Click to expand...
Click to collapse
You are not alone in that sentiment. I won't run a device I know won't receive a CyanogenMod port. The good news is as long as there is root, CyanogenMod can be made to work.
goldenlederhosen said:
When do you think a beta CM port will be ready?
Click to expand...
Click to collapse
"Soon". Myself and a couple others are working on a set of changes for the Rugby Smart (predecessor to the Pro) and once they are further along I will be looking into starting the CyanogenMod port for the Pro.
goldenlederhosen said:
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Click to expand...
Click to collapse
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
goldenlederhosen said:
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
Click to expand...
Click to collapse
As much as I may appreciate a donation, please hold off as I cannot commit to working on CyanogenMod for the Pro in a paid capacity I am comfortable with. I am working 50-60 hour work weeks at my day job so my free time is severely limited. I have every intention on bringing CyanogenMod to the Pro but it is a free time problem more than anything else.
Foreign anglopu
kemonine96 said:
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
Click to expand...
Click to collapse
Okay, will do.
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
Have tried Bin4ry v18 and another script but they didn't work.
The phone has JB 4.1.1. The Kernel is 3.4.0 dated Dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
Thanks for any help or advice.
Is now rooted, read on..
garyo said:
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
...
Thanks for any help or advice.
Click to expand...
Click to collapse
Me too. I've spent probably 6 hours today messing around with the 1.8 version script, on both windows 7 and Linux. It always fails the same place, with mount permission denied ... are you root?
I have other issues with the G9300 that I'd like to tackle, like WiFi range, but digging in requires root access. Here's hoping somebody smarter than I can find a way to root this thing.
wseverin said:
Me too. I've spent probably 6 hours today messing around with the 1.8 version script, on both windows 7 and Linux. It always fails the same place, with mount permission denied ... are you root?
I have other issues with the G9300 that I'd like to tackle, like WiFi range, but digging in requires root access. Here's hoping somebody smarter than I can find a way to root this thing.
Click to expand...
Click to collapse
Same here. I need root to build a custom CWM recovery.
Anyone has rooted phone that can help rip out the rom?
..
Finally. I've rooted my HDC G9300.
See my post in another thread here:
http://forum.xda-developers.com/showthread.php?t=1886460&page=165
My phone is now nicely rooted with no problems. But it's not an easy process.
wseverin said:
See my post in another thread here:
http://forum.xda-developers.com/showthread.php?t=1886460&page=165
My phone is now nicely rooted with no problems. But it's not an easy process.
The tutorial isn't clear about how to run Android Kitchen. In the Android Kitchen folder is a script called 'menu' that has to be executed by cygwin. Launch cygwin first with the .bat file in its install folder. Then, navigate to the 'menu' script. Hint: '/cygdrive/c/<path to Android Kitchen>/menu'
Nowhere does the tutorial say to copy 'Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip' onto your sd. You will want to do that before beginning the final recovery step.
Click to expand...
Click to collapse
Its great you figured out a root method, and thanks for sharing it :good:
I have just run through it on my phone and all has gone well until I got to where mobileuncle tools flashes the recovery.img. It needs Superuser access to do that and I don't have it. I am thinking it must be something to do with the Menu script you mentioned. How to you run that script? What is the command for it?
Thanks for any help!
Sounds like you're 95% there
garyo said:
I have just run through it on my phone and all has gone well until I got to where mobileuncle tools flashes the recovery.img. It needs Superuser access to do that and I don't have it. I am thinking it must be something to do with the Menu script you mentioned. How to you run that script? What is the command for it?
Thanks for any help!
Click to expand...
Click to collapse
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
wseverin said:
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
Click to expand...
Click to collapse
Finally, you rooted the phone. Do you think you could upload the rom somewhere? Others can just download it and flash without going through the entire process. Good Job!!
wseverin said:
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
Click to expand...
Click to collapse
Hi - Yes you are right, I have created the recovery.img and transferred it to the phone.
Thanks for the tip that I don't need to use mobileuncle.. So I have booted up into CWM and have the su-superuser-busybox zip on my sd card. Trouble is CWM doesn't recognise the sd card and says E: unknown volume. That is strange because android sees it fine when the phone starts.
I am still wondering if my problem is from the the android kitchen part. I wasn't able to run android kitchen. I think I better run through the process again. How did you bring up the 'menu' in kitchen? I ran cygwin first and then navigated to kitchens path and used /menu and also ./menu but just got an error message. Even dumped all of kitchens files into cygwins root directory in case I had messed up the navigation path but still got the same error message whenever I tried to run menu. How did you get it to run please?
Thanks for your help :fingers-crossed:
GT35pro said:
Do you think you could upload the rom somewhere? Others can just download it and flash without going through the entire process.
Click to expand...
Click to collapse
I have uploaded the recovery.img that I created here. Remember, because it works on my phone is no guarantee that it won't break yours. You use it solely at your own risk. Also, you will still need to use CWM to install the su+superuser+busybox zip from your sd.
Next problem - no 3G
Having the phone rooted, I've gone on to the next problem that has no ready solution.
That is, no 3G. I use the AT&T network in the USA. AT&T uses WCDMA on 850MHz and 1900MHz for their 3G service. The HDC G9300+ doesn't support WCDMA at 1900MHz, which is the band that AT&T uses most. Where I am (Phoenix AZ) there is only 1900MHz service, which means that I can't get any 3G. Only 2G "Edge".
The problem *might* be remedied through software - or maybe not. If the MTK6577 radio doesn't support 1900MHz in some hardware sense, then the game is over. But I doubt that for two reasons. First, from a marketing standpoint, the AT&T network is too big to just ignore when designing a generic platform like the MTK6577. Second, from a hardware standpoint, the transceiver frequencies are synthesized from one base oscillator through a set of on-chip frequency multipliers and dividers. If the MTK6577 can generate frequencies in the 2100MHz band it can almost surely generate frequencies in the 1900MHz band. What's required is a software driver that properly sets the multipliers and dividers.
My bet is that somewhere out there in the world there is a software driver for the phone's radio that can set the chip to work in the 1900MHz band.
Can somebody find that driver so that we can bundle it into a ROM for this phone? Or a tool to adjust the driver that's bundled with the phone?
Please tell me
garyo said:
has anyone got a root method that works for the hdc galaxy s3 g9300?
Have tried bin4ry v18 and another script but they didn't work.
The phone has jb 4.1.1. The kernel is 3.4.0 dated dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
thanks for any help or advice.
Click to expand...
Click to collapse
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
wseverin said:
I have uploaded the recovery.img that I created here. Remember, because it works on my phone is no guarantee that it won't break yours. You use it solely at your own risk. Also, you will still need to use CWM to install the su+superuser+busybox zip from your sd.
Click to expand...
Click to collapse
Thanks for uploaded your recovery file. I thought I would try that before going through the process of redoing mine. This time it kicked straight into CWM without any sdcard errors, so was able to install the zip file. It is now nicely rooted and has been running for several hours, and as yet I have found no problems.
Great job and thanks for sharing your knowledge :good:
joneswilson02 said:
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
Click to expand...
Click to collapse
http://www.fastcardtech.com/goods.php?u=53399&id=8113
First time I purchased from them, found them very good and had no problems. Took about 15 days to get it. Considering there were xmas & new year holidays at the time it was pretty good.
How to root your HDC Galaxy S3 G9300+
For those wanting to root their HDC Galaxy S3 G9300+ phones follow these steps;
Download wseverin's 'recovery.img' from post #10.
Download my 'MT6577_Android_scatter_emmc.txt', 'su+superuser+busybox.zip', 'SP_Flash_Tool_v3.1224.01.rar' and 'MT657x_USB_Win7_Driver.zip' files that I have attached to this post.
Install the USB drivers to your computer if you don't already have them.
Copy the su+superuser+busybox.zip file to your phones SD Card.
Run Flash Tool (Flash_tool.exe) in administrator mode.
Load my scatter file.
Next, backup your original recovery file (This is very important in case something gets messed up) Do this using the 'Read-Back' function. Select Hex and enter 0x1588000 for Start Address and 0x600000 for Length. Before clicking the Read Back button, shutdown your phone and remove the battery and USB cable. Next click Read Back, plug in the USB cable and replace the battery (But do not switch the phone on) The software will backup the file and come up with an OK window if successful.
Next flash your phone with wseverin's recovery.img. Do this from the Download tab in Flash Tool and tick the Recovery option. Before pushing the Download button you will also need to shutdown the phone, remove the battery and USB cable as above.
Next start the phone holding the volume-up + power buttons. This will boot the phone into CWM. Choose 'Install zip from sdcard', then 'choose zip from sdcard', navigate to the su+superuser+busybox.zip file and select yes to install it.
That's it! So easy!!
If you followed the steps correctly, after you reboot the phone it should have root access.. However, be warned that your phone could be bricked if something goes wrong or your phone is a different model, so do this at your own risk and backup your original first!
PS: thanks to wseverin for the modded recovery file and being the 1st to root this phone.
joneswilson02 said:
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
Click to expand...
Click to collapse
Do I detect a hint of cynicism?
It seems to be a decently built phone. The display is good; actually better resolution than many competing models. Fit and finish are as good as you'll get anywhere. The capacitive touch screen is just fine. GPS, WiFi, and Bluetooth all work well except that the WiFi range is a bit anemic. Software is pretty much standard Android Jelly Bean. I consider it worth what I paid for it, especially since I am not about to spend 3X that for a cell phone. Oh, and it actually makes and receives phone calls!
help me
Help me please, i've bricked my g9300+.
i need a rom.zip to flash with recovery or complete rom to flash with spflashtool.
help me!!!!
bersarak said:
Help me please, i've bricked my g9300+.
i need a rom.zip to flash with recovery or complete rom to flash with spflashtool.
help me!!!!
Click to expand...
Click to collapse
How do you have brick your phone?
With the garyo's guide?
Thanks
I have a G9300+ and I want to root it
root Star G9300+
garyo said:
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
Have tried Bin4ry v18 and another script but they didn't work.
The phone has JB 4.1.1. The Kernel is 3.4.0 dated Dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
Thanks for any help or advice.
Is now rooted, read on..
Click to expand...
Click to collapse
Hello,
First of all, please excuse my english...
I have a Star G9300+ smartphone with the same JB 4.1.1, same kernel (3.4.0 dated Dec 3 2012), same build number (e1920_v77_zlh_9p017_asx_20121203) than yours, but 1Gb RAM memory.
Could I use the same method to root my smartphone? How much RAM have yours?
Thanks!
xnicks said:
Hello,
First of all, please excuse my english...
I have a Star G9300+ smartphone with the same JB 4.1.1, same kernel (3.4.0 dated Dec 3 2012), same build number (e1920_v77_zlh_9p017_asx_20121203) than yours, but 1Gb RAM memory.
Could I use the same method to root my smartphone? How much RAM have yours?
Thanks!
Click to expand...
Click to collapse
Yes mine is also 1Gb RAM. I have read that HDC and Star are the same, however I don't know this for sure. This is where I purchased my phone;
http://www.fastcardtech.com/goods.php?u=53399&id=8113
Does yours look the same??
If yours looks the same you could always try it I suppose, but make sure you backup your phones entire ROM first. That way you can reinstate the original in case it doesn't work.
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://dl.dropboxusercontent.com/u/91693945/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Appreciate the guide, hope it helps someone down the road. I'm in the camp that has no issues going back and forth between AOSP 4.3 or TW. I'll add this Rootz link as well which provides some additional information and might be making its way into roms via Github. Seems like as good an opportunity to spread the wealth.
Zophone i5 v8?
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
***MY FIX***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
shailendrachimade said:
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
Click to expand...
Click to collapse
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Will Try
papp-david said:
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Click to expand...
Click to collapse
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
shailendrachimade said:
Let me try..thanks!
Click to expand...
Click to collapse
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Thank you. I also had this problem with any aosp ROM but the fix stopped working for me with the kk ROMs did you have the same problem?
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
remzej said:
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.. Bit could you explain a little more?
evertking said:
Thanks for the reply.. Bit could you explain a little more?
Click to expand...
Click to collapse
shailendrachimade said:
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Click to expand...
Click to collapse
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://www.dropbox.com/s/bt1ucpgb9xfmjbi/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Try the One+ One or AOSP modded cameras in the Apps and Themes section. One+ One camera is awesome!
Ahmadqatei said:
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Click to expand...
Click to collapse
Link fixed, sorry I don't really keep up with this anymore, my bad
fix front camera
work for my mtk device
edit builtprop, open the editor and change or add
hw.cameras=1
ro.camera.dcim=1
explanation
# hw cameras
hw.cameras = 2 (1 only for the Front, 2 for the Front & Back)
# camera DCIM dir. 0: sd only; 1: nand only; 2, sd first
ro.camera.dcim = 1
This is likely to occur due to the use of internal memory is converted into ROM
while the external sdcard memory is converted into internal
hopefully work
:cyclops:
Just sharing:
flashing didn't work, used servicely and added camera service to hitlist.
can i use it on galaxy core
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
I personally Tested this
Attention if you try this and end up with a brick or your device transforms and tries to destroy you; it's not my fault you did this not me. So just read all of this thread not just the O.P (and read the O.P more then once) to get out of a bind if you reply with "the thread is too long i wont read it please help" don't expect anything short of "there's a search bar use it"
Okay well now, you must be on ZV5 in order to use this system.img
since we of the Boost LG G Stylo don't have the privilege of TWRP because of a pesky locked bootloader and now real way around it....i have edited and tested this stock ZV5 System.img
the things it comes with is Busybox installed (you still need to download the app)
Viper4Android working without having to disable SELinux
rooted and debloated (for the most part)
edited build.prop
Make sure you have a Windows PC
Download the LG Drivers from here
Download this rooted-ZV5-system.img
Place downloaded img to your external SD via adapter or through your phone
Now place SD back into your phone
Reboot your device into download mode
Download this folder and unzip it to your desktop:
Run ports.bat from within the extracted folder, to find your correct port (use the one with: LGVZANDNETDIAG1)
In the LG_Root folder hold shift and right click and choose open command windows here
Type
Code:
Send_Command.exe \\.\COM3
(Make sure your COM port number is correct, it varies)
Type
Code:
dd if=/storage/external_SD/rooted-ZV5-system.img bs=8192 seek=42816 count=327680 of=/dev/block/mmcblk0
you will see a flashing _ line instead of the # let it do it's thing you will know it finished when the # shows back up
Type
Code:
LEAVE
and press enter and let your device reboot
Will this work on the Sprint model?
Ellli said:
Will this work on the Sprint model?
Click to expand...
Click to collapse
It's possible...
Also is there a way for me to make a system.img if I want to go back and recover it?
Ellli said:
Also is there a way for me to make a system.img if I want to go back and recover it?
Click to expand...
Click to collapse
Yes there is but I'm away from my computer at the moment i will give you the command to pull the system.img for sprint tomorrow at the earliest
Ok thanks
V2 change-log Xposed Framework, Deodexing doesn't want to work sadly
Haven't uploaded yet tho
Will this work with metro pcs?
darrick505 said:
Will this work with metro pcs?
Click to expand...
Click to collapse
in theory yes but i wouldn't chance it
Nice. Good Job man. This little phone is finally startin to hum along...thanks for ALL your work!!:good:
Hello Has anyone flashed this on the sprint version?
Thank you
Thank you
Working great so far, was finally able to get some system space cleaned up and truely uninstall bloatware. Now I'm just working on the right sd card format to get Link2SD working.
kwa1dan said:
Working great so far, was finally able to get some system space cleaned up and truely uninstall bloatware. Now I'm just working on the right sd card format to get Link2SD working.
Click to expand...
Click to collapse
use ext 4 and name it sd-ext
Thanks thats what I went with a few hours ago, worked just fine ive been linking the apps through Link2SD now.
Is there an actual features list? I see you said debloated and build.prop edits, I was just wondering what it was exactly that was removed and what edits you did? I just used your root method today on my boost stylo 5.1.1 and it went perfectly! I want to use this too, but don't want to mess anything up. DO I need to factory reset or anything first? Or do I just follow the instructions in the OP? Thanks for all your hard work dude.
EDIT: Did you ever upload V2? Should I just use your guide for adding xposed? There probably isn't much different than a stock img I am guessing?
Rharker85 said:
Is there an actual features list? I see you said debloated and build.prop edits, I was just wondering what it was exactly that was removed and what edits you did? I just used your root method today on my boost stylo 5.1.1 and it went perfectly! I want to use this too, but don't want to mess anything up. DO I need to factory reset or anything first? Or do I just follow the instructions in the OP? Thanks for all your hard work dude.
Click to expand...
Click to collapse
I'll add that in a bit
When I updated to this Rom it came with my mobile data not working. Is there a way I can fix it again? Any build.prop edits can make it work again? Please help me.
MonstaSaleens said:
When I updated to this Rom it came with my mobile data not working. Is there a way I can fix it again? Any build.prop edits can make it work again? Please help me.
Click to expand...
Click to collapse
really?....hmmmm.....when downloading did the download get interrupted at all?
6th_Hokage said:
really?....hmmmm.....when downloading did the download get interrupted at all?
Click to expand...
Click to collapse
No I don't believe so. If it did would it have flashed successfully? Are there any tricks to get it working again? It havnt been working for about a month now.
MonstaSaleens said:
No I don't believe so. If it did would it have flashed successfully? Are there any tricks to get it working again? It havnt been working for about a month now.
Click to expand...
Click to collapse
....possibly a factory reset if that doesn't work flash my completely stock system.img then manually root with my guide