Related
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
AdelaisAer said:
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
Click to expand...
Click to collapse
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
gpfnzl said:
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Oh. Sorry about that. Well, my main question is how to back user data up using the toolkit. I see options for applications and nandroid and stuff, but I don't see userdata such as contacts, sync accounts, etc. The most important stuff.
That's my main concern first and foremost. Also, I'm checking the guide right now; thanks.
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
gpfnzl said:
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
Click to expand...
Click to collapse
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
AdelaisAer said:
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
Click to expand...
Click to collapse
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
gpfnzl said:
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
Click to expand...
Click to collapse
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
AdelaisAer said:
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
Click to expand...
Click to collapse
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
back your sd card up to PC, from memory i think the unlock part wipes your phone
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
ttahatt said:
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh. Derp. Well, I edited my post before yours, and I saw it has two images in it (one of them is radio) and a zip file. So yeah, I guess that contributed a lot to my confusion.
Also, I think my phone is still locked. I have done literally nothing to it yet.
Also, I want to flash it because it's currently in a Rogers/Samsung-type OS, where updates aren't pushed because it takes them months to get the A-Okay, for whatever reason. I want to flash it to the Google-line so I can get regular updates without waiting. :S
AdelaisAer said:
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
Click to expand...
Click to collapse
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Plug your phone in to pc....reboot your phone into fastboot (vol+/vol- and power) see if drivers install (should see bottom right hand side of computer)
gpfnzl said:
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Click to expand...
Click to collapse
My goal is to back my contacts and app data up, and then flash my phone with the new factory os that I got from Google Developer. :S But this whole guide is ajfkjsdkjfksjfkwejfkjsdkjfakw. Also, sorry for ranting. >___<;
See, if Samsung had just pushed updates to Canadian Android phones in the first place like normal people, I wouldn't be here. But instead, they hold onto updates until they (and Rogers) can stamp their names all over it and then takes a few more months just to approve it a second time, for whatever reason. :S
Instead, I have to come here, try to do this whole thing, and then install that factory Google-line OS so I can get regular updates.
Go look in the Rogers community forums - nothing but threads complaining about it. I'm one of very few who actually came to a forum like this.
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Alright, will do.
Also, sorry if my replies get a bit slow now - eating.
EDIT: Ugh, this is getting reaaly confusing now. o-o; Especially the part where you make a backup of the phone build. @[email protected];
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
gpfnzl said:
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
Click to expand...
Click to collapse
Alright. Thank you. :3
So far, I synced my contacts, browser, etc. up with my Google+ account, so that's backed up, and I can go into fastboot no problem and have the toolkit detect it.
I just wanna make sure that there's nothing else that needs backing up (if there is, then what do I backup, and how?), and then just flash my phone with the new 4.1.1, and be done.
Also, thank you so much for actually putting up with me. A lot of people would normally be rather mean/hateful towards new-comers like me, so thank you.
EDIT: Why must this be so complicated... @[email protected] Curse you, Samsung.
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
gpfnzl said:
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
Click to expand...
Click to collapse
Er, how do? o-o;
Plug your phone into your PC
open *my computer* select the *galaxy nexus*, select *internal storage* and copy every thing to your computer.
unlock your lock screen on the phone or your computer wont see the internal storage
Warning:I am not responisible for any damage to your phone and rooting usually nullifies the warranty. so please procede with your own risk
I tried to root my karbonn A2 for 2 weeks and finally i got it. so im gonna share the steps involved in rooting and also provoide the tools for it.
NOTE: I do not take credit for any tool since all the tools were already available online, so credit goes to whoever programmed them. only thing i did was to alter the method slightly to get my phone rooted.
Lets begin. Before we start rooting our phone, most important thing is the drivers. so u need two types of drivers one is ADB (android debugging bridge) drivers and the other is preloader drivers. i have attached both of these drivers in the attachments u can download it.
Step1[only for beginners]: Go to setting>applications>development>enable USB debugging in the phone, then connect your phone to ur pc (remove all previous drivers if u have installed) then go to device manager>devices, right click on the usb device and click update driver and browse to folder containing the SPdrvers (u need to extract the folder from the attachment first).If driver is successfully installed then u should see "android phone" in ur device manager. to confirm it just run adb devices from the command line by chagning the directory to where adb.exe is, u should see the list of devices attached to ur pc. (usually adb.exe will be in android sdk tools folder or if u dont have one then check in ADB folder from superoneclick in the attachment).
Step2: ok, now that u have installed adb drivers, u need to install preloader driver (also known as downloading mode in some devices). to do this, disconnect ur phone from the pc, then switch off the phone, remove the battery and then connect ur phone to pc again (without the battery). then u should see windows trying to install drivers and fails. then go to device manager again and browse to folder containing USB VCOM drivers (see attachment). after it successfully installs procede to step 3.
Step3:: download, extract the files MTKROM and SPflash tool to ur pc. then put the battery inside ur phone then switch it on, connect it to pc (enable debugging all the time). then open command line then go to adb folder then type :adb devices- u should see the list of device attached (u will get some long numbers so dont worry). then type "adb shell" (without the quotes). u will get a $ sign, then type "cat proc/mtd > /sdcard/firmware.info" if its successful then a file named firmware.info will be created in ur sdcard root. then copy that file to ur pc.
Step 4: Now open that firmware.info in MTKROM.exe u should see a list tables and address like in the image below. then click save scatter and rename the filename to MT6575 instead of MT6573 (and leave everthing else as it is). so a file named "MT6575_Android_scatter.txt" will be created.
Step 5: Now open Spflash tool and load the scatter file in that. u should see something like this in the image below.
STEPS TO BACKUP ORIGINAL BOOT AND RECOVERY
Step 6: Before we actually begin to root its important to make a backup of current images. so to do that, go to READ BACK tab in sp flash tool. click on Add>double click on the page file and save as "Boot.img" somewhere safe. then click on "Read Page only", this is very important. then look at the address side by side from MTKROM and enter into sptool. the start address is the address in which the boot.img begins and length is the length of boot.img. so final address will be startaddress+length =start address of next image (recovery.img). In MTKROM the start address is given as "PART ADDRESS". after entering those carefully click ok. if u want to be sure then use programmer calculator and add the address.
Note :the address will be in hexadecimal format not decimal.
Step7: In order to read the firmware from the phone, disconnect the phone from your pc, remove the battery, dont connect it yet. now click on "Read back" button in the sptool (its after Add,remove button). now the software starts searching for the device. now connect the device to the pc (without battery ofcourse). now if have installed USB VCOM drivers correctly then the sp tool should detect ur device and start reading from it. u will see Red colour in the
task bar when it detects then blue colour while the tool is reading the phone. wait untill the reading is complete. A green circle will pop up after it successfully reads from the device. (refer the images below)
Step 8: repeat step seven as described above for recovery.img (save the file as recovery.img) then select "read page only" option, enter start address as 0x0980000 and length as 0x0500000. (please enter the address carefully cross check with MTKROM image addresses.)
Note: You have to disconnect the device first then click read back button after entering the addresses then connect the device, otherwise the sptool wont detect your device!.
Actual Rooting Procedure
Step 9: Now that you have backed up both boot and recovery images its time to start the actual rooting. download the boot.img file from the attachment and save to your pc (dont replace it with your backup image that you saved earlier). go to download tab in the sp tool and tick only boot.img and uncheck all others (if any of them has been checked already) and click on Bootimg and browse for the folder where u downloaded boot.img from the attachment and NOT THE BACKUP! after that disconnect your device, then click download button above( after format->upgrade button) or f9 from keyboard. the tool will start searching the usb com ports. now connect your device and wait till it downloads fully. Note: In downloading your will get RED colour first, then YELLOW colour while flashing, and finally a GREEN circle after flashing is complete).
Step 10: The most important and complicates steps are over. now all you have to do is put your battery to your phone and switch it on. now after it sucessfully boots up, open superonclick.exe (you will get this software online and its very popular tool for rooting) and connect the device to your pc (enable debugging of course), then click Root button in superoneclick and Voila! your phone is rooted. enjoy and dont forget to press thanks button if ive helped
Note: u will need .NET framework 3.5 to run superoneclick.
Method To Unroot
For unrooting your mobile all you have to do is flash the original, backup boot image back to your phone. just open sptool and load the scatter file, then click on bootimg then browse to wherever u have stored backup boot.img then click download button then connect your device without the battery and thats it. you will get back original firmware without the root!.
Clockwork mod recovery for A2
There is no official cwm recovery for A2, but i ported cwm for other MT65xx devices to A2. so here are the steps to flash.
step 1: download recovery.img from the attachment.
step 2: open sp flash tool and load scatter.txt (for detailed description refer rooting steps). then tick recoveryimg and browse and set the path of the recovery.img you just downloaded from attachment.
step3: click on download button at the top or press f9. then take out the battery from the phone and connect it to the pc. the tool will detect your phone and start flashing cwm recovery.wait untill the green circle pops up.
step 4: now put in the battery and press power button+volume up and hold it for few seconds and voila!! cwm recovery boots up. And to revert back to original recovery just flash the recovery.img that you backed up during rooting process using the above steps.
Note: Do Not factory reset your phone without backing up the IMEI number. After rooting your device please backup your phones IMEI number which is stored in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 to a safe place. or there is an application called mobileuncletools (a chinese app) which helps to backup your IMEI to sdcard and restore it back. if u loose your IMEI and reset your phone then you cannot call or recieve sms etc
No service and invalid IMEI solution
explanation:
In case u did factory reset of the phone, then all your data will be wiped including the imei number. it will be reverted to factory imei number, hence you cannot connect to any mobile networks in india or anywhere else because most network operators wont allow to use the network with dupicate or invalid imei numbers. every device has a specific imei number. in this device your original imei numbers (15 digits) will be on the back of your battery.
Restoring is tough very simple procedure, creating the required files is a major headache. At first i thought it was impossible to restore the imei back (trust me i tried all the available solutions that u get in the internet, infact there are 5 different types of solutions, none of which worked for this device). luckily one day i found a chinese software which actually did create a imei file that is compatible with this device (phew !, yeah i know) and so i did successully restored my imei back and i can once again connect to mobile network and make calls..:victory: so here it goes.
How to restore IMEI number? (MUST BE A ROOTED PHONE)
1) if u have made the backup of MP0B_001 file in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 , then install root explorer and simply replace your current file with the backed up MP0B_001 and set the permissions to rw-rw---- and restart.
2) if u havent backed it up (too bad), then download the chinese software sn_gen.zip from the attachments and enter both imei numbers that is found in the back of your battery (enter the numbers correctly and cross check it again, its 15 digit number). then the software generates a new MP0B_001 file, copy and paste in the above mentioned directory and set the permissions to rw-rw---- and restart.:fingers-crossed:
dont forget to press thanks button if ive helped you :good:
Download Links:
Drivers: http://www.4shared.com/rar/XLiLMsG3/sp_drivers_v14.html?
SP flsah tool: http://www.4shared.com/archive/bjTXvBtd/sp_flash_tool_v3122401.html?
scatter txt: http://www.4shared.com/office/W7Fk6VOm/MT6575_Android_scatter.html?
I need to root my A2 too,can you tell me how?
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Sent from my Karbonn A2 using xda app-developers app
vickykeeth said:
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Click to expand...
Click to collapse
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
cm10
abhiatreyas said:
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
Click to expand...
Click to collapse
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
urgent help
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
vickykeeth said:
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
Click to expand...
Click to collapse
lol i was a galaxy ace user untill last dec. (its touch digitizer got broke, so i temporarily bought karbonn). anyway i do know ace can run cm10 and pretty much any device can, even ours can run it. i did not say our device doesnt run at all. i said it wont run smoothly and developing cm other than stock os version is very very difficult since our device is a local device and threre is no lot of support for it. so if anything goes wrong we may permanently brick our devices and may not find solution at all.
on the other hand, since i was a former ace user, i know that even though ace can run cm9 and cm10 there were a lot of problem in getting camera, video recording, and other applications because of unavialablity of their sources. so furthermore most of extra features that arent available in gingerbread cannot be used ex: face recognition, google now,otg usb etc( they are built for high end devices). u wont notice the difference in optimizations and performance of jelly bean in low end devices because they need sufficient hardware to utilize the os to full extent. so only thing u get out of installing cm is user interface (which u can change using of launchers, oh yes there are big bunches of launchers out there) and some features of cm (deodexd rom,custom kernel with overclocking features and some tweaks.)
coming back to our device, ive been trying to build cm7 for our device and its really difficult without a device tree and some good prior experience in building cm for atleast 2 devices. so my advice is that first we will build a fully working cm7 for our device and later if possible we will port cm10.
vickykeeth said:
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
Click to expand...
Click to collapse
what do u mean by reset? did u do factory reset from recovery or did u clear flash from by holding power+down? (oh btw recovery is power+up in our device).
either way ur imei number has been erased and it will be reset to factory number . i spent 1 week day and night searching for a solution and that is exactly why i told u to backup your MB0P_001 file.
in order to repair it u need to root ur phone. follow above steps and paste ur imei number (dial *#06#).
Nothing in SuperOneClick
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
shyamsn00 said:
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
Click to expand...
Click to collapse
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
also, after u root with superonclick, restart it and please check if u have superuser app in ur phone(it will be automatically installed by superoneclick, dont install it manually since the app should be in /system/app and su command should be in /system/bin directory, which u cannot do by installing it manually). if its installed then u have root access, if u still want to confirm just download root checker app from google play and run it.
CM10 means Jelly Bean Which has minimum Requirement of 512MB ram... device cant even Support Cm9(ics)...And generally cynogenmods are not developed for local Indian Brands.....Instead Try this making your phone look like XPERIA:
http://forum.xda-developers.com/show....php?t=2095956
abhiatreyas said:
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
Click to expand...
Click to collapse
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Mr1010ass said:
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Click to expand...
Click to collapse
im sorry, im not able to understand your problem. please give more information about your issue.
shyamsn00 said:
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
Click to expand...
Click to collapse
ok try it once in win7 and check if the issue is resolved, if not please explain clearly what is the problem and what error message you are getting.
need ua help
hey with your help i rooted my phone successfully.. Thanxx alot,,
Bt please invent custom for karbonn A2.. please
Waiting for your reply..
First 3 steps problem
I already downloaded everything and it seems like even before I started I already encountered a problem. When I try step 2 my KArbonn A2 device cannot be found on the list of devices on the cmd.... No "Android Phone" is found on my device manager but only "Karbonn - A2MS USB Device". When I update the driver it says that it is already the best driver for my device.... I need help pls.....:crying:
BOOTLOOP????????
I cannot boot up after flashing the boot.img,you provides...I've been able to flash cwm recovery successfully and make backups of my recoveries and boot.img...But when I flash the provided boot.img,My phone goess inot a bootloop It shows Karbonn A2 splash and shuts down and restarts,doing the same thing over and over again...Please tell me whether it is a problem with the boot.img or have I done something wrong in the flashing procedure???
Thank you..... finally found out where I went wrong... now my phone is rooted..... A hundred thanks....:victory:
Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG G5.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available guides below:
Guides:
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_1
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_2
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Re-install_STEP_3 <------ If you want to re-install stock MM 6.0.1 with root
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Upgrade_only_STEP_3 <------ If you want to root current stock MM 6.0.1
Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 <------ If you want to have stock MM 6.0.1 only (no root, use this if you want to return the phone or sell it)
They will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on File Transfer mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
You read the Useful tips & information for the T-mobile LG G5 post
You read the Changelog + News & Additions post
***Un-root***
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Disclaimer***
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
If possible use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people for making all of this possible:
tungkick
wolfu11
arjuna_
Your work and dedication does not go unnoticed, thank you. I would also like to thank anyone else not mentioned here that allowed the rest of us to get root on our beloved LG G5 phones. The android community is awesome!!!
Sections:
Post#1: Main introduction & Files
Post#2: Useful tips & information for the T-mobile LG G5
Post#3: Changelog + New & Additions
Please leave a thank you if you find any of this helpful
**Useful tips & information for the T-mobile LG G5**
How to install xposed: (Keep in mind that versions will change over time)
Download the latest xposed framework currently (xposed-v85-sdk23-arm64.zip):
- Go to the following web address: http://dl-xda.xposed.info/framework/
- Click on the sdk23 link
- Click on the arm64 link
- Download the latest xposed zip file currently xposed-v85-sdk23-arm64.zip
Download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk):
- Go to the following web address (xda thread): http://forum.xda-developers.com/showthread.php?t=3034811
- Scroll down to the "Attached Files" section and download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk)
Copy both files to the SD-CARD of your phone
Restart your phone into TWRP
Click on the INSTALL button
Flash the xposed framework file (xposed-v85-sdk23-arm64.zip)
Restart your phone and let it start normally
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and make sure there is a check mark next to Unknown Sources option
Open a file manager
Go to the location of the xposed apk
Install the xposed installer .apk file (xposed Installer 3.0 Alpha 4 apk)
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and remove the check mark next to Unknown Sources option
Start the xposed app
How to enter download mode
Power off the phone
Press and hold the VOLUME UP key
Connect the phone while holding the VOLUME UP key to your PC (use a USB-C cable)
Keep holding the VOLUME UP key until you boot into download mode
How to fix the Fastboot device driver issue (no devices detected)
Visit the following website and follow the instructions: Manually installing Android ADB USB Driver
**Changelog + News & Additions**
Changelog (for the guides only):
7.16.16 - All guides have been updated to reflect the new 10d .kdz and .tot files. All links to tools, .kdz, and .tot files have been updated as well.
News & Additions:
7.16.16 - Multiple updates
A modified H83010d rooted .tot file has been released (thanks to Tungkick & wolfu11)
Guides are safe to use again. All links in all the guides have been updated to reflect the new H83010d files
If TWRP is not showing the internal storage but only the external SD-card take a look at post 24
7.9.16 - There is a new firmware update (H83010d) for the LG G5 (T-mobile) which is not compatible with firmware (H83010a) the .TOT files used in this thread have
If you upgrade to this new firmware, you will lose root.
There is no current way to get root on the new H83010d firmware unless the modified .TOT / KDZ files are released with TWRP included
There is an anti-rollback feature in the LG G5 (t-mobile) phone that prevents you from flashing back the H83010a firmware after you upgrade to the H83010d firmware. Attempting to do this WILL BRICK your phone!
Do not attempt to use the guides which are using H8301a .tot / kdz files if you have updated to H8301d. I will be updating the guides as soon as the H83010d modified .tot / kdz files come out.
5.29.16 - LG G5 & LG V10 possible driver issue: First reported on Post#6
If you own an LG V10 and have used your PC to root it, you most likely installed drivers, tools, and or files specific for the V10. What this means is that you may have to uninstall those drivers, tools, and or files prior to installing anything to be used for rooting the G5. This does not include the ADB program which can work for both.
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
mallman said:
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
Click to expand...
Click to collapse
Thank you.
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
Two questions:
1) Does this automatically encrypt the phone? After flashing both the no verity and the SU it boots in to "encrypting" with no other option. I have not had this happen with any other device. Did I mess something up?
2) The password at the beginning of TWRP is requested every time, even after flashing the no verity zip. What did I do wrong?
Click to expand...
Click to collapse
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Thank you for your input skyfox99. Your solution to the issues you faced will help others avoid them. You made me think of something I did not anticipate which is what happens when you attempt to root your G5 using the same PC you used to root a V10. I am definitely adding a service announcement to the Changelog (post#3) to address this possible issue.
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
bigchuq said:
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
Click to expand...
Click to collapse
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Your internal storage gets wiped. That's why they weren't there.
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No I was not, I'll give it a shot. Thanks
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
mikeyinid said:
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No, I copied after wipe so they were there. Computer recognized them and so does file manager.
jun19inf said:
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
Click to expand...
Click to collapse
TWRP has trouble mounting.
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
There is a TWRP bootloop set of instructions in another thread, run those commands and see if it resolves it, maybe?
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
I had to reflash no verity a few times, before installing SU. There seems to be a problem with TWRP.
Sent from my LG-H830 using Tapatalk
I didn't have any of the issues you guys are reporting in this thread. TWRP sees both internal storage and SD card. And has since I originally rooted.
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
shaneg79 said:
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
jun19inf said:
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
Click to expand...
Click to collapse
It's ok I found out it doesn't affect it thanks for your answer.
Sent from my LG-H830 using XDA-Developers mobile app
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
rebelde80 said:
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
Click to expand...
Click to collapse
It's a very weird problem and unfortunately the only thing I can think off is that TWRP might not be compatible with the SD-Card you are using.
HISENSE A2 (6.03 )
https://forum.xda-developers.com/showthread.php?t=3673945
global rom flashing guid and image. this is very good.
but too old version, so e-ink support poor version.
so I made custom system.img from (https://forum.xda-developers.com/showthread.php?t=3673945)
instruction.
1. update a2 to 6.09
1.1. first HISENSE A2 version update to latest version(6.09)
https://pan.baidu.com/s/1cfHYMy
Password: 15k5
1.2. down load and copy SdCard root `A2.bin`
1.3 power off phone
1.4 volume up + volume down and power button
if success sd card upgrade mode begin.
2. write my system.img for (6.09)
here is my hisense a2 'system.img'
https://drive.google.com/file/d/0Bzis7hPFLtDbX0xMWUNwNmdBYTA/view
extract and flashing previous A2 GUIDE.
3. after phone setup you must factory reset.
* simple edl mode enter able hisense a2 when debugging mode.
`adb reboot edl`
and use QFIL flashing
* menu language support only ch and eng.
thank you very much
In addition, can you add multi language, I want to add Japanese, thank you.
multi language can use with molocale2
I tried but too unstable.
you can use molocale2 change any language.
joygram said:
I tried but too unstable.
you can use molocale2 change any language.
Click to expand...
Click to collapse
After using molocale2, I set it in Japanese, but most of the menus are still in English. Only the menu of Google is in japanese. Unable to use properly.Also, can you tell me how this ROM was modified?
Thanks
In addition, the ROM has a bug, when the input *1973461# into the System info menu, will be black screen, no display, the touch failed.
chenrenying said:
After using molocale2, I set it in Japanese, but most of the menus are still in English. Only the menu of Google is in japanese. Unable to use properly.Also, can you tell me how this ROM was modified?
Thanks
Click to expand...
Click to collapse
the menu languahe in the vision-setting.apk
if you add new language. you should modify vision-setting.apk
and add translated strings.
it cannot system.img write directly. because latest system.img not opened.
I just copy latest rom files to system.img
chenrenying said:
In addition, the ROM has a bug, when the input *1973461# into the System info menu, will be black screen, no display, the touch failed.
Click to expand...
Click to collapse
you do not enter sysyem mode
only use
adb reboot edl
if you bricked.
recover with sdcard recovery with vol up + vol dn
step
1. press power button about 30 second longer.
2. volume up + volume down and power button.
then show SDCARD firmware update.
a2.bin file in sd card root. (It may be 6.09 version)
3. enter edl mode with adb command
you should debugging mode enabled.
and
adb reboot edl
4. then use QFIL .
thank you very much
chenrenying said:
thank you very much
Click to expand...
Click to collapse
you are welcome
joygram said:
you are welcome
Click to expand...
Click to collapse
This ROM removed a lot of app, but these China of users is useful, can you help me to do a Google only add Rom? Only based on the official ROM on Google can be added, or can you tell me how to add gapps, thank you very much.
chenrenying said:
This ROM removed a lot of app, but these China of users is useful, can you help me to do a Google only add Rom? Only based on the official ROM on Google can be added, or can you tell me how to add gapps, thank you very much.
Click to expand...
Click to collapse
I am not remove the apps intentionally.
but side effect.
some apps confilct library so can not recognize. and generating system error. so I removed.
(weather app and some e-ink apps)
I'm very sorry :<
Hi,
I tried to update using the A2.rar file. This file seems to be password protected. 55933 seems to work here.
--
With the system image, at first I wondered how to flash this. After unpacking the file and following the instructions given in the above mentioned guide (https://forum.xda-developers.com/sho....php?t=3673945) it worked fine.
Using qfil I selected flat build, found the *firehose* file in the extracted directory and also the xml files (rawprogramm and patch) you have to select. Starting qfil phone was recognized as Hisense... at COM12 during the process it changed to Qualcomm... at COM13. I did not use adb commands (this did not work for me). For me qfil put the phone automatically in download mode.
Up to now all works fine. Menus are in english, some might be in chinese. Gapps, gmail and my old apps installed ok.
Thanks again to joygram
Password for archive is wrong?
@baistan the a2 file for the general system upgrade to 6.09.03 is hosted at a baidu site. You need the pw given by joygram to enter his baidu account. Then you have to install a baidu download client, because the file is 1.48 GB. The file itsself is a .rar archive, which is password protected. I googled the file and found a chinese hisense fans forum. Here a file with the same name was posted. pw was given with 55933
So you need two passwords.
The new rom is only chinese / english and has no gapps.
Joygrams system.img installed fine. GoogleApps workt about two days for me, now it crashed and does not start any more, maybe because of a playstore update. This seems to be common. Maybe this issue can be solved.
Here a google drive linke to the file (makes it easier) https://drive.google.com/open?id=11anmiy8FEQNbVzu9kbS72WKFr-zmHope
Have not got playstore to run again,
flashed the A2 rom again
and use f-droid; uptodown and/or yalp store to install apps.
Thank you
Do you think it is possible to install " 7.0 or CYANOGEN MULTILINGUE " with the support of the " E-INK " screen?
That I cann not tell you. I am no developer, sadly.
I do not know if anyone got TWRP running on this phone. I know, that it is possible to customize TWRP, there are examples on youtube, but I do not know if I am able to do it.
For me it would be interesting to flash gapps. I don´t know if you can do this using qpst.
I hope there is some development for this phone in the future.
OF_Ge_72 said:
That I cann not tell you. I am no developer, sadly.
I do not know if anyone got TWRP running on this phone. I know, that it is possible to customize TWRP, there are examples on youtube, but I do not know if I am able to do it.
For me it would be interesting to flash gapps. I don´t know if you can do this using qpst.
I hope there is some development for this phone in the future.
Click to expand...
Click to collapse
the ROM "JOYGRAM" is in English and Chinese!
By against the Playstore works very well you do not turn off your phone!
from the moment you turned off your phone the factory "Google Play Services" !!
Ducout you must be very careful never to crash and do not repel if the application that works with "Google Play Services" (youtube, play store, gmail, etc ...) no longer works!
we are unable to delete the account [email protected] and "conscious"
I think he should root the phone and add Google Play Service and Play Store!
but I do not know how to sit for root on HISENSE!
I would like to find a charitable soul who could help me carry a Rom Stock 6.0 from Google and add on Driver and E-Ink!
or take the ROM of the HISENSE A2PRO 7.0 Nougat and change it for the Hisense A2 because unless I'm wrong there is not much difference between the 2 phones!
PS: "JOYGRAM" recommend this for translation: you may want to set the language in Japan, French etc ...
this language in the Vision-Setting.apk
I tried to edit this file.
but the system does not start, so I stopped.
but some can stay.
1. Copy Vision-Setting.apk to pc
Use decompile with apktool
3. add a new language in the res and translate the language
4. repack the copy in system.img
I wrote system.img with the Linux system mount in the virtual machine.
I can not do perfact system.img because there is no last system.img.
OF_Ge_72 said:
@baistan the a2 file for the general system upgrade to 6.09.03 is hosted at a baidu site. You need the pw given by joygram to enter his baidu account. Then you have to install a baidu download client, because the file is 1.48 GB. The file itsself is a .rar archive, which is password protected. I googled the file and found a chinese hisense fans forum. Here a file with the same name was posted. pw was given with 55933
So you need two passwords.
The new rom is only chinese / english and has no gapps.
Joygrams system.img installed fine. GoogleApps workt about two days for me, now it crashed and does not start any more, maybe because of a playstore update. This seems to be common. Maybe this issue can be solved.
Here a google drive linke to the file (makes it easier) https://drive.google.com/open?id=11anmiy8FEQNbVzu9kbS72WKFr-zmHope
Click to expand...
Click to collapse
Good evening "OF_Ge_72"
think you can put on google the other version available on fans.hisense because being in France it is impossible for me to download the possible version available on fans.hisense !
because to answer and to Download on Fans.hisense it is necessary to register with a number of Chinese telephone and it is the same for Baidu !
A huge thank you for all
how about e76MINI
could you make it with E76MINI.41 ROM, i really need the GAPPS.here is official firmware link: dwz.cn/77wmyT unzip password 20171124
also maybe could tell me how to do,i will do it myself.my email is [email protected]
xingchenfei said:
could you make it with E76MINI.41 ROM, i really need the GAPPS.here is official firmware link: dwz.cn/77wmyT unzip password 20171124
also maybe could tell me how to do,i will do it myself.my email is [email protected]
Click to expand...
Click to collapse
Hello
did you try with a VPN and download / install Google Play Services and Google playstore?
by the way I take advantage of your passage to ask you if you have access to the forum: fans.hisense.com? (because I'm looking to download the version: http://fans.hisense.com/forum.php?mod=viewthread&tid=123020&highlight=A2+L1261)
Thank you
joygram said:
HISENSE A2 (6.03 )
1. update a2 to 6.09
1.1. first HISENSE A2 version update to latest version(6.09)
Password: 15k5
1.2. down load and copy SdCard root `A2.bin`
1.3 power off phone
1.4 volume up + volume down and power button
if success sd card upgrade mode begin.
.
Click to expand...
Click to collapse
Thanks, but unfortunately the baidu link is down (as far as I understand it). Would it be possible to upload it elsewhere in order to keep your guide alive?
The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo
Thanks. So this is GSI? Bugs?
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain
DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)
I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?
I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany
well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse
I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6
Will this image work with the SM-A505G version?
USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.
InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel
the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP
hey man, the project is being upgraded? Tanks for your time
InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware
I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.