Related
My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem
there was one thread here .. try to search it i forget link it can explain you how to root official 2.1 otherwise run RUU & Do downgrade
according to all the programmes i run to check status of root (latest one is under the hood) it lists
Device: htc_hero hero
Root Status: Device routed
ro. build fingerprint: orange_uk/htc_hero/hero/hero:2.1-update1/ERE27/196735:user/release-keys
every programme that requires root access works for me tho i do have to grant it every time for programmes , the clockwork recovery has to be reflashed if phone has been restarted to enable me to access the recovery, and when i do this su pops up telling me it has been granted.
1 method i tried but never got past step backup recovery was this but i get message backup failed could not run command
"HTC Hero Custom Recovery
Step 1:
It's advisable to format the SD Card before do this process. You're going to lose all the information in the SD Card, do a manual backup to your computer of whatever you want, to do it:
Settings -> SD Card & phone storage -> Unmount SD card -> Format SD card
Step 2:
Download the flashrec from http://code.google.com/p/flashrec/
Download the recovery image provided by Paul from http://www.romraid.com/paul/hero/1.2-hero-recovery.zip
Extract the 1.2-hero-recovery.zip to your PC.
Step 3:
Now copy flashrec and recovery-RA-hero-v1.5.2.img (wich is inside the .zip file) directly to your SD card
Step 4:
Use an app installer from Google Market to install flashrec, i used ASTRO, but can be any other.
Step 5:
Once installed, open the program, click the button "Backup Recovery Image" and wait to finish, shouldn't take much time, this will do a backup of your actual recovery and put it in your SDCard with the name recovery-backup.img.
brisuth said:
My phone settings
firmware version 2.1-update 1
baseband 63.18.55.06PU_6.35.15.14
KERNEL VERSION 2.6.29-36D5CB8D
[email protected] #1
build number 3.35.61.2 cl196735 release-keys
software number 3.35.61.2 browser version webkit 3.1
I have been wanting to install a custom rom on my phone for several months now however no matter what method i try i am unsuccesful closest i have come is using rom manager which allows me to reboot into recovery but once the handset has rebooted home screen and power button just gets me to the triangle on screen and i have to remove battery. all flash recorder methods fail at either back up recovery
or writing flash.
I believe my phone is rooted as i can grant su to rom manager ect and androot tells me i am rooted it is like something resets recovery every time the handset boots into os.
i really have tried every method i have found but dare not try and install anything for fear of recovery not being available to me and i am now wondering if the 2.1 update has blocked something.
please help willing to make donation to any devs that can help me through this as well as the countless others having the same problem
Click to expand...
Click to collapse
You're absolutely right, the 2.1 update for the Hero installs a recovery rom reset, so whenever you boot up your phone normally, it reflashes it (or possibly checks that it's not the original and then flashes).
I don't quite remember where this was done anymore, it might have been a script in /system/bin that gets called from init(rc), called something like flash_recovery.sh. Perhaps someone who isn't running a custom rom could help out and pinpoint it for future reference (I am so not going back from cyanogen 6.0
Edit: I grabbed unyaffs and checked out my old nandroids, it's /system/etc/install-recovery.sh, comment out the line in it (add a # at the beginning of the line) and it will not clobber your custom recovery
i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.
brisuth said:
i have located file but now i feel really stupid as have not got a clue what to edit it with i am assuming it would be some type of txt editor and if u could specify the line i need to edit out or is it the name of the file i am changing,
really am gratefull for you pointing this out i had guessed what was happening just could find nothing to confirm it.
Click to expand...
Click to collapse
It might need to be a text editor that knows not to break unix line endings, but you can copy the file (cat file > /path/to/destination/file) to your sdcard or use adb to pull the file... fairly straightforward I thought.
A big thankyou to duck0 for identifying the problem and botoo for getting me to a happy conclusion with the correct commands
SOLUTION IS HERE USING Console mode from windows using ADB USB DEBUGGING HAS TO BE ENABLED WITH HERO CONNECTED TO PC THEN TYPE THE FOLLOWING
THEN ENTER AFTER EACH COMMAND
anyone needing help setting up adb see this link http://forum.xda-developers.com/showthread.php?t=757233
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
Thats it all done next step
INSTALL ROM MANAGER FROM MARKET IT IS FREE
open it and sellect flash alternate recovery image from the bottom, you can use the clockwork recovery but it is not compattable with all roms.
once done turn phone off, boot into recovery home + power choose to exit recovery with reboot shut down once again and if you can enter recovery then everything is sweet.
So the brilliant gentlemen at xolo have graciously provided us with a spectacular (albeit slightly buggy) update to android 4.4.2 kitkat for our xolo Q700S.
While this has a lot of advantages it lacks a clean and simple rooting method like framaroot or towelroot.
However, there is a slightly complex rooting method available to root our Q700S.
Our brothers with the Q1010i rooted their 4.4.2 devices with a method mentioned here
I just used the method given there and adapted it for our device. If any credit need be given they are owed to the original devs for porting and testing.
So lets get rooting!
1) Download Smartphone drivers for MTK devices from link given here ,unzip and.
- click install.bat
- if that doesn't work : run device management (run> devmgmt.msc). Turn off phone and plug in. Find MT65xx preloader. Update drivers. Browse local harddrive for drivers. Navigate to folder where you unzipped the drivers /SmartPhoneDriver/x86 or x64/infs. That should install drivers.
2) Download SP flashtool for windows from link given here.
3) Download CTR recovery for Q700s ported by tarun from this link
-best if you rename it to recovery.img
4)Download Scatter File for our device. (if it throws an error download scatter file from the attachments)
5) Download SuperSU by chainfire.
- rename to update.zip
- copy to root of sdcard.
Now ensure that you have a proper usb cable, wits, a strong nerve and basic knowledge of how to unbrick a phone if something goes wrong.
All boxes checked? Lets proceed.
>Run SP Flashtool
>Click Scatter-loading
>Select the .txt scatter file
>in the now visible options check only RECOVERY and double click the long empty green bar in the same row. Load recovery.img
>click DOWNLOAD on the top
>turn off phone and connect to PC.
>wait for bar on the bottom to go from red to yellow and then pop-up with download OK.
>now press vol+ and power and boot to recovery
>install.zip from sdcard
>let SuperSu install.
>reboot device (if it shows warning that may lose root access press no)
let android boot up!
if you did everything right then you have a rooted android 4.4.2 xolo q700S on your hands.
have fun!
usb noot stable
Hey .. thanks sir for this
bt flash tool doesnt recognizing my phone ,
it connects only when i press both the volume up and down key.
iS there any other way to install recovery? or by manually from stock recovery ?
or how to solve this prob ???
Sry for bad english
Thanks in advance..
Looking for kernel patch
It is indeed a great post and that'll gonna be helping people but I have a issue with Kernel or to say the root of this device, I have been using link2SD with JB with my sd card having a ext2 format but since I have moved to KK, it seem to have bugging me out all the way,
I can mount my sd card with ext4 but its useless and doesnt let me move my apps to 2nd partion as internal, eventhough I can use ext3 format which ends up with an error at mounting with unsupported transport end point, the reason made me to look for a kernel patch, I believe you'll try this and will be able to resolve for following readers and well thank you for this one.
Looking for a kernel that adds ext2 support.
Use Latest version of link2sd
adarshsamal said:
It is indeed a great post and that'll gonna be helping people but I have a issue with Kernel or to say the root of this device, I have been using link2SD with JB with my sd card having a ext2 format but since I have moved to KK, it seem to have bugging me out all the way,
I can mount my sd card with ext4 but its useless and doesnt let me move my apps to 2nd partion as internal, eventhough I can use ext3 format which ends up with an error at mounting with unsupported transport end point, the reason made me to look for a kernel patch, I believe you'll try this and will be able to resolve for following readers and well thank you for this one.
Looking for a kernel that adds ext2 support.
Click to expand...
Click to collapse
Use the latest version of link2sd, your problem will be solved if you have proper superuser rights ..
help
beingAshar said:
So the brilliant gentlemen at xolo have graciously provided us with a spectacular (albeit slightly buggy) update to android 4.4.2 kitkat for our xolo Q700S.
While this has a lot of advantages it lacks a clean and simple rooting method like framaroot or towelroot.
However, there is a slightly complex rooting method available to root our Q700S.
Our brothers with the Q1010i rooted their 4.4.2 devices with a method mentioned here
I just used the method given there and adapted it for our device. If any credit need be given they are owed to the original devs for porting and testing.
So lets get rooting!
1) Download Smartphone drivers for MTK devices from link given here ,unzip and.
- click install.bat
- if that doesn't work : run device management (run> devmgmt.msc). Turn off phone and plug in. Find MT65xx preloader. Update drivers. Browse local harddrive for drivers. Navigate to folder where you unzipped the drivers /SmartPhoneDriver/x86 or x64/infs. That should install drivers.
2) Download SP flashtool for windows from link given here.
3) Download CTR recovery for Q700s ported by tarun from this link
-best if you rename it to recovery.img
4)Download Scatter File for our device.
5) Download SuperSU by chainfire.
- rename to update.zip
- copy to root of sdcard.
Now ensure that you have a proper usb cable, wits, a strong nerve and basic knowledge of how to unbrick a phone if something goes wrong.
All boxes checked? Lets proceed.
>Run SP Flashtool
>Click Scatter-loading
>Select the .txt scatter file
>in the now visible options check only RECOVERY and double click the long empty green bar in the same row. Load recovery.img
>click DOWNLOAD on the top
>turn off phone and connect to PC.
>wait for bar on the bottom to go from red to yellow and then pop-up with download OK.
>now press vol+ and power and boot to recovery
>install.zip from sdcard
>let SuperSu install.
>reboot device (if it shows warning that may lose root access press no)
let android boot up!
if you did everything right then you have a rooted android 4.4.2 xolo q700S on your hands.
have fun!
Click to expand...
Click to collapse
SP tool shows Error intailizing scatter file failed. please check the name of scatter file load is legal
Elvis8655 said:
SP tool shows Error intailizing scatter file failed. please check the name of scatter file load is legal
Click to expand...
Click to collapse
i have uploaded the scatter file in attachments. download that without renaming.
beingAshar said:
So the brilliant gentlemen at xolo have graciously provided us with a spectacular (albeit slightly buggy) update to android 4.4.2 kitkat for our xolo Q700S.
While this has a lot of advantages it lacks a clean and simple rooting method like framaroot or towelroot.
However, there is a slightly complex rooting method available to root our Q700S.
Our brothers with the Q1010i rooted their 4.4.2 devices with a method mentioned here
I just used the method given there and adapted it for our device. If any credit need be given they are owed to the original devs for porting and testing.
So lets get rooting!
1) Download Smartphone drivers for MTK devices from link given here ,unzip and.
- click install.bat
- if that doesn't work : run device management (run> devmgmt.msc). Turn off phone and plug in. Find MT65xx preloader. Update drivers. Browse local harddrive for drivers. Navigate to folder where you unzipped the drivers /SmartPhoneDriver/x86 or x64/infs. That should install drivers.
2) Download SP flashtool for windows from link given here.
3) Download CTR recovery for Q700s ported by tarun from this link
-best if you rename it to recovery.img
4)Download Scatter File for our device. (if it throws an error download scatter file from the attachments)
5) Download SuperSU by chainfire.
- rename to update.zip
- copy to root of sdcard.
Now ensure that you have a proper usb cable, wits, a strong nerve and basic knowledge of how to unbrick a phone if something goes wrong.
All boxes checked? Lets proceed.
>Run SP Flashtool
>Click Scatter-loading
>Select the .txt scatter file
>in the now visible options check only RECOVERY and double click the long empty green bar in the same row. Load recovery.img
>click DOWNLOAD on the top
>turn off phone and connect to PC.
>wait for bar on the bottom to go from red to yellow and then pop-up with download OK.
>now press vol+ and power and boot to recovery
>install.zip from sdcard
>let SuperSu install.
>reboot device (if it shows warning that may lose root access press no)
let android boot up!
if you did everything right then you have a rooted android 4.4.2 xolo q700S on your hands.
have fun!
Click to expand...
Click to collapse
hi friend
i tried to but i have installed recovery img but supersu is not getting its so error while installing recovery mode pls help
Try Aparted from Google Play
adarshsamal said:
It is indeed a great post and that'll gonna be helping people but I have a issue with Kernel or to say the root of this device, I have been using link2SD with JB with my sd card having a ext2 format but since I have moved to KK, it seem to have bugging me out all the way,
I can mount my sd card with ext4 but its useless and doesnt let me move my apps to 2nd partion as internal, eventhough I can use ext3 format which ends up with an error at mounting with unsupported transport end point, the reason made me to look for a kernel patch, I believe you'll try this and will be able to resolve for following readers and well thank you for this one.
Looking for a kernel that adds ext2 support.
Click to expand...
Click to collapse
Please try Aparted and make both partition as FAT32 & Primary than install Link2SD as a fresh app and it will ask to choose second partition type than select option FAT16/FAT32, It will ask for reboot it will work after that.
Simple way to flash Kitkat & root it (no need to flash stock recovery, use cwm):
1.Download 392.8 mb update.zip (here: http://d-h.st/MfB)
2.Unzip it, goto META-INF/com/google/android and replace the 'updater-script' with the one attached.
3. Now zip it back, and flash it with cwm, carliv etc...
4.To root it, download & flash SuperSu via cwm (here: http://goo.gl/OSKQRQ)
I m having official final Kitkat update in q700s... and official stock recovery... Not able to root... I want to use viper4android... Give a clear direction plz to root it
xolo q700s kitkat root
i tried to root but when i switch my phone of and then nothing happens please help me and ya there is no red to green bar at bottom and i can't see download ok pop up man pls help while i boot it into recovery and try to apply update.zip after it fills one fourth of bar in my phone it says installation aborted #pls #help!!
what is the risk of rooting?
Root xolo q700s plus
can anyone say me how can i root my xolo q700s plus ?????? :laugh:
Followed all the steps, but supersu says su binary needs to be upated. PLease suggest what to do.
unable to download smartphone drivers for mtk drivers
Android Kitkat based ROM for the ZTE Blade L2
SwitchBL2de
ROM Features:
PreRooted
Apex Launcher
Debloated
Micro SD switched with Phone Storage
Zipalligned
ZRAM
build.prop Tweaks for the following :
Video and Photo Quality
Internet Connection Speed/Quality
Network Performance
Download Link:
Removed - Recompiling Rom, My sincerest apologies to DeviRSilva.
I used an earlier version of his kernel for the build - http://forum.xda-developers.com/android/development/kernel-devir-blade-l216-11-2014-t2945103
MD5 : a719cb770585f24c891fe47da9e56245
Note - Updated hosts file for ad blocking (Use xposed module "hosts Enabler" to prevent adverts)
Once Rom is installed and you restart phone from recovery
It may give the following warning "Root access possibly lost. Fix? THIS CAN NOT BE UNDONE"
Select "Yes - Fix root (/system/xbin/su)"
Credits to BSDgeek_Jake for the hosts file (http://forum.xda-developers.com/showthread.php?t=1916098)
*****************************************************************************************************************************************
Custom Recovery
Please have a read through the information in this link : http://www.howtogeek.com/193055/what-is-a-custom-recovery-on-android-and-why-would-i-want-one/
Flashing a custom recovery on the L2 is a simple process.
Things Required for this process:
Rooted Phone - (Please see the post on Rooting)
Mobile Uncle Tools APK
Recovery Image
First you have to allow the phone to install apps that dont come from Google Play Store.To do so,follow the guide :
1.Settings Menu
2.Security
3.Enable(tick) Unknown sources
4.Untick Verify apps
You can always reset these back to how you found them when you are done.
Download Mobile Uncle Tools
Mega Link: http://goo.gl/IkyVDo
or
MediaFire Link : http://goo.gl/c5q6Jh
Copy APK file to your SD card,use your file manager to install it.
Run Mobile uncle tools,allow root permissions when menu pops up.
You can close the app for now.Next thing we need is the actual recovery file itself.I've attached the recovery i find works best
Carliv Touch Recovery v2.2 - MTK CWM-based v 6.0.4.4
Download Recovery.img file
Mega Link: http://goo.gl/1f8OwX
or
MediaFire Link :http://goo.gl/U1D2Zu
MD5 :9f770b95df8e1beabd7417fc112190bc
Once the file has downloaded,copy to the root of your SD Card.
Open Mobile Uncle Tools and Select "Recovery Update".
Be sure to Select the downloaded recovery image,not anything else.
Select the file and proceed with installation.Mobile uncle tools will then prompt you to reboot into recovery if the update was successful.Select Yes and the phone will reboot into the new recovery menu
Credits to :
eddy.rugal - Base Rom
Carliv - For Recovery
njava - For Mobileuncle MTK Tool
Update
Resize Apps Partition
WARNING! This can BRICK your phone if done incorrectly.
PLEASE FOLLOW ALL STEPS CORRECTLY.
Please make a backup of all your important stuff.
Make a backup in the recovery.Make 100% sure the backup completes without any errors
Reboot into recovery mode (Hold the Up button and press power button to turn device on)
1.Select Backup and Restore
2.Select Backup and Confirm(Proceed)
Once the backup is complete,the backup is located in "clockworkmod" folder on SD Card
You have to factory reset device,so be prepared to reinstall apps/games (You are going to lose data)
If you are fine with all of the above,The following mod increases the App Partition size from 1GB to 2GB.It rewrites the Internal Storage to 513MB(Used for videos/pictures,which is fine since we use our Micro SD cards for that)
If you are happy with all of the above,you can proceed with the next step :
Firstly,Download all files required and copy to SD Card
2 GB for apps_Jellybean_4.zip (232.63 KB)
Mega Link - http://goo.gl/ao3NFO
or
Media Fire Link - http://goo.gl/3j9RWm
AND
MTK_Nvram_Tool.zip (2.9MB)
Mega Link - http://goo.gl/Z2Chpx
or
Media Fire Link - http://goo.gl/sjah8X
Once on SD Card,reboot into recovery mode (Hold the Up button and press power button to turn device on)
1.Select "Install Zip"
2.Select "Choose zip Sdcard"
3.Choose "MTK_Nvram_Tool.zip"
4.Select "Yes - Install MTK_Nvram_Tool.zip"
5.Click Next
6.Select "I Agree with this Terms and Conditions" and click Next
7.Click Next again
9.Choose 'Nvram Backup"
Once its done it should say "Backup Completed"
Under that it should say "Nvram Backup Successfully Completed"
It give the location for that backup,always keep that file (Copy to the PC Later)
10.Click OK
11.Click Exit
12.Click Yes
Now you are back at the install update from zip file screen.
13.Select "Install Zip"
14.Select "Choose zip Sdcard"
15.Choose "2 GB for apps_Jellybean_4.zip"
16.Select "Yes - Install 2 GB for apps_Jellybean_4.zip"
17.Go back to main menu
18.Choose Wipe menu
19.Choose Wipe Data (Factory Reset) -THIS WILL ERASE YOUR DATA
20.Wipe Cache
21.Wipe Dalvik Cache
22.Go back to main menu and reboot phone
The phone should reboot.If you get a message saying you have to format phone storage,click yes to format.
Go to Settings,Storage and See Total space is now 1.97GB
If the phone wont boot,power down,then hold up key and turn on to get into recovery mode.
1.Select Backup and Restore
2.Select Restore and Confirm(Proceed)
Restore the backup you made earlier.
This should let the system load when you reboot again,even if it asks you to format the phone again.
Copy NVRAM Backup to PC for safe keeping.
If you want to return to original/stock
Follow the same procedure as above but use the following file instead of the 2GB File
Stock Partition_Jellybean_4.zip (232.63KB)
Mega Link - http://goo.gl/pMn0ea
or
Media Fire - http://goo.gl/KJfRF7
Credits to :
AnoopKumar - MTK Nvram Tool
Andalitez said:
Hi Guys
Just an update.I downloaded the update from the website again,used winRAR and replaced the modem file in the system.
Everything works great now
Click to expand...
Click to collapse
Hey man can u yplease hook me up with the modem file im kida stuck with unkown baseband too
Replied
BlaqueDroid said:
Hey man can u yplease hook me up with the modem file im kida stuck with unkown baseband too
Click to expand...
Click to collapse
Hey man.
Sent you a PM.Currently working on a rom,will only be able to upload it for you in afew hours
ZTE
ztedevices.com/search.html?keyword=blade l2 look on there for the firmware for your device , push via adb sideloading and you should be set
noob problem...
guys, can you please help me...I also have the same problem when I flashed the kitkat rom...my blade l2 now can't read my simcard...what should I do?...
No Sim Detected
eochi18jhae said:
guys, can you please help me...I also have the same problem when I flashed the kitkat rom...my blade l2 now can't read my simcard...what should I do?...
Click to expand...
Click to collapse
Okay,you have to download the firmware version for your country,and have custom recovery installed on the phone.
So if you in UK,download the rom for your phone from UK provider.(doesnt matter if its JB or KK)
http://www.ztedevices.com/support/index.html
Once you have the rom,Use winRAR to do the following:
1.open the rom from your country in winrar so you can see the contents.
2.Open system folder (dont extract,just navigate into the folders in winrar)
3.Open "etc" folder
4.Open Firmware folder
5.Select "modem_1_wg_n.img" and extract it(i just drag and drop on desktop)
6.Open the Kitkat firmware you've downloaded using winRAR
7.Open System folder
8.Open "etc" folder
9.Open Firmware folder
10. Copy the "modem_1_wg_n.img" into that location(drag and drop from desktop)
11.winRAR asks if you want to :Add/Replace file/s? Select Yes or OK to allow it to
12.copy entire firmware to phone and reflash it on the phone from the SD card
I dont know if you can just replace the modem file after having loaded the firmware.I didnt try or test it.it may or may not work.
I am working on Custom Firmware for this phone though.
latest achievement was i managed to get the phone to see the SD card as phone storage thanks to various xda guides.this will be built in
FIrmware should be ready in a few days after testing.if anybody is interested in trying it out,let me know
problem solved...
Thank you sir...problem solved...it's really hard to be a noob...have to understand a lot of things now....I'm willing to try your firmware on my phone...upload it when done...keep up the good work...sorry for my english...
Post has been updated
I need to talk to you.... Go read my PM
installation is always aborted.. PLEASE HELP
Replied
Thanks
The thread is so useful... Keep up the good work, I don't have patience to try the new ROM!
Is there any chance for kernel supporting overclocking and undervoltage, also with more Gvernor and I/O Sheduler options?
Also Would be gorgeous if there's tap screen to wake option, this would need custom kernel too...
I'm now using DeviRSilva's kernel, which is doing great! Man, don't be afraid to relese it and continue tweaks
Still I'm a noob and maybe half of theese wishes are impossible, but would be so cool if they're possible to develop!
PD: I saw a site promoting Lollipop ROM for our L2 is that real?
PD2: Sorry for my awful English and probably stupid requests and questions...
helpppp
I have probelm, phone do not show sim card, on official site there is no serbia rom please how to fix it?
Andalitez said:
Replied
Click to expand...
Click to collapse
It fails to flash the ROM with the updated radio file. Just stops at Can't open... file.zip '(bad)'. Installation aborted.
How to fix?
Hi how do i unroot the zte blade l2?
And how to I remove costum recovery and reinstall stock recovery and stock rom?
Thanks just asking in case of sending it back for repairing.
Just noticed that the download link has been remoded.
Can someone provide a link for this rom?
Thanks.
Does this ROM have Greek language installed ???
no links are working
I need a copy of carliv recovery and backup of stock recovery as u think although my mobile mainly working I think the recovery is corrupt and has screwed my sound thanks in advance as I am taking a giant leap and biting bullet to try this recovery hope it can flash the legit kit kat if ever released by zte or virgin UK thanks
Andalitez said:
Android Kitkat based ROM for the ZTE Blade L2
SwitchBL2de
ROM Features:
PreRooted
Apex Launcher
Debloated
Micro SD switched with Phone Storage
Zipalligned
ZRAM
build.prop Tweaks for the following :
Video and Photo Quality
Internet Connection Speed/Quality
Network Performance
Download Link:
Removed - Recompiling Rom, My sincerest apologies to DeviRSilva.
I used an earlier version of his kernel for the build - http://forum.xda-developers.com/android/development/kernel-devir-blade-l216-11-2014-t2945103
MD5 : a719cb770585f24c891fe47da9e56245
Note - Updated hosts file for ad blocking (Use xposed module "hosts Enabler" to prevent adverts)
Once Rom is installed and you restart phone from recovery
It may give the following warning "Root access possibly lost. Fix? THIS CAN NOT BE UNDONE"
Select "Yes - Fix root (/system/xbin/su)"
Credits to BSDgeek_Jake for the hosts file (http://forum.xda-developers.com/showthread.php?t=1916098)
*****************************************************************************************************************************************
Custom Recovery
Please have a read through the information in this link : http://www.howtogeek.com/193055/what-is-a-custom-recovery-on-android-and-why-would-i-want-one/
Flashing a custom recovery on the L2 is a simple process.
Things Required for this process:
Rooted Phone - (Please see the post on Rooting)
Mobile Uncle Tools APK
Recovery Image
First you have to allow the phone to install apps that dont come from Google Play Store.To do so,follow the guide :
1.Settings Menu
2.Security
3.Enable(tick) Unknown sources
4.Untick Verify apps
You can always reset these back to how you found them when you are done.
Download Mobile Uncle Tools
Mega Link: http://goo.gl/IkyVDo
or
MediaFire Link : http://goo.gl/c5q6Jh
Copy APK file to your SD card,use your file manager to install it.
Run Mobile uncle tools,allow root permissions when menu pops up.
You can close the app for now.Next thing we need is the actual recovery file itself.I've attached the recovery i find works best
Carliv Touch Recovery v2.2 - MTK CWM-based v 6.0.4.4
Download Recovery.img file
Mega Link: http://goo.gl/1f8OwX
or
MediaFire Link :http://goo.gl/U1D2Zu
MD5 :9f770b95df8e1beabd7417fc112190bc
Once the file has downloaded,copy to the root of your SD Card.
Open Mobile Uncle Tools and Select "Recovery Update".
Be sure to Select the downloaded recovery image,not anything else.
Select the file and proceed with installation.Mobile uncle tools will then prompt you to reboot into recovery if the update was successful.Select Yes and the phone will reboot into the new recovery menu
Credits to :
eddy.rugal - Base Rom
Carliv - For Recovery
njava - For Mobileuncle MTK Tool
Click to expand...
Click to collapse
any news on the kitkat rom yet? super excited to try this out!
is the link for the rom gone?
i dont see it
BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18
Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.
Reserved
Works great on OEM 6.6, thanks for the tool!
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for
Does Works to unlock 7.4.2?
khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.
edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.
OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--
torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38
gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.
It's basic, libsec-ril.so is for sim card.
If your sim card is working before download Lineage OS you simply no need to download baseband/upgrade modem.
1.Need Root device
Example Magisk, SuperSU
2.Need Root File Manager
Example Root Explorer
3.Replace this file
Root/System/Lib/libsec-ril.so
0.How to get working sim card libsec-ril.so ?
-Find Lineage OS previous version that can make your sim card exist in your phone.
-Flash rom to that old version.
-Go to Root/System/Lib/ and backup libsec-ril.so
-Flash rom to new version and go to step 3 to replace file
-Turn Airplane mode on off, if not working reboot.
Or you can use this link to download libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk
Im sure file in that link is working for all note3 hlte if not please go to step 0
If you find anyone got problem like this, please help them, spread the solution.
Congrats Lineage OS team, for messed up basic thing in phone.
Hi,
this did not work for me. I used adb push while in twrp. The files and folders were deleted upon rebooting. What worked for me on my Galaxy Note 3 was https://forum.xda-developers.com/showpost.php?p=72986417&postcount=4141
QUOTE=Verband;73136081]Hi,
this did not work for me. I used adb push while in twrp. The files and folders were deleted upon rebooting. What worked for me on my Galaxy Note 3 was https://forum.xda-developers.com/showpost.php?p=72986417&postcount=4141[/QUOTE]
Permission denied.
That because admin access only RO(read only) in Root/system/lib
lib folder need to change to RW(read write)
You need follow my step for it to work, my step not using twrp, you need root explorer or any file manager that can change lib folder to RW.
Thanks
It worked for me first time. ?
I also have Galaxy Note 3 and Lineage OS build "lineage-14.1-20170725-nightly-hlte-signed".
@ Anon_Help_You
Perfect. Thanks!
HOLY CRAP YOU'RE A LIFE SAVER!!!!
I wonder if this would work with the Resurrection Remix no sim card found issues I have as well
I messed around so much for the last few days trying to update modem... finally saw this thread. Sim card now working, I had to re-register on network with choose network provider (might be cos I'm roaming) before I had signal though. THANKS SO MUCH FOR YOUR SIMPLE SOLUTION!!!
Thank you Man, It fixes the IMEI error too, flashed lineage-14.1-20170829-nightly
Anon_Help_You said:
It's basic, libsec-ril.so is for sim card.
If your sim card is working before download Lineage OS you simply no need to download baseband/upgrade modem.
1.Need Root device
Example Magisk, SuperSU
2.Need Root File Manager
Example Root Explorer
3.Replace this file
Root/System/Lib/libsec-ril.so
0.How to get working sim card libsec-ril.so ?
-Find Lineage OS previous version that can make your sim card exist in your phone.
-Flash rom to that old version.
-Go to Root/System/Lib/ and backup libsec-ril.so
-Flash rom to new version and go to step 3 to replace file
-Turn Airplane mode on off, if not working reboot.
Or you can use this link to download libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk
Im sure file in that link is working for all note3 hlte if not please go to step 0
If you find anyone got problem like this, please help them, spread the solution.
Congrats Lineage OS team, for messed up basic thing in phone.
Click to expand...
Click to collapse
It worked for me after flashing lineage-14.1-20170829-nightly-hltetmo, fixed the IMEI error too
Dosen't work.
Anon_Help_You said:
It's basic, libsec-ril.so is for sim card.
If your sim card is working before download Lineage OS you simply no need to download baseband/upgrade modem.
1.Need Root device
Example Magisk, SuperSU
2.Need Root File Manager
Example Root Explorer
3.Replace this file
Root/System/Lib/libsec-ril.so
0.How to get working sim card libsec-ril.so ?
-Find Lineage OS previous version that can make your sim card exist in your phone.
-Flash rom to that old version.
-Go to Root/System/Lib/ and backup libsec-ril.so
-Flash rom to new version and go to step 3 to replace file
-Turn Airplane mode on off, if not working reboot.
Or you can use this link to download libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk
Im sure file in that link is working for all note3 hlte if not please go to step 0
If you find anyone got problem like this, please help them, spread the solution.
Congrats Lineage OS team, for messed up basic thing in phone.
Click to expand...
Click to collapse
I tryed everythink but still donsen't read the sim card and no IMEI code...
kijijiusername said:
I tryed everythink but still donsen't read the sim card and no IMEI code...
Click to expand...
Click to collapse
Flash this: https://www.androidfilehost.com/?fid=673368273298969340
AP choice via odin.
Enter Download mode via Vol-, Power and home buttons after removing the battery and inserting it again.
had the same problem today and just fixed it.
hope that works for you
using my N9005
thanks thanks thanks
mgh97 said:
Flash this: [can't posted links now]
AP choice via odin.
Enter Download mode via Vol-, Power and home buttons after removing the battery and inserting it again.
had the same problem today and just fixed it.
hope that works for you
using my N9005
Click to expand...
Click to collapse
what the heck! it's working!!! i can't belive it. THANKS SOO MUCH
kijijiusername said:
what the heck! it's working!!! i can't belive it. THANKS SOO MUCH
Click to expand...
Click to collapse
i've figured it out 3 hours ago
happy that i could help ya
Thanks so much for this quick fix, it worked perfectly.
Is this going to be submitted as a fix for future lineage os builds...?
Update modem and baseband, do not replace libraries
It shouldn't be fixed by replacing a library: the real problem is that your modem and baseband versions are too old. You need to update them. My Note3 was increasingly having trouble connecting to LTE networks before I installed LineageOS (I was on CyanogenMod a long time). After the baseband and modem updates (which you don't get automatically anymore if you install a custom ROM), that's working like a charm again, and the missing SIM problem is gone too, with LineageOS builds working out of the box.
Works!
Hi,
I replaced
root/system/lib/libsec-ril.so
by the old version of Cyanogmenod 13. Not SIM and GPS works again.
What I did:
- extract libsec-ril.so from my TWRP backup (using RAR)
- boot into TWRP recovery, overwrite file
Thank you very much!!!
Lysathor said:
Hi,
I replaced
root/system/lib/libsec-ril.so
by the old version of Cyanogmenod 13. Not SIM and GPS works again.
What I did:
- extract libsec-ril.so from my TWRP backup (using RAR)
- boot into TWRP recovery, overwrite file
Thank you very much!!!
Click to expand...
Click to collapse
care to share on how to perform the steps in details/pictures?thank you in advanced
it seems these steps no longer working for latest build lineage-14.1-20171107-nightly-hlte-signed.zip,no sim detected,or it is just happen to me? anyone else having a problem?
@ulats07 same happening to me with lineage-14.1-20171107, the libsec-ril.so is not present in /system/lib anymore, only libsecril-client.so and libsec-client-sap.so.
i will try @svenberkvens suggestion and update the modem and baseband
EDIT:
sorry, can't post links , replace DOTs and remove spaces
so i followed the instructions from https://jira DOT lineageos DOT org/browse/REGRESSION-773?focusedCommentId=17429&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17429 (lineage jira website) to update the modem and sim works now without replacing the libsec-ril.so file.
pasting the instructions here
Make a MODEM backup with TWRP before running it in case of errors
What worked for me:
- Download Kevin's tar https://www DOT androidfilehost DOT com/?fid=673368273298969340
- Rename the .tar.md5 extension to .tar
- Extract the modem.bin file
- Poweroff your phone. Don't reboot into download, just power it off, otherwise the flash will seem correct except that it won't actually be done
- Put your phone into download mode (vol down + home + power)
- Use heimdall (last version, 1.4.2 from github, other versions won't work) to flash the modem using :
- (sudo) heimdall flash --MODEM modem.bin
- Your phone will reboot and SIM should work
Click to expand...
Click to collapse
I'm on mac and I used heimdall-frontend, detailed instructions follow:
- download latest version from https:// github DOT com/Benjamin-Dobell/Heimdall/releases (heimdall git)
- extract and open in terminal
- `cd Heimdall-1.4.2`
- follow https://raw DOT githubusercontent DOT com/Benjamin-Dobell/Heimdall/master/OSX/README.txt (build instructions) from the bottom of the README, pasted below and modified slightly (specifies LIBRARY_PATH and puts the app in the Applications folder)
Code:
brew install libusb qt5 cmake
mkdir build
cd build
cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -DQt5Widgets_DIR=/usr/local/opt/qt5/lib/cmake/Qt5Widgets ..
LIBRARY_PATH=/usr/local/lib make
cp -r bin/heimdall-frontend.app /Applications
open heimdall-frontend go to:
- Utilities -> Detect Device -> Detect
- Utilities -> Download PIT -> Download
- Flash -> Options -> Specify your PIT file
- Flash -> Partitions -> Add
- Flash -> Partition Details -> Partition Name -> MODEM
- Flash -> Partition Details -> File -> modem.bin (from the extracted Kevin's tar)
And now a working guide for windows would be nice
I allready tried the steps which where mentioned in the posts before but without success
So is there someone who can tell me how this works on Windows with Odin and the latest "lineage-14.1-20171107-nightly-hlte-signed.zip" version?
Note 3 Sim Card not detected
Hey,
Ive the same problems with my Sim detection now, it stopped working after updating to the latest Nightly 07-11. However, even using an old Nandroid Backup (where SIM worked) doesnt work, flashing another ROM also didnt fix the problem. (tried Dirty Unicorns, Lineage from mid 2017, Resurrection) I also tried flashing a new modem but the problem persisted. Im not too experienced with all that Android stuff and would really appreciate any help.
Thanks in advance!