Related
Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)
Awesome! Thanks! disregard my PM lol.. Great timing.
VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!
im trying it now nice work
Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!
please take note orientation doesnt work. please put in first post.
otherwise, great work!
should i do adb install or adb push?
blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!
thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build
dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?
blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.
ok i got it i just adb pushed them to system/app works great
obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.
Amon_RA just sent word — KaKaRoTo’s PSFreedom is now available through recovery mode on your HTC Android-enabled phone. What’s that mean? It means no more flashing kernels leaving WiFi and whatever other functions inoperable. Not to mention it’s way less tedious than backing up, flashing, and restoring all the time. Three separate recovery images have been released:
HTC N1 by Amon_RA
Features everything from RA Recovery v1.7.0.1 including ABD & mass storage.
HTC Dream / Sapphire 32B by Amon_RA
Features everything from RA Recovery v1.7.0.1 including ABD & mass storage.
HTC Desire by Klutsh
Features everything from ClockworkMod v2.5.0.9 including ABD & mass storage.
It’s simple: Flash the new recovery, boot to recovery mode, select the new PSFreedom menu option and select a payload to use. Each recovery image comes with these 4 payloads:
Homebrew only: No Blu-Ray Disc (BD) emulation, meaning no backup support.
Homebrew only with peek/poke: Again, no BD emulation, but adds peek & poke sys calls for certain homebrew. Peek/poke was introduced in PSGroove a couple weeks back.
Homebrew + BD Emulation: As the name suggests, this version enables homebrew and backup support.
Homebrew + BD Emulation with peek/poke: Put two and two together.
Amon_RA’s recovery also comes with a “test only shellcode” payload that is used for debugging purposes. Regular end-users will likely never use it. Then all that’s left is attaching your phone to your PS3 and following the jail break steps:
Kill main PS3 power source
Reconnect main power
Press power button immediately followed by eject.
If you know what you’re doing, then go ahead and download the appropriate recovery image and flash it. Otherwise you can follow Amon_RA’s instructions here. Just like a cat — there are multiple ways to flash a recovery image.
Update: You may need to re-download the N1 or Dream version if you’re experiencing BD emulation issues. Both downloads have been updated to v1.1.1.
Download:
PSFreedom Recovery for N1
PSFreedom Recovery for Dream / Sapphire 32B
PSFreedom Recovery for Desire
Source:
http://www.ps3-hacks.com
Awesome , thanks for all the effort
So with this img it leaves the phone fully working right? I saw another img that broke wifi and usb storage
xile6 said:
So with this img it leaves the phone fully working right? I saw another img that broke wifi and usb storage
Click to expand...
Click to collapse
Whit this you will not have problems... it do all in the recovery and when you boot the phone to the system, dont have to worry whit the wifi or usb problem...
Great now I just need to get my hands on a ps3
EBI1 32A, Rogers drean
can someone plz post a version of this for the 32A rogers dream?
thanks
any plan to update this to Hermes V3?
onilink67 said:
any plan to update this to Hermes V3?
Click to expand...
Click to collapse
We can only hope. I am anxiously awaiting.
G1ForFun said:
We can only hope. I am anxiously awaiting.
Click to expand...
Click to collapse
Its not going to happen. Amon-Ra actually pulled this due to not wanting to get targeted by Sony. The actual rom may continue with updated payloads but I dont know how this will get updated. I searched for the source to this but cant find it anywhere. I wanted to replace the Hermes V1 payload with the Hermes V3 payload and recompile but have no idea where to start. I looked for a good write up on how to build your own recovery image but I think this may be a little above my programming scope. Im going to dive in anyway if I can find source or if I can figure out a way to decompile the img I already have and inject the V3 payload. If I can get it working I will release but dont get your hopes up. I really hope Amon-Ra changes his mind but Sony is out for blood.
bigd5783 said:
Its not going to happen. Amon-Ra actually pulled this due to not wanting to get targeted by Sony. The actual rom may continue with updated payloads but I dont know how this will get updated. I searched for the source to this but cant find it anywhere. I wanted to replace the Hermes V1 payload with the Hermes V3 payload and recompile but have no idea where to start. I looked for a good write up on how to build your own recovery image but I think this may be a little above my programming scope. Im going to dive in anyway if I can find source or if I can figure out a way to decompile the img I already have and inject the V3 payload. If I can get it working I will release but dont get your hopes up. I really hope Amon-Ra changes his mind but Sony is out for blood.
Click to expand...
Click to collapse
All good I got the controller stuff working on v1 payload.
maybe someone can do an "annon" and have the same skillz amon has and release a new "version" maybe amon's twin with a different name
i search a amon_ra version for desire
wub wub this is just a test message ^^
so, is this SFdsGRATE?
asb123 said:
so, is this SFdsGRATE?
Click to expand...
Click to collapse
Thats the best part
Welcome to Androot-N7p-ROM for the NextBook 7 Premium *ONLY.
I decided to change up some of the apps and generalize the rom in terms of its boot-animation screen. It runs on LauncherPro (just choose it as the "always"/default upon first instance of it. The Launcher that comes with the device isn't so great, but I left it there just in case.
It's based on the first known rooted ROM for this device: 'DocHoppy's ROM'. Credit for most of this ROM goes to him and to 'Wendal' for his toolset for packing the ROM (into cramfs) for the Nextbook 7 Premium device.
As such, it is a beta/ work-in-progress.
Androot-N7p-ROM v0.2
[ 146 MB ]
download here
Instructions:
*WARNING: FLASHING THIS DEVICE WILL ERASE YOUR DATA AND APPS!!!!*
Download image.
Rename file to update.img
copy file to root of SD card.
Follow on screen prompt asking if you want to run update image.
Disclaimer:
I am not responsible for bricked devices.
Here's my changes..
removed:
-youtube player <- the real youtube app is better
-explorer <- redundant
-slide me app market <- redundant now that Google's Market is installed
-quick search box <- Google Search widget is better IMO
kept/added:
-Market <- the real Google one
-root explorer - an alternative & capable file explorer
-astro file manager <- we all know it well
-quickpic 1.5.2 - a much lighter & more efficient photo organizer/viewer
-3D gallery <- some love it, some hate it
-brightness level 1.0.0 - quicker brightness changes
-ConnectBot 1.6.2 <- for those that need a SSH tool
-Officesuite full <- may as well keep it
-Titanium Backup 4.6.7 <- has some very handy tools aside from backups
-LauncherPro 0.8.6 <- may be old, but it's smooth and capable
-superuser <- because this rom is rooted
-has some of the Google Apps (go ahead and add as you see fit)
-has a custom boot animation.
Click to expand...
Click to collapse
Known Issue:
Apps2sd reports SU Binary out of date. Attemps to update this via superuser fails due to cramfs file system.
It's not perfect, but it does work well and I run it as my daily driver on my N7P.
Please give feedback or suggestions! I trust the pro devs could easily help me out with the little things!
-------------------
here are other threads related to the Nextbook 7
http://forum.xda-developers.com/showthread.php?t=1410862 (dochoppy's rom)
http://forum.xda-developers.com/showthread.php?t=1190990 (rooting talk? )
Since I'm new to modifying/cooking ROMs, here's my
Questions I have for the devs that cook ROMs all the time...
(lol)
Where do I edit the items that show in 'settings > about' in the device?
How do I change the default shortcuts that LauncherPro puts on the dock?
How do I change what icons are default on the home screen?
Where do I put custom wallpapers as part of the rom?
How do I modify Android UI colours?
Can the dialer be removes without losing "contacts"?
How do I create a shortcut to "contacts" without the phone/dialer?
(more to come I'm sure)
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
In Dochoppy's original rom/post he mentions that the device will need to have a serial number starting with YF1011. That stands the same for this rom, as it's derived from his.
Having an invalid update.img firmware file could be due to a number of things, but the one I have here works on my device.
I wish I had more of an answer, but by all means try out the tools for repacking the rom.
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
xxProphecyxx said:
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
Click to expand...
Click to collapse
I had mine half dead for a short bit until i found i could go into a low level bootloader mode and recover it. I am working on getting a the tool/images i used to recover mine uploaded and such.
Download and extract n7p_rescue_kit.zip
Reboot device using paper clip then quickly press and hold reset until you get black screen with usb plugged in
When windows wants driver give it the respective folder for your os (32bit or 64bit) from Drivers folder from the download
Run RK29update.exe if it says "Found RKAndroid Loader Rock Usb" on bottom you are good but if it shows "No Found RKAndroid rock usb" repeat last step.
Either flash all of the default selected items or do just system (since bootloop is in system)
Hope this helps
P.S. If you pack then unpack your custom one you can flash JUST system using the tool but be sure to use the offsets that are pre-loaded.
use a pin to push the reset button on the back to break out of the boot loop.
If after this your rom still bootloops, try putting a different update.img rom to flash, on to the sd card. Then boot into safe mode by holding all 4 front buttons after boot. the update should be found and installed after that.
Thanks!
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
aberrantjots said:
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
Click to expand...
Click to collapse
Install "Quick Sync Settings" to get to the hidden settings view.
Also did you use this guide for market? That one worked great for me.
Thanks
Working great for me so far. Thanks sharing your work.
Nice!!!
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
lost enigma 208 said:
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
Click to expand...
Click to collapse
Not sure if this rom will work for you, just guessing by your serial number. If it is to work changing between roms on these tablets is very easy. Just download the image onto the root of your sdcard, rename it update.zip (not update.zip.zip) your tablet will recognize it as an update and ask if you want to proceed. If you say yes then follow the prompts and your in business!
Sent from my NXM726HN using XDA App
Just go this to day and was plesantly suprised to find this rooted rom. Just wanted toy let you know that my S/N is YF12112xxxx and this rom work prefect for me (so far) Thanks for all the work you guys have done here. Also is there anyway to over clock the processor in out tabs?
Thanks for the comments thus far!
I would like to overclock this thing too, but that might be further down the road, as priority is on getting a different file-system for the /system volume.
Version 0.4 is coming next.
FYI:
There will be a larger span of time between updates on this particular rom for the N7p, because I will be using more stable conjumbles of things from other roms for this device. This rom is more of a remix or derivative than an entirely different rom.
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
fireproof34 said:
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
Click to expand...
Click to collapse
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
sgtfoo said:
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
Click to expand...
Click to collapse
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
fireproof34 said:
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
Oh I was talking about currents and maps. Both of those can be installed via market. I have them both on my tablet.
The ad-hoc networking is something worth putting in a later release though.
good mention.
Runs great
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Welcome. Lots of searching and trial and error ,but this is a great place to start!
lrmahon said:
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Click to expand...
Click to collapse
Sent from my NXM726HN using XDA App
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
You can create dumps of your partitions using ADB shell in system; TWRP is not required to do this.
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
A very similar thread with the same topic has been discussed a few days ago - you can check here
Anyone can compile TWRP - it's opensource. Pixel 6+ owners are unlikely to get an official build from TWRP since it requires a volunteer to maintain the repo, deal with bug reports, etc.
It's recommended to simply compile the image on an individual basis (you really don't want to rely on a third-party supplied image when you have no way of knowing whether it's safe or not). Compiling isn't a difficult process, but does require an hour or two of reading TWRP's and Google's applicable developer pages, along with ~30 - 60 minutes of set up time on a PC/laptop (I prefer to compile within an Ubuntu VM, but I believe it can also be done in Windows' WSL).
robroy90 said:
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
Click to expand...
Click to collapse
They still haven't finished official support for Android 12. Since recovery resources on A12+ are located in vendor_boot, bigbiff is trying to figure out a decent way for TWRP to live there, at least as far as the Pixel 5 is concerned. Not sure what other obstacles may be present on the Pixel 6 series and above.
nooted1 said:
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
Click to expand...
Click to collapse
Hey thanks for this! How did you flash just the recovery partiton on the Pixel? I am an old hand with Odin on the Samsung devices, but Google official devices are still new to me. Will the StagOS recovery recognize an external USB-C flash drive for storage?
s3axel said:
A very similar thread with the same topic has been discussed a few days ago - you can check here
Click to expand...
Click to collapse
Thank you, I went over there and read everything. Much appreciated!