"@Cleopatra"
Obviously my post was partly misleading.
Quote:On the desktop PC I would check now whether the card reader is properly connected and detected by the OS. I would use lsusb and lspci.
By that I meant that if it was a Desktop PC related problem, then I would type 'lsusb' there. Since it is an Android problem I did this check on my phone's terminal. And there (on the phone) only the USB port was listed. I think, that the SOC design doesn't require the phone's card reader to be connected to USB. I hope that made my idea more clear - although it led to nothing.
Did you check the creation ob the block devices in the phone's normal operation mode or in recovery mode? I didn't connect the phone to my desktop PC because on Windows 10 the MTP drivers got seriously destroyed so the phone was not recognized any more. I did the 'ls /dev/block' in recovery mode (TWRP) on the phone's terminal. It's provided by TWRP.
(2016-09-05, 06:34)tom.1 Wrote: [ -> ]"@Cleopatra"
Obviously my post was partly misleading.
Quote:On the desktop PC I would check now whether the card reader is properly connected and detected by the OS. I would use lsusb and lspci.
By that I meant that if it was a Desktop PC related problem, then I would type 'lsusb' there. Since it is an Android problem I did this check on my phone's terminal. And there (on the phone) only the USB port was listed. I think, that the SOC design doesn't require the phone's card reader to be connected to USB. I hope that made my idea more clear - although it led to nothing.
Did you check the creation ob the block devices in the phone's normal operation mode or in recovery mode? I didn't connect the phone to my desktop PC because on Windows 10 the MTP drivers got seriously destroyed so the phone was not recognized any more. I did the 'ls /dev/block' in recovery mode (TWRP) on the phone's terminal. It's provided by TWRP.
I check the blocks in normal operation mode.
All Windows OS are a real tragedy for Android LOL
(2016-09-05, 06:44)Cleopatra Wrote: [ -> ]I check the blocks in normal operation mode.
All Windows OS are a real tragedy for Android LOL
Your results are no surprise then
- in normal mode the microSD card works.
My laptop is new since 2 months and I've left some space for linux, but hadn't the time to install it. Maybe this time is now ...
Regarding the microSD problem I found that the kernels of the stock recovery and daohoa24's recovery are identical. I did this check with Windows' 'fc /b file1 file2' command. Hope this is as accurate as a diff. That fact leads me to think that the microSD functionality might have been left out intentionally. I have no deeper insight in the structure of Android and it's operation modes and assume that recovery and normal mode have dedicated kernels. The manufacturer's updates normally don't need access to the microSD card. Maybe they've left it out to save space or whatever reason they had
(2016-09-05, 07:01)tom.1 Wrote: [ -> ] (2016-09-05, 06:44)Cleopatra Wrote: [ -> ]I check the blocks in normal operation mode.
All Windows OS are a real tragedy for Android LOL
Your results are no surprise then - in normal mode the microSD card works.
My laptop is new since 2 months and I've left some space for linux, but hadn't the time to install it. Maybe this time is now ...
Regarding the microSD problem I found that the kernels of the stock recovery and daohoa24's recovery are identical. I did this check with Windows' 'fc /b file1 file2' command. Hope this is as accurate as a diff. That fact leads me to think that the microSD functionality might have been left out intentionally. I have no deeper insight in the structure of Android and it's operation modes and assume that recovery and normal mode have dedicated kernels. The manufacturer's updates normally don't need access to the microSD card. Maybe they've left it out to save space or whatever reason they had
If your laptop has AMD/ATI,
I suggest you Ubuntu Trusty Tahr LTS.
It is because Trusty Tahr support the AMD/ATI,
instead the latest Ubuntu versions do not support proprietary drivers,
and they use open source drivers.
I recommend you to do not update Trusty Tahr (sometimes it ask you it).
Hello again! I have tested the phone running the Halo 7 port from @Cleopatra a bit more, apps running smooth, tried another launcher (Zen UI) but it reverts to Uni Launcher. I have just made the 5$ donation since I believe people dedicating their time for this should be rewarded.
The biggest issue I have now after inserting a SIM is that the IMEI is invalid and the Chamelephon app won't open. Tried uninstalling it and installing the one from the store, nothing happens. I have the sticker on the back of the phone and on the box with the IMEI, how can I reset it in the phone? I see in some tutorials 2 IMEI are needed, there is only one on the sticker though and a CMIT ID.
Could someone please explain how to reset this so I can test cellular use. I can see the networks here in Norway are recognized (2G, 3G, 4G9 but the phone cannot connect due to Invalid IMEI error.
EDIT: I have managed to set the IMEI using MTK Engineering Mode app (RTFM to me). What about IMEI 2, is this in case one wants to use the 2 SIMS? I see that now the phone connects successfully to 4G network, will test a bit more.
As I mentioned, I tested another launcher, ZEN UI which looks very nice, but a weird issue when running it, a lot of Chinese name apps are shown (see
[Only registered and activated users can see links Click here to register] ) Are these system apps or what? They are not shown by UI Launcher in any case. has someone tested another launcher which runs more stable? Thanks!
@smithie :
Question :
1) Do you have flashed the "2.16_utility.zip" ?
2) Do you have micro SIM or nano SIM ?
Into "2.16_utility.zip" there is also "Chamelephon".
It works very well on my Pepsi.
Try to tap on SuperSU and check if "Chamelephon" is in the list.
Try to restart the phone (sometimes needs some time to think).
In conclusion, if you want my opinion ... use UNI launcher.
Regards
(2016-09-05, 15:39)smithie Wrote: [Only registered and activated users can see links Click here to register] ) Are these system apps or what? They are not shown by UI Launcher in any case. has someone tested another launcher which runs more stable? Thanks!
these chinese apps are Skins vor themes for uni launcher. i simply disabled them and habe no issues
(2016-09-05, 15:39)smithie Wrote: [Only registered and activated users can see links Click here to register] ) Are these system apps or what? They are not shown by UI Launcher in any case. has someone tested another launcher which runs more stable? Thanks!
these chinese apps are Skins vor themes for uni launcher. i simply disabled them and habe no issues
Hello, how can I add IMEI back to Pepsi phone after root and custom rom?
Sent from my H7 using Tapatalk
![[Image: 2afgydc.jpg]](http://i63.tinypic.com/2afgydc.jpg)
![[Image: 90oeis.jpg]](http://i64.tinypic.com/90oeis.jpg)