[TUTORIAL][GUIDE][HOW TO] Root Alcatel One Touch Pop S3 5050 | Every Android version - Android General

Hi everyone,​I have been in possession of an Alcatel One Touch Pop S3 5050 for quite a long time and was not able to root it until recently.
I will share my method in this topic but first of all, I have to thanks Decker.Kaluga for developing a custom CWM recovery image that kind of work on this device. You can find a good tutorial on how to install CWM on OT-6036Y or OT-6050Y on his website.
My second thanks goes to morgs640 for the idea of adapting Decker's work on Alcatel Pop S3.​
This method may work with other Alcatel devices, see last question in the FAQ section for more informations.
This method should not arm your device but as any root operation, there is always a risk. I am not responsible if anything goes wrong.
Click to expand...
Click to collapse
Step One
- Download Decker's custom CWM recovery here: cwm_alcatel_6050y.7z
- Unzip it
- Install adb drivers
Step Two
- Download latest zip version of Supersu from Chainfire, currently the 2.46
- Rename the archive as update.zip
- Put this file in the CWM recovery folder
Step Three
- Connect the device in USB, activate debug option and make sure adb is working by going to the folder where you have unziped the custom recovery
Code:
adb devices
- Navigate inside the device memory to identify the location of the internal and external memory:
Code:
adb shell ls /storage/
For internal memory, it should be:
Code:
/storage/sdcard0
And for external memory (sdcard):
Code:
/storage/sdcard1
- Push the Supersu zip file to external memory
Code:
adb push update.zip /storage/sdcard1/
- Take note of the position of the update.zip file inside the external memory
Code:
adb shell ls /storage/sdcard1/
In my case, this command returns:
Code:
- Android
- DCIM
- Documents
- Download
- LOST.DIR
- Pictures
- Ringtones
- data
- media
- update.zip
My update.zip file is in 10th position.​
Step Four
- Reboot the device in fasboot by pressing Volume Down and Power until logo Alcatel pop S3 appears
- Verify the device is connected:
Code:
fastboot -i 0x1bbb devices
Boot the device with the custom recovery:
Code:
fastboot -i 0x1bbb boot cwm_recovery_6050y.img
NOTE: This does not install the custom recovery on the phone so pressing Power during 5 seconds will reboot the phone normally.
The screen will turn white, wait until it stabilizes.
The screen will remain white as the recovery is not specially developed for this device but it should work anyway.​
Step Five
This is the tricky part, the menu does not display but the recovery is running anyway.
The menu you are not seeing is the following:
Code:
> reboot system now
> install zip
> wipe data/factory reset
> wipe cache partition
> backup and restore
> mounts and storage
> advanced
By default the cursor is on the first option.
- Press Volume Down once then Power to enter the install zip option.
This menu will be opened:
Code:
> choose zip from /sdcard
> choose zip from /storage/sdcard1
> choose zip from last install folder
> install zip from sideload
> toggle signature verification
+++++Go Back+++++
- Press Volume Down once then Power to enter the choose zip from /storage/sdcard1 option.
This will open the external memory folder:
In my case:
Code:
Android
DCIM
Documents
Download
LOST.DIR
Pictures
Ringtones
data
media
update.zip
- As you know exactly the position of the update.zip file from Step Three, press Volume Down accordingly.
In my case, 9 times to go from Android folder to update.zip​- Then press Power
It will prompt for a confirmation:
Code:
> No
> Yes - install update.zip
- Press Volume Down once then Power to install.
- Finally, Press Power one more time to confirm installation, then reboot manually the device by pressing Power during 5 seconds.
If the process has been successful, when rebooting it will display a text saying that the list of application is being updated.
--------------------------------------------------------------------------------------------​
Edit:
As neileverett suggested, the external memory sdcard could be recognized as sdcard0 instead of sdcard1.
To determine how the sdcard is named by the system, I recommend to use a browser as ES File Explorer or Astro Manager to write down all the content of the external memory and compare this list to the result of the ls command from Step Three.
--------------------------------------------------------------------------------------------​
FAQ
Q: My device never connect in adb.
A: First verify that adb drivers are installed.
In my case when I connect the phone, it first emulates a CD player device with a folder containing the generic drivers.
I have to safely remove this emulated CD first (right click on the System Tray icon -> remove device) before the phone accepts to connect itself with MTP or ADB.
Q: I do not have a sdcard.
A: You can try to do the process with internal memory.
First, you will need to navigate the memory with adb shell to find Internal memory
Code:
adb shell
Code:
shell#ls /storage/
shell#ls /mnt/
...
Some examples of the possible location of the internal memory
Code:
/storage/emulated/
/storage/sdcard0
/mnt/shell/emulated/0/
etc.
Sometimes, you get a menu like this prior the actual content of the sdcard0 (internal memory)
Code:
/0/
/legacy/
/obb/
After entering in /0/ or in /legacy/ you should get the actual content of the memory.​- Then push update.zip to internal memory
Code:
adb push update.zip $INTERNAL_MEMORY_LOCATION
- In Step FIVE, while in the second menu, choose choose zip from /sdcard by directly pressing Power
From a system point of view, it can open /storage/emulated/ or /mnt/shell/emulated/ that means the folder opened will not be the Internal Memory but a parent folder.
I recommend that you try every possibility by:
- First considering that pressing choose zip from /sdcard led you to the actual Internal Memory content and you shall proceed as normally by looking for update.zip in the current folder.
If it did not work:
- Consider that a parent folder is displayed and the actual memory is in the first sub folder
- Press Power to enter the first sub folder (which may be the Internal Memory) and try to install update.zip​- Consider that a parent folder is displayed and the actual memory is in the second sub folder
- Press Volume Down then Power to enter the second sub folder (which may be the Internal Memory)​- ...
After each try, reboot and look for the pop-up saying that the list of application is being updated.
You can go on with up to 2 levels of sub folders.​
Q: I tried everything, it still do not work.
A: If you have a lot of folders and files in the Memory, the list of content on the CWM recovery will be displayed on several pages.
Make a backup of the Memory, then empty it and add only the update.zip file.
Restart then from Step One.
It should be easier to find the update.zip file.
Q: I own a different Alcatel model, could this trick work with my device?
A: First you can try the other CWM Recovery image Deckter has developed: cwm_alcatel_6036y_v2.7z
To verify that the recovery is correctly booting on the device, when the white screen stabilizes, try to press Power twice.
If the recovery is working, it will enter in the first menu (reboot system now) then confirm the reboot.
In case, after this manipulation, the phone does not reboot, it means the recovery is not working for your device.
(Credits @Decker.Kaluga)
(Credits @morgs640)
(Credits @ModernWorld)

I have just successfully used this method to root my Pop S3 - thanks for the method!
One thing to note:
I found that the method didn't work initially, then with some digging realised that my sdcard was mounted as sdcard0 rather than sdcard 1. It turns out this is because I had changed the default install location under settings - storage to 'external sd card' rather than the default of 'phone storage'.
I temporarily changed this setting back to 'phone storage', and then your process worked first time! Might be worth adding this info to the post?
Thanks once again!

OMG !
So it works with the last update available ?
Possible to have a viewable recovery in the future ?

Draky50110 said:
OMG !
So it works with the last update available ?
Click to expand...
Click to collapse
This should work with any update
Draky50110 said:
Possible to have a viewable recovery in the future ?
Click to expand...
Click to collapse
Decker is willing to develop a CWM for Alcatel Pop S3 but does not possess the device. You can support it on his website. You'll find a link in the description of the Tuto.

Thanks
first thank you for the help. but my visit is to ask permission to make a video tutorial and so Decker.Kaluga to advertise can buy the pops3 and thus make the cwm for it.

negurras said:
first thank you for the help. but my visit is to ask permission to make a video tutorial and so Decker.Kaluga to advertise can buy the pops3 and thus make the cwm for it.
Click to expand...
Click to collapse
Of course, feel free to post the link.

I need help.
When I enter into the custom recovery, it displays a menu. First choose a language. Then a selection. It says:
Reboot system now
Apply update from ADB
Apply update from sdcard
wipe data/factory reset
wipe cache partition
Chose apply update from sd card, it only shows ../
I have a Alcatel pop s3. Please I really need help.

Did you put the update.zip into your SD card ?

DanIgnes said:
When I enter into the custom recovery, it displays a menu. First choose a language. Then a selection. It says:
Reboot system now
Apply update from ADB
Apply update from sdcard
wipe data/factory reset
wipe cache partition
Chose apply update from sd card, it only shows ../
I have a Alcatel pop s3. Please I really need help.
Click to expand...
Click to collapse
It's because you entered in the Alcatel Recovery mode not in Fastboot mode.
From Alcatel Recovery you can only install application signed by Alcatel.
Fastboot mode displays the Alcatel Pop s3 white logo on a black background (this is the first logo that appears when booting normally). Fastboot doesn't display anything else.
To enter Alactel Recovery it's: Power + Volume Up
To enter Fastboot it's: Power + Volume Down
You can also enter in Fastboot by entering the following while still in adb at the end of Step Three:
Code:
adb reboot fastboot
Once in Fastboot, go on with Step Four and so on.

Thanks for this
Any methods in sim unlocking? costum ROMs?

working recovery for 5050x
Hi! I ported recovery for 5050x. screen is work, you can install zip and backup you partitions.
1. extract
2. cmd to folder recovery
3. shutdown phone
4. press Power + vol- on phone it vibrate and connect phone to PC
5. type to run recovery
fastboot -i 0x1bbb boot recovery.img
or to flash recovery
fastboot -i 0x1bbb flash recovery recovery.img

i can't go in fastboot mode
I can not seem to come into fastboot mode POWER + Vol- and with code

Can somebody please make a video tutorial of this? I would love to root my One Touch Pop Icon.

Thank you good job

TWRP 2.6.3.0
amraouifathi said:
Thank you good job
Click to expand...
Click to collapse
You welcome
I ported TWRP 2.6.3.0, but I have not checked thoroughly.
Before backup you mast mount /system /custpack in Mount menu or you cant see backups in Restore menu.

All work good just the fast start don't work please upload the stock recovery

Stock recovery
amraouifathi said:
All work good just the fast start don't work please upload the stock recovery
Click to expand...
Click to collapse
Stock_recovery

Oh thank you i try now lol you are very fast

update TWRP 2.6.3.0
TWRP 2.6.3.0
+system and custpack backup and wipe like one partition
+you can backup persist и firmware

The stock work now i test the twrp

Related

Internal and external sd unmounted, can´t access to recovery and fastboot

Hi there,
I bought ZTE U819 and I was trying to replace the Chinese recovery, but I chose a not compatible recovery version by mistake, so:
- I Can´t access to my device recovery (Up Volume + power).When I try to enter, the device always restart
- I Can´t access to fastboot mode
- The internal sd and sd card are unmounted
- I only can access to system folder by root explorer
- It´s rooted
The only way to install apk is with iAPK
* I tried to edit vold.fstab but not worked.
* I tried to install the right recovery from adb but I could,´t do it (It was probably because I made something wrong)
* I tried to copy the correct recovery to system through airdroid, but I can´t sent files to system folder (because It will need a hard root?)
I think if I copied the right recovery to system folder, I could install it with goo manager or similar...
Is there any way to install through adb or terminal emulator?
Thank you ever so much!!
I know this method works with some Android ROMs.
When you do a restart of the phone, at one stage, you will see screenfuls of text messages scrolling past. At this point quickly press the Power button - this might bring you to the recovery screen.
If Power button does not work, you can try the single Vol Up, Vol Down or Home button, one at a time, at the scrolling text messages screen.
You may have to restart a few times to catch that moment of the scrolling text messages and try with each of the buttons.
Hope this works.

[Guide] Dual Boot Any MMC Block Based Device with separate recoveries [NOOBS Welcom]

Ok guys this is my first tutorial, so bare with me. This all started when I wanted to dual boot my Note 10.1(N8013), & came across this thread. If I hadn't found that thread, I would never have come up with this, so thanks are owed to the author. Now then, enough with my ramblings, lets get to the point.
What will this guide get you?
With this guide, you'll get two completely separate ROMs, each with their own recovery menu, so you will be able to use the recovery menu on each ROM individually. You'll also get scripts for switching between roms, & recoveries.
What is required?
*Android Device with MMC Partitons(Ex: mmxblk0p1)
*Computer with Windows
*USB Sync Cable
*8 GB or larger MicroSD Card
Prepping SD Card:
Backup your sd card if you want to keep your data. Install AParted onto you device from the Play Store. Open Aparted, granting root access when prompted. Decline the "Agreement" because it will just try to install junk. Tap "configuration", then tap the drop box under "Detected devices". You should see "mmcblk0", "mmcblk1", and possibly "usbdisk". If you don't have both "mmcblk0", & "mmcblk1", then stop here, because this guide isn't for you. If you do, then select "mmcblk1" from the list, tap "Save", then "OK". Tap "TOOLS", you should now see parts 1 through 4, "Part: 1" should say fat32 or similar, and say the size in MB of your external SD card. If it does, then tap the checkbox next to "Part: 1", next tap the drop box that says "Create", select "Delete" and tap apply. Once done, all parts should say empty, now for the semi-hard part. We're going to create 4 partitions. The first partition is going to be the standard external sd partition, that will show up in both roms, lets make it. Tap "CREATE" on the top, tap "+", tap the box with "0MB" in it, set it to the size you want the card to be, keeping in mind, that we need at LEAST 4972MB of space for the second ROMs' partitions. Also the more space you leave, the more space you can put into the second ROMs' "Internal" memory. Tap "+" once more, tap the "0MB" box again, this time putting in "1537", tap "+", this time put 839. On the next one put the rest of the remaining space into the box, this one is the data partition, aka the internal memory of the second rom. Tap the menu button, and tap "Apply changes", when done we are finished with the partition setup.
Getting Necessary Files:
You'll need to dump your boot.img, so you can switch between the ROMS(Google is your friend.). Download the ROM you want to use as the second(Has to be CWM flashable). Be sure this ROM has a boot.img included, if it doesn't, then take the boot.img you dumped, and put it into the root of the ROM. Next we need to get the proper GAPPS for the ROM we're installing (If it's a ROM that requires GAPPS.). Next we want to get a recovery, cwm, stock, etc. We need to get the recovery.img of the recovery we want to use, for cwm, you can just open the tar.md5 in WinRAR, and extract this file. Finally you need to download the attached Application I've created especially to convert ROMs to run from the SD Card, it also modifies recovery.img to apply any changes to the SD card ROM, instead of the Internal ROM. I haven't scanned it for viruses, but I don't think it should be a problem, of course you're free to check it if you like, in fact I encourage that you do.
Getting Important Info About Device:
We need to find out what block corresponds to what partition of the devices' internal ROM to input into the application, so it can replace them in the ROM. If your device is a Note 10.1(N8013) then you can skip this section, because the configuration file for that device is already in the attached archive. You need the block numbers for, System, Data, Cache, Boot, & Recovery(Ex: mmcblk0p1). If you can't find them on Google, then you can find it using adb. With the device connected, and with usb debbuging enabled. In cmd type "adb shell cat /proc/emmc", you should see a list of blocks(Ex: mmcblk0p1), with corresponding labels(Ex; /system). Take note of the blocks with the labels,System, Data, Cache, Boot, & Recovery, or similar. If typing "adb shell cat /proc/emmc" doesn't give you labels or doesn't show any information at all, then you'll need to find the labels for the blocks on google.
Using ROM 2 SD:
Extract "ROM-2SD.rar", copy the ROM you with to install into the "Original ROMs" folder, copy GAPPS into "GAPPS" folder(If ROM requires GAPPS) , & copy the "recovery.img" file into the "Recovery" folder. Run "ROM 2 SD.exe", check "Create modified recovery", don't check "Flash boot.img on install", check "Merge GAPPS" (If the ROM requires GAPPS, this will make sure GAPPS are installed when the rom is.). Click "Browse...", select rom from the menu. If you have the N8013 click the "Device:" drop down menu, and select "Note 10.1 (N8013)". If not type "mmcblk1" into "SD Mount:', and put the appropriate block into the corresponding text box. Click convert rom, click "Ok". Select GAPPS, and recovery when prompted to. when you get the prompt that its done, close the application.
Installing the ROM:
First, copy the unmodified/dumped boot.img to the EXTERNAL sd card. as bootStock.img. Next, copy the boot.img from the "Converted ROMs\[ROM_NAME]" folder to the EXTERNAL sdcard as bootSD.img. Now, copy the recovery.img from the "Converted ROMs\[ROM_NAME]" folder to the EXTERNAL sdcard as recoverySD.img. Finally, copy the unmodified recovery.img to the EXTERNAL sd card. BACKUP YOUR ROM BEORE GOING ANY FURTHER! Copy the converted ROM from "Converted ROMs\[ROM_NAME]\[ROM_NAME].zip" to the EXTERNAL sd card. Install the ROM as you usually would. After installing the ROM reboot, your device should boot into an unchanged Internal ROM, as if nothing has changed. Now we will create a script to boot into the newly installed ROM. Open notepad and copy the following(Replacing path to external sd, boot block, & recovery block.)
Code:
#!/system/bin/sh
#Flash boot
dd if=/path/to/extsd/bootSD.img of=/dev/block/[BOOT_BLOCK_HERE]
#Flash recovery
dd if=/path/to/extsd/recoverySD.img of=/dev/block/[RECOVERY_BLOCK_HERE]
reboot
Save the file as "Boot_SD.sh", and copy it to the EXTERNAL sd. Don't Run it yet, because it'll flash the recovery, we want to make sure the second ROM will boot first so you can use the recovery menu to fix it if not. Connect the device to the computer, open cmd, & type "adb shell", "su", "dd if=/path/to/extsd/bootSD.img of=/dev/block/[BOOT_BLOCK_HERE]", if that finishes successfully, then type "adb reboot". the device should reboot into the second ROM, if it does then the install was successful, and we can now proceed to create the Boot Stock script, path to external sd will be different on a custom ROM from the stock ROM:
Code:
#!/system/bin/sh
#Flash boot
dd if=/path/to/extsd/bootStock.img of=/dev/block/[BOOT_BLOCK_HERE]
#Flash recovery
dd if=/path/to/extsd/recoveryStock.img of=/dev/block/[RECOVERY_BLOCK_HERE]
reboot
Save as Boot_Stock.sh, copy to EXTERNAL sd. Then run the script as root using Root Browser, or whatever you usually run scripts with. The device should then reboot, if it doesn't then you probably need to search Google on how to root of adb. Once it reboots, I should boot back into the first ROM. You can now run the script we created first at any time to get back to the second ROM. We're almost done run the script to boot sd, then boot into recovery, the way you normally do. This recovery should only affect the Second ROM, to test this clear the davlik cache, & reboot into the ROM if it has to prepare a number of apps, then you know it works, and its safe to use the recovery, whenever you run a script the corresponding recovery will be flashed, so you can use the recovery on the second ROM, as you would on the stock ROM.
Notes:
Whenever you want to install an updated version of your ROM, you must run the ROM through ROM 2 SD, just like we did earlier. After you know this is compatible with your device, you can check "Flash boot.img on install" which will automatically flash the boot.img when you install the ROM. Don't forget to copy the converted boot.img to the external sd as bootSD.img, any time you install a new ROM/Update. GAPPS can be installed from recovery without modification, just make sure you do it when the recovery is on the second rom. Let me know of any bugs in my application, or with this tutorial, I will make the necessary changes ASAP.
​

[Q] Im stuck in recovery

So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
gamehero said:
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
Click to expand...
Click to collapse
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
GuiltyGod said:
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
Click to expand...
Click to collapse
So I got to step 4 and I see the mount system but I don't see umount sdcard
Then mount system or skip this part
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
GuiltyGod said:
Then mount system :S
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
Click to expand...
Click to collapse
adb push ROM.zip /sdcard/ROM.zip if I dont have the sdcard umonted will this still work?
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
GuiltyGod said:
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
Click to expand...
Click to collapse
so I wrote the command and it sad "5143kb/s «241840314 bytes in 45.912s»"
then i went install the zip and I can't find it
ok i went and mounted the data , pushed the file and installed it, thank you so much
But now i need to install the stock backup that I did with TWRP
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
GuiltyGod said:
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
Click to expand...
Click to collapse
it's all good now but now i have CWM and i need TWRP to install my stock backup
Watch this video (shows you how to change recovery in general):
http://m.youtube.com/watch?v=jnESTcH2ioA
And read this instructions if you still have some doubts and want to go for sure (recovery for LG2 D802):
http://forum.xda-developers.com/showthread.php?t=2472223
Sry I am a bit lazy right now xD Came back from work

[xt1920-15] [pettyl] stock firmware rooted latest ota updates fixed + 'badkey' fix

Just for the record, Motorola phones and normally quick and easy to ROOT however this is been a right pain in the ass. No guide on here has worked properly for the UK version anyway so soon after I found a working way i thought i would do this to help anyone else....
Requirements:
unlocked bootloader
THIS ZIP FILE
extract the files and open a cmd prompt in the ADB folder or run a cmd and us 'cd C:\adb\' [or location of the unzipped adb folder]
run 'fastboot boot recovery.img'
backup the cache partition so it creates the TWRP>BACKUPS>SERIAL>ROM folder
copy the rooted rom folder to TWRP>BACKUPS>SERIAL>*here* [ please note serial stands for the serial number of device and this will vary with each person]
hit restore, system + data + boot,
when finished reboot to recovery
you are now in the stock recovery so hold the power button and tap volume down to unlock the menu then you want to wipe data factory and just use data AND NOT the personalised content as well..
then reboot
do the initial set up.
then perform 2/3 system updates [security patches i believe? from the system settings > updates]
when all this is complete, afterwards click on magisk manager and let it update. It will then give you a warning error saying the version of magisk too old.
so power off your phone and then put it back into bootloader. [hold power + vol down from a powered off state]
use fastboot boot twrp_james.img [from cmd promt inside adb folder]
when the recovery loads in the same cmd prompt type adb push Magisk-v18.1.zip /sdcard/ [or u can just copy the zip file onto the storage if it shows up on ur pc]
install magisk 18.1 and then reboot to boot loader and use fastboot flash logo logo1.bin to remove bad key error
have been in a mad rush to get this done before i go work hopefully you can understand if there are any problems just msg me
TheLastAlphaUK said:
Requirements:
unlocked bootloader
THIS ZIP FILE
Click to expand...
Click to collapse
BACKUP MIRROR OF FILE [MEGA]
Hi there, im unable to backup the cache partition (showing as 0mb in cwm) think it may have something to do with encryption.
I have my phone in a somewhat usable state by restoring cwm backup i found on xda, but when booting custom recovery it will not mount /cache ,/data etc
Would love to follow your instructions, do you have any ideas
links are dead
I have unlocked the bootloader and flashed TWRP on this phone to root.
i have not found a live link for any LineageOS or other custom rom, but root still works on stock rom.
i have saved all the necessary files on my PC so if you need help just reply or message me

[Error][fix][Solution][Guide]Errors in flashing custom rom in Lenovo A2016a40 and ways to tackle/fix them

CASE: After flashing lineageOs 14.1 on my Lenovo A2016a40 (chipset: MT6735M) using TWRP, I lost my IMEI and Baseband version which made my phone just like a screen with no calls, no connection, no internet. so, basically I had no option than to flashing the stock ROM (eventually I need that custom ROM as that is an upgraded one). I flashed only secro.img on the custom rom using SP Flash Tool that caused a bootloop ( I again had to took help of the stock rom ).
Now, the question is:
1. Can I flash secro.img on that custom Rom, if yes, how?
2. If not, how can I get back my baseband version?
today I flashed ressurection remix 5.8.4 on the mentioned device and that caused the exact same problem as mentioned.
Well, today I succeed after 2 weeks of sleepless nights in search of a solution that elaborates how to flash a custom rom successfully on the mentioned device(i.e. Lenovo A2016a40 (also known as Lenovo vibe B)). Now, as I felt the frustration of seeing the phone without network and everything else, I want to mention the whole process I've gone through.
Here is the step-wise guide on how to flash a custom ROM on Lenovo A2016a40 (Hope it works with other devices too)
NOTE: Here in this tutorial I'm not asking you to try a custom rom, it's upon u to use custom rom or not. this tutorial is to guide those who has already stepped into the process and get into an error or so(hope not so). any damage to your device is solely your responsibility, try in your own risk if you want.
GOOD LUCK
BEFORE FLASHING:
1. Take your normally functioning device.
2. Root that device.
For Lenovo A2016a40 I've followed this neat and clean page and found it helpfull.
Here is the summary of that really clean page (the page is a bit outdated follow my paths for updated method (as in December 2020) ).
a) Download and install Magisk Manager app on your andrid device.
b) Launch the app and tap on "install" that is on the same slide as the logo, and then choose to patch boot image by tapping on "Patch Boot Image File" after which the patching process will start which will create a image file called "magisk_patched.img".
c) Transfer that magisk patched image file on your PC.
d) Connect your device to your pc where you have stored magisk patched image.
e) Now enable "USB Debugging" and "Enable OEM unlock" from Settings>Developer's option (or, Settings>About Phone>7x tap on Build Number>Settings Home> Developer's option)
e) (Assuming you have ADB and Fastboot installed, if not follow whatever google says.) Now, open cmd on the folder where you have kept that magisk pathced image by
Code:
Shift+Right Click
and selecting "Open Command window Here" and check for your device's connectivity by typing
Code:
adb devices
in cmd, and after confirmation(seeing device's serial number) type
Code:
adb reboot bootloader
to enter fastboot mode (Fastboot Mode written on screen), confirm connectivity by
Code:
fastboot devices
, being confirmed type
Code:
fastboot oem unlock
to unlock bootloader and then do press
Code:
Volume up
button to unlock bootloader.After seeing "Okay " on command window, type
Code:
fastboot flash boot magisk_patched.img
and finally
Code:
fastboot reboot
and then press and hold
Code:
power + volume 'up'
buttons of your phone for about 10 seconds and then navigate to 'Normal mode' by using
Code:
volume up
button and confirm by using
Code:
volume down
button and wait for device to start.
f) Check Root status using Root Checker like apps
2. Backup some important system files.
This step is essentially important. I got into this from this thread.
a) Install Root Manager or similar apps and grant them root permisions.
b) Head to /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
c) Copy the mentioned files into a safe place(generally in external sd card) or newly created folder.
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
d) Now, head to /data/nvram/md/NVRAM/NVD_IMEI and copy the file named
Code:
MP0B_001
to another safe place generally in external sd card.
NOTE: All the above mentioned files are important for your device's network functioning.
e) Now, backup or replace whatever you want to keep (personal things).
FLASHING:
1. Download your preferred custom rom(.zip file) strictly for your device and transfer them into the inserted sd card or phone internal memory.
2. Install a custom reecovery.
Download your preferred custom recovery. I've used TWRP custom recovery and going to describe processes for that only.
a) Connect your device to pc and confirm connect by above mentioned method from the downloaded folder and then unlock bootloader the same way as mentioned above.
b) After unlocking bootloader run the commands as mentioned below (press "Enter" after each line)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
c) Now, enter the menu containing "Normal mode" option by the same mentioned method and this time select "Recovery mode" and you will get into TWRP custom recovery.
NOTE: Critical error can occur if you do pull out the battery and power off the device by any other means.
NOTE. After entering TWRP you can face an error saying
Code:
/data not mounting
or something like that, in that case head toward wipe section, select "Advanced wipe", select 'Data' and select 'Repair File system', then change partition style to "ext2" and then back into "ext4" and this solves the problem.
3. Backup your system and whatever you like. (generally "secro" "nvram" & "nvdata")
4. Free space for new custom rom by entering Wipe section and selecting the following
Code:
Dalvik/ART
system
Data
Cache
Internal Stoage (if you want to or optional)
5. Install your custom rom (with Gapps and Root if you want).
Enter "Install" section select and install .zip files for custom rom, gapps and root one by one or at once, whatever you want.
AFTER FLASHING:
Welcome to your literally new phone.
while you are expecting to celebrate it, you will find some of the most frustrating errors like Unknown Basband, Null IMEI.
Now to solve those errors follow the below mentioned points one by one
1. install root manager like app and grant root permission.
2. copy and paste the 7 files that you have copied earlier (expdb, proinfo, protect1, protect2, nvdata, nvram, secro ) to the path as " /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name", if prompted select "Overwrite", then select the files and provide them all 9 permissions you will get in permission section for those files.
3. Reboot Device.
4. now, delete the folder named "nvram" in path "/data/nvram" to get your baseband version back, as mentioned in this thread, and it worked for me, you may have to try deleting it 3-4 times continuously.
5. Reboot device.
6.Now, copy and paste the copied 'MP0B_001' file to the path as "/data/nvram/md/NVRAM/NVD_IMEI" and similarly assign all the 9 permissions asked in permission window.
7. Set APN if needed. follow this tutorial and you may not be able to save changes (hope not), if so, try putting some random name in the 'Name' field like "avghbejugcbjnsjckln".
8.Reboot Device.
Enjoy the fresh new customization.
NOTE: Keep your device's stock firmware and sp flash tool with you. it will help you get your device back from a bricking type error. try in your own risk.

Categories

Resources