Related
Hi All!
Since this is my first tutorial, I am asking xda-developers' seniors' permission to post this.
I managed to root and install ROM on my P780, and I notice that there is no simple tutorial to root or/and install CWM and ROMs, so I thought why don't I do my own simple tutorial, especially for beginners like me?
1. ROOTING
Actually, rooting is simple for this phone. I used Framaroot for my phone. Thanks to Alephzain (search Alephzain framaroot in xda-developers forum). Just download Framaroot 1.6.1 from his tutorial, install it, and follow the instruction. Simple.
2. CWM
I know there's a lot of easy ways out there, but I used Mobileuncle for mine. Open PlayStore, search for Mobileuncle MTK Tools, download, install. You can get many CWM 6.1 img type out there for P780 (sorry I'm denied to post links), put it inside your SDcard. Then, open Mobile uncle, tap Recovery update, find your img file name. To find out there's CWM installed, just reboot to CWM when finished, or press volume up + volume down + power button when phone turned off.
3. ROM
I managed to find many available roms in needrom site. Some use CWM and some use Flashtool. I don't know, but I failed all ROMs that use CWM, so I'll tell you how to use Flash tool.
First, download flashtool and MTK drivers on your PC (I use Windows 7). Then, download your desired ROMs or stock ROM. There are direct links in the needrom site. Just register to see the links.
Install MTK drivers first. Then run Flashtool. click scatter-loading. Find MT6589_Android_scatter_emmc.txt in the downloaded ROM folder. Make sure DA DL All With Check Sum box is checked. Click firmware upgrade. Turn off phone. Connect via USB.
Wait until finished. (Green Circle Pop Up Window). Done. Restart phone.
Hope it helps. Press thank if I helped.
zainal2adidin said:
Hi All!
Since this is my first tutorial, I am asking xda-developers' seniors' permission to post this.
I managed to root and install ROM on my P780, and I notice that there is no simple tutorial to root or/and install CWM and ROMs, so I thought why don't I do my own simple tutorial, especially for beginners like me?
1. ROOTING
Actually, rooting is simple for this phone. I used Framaroot for my phone. Thanks to Alephzain (search Alephzain framaroot in xda-developers forum). Just download Framaroot 1.6.1 from his tutorial, install it, and follow the instruction. Simple.
2. CWM
I know there's a lot of easy ways out there, but I used Mobileuncle for mine. Open PlayStore, search for Mobileuncle MTK Tools, download, install. You can get many CWM 6.1 img type out there for P780 (sorry I'm denied to post links), put it inside your SDcard. Then, open Mobile uncle, tap Recovery update, find your img file name. To find out there's CWM installed, just reboot to CWM when finished, or press volume up + volume down + power button when phone turned off.
3. ROM
I managed to find many available roms in needrom site. Some use CWM and some use Flashtool. I don't know, but I failed all ROMs that use CWM, so I'll tell you how to use Flash tool.
First, download flashtool and MTK drivers on your PC (I use Windows 7). Then, download your desired ROMs or stock ROM. There are direct links in the needrom site. Just register to see the links.
Install MTK drivers first. Then run Flashtool. click scatter-loading. Find MT6589_Android_scatter_emmc.txt in the downloaded ROM folder. Make sure DA DL All With Check Sum box is checked. Click firmware upgrade. Turn off phone. Connect via USB.
Wait until finished. (Green Circle Pop Up Window). Done. Restart phone.
Hope it helps. Press thank if I helped.
Click to expand...
Click to collapse
nice and deep explanation, thanks for your sharing
I really hope this smartphone gets developers attention
lenovo or some others gift reputed developers like ravi kiran cg a lenovo p 780. i really want to buy this phone but no developer support for it is a great bummer.
i am about to buy this phone...i do hope we could help each other out in improving this phone support
If u from malaysia and can read malay, u can copy all my P780 tuto's here
http://www.lepakspot.com/showthread.php?pid=3567#pid3567
More to come just need more support from P780 users
Edit: i only share the stable official ROW 119 (world) rom in it
ROM
Has somebody tried this
ht_tp://kitkatjellybeanj.blogkats.com/2013/09/upgradeupdate-lenovo-p780-to-44-kitkat.html
deepakanto said:
lenovo or some others gift reputed developers like ravi kiran cg a lenovo p 780. i really want to buy this phone but no developer support for it is a great bummer.
Click to expand...
Click to collapse
That's what I'm saying. It looks like the only long-use device with developer support are the MAXX line of devices from Motorola. But those are all Verizon exclusive, and I'm on T-Mobile here in the US. Also, the older devices use OMAP chips, which have also lost almost all support from everyone.
zainal2adidin said:
Hi All!
2. CWM
I know there's a lot of easy ways out there, but I used Mobileuncle for mine. Open PlayStore, search for Mobileuncle MTK Tools, download, install. You can get many CWM 6.1 img type out there for P780 (sorry I'm denied to post links), put it inside your SDcard. Then, open Mobile uncle, tap Recovery update, find your img file name. To find out there's CWM installed, just reboot to CWM when finished, or press volume up + volume down + power button when phone turned off.
Click to expand...
Click to collapse
Thank you for your tutorial !
I have a problem on Step 2, I open Mobileuncle, download the P780 CWM image, reboot, but everything is in Chinese :|
How can I find an english version ?
L.E. Found it here:
http://www.lepakspot.com/showthread.php?pid=3567#pid3567
encik_racun said:
If u from malaysia and can read malay, u can copy all my P780 tuto's here
http://www.lepakspot.com/showthread.php?pid=3567#pid3567
More to come just need more support from P780 users
Edit: i only share the stable official ROW 119 (world) rom in it
Click to expand...
Click to collapse
You have a great tutorial there, but if it's not too much to ask, can you post also an english version of it (google translate does a pretty poor job)?
I can offer support as P780 user
Hi Guys... Will it support Indian languages?
translation
zangaby said:
You have a great tutorial there, but if it's not too much to ask, can you post also an english version of it (google translate does a pretty poor job)?
I can offer support as P780 user
Click to expand...
Click to collapse
I just completed this guide's translation; simply follow the original link to the forum post on LepakSpot.com and locate it there.
encik_racun said:
Here u go hxxp_//www_dot_lepakspot.com/showthread....d=3567#pid3567
Click to expand...
Click to collapse
Hope this is helpful... :laugh:
Help with P780 bootloop
I realize this is long, but I thought it best to be as specific as possible....
A 'little' history:
I'm fairly used to working with Android but would only consider myself an intermediate user. That said, I'm an experienced PC/Linux user and am not afraid of terminals etc. All things considered, I made a pretty lame mistake while tired one evening.
I own a Lenove P780 and rooted it using Framaroot (because I was seriously tired of getting dangerously low on storage due to only 4 gb internal; 8gb not available in Indonesia). However, on this ROM version (P780_ROW_S115) there wasn't an option to install to extsd, so I needed a program to do so. I used Link2sd but needed to repartition my sd card first in order to do continue. I used Aparted to create a 1gb swap file (amazing what this did for my RAM usage), 4gb ext3 install partition and the rest simple storage formatted using FAT32 (it's a 32 gb Sandisk Extreme). Then, I moved almost all of my downloaded apps and a few included apps to the external sd ext3 partition. Sweet, no more space issues.
I then installed a CPU governor, can't remember the name off hand now. Set a number of parameters and found further performance benefits, especially battery usage. Following that, I then installed ROM Manager Lite. Nice tool. Now is the point when I really wanted to make a back up of my ROM, so I attempted to install CWM or TWRP recovery using ROM Manager Lite's update/download section to no avail. I ended up using MobileUncle to do the trick; found out the version of TWRP that many forums stated worked with the P780 (2.5.0.0 if I'm not mistaken), copied it to the root of the extsd card and installed with MobileUncle. All great so far...
Until I went to make a back up. When in the graphical interface of TWRP while ROM running there was the option to back up to internal or external, I ticked external. It then rebooted into the actual recovery UI, however eemc was the only option to back it up to and it stated the external sd had 0MB. I tried this many times and still the same issue; can't make back up and external not recognized. Google to the rescue. Found out that perhaps it could be an issue with improperly formatted storage cards. I had to assume since I have 3 partitions on the card, that it can't read the storage one. In order to test the theory, I was about to buy a new card, format it to FAT32 with that being the only partition on it and attempt a back up. However, before I had the chance to do that, I decided to try a provided Recovery in MobileUncle. I thought I had chosen a ROW version but I obviously hadn't and turns out it was a Chinese one... Man, if only I were a bit more patient (read: not so stupid)...
Anyway, of course you already know the scatterfile ect. is different from ROW and now I'm stuck in bootloop. I've studied my options and am going to use Flashtool but have a question before I do any more damage... He..he..he... Should I simply use the official ROM from Lenovo (I have ROW_s115 and can only find official ROW_s119 online; no OTA updates available prior to this mishap in Indonesia) and only tick the Recovery box in Flashtool, or can I simply load the s119recovery.img, tick the Recovery box and go for it? I assume that it would be better to use the full stock ROM instead of simply using the Recovery.img in Flashtool considering it may need to redo the filesystem as well... Not sure really. What do you think would be best? Also, would the recovery in the stock ROM P780_ROW_s119 be the same as the stock ROM s115?
Any expert (or any) advice would be very appreciated... Thanks in advance!
Michael
hi i have a problem with my p780
I followed step 1 was fine
Step 2 all right, then reset growth
and does not start, there is logo "Lenovo" stay 3-4 sec and disappears and then appears again and so dont start
I tried to volume up + volume down + power button and so dont start
I managed to get only in factory mode* just as it is in Chinese and fail
you can help Please
"sorry for my english or sorry my english"
Bulegila said:
I realize this is long, but I thought it best to be as specific as possible....
A 'little' history:
Any expert (or any) advice would be very appreciated... Thanks in advance!
Michael
Click to expand...
Click to collapse
I dont know if you are really "bule" or it's just a nickname, but if you are really a bule and as you said you live in Indonesia, i assume you know Bahasa Indo even just a little maybe you can check at
www.kaskus.co.id
and search keyword "Official Lounge Lenovo P780" or
on Facebook groups "Lenovo P780 Indonesia". You can get plenty stuff there.
Hit thanks if I helped you even just a slight.
Sent from my Lenovo P780_ROW
Does anyone have any functional utility to repartition internal storage for asia version (for Lenovo P780 / MTK6589)? For world version i know function utilities.
bulegila
anchaz_al_ayaz said:
I dont know if you are really "bule" or it's just a nickname, but if you are really a bule and as you said you live in Indonesia, i assume you know Bahasa Indo even just a little maybe you can check at
Xxx_kaskus_co_id
and search keyword "Official Lounge Lenovo P780" or
on Facebook groups "Lenovo P780 Indonesia". You can get plenty stuff there.
Hit thanks if I helped you even just a slight.
Sent from my Lenovo P780_ROW
Click to expand...
Click to collapse
Iya, saya memang bule yang tinggal di Indonesia dan situs Web itu akan tolong banyak, pasti. Terima kasih. Masalah P780 sudah akhirnya selesai dengan bantuan dari lepakspot.com yg tadi dalam post encik_racun. Saya udah translate guide dari bahasa Indo ke Inggris di website tersebut.
If anyone that is restricted to using English needs some help upgrading to ROW_119, the guide and it's translation can be found from the link in the following quote:
encik_racun said:
If u from malaysia and can read malay, u can copy all my P780 tuto's here
hXXpwww_lepakspot_com_showthread....d=3567#pid3567
More to come just need more support from P780 users
Edit: i only share the stable official ROW 119 (world) rom in it
Click to expand...
Click to collapse
Lenovo P780 8Gb custom rom
Links here
https://www.facebook.com/groups/229759483863558/
If somebody need good recovery, try this: http://d-h.st/5U4
It is Carliv Touch Recovery 2.2. - They have some function as TWRP, some as CWM (6044).
In this zip are two zip with different version of CTR. First is for asia base rom (as s135, s125, etotalk, etc.), second is for world base rom (s119, s110, etc.). I personaly ported/tested in my P780 with miui, lewa, viberom and Sxxx stock version.
---------- Post added at 12:12 AM ---------- Previous post was at 12:03 AM ----------
Bulegila said:
I realize this is long, but I thought it best to be as specific as possible....
A 'little' history:
I'm fairly used to working with Android but would only consider myself an intermediate user. That said, I'm an experienced PC/Linux user and am not afraid of terminals etc. All things considered, I made a pretty lame mistake while tired one evening.
I own a Lenove P780 and rooted it using Framaroot (because I was seriously tired of getting dangerously low on storage due to only 4 gb internal; 8gb not available in Indonesia). However, on this ROM version (P780_ROW_S115) there wasn't an option to install to extsd, so I needed a program to do so. I used Link2sd but needed to repartition my sd card first in order to do continue. I used Aparted to create a 1gb swap file (amazing what this did for my RAM usage), 4gb ext3 install partition and the rest simple storage formatted using FAT32 (it's a 32 gb Sandisk Extreme). Then, I moved almost all of my downloaded apps and a few included apps to the external sd ext3 partition. Sweet, no more space issues.
I then installed a CPU governor, can't remember the name off hand now. Set a number of parameters and found further performance benefits, especially battery usage. Following that, I then installed ROM Manager Lite. Nice tool. Now is the point when I really wanted to make a back up of my ROM, so I attempted to install CWM or TWRP recovery using ROM Manager Lite's update/download section to no avail. I ended up using MobileUncle to do the trick; found out the version of TWRP that many forums stated worked with the P780 (2.5.0.0 if I'm not mistaken), copied it to the root of the extsd card and installed with MobileUncle. All great so far...
Until I went to make a back up. When in the graphical interface of TWRP while ROM running there was the option to back up to internal or external, I ticked external. It then rebooted into the actual recovery UI, however eemc was the only option to back it up to and it stated the external sd had 0MB. I tried this many times and still the same issue; can't make back up and external not recognized. Google to the rescue. Found out that perhaps it could be an issue with improperly formatted storage cards. I had to assume since I have 3 partitions on the card, that it can't read the storage one. In order to test the theory, I was about to buy a new card, format it to FAT32 with that being the only partition on it and attempt a back up. However, before I had the chance to do that, I decided to try a provided Recovery in MobileUncle. I thought I had chosen a ROW version but I obviously hadn't and turns out it was a Chinese one... Man, if only I were a bit more patient (read: not so stupid)...
Anyway, of course you already know the scatterfile ect. is different from ROW and now I'm stuck in bootloop. I've studied my options and am going to use Flashtool but have a question before I do any more damage... He..he..he... Should I simply use the official ROM from Lenovo (I have ROW_s115 and can only find official ROW_s119 online; no OTA updates available prior to this mishap in Indonesia) and only tick the Recovery box in Flashtool, or can I simply load the s119recovery.img, tick the Recovery box and go for it? I assume that it would be better to use the full stock ROM instead of simply using the Recovery.img in Flashtool considering it may need to redo the filesystem as well... Not sure really. What do you think would be best? Also, would the recovery in the stock ROM P780_ROW_s119 be the same as the stock ROM s115?
Any expert (or any) advice would be very appreciated... Thanks in advance!
Michael
Click to expand...
Click to collapse
Is absolutely important!!! If you have Asian version rom on your phone (s135, s125, etotalk, etc), you must have the Asian recovery. If you have a world rom on your phone (s119, s110, etc), you must have the world recovery.
Try this recovery... http://d-h.st/5U4 (in this zip file is both version).
Hi, try this blog about lenovo p780, my be you find answers. http://lenovop780en.blogspot.ro/
Sorry for my english.
my experiences with this device
I will share my experience with this device.
I got it with a VIBEROM_V1.0_1347_3_ST_P780.
gives a good impression, most apps work very fine.
but
root wasn´t possible (see needrom thread, now there seems to a way how to root it)
my external bluetooth keyboard don´t work
that is a nogo - so I flashed
http://forum.xda-developers.com/lenovo-p780/development/rom-lenovo-p780-pre-rooted-official-t2553725
S123 worldwide rom --> no external keyborad
chinese rom S135 --> no external keyborad
within this rom there is offered an update to viberom VIBEROM_V1.0_1405
I did so: no multilanguage, no external keyboard
then http://www.needrom.com/mobile/lenovo-p780-2/
German ok, but no external keyboard.
--> I sold the device on evbay.
Don´t get me wrong. It a good device, good screen, good touch.
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
dwelch77 said:
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
Click to expand...
Click to collapse
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
aicjofs said:
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
Click to expand...
Click to collapse
Exactly. I can not navigate the options at all. Volume - doesn't do anything, Volume + doesn't do anything.
OK scratch all of that. So while I was messing around with it this morning I accidentally dropped the tablet. After "impact calibration" the keys worked and I was able to get into TWRP. And Nabi Lab recognized it was plugged in. I was able to get it set all the back to factory with the factory boot recovery in place as well. As of right now update 2.1 is downloading and I'm keeping my fingers crossed that it will work.
The only thing I can think of is something on the board might have a broken solder connection, so as of right now I'm touching it as little as possible until the updates are done. I'll post back here when I have more information.
Nabi 2 Bricked ?
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Dowmole said:
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Click to expand...
Click to collapse
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
aicjofs said:
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
Click to expand...
Click to collapse
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Dowmole said:
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Click to expand...
Click to collapse
So what exactly did you do again? It was an original Nabi2 on ICS, and you "wiped" it. What exactly did you wipe? All the partitions not showing up is usually I sign of the wrong TWRP build but you said you tried both. Plus I have never seen where you can't mount the MicroSD
In the terminal app in TWRP(both versions) what does it say if you type
cat /proc/partitions
does it look like this:
major minor #blocks name
179 0 7766016 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 823296 mmcblk0p3
179 4 481280 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 1536000 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 65536 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 4485120 mmcblk0p11
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
or more like this
major minor #blocks name
179 0 7766016 mmcblk0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
Thanks for your help on this aicjofs I really appreciate it
It shows :-
179 0 31166976 mmcblk0
179 1 1 mmckblk0p1
179 5 31164416 mmcblk0p5
The whole "short" story was....When I received the Nabi 2 just over a year ago I had to somehow get Google Play Store on it. As we know that wasn't possible until recently so I followed the guide by Victoria (I think from memory) on Youtube. This then did not allow me to do further Nabi updates. I managed to get this back to stock from your guide and then update bit by bit to the latest update (wit Jellybean). All was great until I realised that the wrong one of my children had been setup on it. I removed the user (from the parent portal on the Nabi website). This then stopped me using the external SD card (media errors stopping it)
So stupidly (in hindsight) I took it upon myself to wipe the Nabi from within Jellybean and re-boot, thinking that it would be a straightforward re-setup. But it wasn't. It seemed to have un-mounted everything. So now within TWRP I cannot mount data, system, cache, external sd card. and therefore cannot wipe those folders and start again (from TWRP that is). I have tried to mount those folders from terminal but am getting nowhere
Thanks
Dowmole
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Dowmole said:
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Click to expand...
Click to collapse
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Radmatazz said:
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Click to expand...
Click to collapse
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Your solution was awesome!
2girlzdad said:
I had a similar issue -- I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Click to expand...
Click to collapse
-----> My issue was EXACTLY the same, I used your solution and viola, it is fixed, it even auto asked me to install root before I rebooted! THANK YOU... as a rank amateur, I feel I should share the finer details of my solution to help anyone else out that also has this problem.
I did a couple things different from this, that I should share so that all will benefit.
I use NabiLabGUI. The TWRP that comes with it does NOT work with my build. I searched for the TWRP that comes with it,
Found at my 'C:\Users\Spam\AppData\Local\Apps\2.0\7J1BHCKA.8HM\5YTQ71XH.YAP\ then 2 sub directories,
nabi...exe_3432fd94fe885e67_0001.0002_none_141f851fecdb6e30 and
nabi..tion_3432fd94fe885e67_0001.0002_f75a67d47ecb93e2
since I have a nabi 2 NV7A, for my daughter, I opened the subdirectory '2' in each replacing the 2\recovery\new\recovery.img with the one from twrp-recovery-JBNV7AUS-263.zip (note you must rename it to 'recovery.img')
I then ran nabilabgui, simply selecting the recovery installer, to easily load the recovery image, booted into the now version 2.6.3 TWRP, and loaded the 'twrp-recovery-JBNV7AUS-263.zip'
No boot/softbrick
I am unable boot beyond the bootloader screen. I cannot gain access via Nabi Lab GUI with ADB but I can via Fastboot. So my issue is how do I fix my Nabi 2 via Fastboot? I need commands and where and what files to get back to stock.
Thank you,
Niles
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Doozeman said:
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Click to expand...
Click to collapse
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
aicjofs said:
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
Click to expand...
Click to collapse
Thanks very much for the reply. I did have PDANet installed and my computer couldn't see the tablet. I will try again soon later. I think my problem has arisen since i followed a procedure from this link http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98 and I may have messed up flashing this file http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91 too early!. Ultimately I wish to have this file http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85 on the tablet and it being up and running with no problems.
First things first though I need to get the tablet seen by the computer.
Do I need to uninstall my Nexus 7 and Samsung Galaxy S III drivers first before installing PDANet? Once installed how do I get fastboot installed?
Many Thanks in Advance,
Doozeman
Okay I now have found how I can install TWRP via your command but I'm still unable to install an OS on the tablet. NabiLabs refuses to see the tablet and I am now stuck. Tell you what like this is a steep learning curve for me! Why can't this tablet be as easy as the Nexus 7 to flash or recover?
Have you any more suggestions as to how I can proceed? Is there another way I can push installation files? I have tried copying stock restore files (as supplied by Nabilabs) to a micro sd card using the following layout TWRP/BACKUPS/"My Device Number"/restore but no matter the version of TWRP installed there are no files shown to restore.
*Update* I have tried to install the latest TWRP via flashable zip but it won't install because of the missing folders as there is no OS installed. I get an error status 6. Unable to mount /data, /system, /cache etc.
I'm beginning to fear that I have killed this tablet
I'm tearing my hair out here!!
Many Thanks in Advance
Completely and totally stumped
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
sandrewmorrison said:
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
Click to expand...
Click to collapse
Usually a sign u flashed ICS TWRP instead of JB.
aicjofs said:
Usually a sign u flashed ICS TWRP instead of JB.
Click to expand...
Click to collapse
Can you tell me the version numbers of each version? I believe I have tried both. Both have told me I have no OS installed, cannot mount any internal anything, can't format it, and doesn't show any internal storage space. It comes up as 0mb.
Hi All,
Let me share my experience on how I updated my Huawei P9 Plus for Latin America region. Hopefully this will help others to get their phone successfully working on Nougat.
Requirements:
Unlocked bootloader (there are plenty of articles about how to do this online)
Custom Recovery (TWRP) - Use only the one from this thread: https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Data File - Download it from here
Micro SD (4G or bigger)
First off, I followed the instructions from here: http://ministryofsolutions.com/2017/06/huawei-p9-plus-vie-l29-nougat-b361-emui-5-latin-america.html
I know here there are many tutorials on how to do it, but this was the site I used as it had 3 different ways of doing it and it was pretty straight forward. I used the 1st method which required to make the change on HiSuite and Huawei Updater.
The struggle happened when the phone rebooted, the phone got into a C900 version and the ROM itself got installed but many apps were missing and bluetooth was dead. There's a reason for that! The installation is a 2 part process and the files installed are:
update.zip (The basic ROM)
update_data_full_hw_la.zip (Drivers, 3rd party apps, Huawei apps such as notepad, calculator, among others)
Evidently, the 2nd file was not installed, ergo, the ROM was not entirely installed. Let's say that it's like installing Windows 10 with drivers and apps for windows XP!
But... Why did this happen? Well, the answer is simple, Android 7 encrypts the DATA partition, this is where the missing apps are installed and when the update runs, the 2nd file is not installed due to this issue (the partition becomes READ ONLY).
At this point, create a folder on the root of the Micro SD called dload, put the update_data_full_hw_la.zip file there, DO NOT UNZIP IT!
This is the tricky part! I looked for TWRP for this phone and NONE of the vienna versions worked, so, finally, I found the thread mentioned above on this post and installed TWRP for Honor 8. Installation steps can be found on the article.
Finally, I rebooted into recovery (Vol Up + Power button). Recovery works! Now, go to Install in TWRP, change to External Storage (by default, TWRP looks for the internal storage) go to the dload folder and then select the update_data_full_hw_la.zip file, it will start installing the file, it will take a few mintes.
Finally, TWRP will ask you if you want to format cache/dalvik. Do so.
The phone will reboot and the ROM will be fully installed and everything will be working with all apps, settings and everything as you had it on Marshmallow but now... On Nougat!!!
I hope this helps!
Hello! First post here!
Just got a new STF-L09 on the amazon cyber Monday sale (had an iphone before) and in my excitement to start messing with it, I managed to brick it.
I was following this guide: https://forum.xda-developers.com/honor-9/development/beta-twrp-3-1-1-0-t3654355 and did a full format through TWRP to try and get rid of the encryption in order to root it. Now my device is in a bootloop. I've been looking through older posts here on XDA, boycracked and a few other places but there seems to be quite a bit of contradictory information and I don't want to make anything worse.
What I have:
- An unlocked bootloader
- Working TWRP 3.1.1
- ADB and fastboot (over USB from my laptop running linux)
- A microSD card
- Ability to boot to force update process
What doesn't work:
- my TWRP backup (I didn't realize the one I tried to make failed/got deleted).
- the stock eRecovery tool. Even on stable wifi it cannot retrieve package information from server. I'm assuming this is because Huawei hasn't made the recovery firmware available over this channel for this model.
I'm now trying to do a force update using a stock ROM and my external SD, but I'm having trouble for two reasons:
1. I'm not exactly sure what my initial firmware was, so I'm not sure which ROM to pick.
2. I can't successfully transfer the contents of the update.zip I'm trying to use into a dload folder on the root of my sd. I'm assuming this is because the sd card is formatted to vfat and the UPDATE.APP file is larger than 4GB and therefore not supported on vfat.
Can anybody tell me:
A. How to find out what my initial firmware designation would have been? Phone was recently purchased for UK market, blue colour, 64GB internal memory. Came with EMUI 5.1. I have S/Ns and so on if that helps.
B. How to perform force update with microSD in my situation? Can I format the card to NTFS or another format that supports >4GB filesizes? Am I using the wrong ROM (This is the one I'm trying to use: http://androidhost.ru/v5 )? What files exactly should go into /dload/ at the root of the sd?
C. Is there another procedure I should try in my case? I am able to use fastboot, and I understand it would be possible to flash files onto the device using that, but I'm just getting started with Android and I'm not really sure about the functions of the various images/partitions (eg. data, cust, boot etc.). Is there any hope of the eRecovery tool coming online?
I know some of you have had some success coming from similar situations. I'd really appreciate any help you guys could give. Happy to throw some dosh to anyone who can help put me back in business!
Fixed my own problem 5 minutes later with help from this thread:
https://forum.xda-developers.com/honor-9/help/help-to-restore-l09-bootloop-t3651641
Wrote up my procedure there. But thanks anyways guys!
:victory:
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