Database Users

Some advice on "upgrading" my ALE-L02

Hi guys,
I'm a little noob with geek stuff but still I like to do it by myself.
Story: I went abroad for a six months trip and I bought a P8 lite in Japan (Soft bank carrier). The model is a ALE-L02-C111B210 (single sim) and from my search on the forum, I understand that it is the same as L21 except LTE frequencies may not work. I have different ideas but I'd like to check before doing anything stupid (which I am )
The phone has a lot of japanese crappy apps that I cannot uninstall and no updates are provided by this carrier. That why I want to root it and debrand it.
1- When I put my european simcard, it ask me for a network unlock code. I cannot get it from the carrier because my account was closed and they don't want to hear anything. I then found website who can give me a "generic" unlock code for this device against 10€. Before paying for a code, I'd like to know if rooting the phone and puting a custom/unbrand rom, it will also unlock the network or not. I compare to my old iphone who can be unlocked once rooted
2- I read a LOT of threds about L21 and several people with the L02 used the video for RootJunky who give all required files included a firmware file but an old one I think (V100R001C636B120).
Can replace it with one I got from huawei website but following the same procedure ? for instance : HUAWEI P8 Lite Firmware(ALE-L21, Andriod 6.0, EMUI 4.0, C432B565, Austria, Single SIM, Channel-Others)
3- dumb question. what's the stock rom for ? because it is only 34Mb on the RootJunky repository
Thanks a lot for any help/answer

bobbob601 said:
Hi guys,
I'm a little noob with geek stuff but still I like to do it by myself.
Story: I went abroad for a six months trip and I bought a P8 lite in Japan (Soft bank carrier). The model is a ALE-L02-C111B210 (single sim) and from my search on the forum, I understand that it is the same as L21 except LTE frequencies may not work. I have different ideas but I'd like to check before doing anything stupid (which I am )
The phone has a lot of japanese crappy apps that I cannot uninstall and no updates are provided by this carrier. That why I want to root it and debrand it.
1- When I put my european simcard, it ask me for a network unlock code. I cannot get it from the carrier because my account was closed and they don't want to hear anything. I then found website who can give me a "generic" unlock code for this device against 10�¢?�¬. Before paying for a code, I'd like to know if rooting the phone and puting a custom/unbrand rom, it will also unlock the network or not. I compare to my old iphone who can be unlocked once rooted
2- I read a LOT of threds about L21 and several people with the L02 used the video for RootJunky who give all required files included a firmware file but an old one I think (V100R001C636B120).
Can replace it with one I got from huawei website but following the same procedure ? for instance : HUAWEI P8 Lite Firmware(ALE-L21, Andriod 6.0, EMUI 4.0, C432B565, Austria, Single SIM, Channel-Others)
3- dumb question. what's the stock rom for ? because it is only 34Mb on the RootJunky repository
Thanks a lot for any help/answer
Click to expand...
Click to collapse
1) Which website? Are you sure it is safe? Don't give credit card information on such sites without confirmation. Iphone rooted?Iphone can be unlock and jail break but remember root is different from jailbreaking.
2) You may flash other country firmware. It's no big deal. But you may need to unlock bootloader.
3) stock rom is the default rom that phone comes with. Its size is usually above 1GB. 34MB can't be stock rom.

bobbob601 said:
Hi guys,
I'm a little noob with geek stuff but still I like to do it by myself.
Story: I went abroad for a six months trip and I bought a P8 lite in Japan (Soft bank carrier). The model is a ALE-L02-C111B210 (single sim) and from my search on the forum, I understand that it is the same as L21 except LTE frequencies may not work. I have different ideas but I'd like to check before doing anything stupid (which I am )
The phone has a lot of japanese crappy apps that I cannot uninstall and no updates are provided by this carrier. That why I want to root it and debrand it.
1- When I put my european simcard, it ask me for a network unlock code. I cannot get it from the carrier because my account was closed and they don't want to hear anything. I then found website who can give me a "generic" unlock code for this device against 10€. Before paying for a code, I'd like to know if rooting the phone and puting a custom/unbrand rom, it will also unlock the network or not. I compare to my old iphone who can be unlocked once rooted
2- I read a LOT of threds about L21 and several people with the L02 used the video for RootJunky who give all required files included a firmware file but an old one I think (V100R001C636B120).
Can replace it with one I got from huawei website but following the same procedure ? for instance : HUAWEI P8 Lite Firmware(ALE-L21, Andriod 6.0, EMUI 4.0, C432B565, Austria, Single SIM, Channel-Others)
3- dumb question. what's the stock rom for ? because it is only 34Mb on the RootJunky repository
Thanks a lot for any help/answer
Click to expand...
Click to collapse
hi,first of all you need to unlock bootloader,watch this video tutorial https://www.youtube.com/watch?v=63L7FBuWFrc once your bootloader is unlock,you can try what i post here http://forum.xda-developers.com/p8lite/help/single-sim-to-dual-sim-b575-t3489180

Suleiman01 said:
1) Which website? Are you sure it is safe? Don't give credit card information on such sites without confirmation. Iphone rooted?Iphone can be unlock and jail break but remember root is different from jailbreaking. .
Click to expand...
Click to collapse
The website should be ok, it has a good rating of trustedshops. does not look fake, but still, I'd like to know if buying an unlock code will be necessary after rooting/changing the rom .[/QUOTE]
Suleiman01 said:
2) You may flash other country firmware. It's no big deal. But you may need to unlock bootloader.
Click to expand...
Click to collapse
yeah, I think I did this step with sucess thanks to a tuto from xda
Suleiman01 said:
3) stock rom is the default rom that phone comes with. Its size is usually above 1GB. 34MB can't be stock rom.
Click to expand...
Click to collapse
it is what I thought. file must be corrupted.
Thanks for all your answers Suleiman01

Today received 128G - 4g RAM - need a little help

I have bought the 128 gig storage - 4 gig RAM from china and it arrived today, need some help and have some questions here:
1. In "about phone - Model number" section it said ZTE A2017, No app drawer, No G or U after the model number, no google play store, I searched a little on the various models, it seems mine is Chinese, am I right?
2. Is it possible to unlock the bootloader/ root/ xposed for my device model ( Chinese)?
3. If the answer is yes, Can I flash G or U model to the device? or because of its possible band differences and 128 G storage instead of 64 G it will cause problems?
4. It has android version 6.01 , mifavor ZTE_A2017V1.0.0B07, it said I can update if to B13, size 711.75 mb, are the info and changelogs are in Chinese, I don't know is it Nougat or just a regular bug fixing update. anyone have the same device that could help me here? I read in previous mifavor roms it is possible to unlock the BL, Should I update now?
please check the attachments
Thank you in advance

This is a Chinese version of axon 7 (that's why you don't have G or U). As I know so far only this version have combination of 128GB/4GB.
There are development section for rooting unlocking - just jump there and read a loot of stuff.
Probably the whole process is nearly same as U and G model.
Also you might have Chinese recovery menu. I do not have Chinese version of axon 7 in my hand but I have few others Chinese exclusive phones and they have some type of Chinese language core.
And before update search that unlocking method work with B13.
Cheers

Pretty sure bands are set by hardware and are not changeable.

Read your post again and see you just want to flash other firmware. This is fine if you follow the twrp flashable firmware guide.

MrMD69 said:
This is a Chinese version of axon 7 (that's why you don't have G or U). As I know so far only this version have combination of 128GB/4GB.
There are development section for rooting unlocking - just jump there and read a loot of stuff.
Probably the whole process is nearly same as U and G model.
Also you might have Chinese recovery menu. I do not have Chinese version of axon 7 in my hand but I have few others Chinese exclusive phones and they have some type of Chinese language core.
And before update search that unlocking method work with B13.
Cheers
Click to expand...
Click to collapse
It seems bootloader of U models in previous firmware builds can be unlocked, seen it on youtube, I want to know if I do the same with my Chinese model it won't brick the device; hoped someone did this before, then I wanted to flash the G or U model on it, it would be so good if someone know if specific bands are limited in other models and they have all actual similar inside that could be useable in different models or some bands are really missed in different models and if not, maybe flash U firmware with Chinese model bands separately, confused here that I am only one trying to do that!
Chines recovery menu?! now I am :silly: now I am pissed why i did not think about it before
I think frimware numbers are different from U and Global models, last U model frimware is B29 and Chinese is B13, am I right? if that so I could not use the unlocking method on it
reasons that I order from China:
1. I don't live in US, I'm in middle east, even though I can get it with help of my brother who lives in US I have preferred not to bother him for purchasing and sending by post, tax...
2. when I decided to buy one, 128 G wasn't available in US
3. 64G is not enough for me especially with these VR programs and games sizes and yes I know I can expand with MicroSD but it's not adaptative and I always prefer more internal storage and it is UFS 2 and I want to use my 2sims on it.
4. this model cost me around 350 US$ (silver color), that's a good deal; this year BF the 64G model were 350$ , also 128+6 G is around 500 US$ and I think its not worth the 150 extra $.

lafester said:
Read your post again and see you just want to flash other firmware. This is fine if you follow the twrp flashable firmware guide.
Click to expand...
Click to collapse
You said bands are not changeable, but if I flash other models frimwares like U or G model if the bands weren't there it could cause problem.
another question is firmwares of the same models but with different storage ( 64/128G) or Ram (4/6G) are different?

G900V CID 11 Running CyanogenMod 14 - Unable to make phone calls/Use sms

Hi, in an attempt to unlock Wifi Tethering capability on my phone, I installed [G900F]CyanogenMod 14.0-20161020-UNOFFICIAL-klte, and now I'm unable to make phone calls or use SMS/MMS.
Is there anything I can try to get service back?
I've tried installing a new modem with no success, using Odin, FlashFire, Terminal Server. I'm not confident I was doing it correctly though, or even if I was using the correct modem files.
I was able to root the phone with Stock firmware, but Mobile Hotspot/Wifi Tether wasn't built-in, and I had no success with any of the apps... FoxFi, Wifi Tether Router, Barnacle Wifi.
Some more information on the phone:
It's the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V. I took it to the Verizon MVNO PagePlus and they were able to activate the phone, and everything was working perfect, until installing CM14.0.
A roadblock I found out, that might be the root of some of the problems, is the phone may not have the ability to unlock the bootloader, possibly limiting some modding methods. When looking at /sys/block/mmcblk0/device/cid, it starts with 11, designating a Toshiba eMMC chip.
I'll take any suggestions, or alternatives... I don't mind using the stock firmware or any other Roms. The main feature I'd like to have is the ability to use Wifi Tether and the basics, make calls, send sms.
Thank you.

I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?

leotakacs said:
I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?
Click to expand...
Click to collapse
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.

You will not be able to run any version of Cyanogen on your Toshiba S5 properly. Your best course would be to install FlashFire from the play store and use it to install a TouchWiz ROM such as Moar (5.0) or Phoenix (6.0).

TechFellow1 said:
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.
Click to expand...
Click to collapse
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip

Hariiiii said:
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip
Click to expand...
Click to collapse
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?

leotakacs said:
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?
Click to expand...
Click to collapse
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.

Hariiiii said:
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.
Click to expand...
Click to collapse
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol

KaptinBoxxi said:
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol
Click to expand...
Click to collapse
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Delgoth said:
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?
Click to expand...
Click to collapse
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.

Hariiiii said:
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.
Click to expand...
Click to collapse
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).

Hariiiii said:
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).
Click to expand...
Click to collapse
alright, that makes sense. Thanks for explaining. Always interested in these things since i don't QUITE understand exploits at that level. I do mainly apk modifications and software dev

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD

Legitsu said:
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD
Click to expand...
Click to collapse
I understand plenty enough to know the difference in the flash chips cid's with such like that... The fact of the matter i was trying to get at is that most Straight Talk phones are unlocked entirely without a care in the world, regardless of their CID/branding. Without the proper commands and 3rd party support, I get that there won't be a way. That's why I check my CID's first before buying S5's or Note 4's

Some questions about Rooting, unlocking boot loader, and installing custom ROM

I have an SM-G900I. I rotted this device a few weeks ago by using CF Auto Root. I want to install a custom ROM. I can't understand exactly what you need to do though. I read in some places that you need to unlock your bootloader for TWRP, but another website said I do not. So what's the difference between root, and unlocked bootloader? What exactly is TWRP and how does it let you install a custom ROM? I was thinking of installing Ressurection Remix Pie. Will this work with my phone?

skillz21 said:
I have an SM-G900I. I rotted this device a few weeks ago by using CF Auto Root..........
Click to expand...
Click to collapse
I don't have this variant but, the following thread is what I had used to Unlock the Bootloader on both of my Galaxy S5 devices.
https://forum.xda-developers.com/showthread.php?t=3561529
Regarding your other questions...
There's 2 different types of Unlocking that can easily be confused.
1) Carrier Unlocking (aka SIM Unlocking) = This unlocks the devices restrictions to a single carrier.
2) Bootloader Unlocking = Unlocks the restriction within the devices Bootloader that prevents it from rejecting Custom Recovery and Custom Firmware from being installed on the device.
TWRP is a Custom Recovery that is a simple software that loads before the Firmware. For example, the TWRP Software is kinda like the BIOS Software on a PC/Laptop whereas the BIOS loads before the Software on the Hard Drive.
Rooting a device only allows the ability to Read/Write/Modify certain areas within the currently installed firmware that are otherwise Read only.
There's much more to it that would take small book to explain it but, this is a very condensed explanation.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

Can you flash Verizon Note 4 (SM-N910V) with any other snapdragon variant firmware?

So I have been following XDA for the past 5 years and this is my very first post. Have some experience with flashing custom roms on different phones and most recently a T-mobile S7-edge (SM-G935T). I flashed a (SM-G935U) firmware on it for the sake of debloating and fully unlocking the device. It worked like a charm, now am tinkering around with a Verizon Note 4 and am unable to find the answers I seek. The problems with this stock firmware is that it is heavily bloated with carrier apps , gets slow at times , unable to use data, hotspot and other such functionalities making me search the internet to flash it with a stock rom which solves all these problems. My question is that what things should i keep in my mind to find a compatible rom and secondly , are these roms for Note-4 (snapdragon variants) interchangeable as done with S7-edge mentioned above. And if it is then what rom will be best to flash for use in Asia. Necessary Information will be provided upon demand. Replies and comments will be appreciated. :fingers-crossed: . P.S I dont wanna flash any unofficial builds.

Yes you can. I have a Verizon Note 4 and I used this method in order to first unlock the bootloader, then flash Magisk for systemless root.
Unlock bootloader and root VZ galaxy note 4: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593.
Install Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

changing SM-N910v firmware with SM-N910c
SO i just Went thru the internet and found out that Asian Versions of Note 4 had SM-N910c firmware variant flashed to them, should I flash it? any suggestions?

As an experienced flasher of over 20 Note 4 devices (plus a few more), be careful flashing firmware for other Note 4 devices on a Verizon Note 4 unit. They usually will not work. Several varieties of the device are Snapdragon processors. However the C model is an Exynos processor. This would be like installing IOS software on an Android device. They are not interchangeable. You'd be best to stick with something designed for your N device.
Even then ... using a different ROM (maybe for T or F) can lead to only partial usability of that device. Your data may not work, your cell service may not work, your wifi may not work, etc... Or it won't even boot at all.
Thankfully, Samsung has provided us with ODIN, which is a software program to reflash a device that's been hosed by a malformed ROM. If you want your phone to work, remember the following:
1. Only flash COMPATIBLE software for the processor.
2. Only flash the same variant of ROM to that device (VZW in this case). This is to prevent data carrier problems. An F ROM may boot, but not be fully functional.
3. If you want to try a new unofficial ROM, get one for that device and processor. Be aware that compatibility is not always guaranteed, but Lineage OS 9 ROMS are better than Android 8 as for compatibility. I've tried them all.
4. A stock ROM will have bloatware. If you are rooted, you can remove most of that (if you know how).
5. Last but not least... if you want to stick close to stock, use ModestROM. You'll get 6.01 and some bloatware, but it will be closest to stock as possible with root. Other ROMS might work, but for full functionality, stick with a ROM designed for your device. Otherwise you will experience problems, or worse. You could have a new paperweight!