Hi all,
After spending many hours trawling the internet, and especially this forum I still am having problems getting ANY custom rom I've tried booting on this phone
I know it's old, but it's just a phone I had lying around and want to use it as a small tablet for my 6yo daughter.
I can flash any "stock" rom I've found with odin, but when flashing using an install from an SD card through CWM, it just hangs on the Samsung bootscreen.
CWM installs as the default recovery console, so something is going on the phone, but it won't boot to android.
Oh I'm also using a 5830I rom, but my research has shown this is basically the same phone?
I've used CM7 and tried lots of other custom roms with the same outcome - please can anyone help!?
My daughter is dying to use her new games machine, but the stock rom is sooooo laggy and slow it's no good at all!
Thanks in advance.
@macsbig, "About device" information from settings of your device please < home+power button for screenshots > or kindly state the full details here.
Your original CSC/PDA/MODEM parts of your device <Dial *#1234# >
Your Region /Country/ carrier you are staying please.
Thanks for the reply ehsanotaku!
PDA : S5830iXXLA4
PHONE : S5830iXXLA2
CSC : S5830iOXXLA2
I'm in the uk. This is not the original rom (that got stuck in a bootlock) and the only way to get the 'phone working again was to flash with a stock rom from the internet.
The original rom was from "Three".
During my various attempts at flashing a rom I have ticked the "re-partition" box and tried both "cooperve_0623.pit" and totoro_0623.pit
I've flashed my P5110 tablet, and a Galaxy S1 for my son with no problems - odd!
@macsbig, How come you are ended up with outdated ( 2012 ) s5830i in the first place ? Any particular problems with your s5839i original firmware ( do you know your original CSC/PDA/MODEM parts ) ? Are you absolutely sure this is not re-branded version ( "About Device" info of the original phone would be nice to see though ) Did you take any Nandroid back up of all of the original partitions of your s5839i through temporary CWM zip file ( files will be stored inside your Clockworkmod directory inside the root of the SD card )
Do you still have access to Recovery stock e3 console and Download mode ?
Another important subject in need of clarification are ".pit" files ( partition table info ) and Re-partition option. Playing around with wrong .pit file such as totoro and incorrect usage of Re-partition will lead into hard bricking of your device .
Since you already did modify partition table couple of time partially without success , I would suggest the following process :
1. Download one of the newest non wipe xxx.tar.md5 s5830i firmware from here < It is free, but registration is required > Probably 2013 xxMD1 is the right one for our experiment.
2. Make your wipe flash able zip package through splitfus2 tutorial provided here, my comment @ post 9 or simply you may use European/Russian pre-made package from here , your choice though ( I would advise the first method , but the latter also will work ) .
3.Get the following files:
3.1 - Odin3.v3.07.Cooperve.exe from either places would be fine : 1 , or any sticky post in general/development section will do ( correct cooperVe .pit file will be resided inside the package )
3.2- Get the Temp-CWM 5.0.2.6 or 5.0.2.8 zip file from here or here < put the zip file inside the root of your SD card for flashing later >
3.3- Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar from post#27 , my attachment .
3.4 - SLIM_CM7.2_Cooperve #4 Rom < put it inside the root of SD card >
3.5- This kernel is also goes into Root of SD card for later usage .
3.6- EXT4 Formatter Tool , into the root of SD card again.
4- Now , if you don't have proper drivers installed inside your Windows PC , you can get then form here .
Ok, assuming you have at least access to Download mode , provided the combo keys work (pressing Vol(+) + Vol(-) + Power Keys) Go there according to manual :
-Power off your Phone.
-Get into "Download mode" by pressing Vol(+) + Vol(-) + Power Keys.
-press volume up
-Open Odin3.v3.07.Cooperve.exe
-Connect your phone to PC via USB cable.
-Make sure that your phone is detected in "ID:COM" area.
- Put your wipe PDA/CSC/MODEM/ boot loader/pit files into their proper places , Re-partition is ticked , Factory reset and reboot selected by default >> push the START !
- DO NOT disconnected nor disturb the flashing Nand process , until the process being terminated . Now you must be out of boot loop .
For completing our partition conversion and also put some cm7.2 custom Rom into the test at the same time , do the following :
- Boot into stock e3 recovery >> wipe data and flash your Temp CWM
- CWM > wipe data > wipe cache > wipe Dalvik cache
- Flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
- Flash kernel_CM7_v4.0_cooperVe .
- When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
- Wipe data, cache and Dalvik
- Go to "mounts and storage", and make sure /system partition is mounted (will show -unmounted ; it is like ON/OFF switch)
- Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM, you have already got inside your SD <SLIM_CM7.2_Cooperve #4>
- Reboot
waiting for some good news ............
It's a long story, but here goes!
I had a couple of old phones we no longer use hanging around the house, so I thought it would be good to let my (young) children use them as simple games playing deivices. It doesn't matter too much if the phone is dropped and damaged etc, as I probrably wont use them for anything else as we have new phones.
Within a couple of days - and I'm not sure what happened, my daughters phone was stuck in a boot loop (samsung and "Three" logos repeatedly). Having no experiance of "unbricking" phones I immediately reached for google, and set out on my quest to sort out her phone for her (as we had lots, and lots of tears over her new toy!). The phone has no sim card in and is on wifi for installs etc.
After searching I found a rom that would load on and make the phone good again, this one: S5839iXXLK2_S5839iH3GLC2_S5839iNELK1_HOME.tar.md5
This worked ok, but was very laggy, and irritated me imensely as I was sorting games etc for her, so I decided to to instal a custom rom. After 3 roms refused to load (just stuck on the "Samaung GALAXY Ace GT-S5839i boot screen) I decided to try flashing it to 5380i firmware and Pit file - as nearly all custom roms for the ace seem to be for the 5830i variant - I wondered if this would sort my problem!
It didn't! But now it has become a challenge, and a chance to learn something of Android and how it works - as I said in my last post I have successfully flashed an I9000 with carbon and my P5110 with CM11, I learnt how to do this by what I've learnt from reaserching about this phone, so it has been a worthwhile excercise!
But back to the point. No I don't have any back-ups of the original phone, I neither had the knowlege, or know how of having or needing to do this - it's only now I'm finding my phones/tablets so facinanting!!
Yes I am now back to the stock (e3) recovery, which I can get into.
Many thanks for your help so far - I will try your ideas and repeort back!
@macsbig, Yes do that please and after resolving your initial problems , here is a confirmed list of the games compatible with your GPU/CPU of your child's legacy device . Also you can use chainfire 3d only under stock firmware/rooted phone for the games required plugin(s) and app being activate for proper almost lag free experience . You may read theses links as well for some insight : 1 , 2 .
The ext4 formatter link doesnt work my friend
macsbig said:
The ext4 formatter link doesnt work my friend
Click to expand...
Click to collapse
Just cross-linking it ( wasn't my links to begin though ^:^ )
Attached the flash able zip file to the post body .
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Sent from my GT-I9300 using XDA Free mobile app
macsbig said:
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Click to expand...
Click to collapse
Well , researching a new area of knowledge ( in this case customization/rooting/bricking/moding and many more technical things inside XDA) can be a bit overwhelming.I do agree with you that the sheer wealth of material means that it can be overwhelming, but more you read and spend time @ XDA, more you will get the hang of the material presented here .
Nevertheless we are here to share/help all of the possible/working solution mate. Just ask anything you can not understand very well . I will try to depict even more detailed walk-through guidelines.
Regards
Right, I now have a custom rom on the 5839i!
I didn't have too much time last night, so what I did was flashed the phone with Odin, using the bootloader and pit file you specified. I then rebooted into the stock revovery, wiped the Data, Cache and Delvic partitions, then booted into CMW 5.0.2.6 and flashed the EXT4 Formatter tool. I then installed the kernel you specified
After that I rebooted into the CMW recovery from the new kernel and followed your instructions - and Voila! It booted into the slim rom you linked me too
Just to test it wasn't a fluke, I then installed CM9, and that went on fine too - with just the normal steps.
I now have to decide after your other advice, whether I go for a stock rom, and try and get rid of the lag, use chainfire 3D etc or go for a custom mod!
Is there a similar app for modded roms's like chainfire 3D to help game perfomance on this limited hardware? I'd really prefer to use a modded rom and build up from there, but as I stated earlier in the post, this will be used only for games and listening to music from youtube, so i'll maybe have to research some more to find out what would work the best.
Many, many thanks for your help, I've learnt alot during this project!!
Oh as a bit of an aside, got a bit worried when downloading some of the links, some of the "download managers" were causing my anti-virus and anti-malware software to give me warnings!
Thanks again
@macsbig, Glad everything worked out for you mate . To address your concerns I must say that I did not come across any working solution for accelerating your GPU with reduction [email protected] custom Roms unfortunately ( only works on stock fw/rooted device) .
For CM9 beta Rom available @ development sub forum , this is an unstable Rom with some serious problems , because of ICS bugs an other things( Read this troubleshooting session and links provided there ).
For malware's concerns they are mostly false positives . Even virus total wold miss lead you in many cases, due to nature of advertising agent implanted inside some of the app inside system directory of custom Roms . You can simply replace the app in question with another one free of adverts. However they are harmless mostly. Please read this discussion (post #472-475) (post#291-298) between me and moderators team for more information about advertisement policies. Basically we have a very good control over materials presented here , thanks to mod teams .
Hope I did help you with your quest
My apologies, when I said that I was getting anti-virus/malware warnings, that was aimed at when I was trying to download the files on "mediafire(?)" and such like. They want you to install a stupid downloader etc., which then installs some crap on your pc.
Had it when downloading splitfus2 if I recall correctly (it was late 12am!).
That's why in the end I decided to use a pre - split (is that what you mean by wiped?) rom in the end.
I'm gonna have a play with the 'phone again later when I finish work.
Related
Hi all
I am opening up this Q&A thread as extension to my ROM threads, for the simple reason that ever since there is a limitation preventing new users from posting in development threads, I get flooded with PM's. So I intent to move any Q&A, help requests, as well as free and open discussions between users here.
Since the A750 and A789 are so similar, and I put the same stuff in them, I extent both into this one Q&A thread, and in fact, much of it knowledge applies to other Lenovo's like the P700, P700i, S880, A660 which are again very similar and I even use them as basis of my ROM.
Also, I am not intending to be topic police. Like in my other threads, I do not mind if you guys share knowledge about APKHOT or Smileyvvv or Etotalk ROM. As long as it is helpful. Also, I may not always reply myself, so feel free to help each other.
Link to the original threads:
[ROM][2012.xx.xx] Lenovo A750 custom ROM (GB&ICS). <last page>
[ROM][2012.xx.xx] Lenovo A789,P700i,A660 factory&custom ROM (ICS). <last page>
Other related threads (not all mine):
CWM flashing tutorial (update using recovery)
MT6575 flashing tutorial (update using flash utility
Lenovo Original recovery tutorial
[SCRIPTS] Unpack / repack MT65xx boot.img, recovery.img or logo.bin
[REF] Unpacking and repacking stock rom .img files
[UTIL][APP]Lenovo Security / LeSec app (anti-virus/spam/theft/firewall)
[TOOL][TUT]Backup and Restore Mediatek based phone's IMEI
How to DIY : Self root/gapps/playstore/locationfix/clean my ROM
This is a guide on how to root & cleanup your China ROM yourself. It will probably work on all ICS China phones. But it requires & starts with the availability of a recovery image for your phone
There are in fact a few steps:
- Get a proper recovery image for your phone.
- Root it by installing Chainfire's root package
- Install Google GMS ('GAPPS') to get Play Store and Localisation to work
And optionally
- Install Mobile UncleToolset
- Install an extra small fix with location services
- Install an extra small fix with latest APN list
- Install an extra fix to remove well known Chinese system apps
Recovery image
The Recovery Image allows you to boot into an alternative small Linux that you can then use to update the main Android. Updates usually come in "update.zip" scripted files. And the recovery has some other utilities like backup or wipe the entire phone. Getting a working recovery for your phone is step number one, because if you have a recovery, you can do everything else.
To check if you already have a recovery: Well, try to boot into it. The boot sequence may vary with the phone, but on MediaTek phones it is usually to replace the battery and then press&hold both volume buttons while powering up. I have seen it where you need to actually press the power button a split second before pressing both volume buttons. Try a few times, replacing the battery each time.
If you get to a screen that reads CWMR or CWMR Touch (short for ClockWorkModRecovery), you are all set and can continue with rooting. CWMR it is the most common open recovery image. If your recovery is closed, then you need to search the web for a working recovery for your specific model. Each brand and model needs its own recovery, because screen drivers, buttons and partition tables may differ.
Search the web is the best advise. Search wide and search deep. If you cannot find any recovery, then see if you can find a full ROM for your phone. If you have a working ROM image, then there are people on XDA that can make a recovery for you, but typically you need to show/prove that you have really tried to find one yourself.
Flashing a recovery
If you do find a recovery, that you suspect is the correct one for your ROM, then comes the scary part: Flashing the recovery to the phone.
This paragraph is specific to Mediatek based phones. On different hardware you also need a recovery, and once you have a recovery, you can use the other parts of this post, but how to flash other hardware, I do not know, sorry
Flashing using the flash tool is scary to new users. Because new users suspect that if they mess it up, the phone dies. And this is correct! But if you only flash the recovery.img part, you should be fairly safe. Read this manual on flashing. Getting the USB driver installed is sometimes a bit tricky, you may also want to read post #21 and post #25 for help.
I have seen several people asking 'where to find the scatter file'. Well, it comes with the ROM you want to flash. If your ROM file does not come with a scatter file, then is not a ROM file that can be flashed with the flash utility, but with an open recovery.
Rooting
Once you have a working recovery, the rest is simple. For rooting, 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
This usually works by putting the zip file on the SD card (its name can be anything, though for some limited recoveries it sometimes must be named 'update.zip'), booting into recovery, and selecting the zip file to update.
Google GMS (Market/Play Store, Location, etc)
Simply install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9. This is their explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip for ICS and gapps-jb-20121212-signed.zip for JB and can be found here. You probably also want to wipe your cache partition after doing this.
Mobile Uncle toolset
Just install this program apk (so not through the recovery, just install it normally). Or search the web for the latest one.
Fix location services
If location services does not work, do apply Google GMS (GAPPS) above. If it still does not work, it may be because the phone is programmed to use Chinese location services. This patch will tell it to use GMS. The patch will apply, and probably even work, on all ICS phones. But was originally made&tested on a Lenovo A750 ICS. Its called V1.3 because many people have downloaded the A750 v1.3 patch and used it on many MT6575 phones. It is still the same patch, except the update.zip is tweaked to work on any ICS phone, not only MT6575 ones.
Sometimes you also need to go into MobileUncle tool, the MTK Engineer mode, and in location settings. Depending on your exact model, somewhere in there is a NetLoc or NetLocation and a GeoCoding setting, with options of MEDIATEK and GOOGLE. Ensure they are set to GOOGLE.
After messing with location settings, it is best to also wipe cache.
Fix APN list (or My 3G does not connect!)
You can always add your own APN (Access Point Names) from the settings menu. Just add your own, and select that over the pre-build one. But this package will update with the latest list as maintained by CyanogenMod 9. The update.zip was made in such a way it should work on all ICS phones, Mediatek or other.
Clean well known Chinese system apps
<patch still coming>
==========================================
List of known recovery images for Mediatek Flash tool:
Lenovo A750 : 592zn : See also this post #607, nandroid backup does not work.
Lenovo A789 : 592zn or APKHOT
Lenovo P700i : My own, based on APKHOT with CWM.
Lenovo P700 : My own, based on CWMT / 592zn. nandroid backup will not work.
Lenovo A660 : My own, based on APKHOT with CWM
Lenovo S560 : My own, based on APKHOT with CWM (as yet untested)
Additional Recovery Images in this post.
If you feel you searched all over the web, and could not find a recovery for your model, and you next feel you should ask me or one of the other people on XDA to make you one (which I am not encouraging), than please be aware we need at least a 'standard ROM' for your phone to start from. Without it, I can do nothing. So go back out there, and find a standard ROM, does not matter what language, as long as it is for your specific phone model and known to work.
Also, as an extra warning : If you are flashing, and you experiment with 'suspicious' ROM sources, *never ever* flash the preloader, mbr, ebr uboot. Only flash those from a trusted source and if they belong to your exact brand and model phone.
One more reserved
lolo250612 said:
Hello from France,
Just a little message to thank you very much for your very useful "Lenovo A789 factory&custom ROM (ICS)" thread. I have just bought a A789 from etotalk, and your posts really help to master the beast.
I can't participate to the thread because I am a new member and consequently can't post message to this development thread. And this very sad, because I have discovered a shortcoming of this phone. Apparently, the ICS entire phone encryption does not work and, according to some information I have gathered around the web, it may be due to the fact that the internal sd partition is not ext4 which seems to be required.
It may be due to the fact that the kernel does not support ext4. If this was the case, I would be very pleased to activate the option, recompile it and share the result with other people at xda. I have done it for two types of Samsung Galaxy phones.
In this case, the two problems I would be faced with are:
1) Getting the kernel sources. For Samsung it is quite easy. For Lenovo, I am not able to find them (I can't read Chinese).
2) The process to package the new compiled kernel to a zip, compatible with cwm.
Anyway, thanks for your help and to share your knowledge.
Sheers,
Laurent
Click to expand...
Click to collapse
cybermaus said:
well, not sure about encryption, but I can *assure* you that the phone supports ext4, because in fact the root; system; cache; secro and data partitions are all in ext4 . I know that quite certain, because to unpack/repack, I need to recreate an ext4 loop device.
Internal SD is indeed FAT partition. But it is normal for SD to be FAT
Click to expand...
Click to collapse
It is possible the encryption fails on the FAT of the SD card. It is an internal device, if that encryption utility tries to parse all the internal partitions, it may fail on FAT, but I am guessing here. However, then it would fail on pretty much all recent china phones, they all seem to have this internal SD card. You could try to simply format the internal SD as ext4.
I do not think it would fail on the recovery or boot sections. Those are all nicely wrapped up in the first partition of the emmc chip (emmc0p0 or something) in a proprietary filesystem, as I suspect true for all Androids. So your tool would know to exclude that the first one. However, if you want, you can get the original recovery you asked about from the original A789 ROM in my Dev-Host.
Edit: Encryption issue solved, see post#9 below
I already managed to build a multilang framework-res.apk for the A789 ROM. But now there are all those apps that need to be made multilang also - settings.apk and more... a lot of work.
Is it possible to take a P700 ROM with A750 kernel and flash it to the A750? Or a P700i ROM and A789 kernel for the A789? They seem to be almost identical.
Any plans to integrate the long press home button function in A750_ROW_S114_cybermaus_ICS_V3.1? Would like to test this rom but this missing feature is essentail for me...and onother question: V3.1 is also for A789, right? Same problem with long press home feature?
@oz42
Well, I am a little disappointed about that question. Putting the P700_ROW on the A750 is *exactly* what my V3 series is. Works wonderful. It's the reason I have been updating this thread for the last two weeks. Problem is that the only extra language is Vietnamese. You may want to re-read posts #2 and #585 in the A750 thread.
I suspect the same is true for P700i and A789, but I did not find a P700i_ROW rom yet. I did find a S880_ROW, and when I have time (later this weekend) I will check if that has proper multilanguage (edit: No. It adds ru, vi, id to en and zh. Not quite what I had hoped for)
@metzner
Yes. When I know how. But I do not have a clue at this moment. I am very pleased about the V3.1, but the missing long press is annoying me at times.
No, V3.1 is not for A789 (yet). They have different partitions, different schreen driver. YOU CANNOT flash a A750 on A789 (or any MT6575 on MT7577) without 'porting' the ROM. I do have a Frankenstein ROM, using p700_ROW with kernel/partition/modules/baseband from A789. But it was not tried out yet.
A789: Encryption problem
I have installed aLogcat to determine what could block the encryption service on the different ROMS I have tested on my A789. The interesting part revealed to be:
E/Cryptfs ( 87): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Googling for this problem, it appears that there is a strong probability that the culprit is CWMR that I have installed almost right after getting my phone. See: http://forum.xda-developers.com/showthread.php?t=1792101 or http://rootzwiki.com/topic/25652-fixing-galaxy-tab-2-encryption/.
So if somebody has a package that can be safely used with mt6575-flashing tools, to recover the stock recovery or, much better, to install a "clean" version of CWMR, I would be glad to test it and see if it is actually the origin of the encryption problem.
Edit:
@Cybermaus: I have just noticed that you have already addressed part of this message. I have already tried to format the internal sd as ext4 with Minitool partition Wizard on Windows. This fails also. Moreover, the system reports a failure on this partition and ask to reformat it as vfat. I will try by putting back the original recovery from your 4shared. Thanks a lot.
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
That means replacing it with factory recovery will not help, unless if you then also wipe using that factory recovery, and that factory recovery does leave 16KB. You could also try wiping it from the settings menu.
After you have tried the factory , let me know. I think I can make an empty /data for you that is 16KB shorter than the partition, but you would have to apply it using the flash-utility method.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Hi cybermaus
Thanks for your contribution. Please help me if you've free time.
Does this custom ROM support traditional Chinese character?? I'm sure Chinese support would include simplified Chinese.....
@loimlo
The A750 V1 and A789 V2has two forms of Chinese, which I cannot read, but I suspect are traditional and simplified. The A750 V3 has one form of Chinese, which I still cannot read, so I am not sure which of the two, but here is a screenshot of it, let me know which it is.
Amadis223 said:
Hi, I wrote with yuweng on this subject. And it is very strange. He says, that mt6575 has only ext4 filesystem, but I,am sure,that I have mt6575 and yaffs filesystem. What do you think ?
Click to expand...
Click to collapse
Well, all the MT6575 and MT6577 based ROM's that I have dissected have ext4. This is probably because mediatek provides ext4 in their development kit. So yeah, I think all mt6575 are on ext4, and not yaffs. I think maybe the mt6573 has yaffs.
cybermaus said:
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
Click to expand...
Click to collapse
I agree with you.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Click to expand...
Click to collapse
I have flashed userdata.img. That WORKS :victory:. The phone reboots and then encryption starts. Done in less than 5 minutes. Great. Now, just have to tried one of the utility around that allows to have an encryption password different from the lock one. Many thanks for your help :good:.
hi there,
I just got a Lenovo A789 and i just installed A789_S228_cybermaus_V2.1 and it works perfecly...
i'm new to android and i can't get cellular data to work ( i have reason to believe that it worked in original ETOTALK rom, but im not sure ).
1) i do have a data plan
2) cellular data / mobile data is turned on
3) 3G card with cellular data plan is in slot 1
wrong basebands or apn settings (Portugal, Vodafone) ? ( i can see them in mobileuncletools but i cant change them )
help?
note: i cant follow most of android tips that i googled because some of the menus to edit APN settings do not exist on this rom :\
@spinal2k
Well, the simply solution would be to try and apply the A750 V1.4 as listed in post#2. It only applies location fix and new APN list, so its safe on the A789, even if it was originally for A750.
Second option would be to Google for the keyword APN together with your provider and country names.
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
cybermaus said:
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
Click to expand...
Click to collapse
ok, thanks for the tip... how can i see mmc/mnc on mobileuncle tools?
According to that wikipedia page, my MMC/MNC is 268/01 and that it uses GSM 900 / GSM 1800 / UMTS 2100.... On mobile uncle engineer mode i can see that on the 1st sim card UMTS 2100 doesn't exist ( only UMTS 2000 )... :\
acoording to the "you can change APN in..." i can't changed them, just see them... they look fine to me, they're not wrong...
:\
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
cybermaus said:
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
Click to expand...
Click to collapse
oh, i couldn't see that i could add new.... Now i added an optional apn ( even though the one listed was on official carriers page ) ... now its working...
Thank you for the tips... keep them updates coming
note: i did update with A750 v1.3 and i saw no changed in apn list...
A750 V3.1 battery life
I have been using the cybermaus V1.3 ICS for ages, and it works really well. Recently tried the V3.1 ICS.
Also seems to work really well as well, and a definite plus is the 3G signal strength - I see a definite improvement.
There is a dealbreaker problem for me, though - the battery life is noticeably worse than the excellent life on the V1.3 rom. I'm a noob - tried clearing user cache/dalvik, but not reset (I want to keep my apps/data).
Any suggestions before I go back to V1.3 - thanks.
zapzog said:
Any suggestions before I go back to V1.3 - thanks.
Click to expand...
Click to collapse
Well, a request more than a suggestion: your battery is now a few months old, so slightly less good then when new, but you got used to it. But now, due to the flashing of a new ROM, you are playing on it more, and it is in your attention very much.
I cannot properly test myself, I have to tether it daily for data access. So please try to get a proper test of it:
Stay with V3.1 a few bit longer, at least 2 battery cycles extra. (you can barely have had one) so you get a better baseline. Charge the same method as before (I find that charger works better than PC-USB) After two more cycles, when you have a proper idea on the life, go back, and get a renewed baseline on V1.3 also. And then report your results
Hello members hoping I can get some guidance.
Damaged my old phone in a accident the other week so I used my wife's old spare (unlocked) Galaxy Ace GT-S5839I.
As you all know it's a bit dated and slow so I decided to read (a lot) of this forum and decided a rom update was in order.
Looked at the CynagenMod roms. Read the tutorials and downloaded necessary files for the update from SD Card.
Started with CM9_cooperve_Beta_05, excellent rom, used it for 24 hrs but it's unsupported and has a few bugs.
So I decided to go for cm-11.0.0-GT-S5830i-cooperve, again excellent rom but it wouldn't boot with my sim card installed which defeats the objective of having a phone for communication.
I read about installing the modem file to overcome this sim problem and so installed MODEM_S5360_XXMK1.
This did not solve my sim boot issue, so the decision was made to revert back to CM9_cooperve_Beta_05 till I found something withy less issues.
This is when I started having an issue with the rom, though I can't remember the exact phrasing but it was something like Encryption Error when the rom booted, my only option was to reboot and wipe cache etc, which I did, however this did not solve the the issue. It just booted again, every time, with the same encryption issue.
So I came back to these forums and read many threads, some advice was that the intenral sd card was now unreadable, which I guess is real bad.
Other suggestions were to flash a stock rom to the phone, using odin, this could solve the issue, so I have, except now the phone is in a kind of boot loop. Showing a brand logo (used vodaphone and orange roms amongst others) then the Samsung logo then brand logo and so on, stuck in a boot loop I guess.
I have also read that to overcome this boot loop, if the internal sd is damaged, is to use my sd card as an external sd replacement for the internal sd.
This is as far as I got as its 6.15am and I haven't been to sleep yet.
Now most advice on the internet is a little flaky at best so im hoping any members here may be able to give me some good solid advice as to how to best rescue this phone as I really don't want to give up yet.
I can still enter download and recovery modes with the phone.
So please, someone throw me a bone here.
@ cbagy , So your internal partitions at first was transformed into EXt4 if I am not mistaken (CM9_cooperve_Beta_05) , then you decided to convert them into MTD through CM11 , which I have no idea what was your guideline to do so . Finally to make the long story short you couldn't revert back to clean installation state << RFS partitions> ( stocked in endless boot loop I assume ).
First few tips about ICS based Roms ( i.e : Beta 5 CM9 ) : "Encryption Unsuccessful - Reset Android" warning is due to a bug in the firmware for the memory card in your phone, which might be triggered by ICS incorrect function << I am just a novice Android guy, So I might be wrong on many counts ,, just trying to help though >> (/data and /sdcard partitions are no longer accessible). So lets not assume we have a worst case scenario , which is Samsung Captivate/Hardware related problems ; a.k.a : Bad internal SD.
S5839i and s5830 i have a very similar CSC/PDA/MODEM functions , so just grab one of the newest Wipe flash able package made by splitfus2 app ( preferably based on your region /Country, if you insist ) >> I need you to read post#8 starts from the line "-from sammobile database; this page......." to the end of my comment to get to clean state, which is required for rest of the process .
Requirements :
Temporary CWM zip flash able file( 5.0.2.6) or ( 5.0.2.8) , CooperVe compatible; obtainable from >> 1 , 2 , 3 , 4
Proper drivers installed inside your PC; Download Odin3.v3.07.Cooperve ( i,e : this post or any official sticky topic) >> pit file is also resided inside the file .
Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar > or any working version for this device you got . ( could be found in post 8 )
After bypassing loop issue , I would like to suggest downgrading to CM7.2 based Rom, using EXT formatter tools to convert into EXT4 manually;installing CM Specific Basic Kernel - BroadcomCM[COOPERVE][v4.0 ]; and rest of story @ post#3,4 .
Before starting with your CM7.2 based, You need to Re-partition your 2 gb SD card through your Temp-CWM >> Go to "Advanced" >Select "Partition SD Card>Choose your SD-ext size (/data is bound to be the first size you choose << for 2 GB, 512 MB max>>, the rest would be /sdcard ; swap "0" MB)
last resort is Editing "etc/vold.fstab" and swap path of internal and external SD card as you have suggested for possible bad SD .
So , for now proceed with initial boot loop issue and report back ,,,
Edit : Reading at least few pages of this topic is recommended, if you like to learn more about ICS problems.
Excellent news, all working, thank you so much you are a star.
All ready had most (if not all) the tools required.
Phone back to stock using a Euro/Russian split rom.
Seems the split roms work with through Odin where as the one file rom doesn't.
Phone reports a S5380I device rather than a S5839i but that doesn't matter.
Im ready to move to a 7.2 rom.
Continuing to read the last part of your post regarding reformatting etc but it's all a little hazy for me right now but I will continue reading.
Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
nashsx said:
Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
Click to expand...
Click to collapse
Humm,, Please define the version of Temp-CWM you did flash( CooperVe compatible assuming)
Define 'flashed a kernel' please, Your stock firmware already contains a stock kernel, which is quite capable of performing what we are expecting from basic kernel. ( Explains in details how did you install custom kernel or custom Roms etc etc,,)
Always do your Nandroid/EFS/Data back up prior to tinkering though.
IF the only option available to you due to soft bricking is , Downland mode >> upon flashing over Odin your /data partition will be wiped out for successful restoration of your device.
waiting for your through explanation,,,,,,
Hello,
thanks for your reply. Unfortunately I cannot specify the CWM version anymore, but I flashed a custom kernel via the CWM, it was a flashable zip file downloaded somewhere in this forum that I flashed using CWM (which I installed using ODIN, iirc). The reason I cannot say what CWM I installed is, I had a data loss on the hard drive inside my computer where I downloaded the files to. If it's really important to know what kernel it was, then I believe I could reconstruct this by searching the custom kernel section for the specific device in this section, I am sure I will know when I read the name again. While waiting for a new reply I'm gonna do this to find out what kernel I flashed via CWM.
The problem with the last resort suggested by you, ODINand download mode and this stuff, is that the data I need to restore is located in data partition if I am correct. Or maybe I'm wrong? The data is from the android text editor notepad which I found out doesn't store data in /sdcard partitions, neither internal nor external, so if I'm right, this means it's being stored in the application's data directory. Please tell me if I'm wrong with this guess.
.
Regards,
Nash.
@nashsx, I fully understand your concern in regards of sensitive data recovery from internal SD partition. However you need to be more specific with all of the tools and Roms you did use whenever you ask for accurate assistance .
Nevertheless I am going to explain all of the errors and possible symptoms you might encounter during CWM flashing to Kernel procedure .
First , You need to comprehend that for your device's ( known as CooperVe) safety we need to use compatible temporary CWM flash able zip file or CWM comes with kernel . The latter is not recommended though for many reasons I would not engage at the moment ( files could be found here or here for instance,,,OR any official sticky topic )
As for kernel Let me be clear : We do not flash custom kernel on top of stock firmware for s5830i/C/M/5839i devices under any circumstances. This is a correct order >>
Stock Firmware >Custom Rom based on stock kernel > Custom kernel
Alternative : flash Custom Rom comes with custom Kernel , and there are so many wiping and formatting process will be involved in between flashing I would not go into more details .
Basically we are obtaining an exclusive right to use Mods/Scripts/Tweaks : performance , battery ,, etc etc at boot time , by activating our init.d support with the help of custom kernels and much more stuff we can perform after flashing. ( Well established name you requested : Rafael.Baugis ; ThunderKernel ; CyanogenMod 7.2 Specific BASIC Kernel ; Hells Fusion )
Now a little educational standard internal memory partitions one- on-one :
/boot
/system
/recovery
/data
/cache
/misc
SD card partitions :
/sdcard
/sd-ext
/data or User data , is the part in question you are trying to access via recovery , which is not an option anymore sadly.
This is where your contacts, messages, settings and apps that you have installed go. Wiping this partition over Odin with the help of wipe - flash able 3 parts package made by splitfus2 app( and other options ticked : re-partition and pit & boot loader selected ) for example ;essentially performs a factory reset on your device; restoring it to the way it was when you first booted it.
We only have 2 options ( if you can call it an option at all in reality ) for recovery procedure , since you don't have access to either of stock e3 / CWM recovery consoles .
1.Normally During boot loop ADB won't work, but we can give it a try ( ADB debugging option must be ticked inside Developer settings inside your Android OS ; platform-tools is required or any GUI based app such as Droid manger will do .
2. Flashing only one part file ( xxx.tar.md5) Over Odin3.v3.07.Cooperve ; you may pick your file from here < registration is required >. Proper drivers installed inside your PC; Put the file into PDA part and do not touch anything else ( Factory reset and Re-partition not selected, Reboot option is OK though ) > click start. ( Do not remove USB cable till the process being terminated and take a complete screen shot of Odin log file entries for me.
This method does not wipe the partition in question., but there is a strong possibility you can not bypass the initial boot loop to get into the OS though.
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download