Related
So for Stock A500 users stuck at the Acer Logo, or maybe some other strange issue with the tablet not booting, you may want to try this method first before rolling up your sleeves and moving on to getting your UID, which involves the use of Linux for the most part.
Download these full ICS Update files for the A500 (501 owners can try this also, but you'll have a 500, but that might can be changed later)
These files are already "decrypted" and are named differently as to keep them separate. Download them all to a folder.
Now, select one of them, rename it to "update" (end result is a file called update.zip) copy it to SD card, boot tab and see if it installs. If it hangs on the install, delete it from SD card, and do the same with the next. Hopefully one of them might take. You may have to try all 4 of them before one works. It's hit and miss.
http://d-h.st/Zf8
http://d-h.st/2cm
http://d-h.st/gw8
http://d-h.st/KXl
Mega Links:
https://mega.co.nz/#!lM5iQYLZ!TKx3ZIsN1-L4-Lk2LveHhEjb-PejZ1ZNZPwdsBsuNZM
https://mega.co.nz/#!8R5X3T6C!D-j_EcGhkWyhG8nyprhimcic_uf2chA-rXlnqaLIe7k
https://mega.co.nz/#!sBwwVDQB!cDmVCNH63i-eAMnvtrro7rMGjXDMJPqJbgbXjzX6jDQ
https://mega.co.nz/#!MQhB1L5R!Dj06bqJVgXZ1JAnLGvX1CuUqNs3lXtg8NkxkfbU4osY
Hope this gets you going.
MD
Bricked Iconia A500 working again
Hi, after nearly 3 years my Iconia A500 bricked when I tried to play a viseo file via the usb port.
After reading the forum I tried the first update zip file from this thrread and BINGO it worked
Thanks guys for the good job done:good::good:
studioph said:
Hi, after nearly 3 years my Iconia A500 bricked when I tried to play a viseo file via the usb port.
After reading the forum I tried the first update zip file from this thrread and BINGO it worked
Thanks guys for the good job done:good::good:
Click to expand...
Click to collapse
How long does it take to load, how long should I wait to try the next one?
gonka95 said:
How long does it take to load, how long should I wait to try the next one?
Click to expand...
Click to collapse
Because it is some weeks ago I can't remember how long it took to load but it was not extreme. I think all was done in 1 or 2 hours. But during the process you get already some info that the tablet is working "normally"
Good luck with trying, my tablet is still working fine
PH
I have try with all update.zip and my tab is always block on "Android" logo.. can u help me?
megoza said:
I have try with all update.zip and my tab is always block on "Android" logo.. can u help me?
Click to expand...
Click to collapse
First of course, is that the file must be renamed to just "update.zip" and if you are doing this from a Windows machine, you may not see the ".zip" part. Do not be worried about that and just rename to "update". I copied each file, in turn, to the MicroSD card BEFORE renaming the file. That way, you retain the original and don't end up with "update", "update(1)", update(2), etc.
Have your Iconia A500 fully charged and powered off. Disconnect the power cable. Install the MicroSD, loaded with the "update.zip" file (the gold contacts side of the card face the screen side on the A500) into the card slot in the top of the Iconia A500. Holding the left side of the Volume Switch down, press and hold the Power Button down. When the tablet powers up, release just the Power Button. When you see the writing appear in the top left corner of the screen showing that it is loading the update file, release the Volume Switch. You should shortly see an Android figure with a spinning ball of triangles (not sure of the correct geometric term) in its belly. If the Android changes to laying down, with a red triangular exclamation, that version did not work. You should see a light blue thin progress bar if it is loading.
---------- Post added at 03:14 PM ---------- Previous post was at 03:01 PM ----------
I tried the different files. The "41-124-01-update.zip" loaded, but the progress bar only got about 20% - 25% along the way before not progressing any further. I left it overnight, and in the morning, it was still the same. The ball of triangles is still spinning in the Android's belly, but no progress is happening. The first time this happened, after an hour, I manually powered down the tablet, and then powered it back up. I got the buzz and the ACER logo (constant brightness), but it went no further. It just hangs there. And yes, I tried the external Factory Data Reset, and no, it did not work either!
Any ideas on what might be stopping the progress bar, or how to get the update to completely load?
Has anyone had any luck installing an alternative bootloader and then installing a different image?
Is this a software or hardware issue?
NOTE: My A500 Iconia experienced the exact same issue regarding failure to boot that has been described by hundreds on various forums. I was hoping that I'd finally discovered a fix.
Hi do you mind upload these files again? They are no longer exist.....Thanks!
Aelliseu said:
Hi do you mind upload these files again? They are no longer exist.....Thanks!
Click to expand...
Click to collapse
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Moscow Desire said:
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Click to expand...
Click to collapse
Is this valid also for A501 and, if not, where can I find the update.zip for A501? Thanks!
lahor said:
Is this valid also for A501 and, if not, where can I find the update.zip for A501? Thanks!
Click to expand...
Click to collapse
Well, they will run on a 501, but you won't get 3g or GPS.
www.acer.ru has the 501 ICS update files. You will need to match the update to your current Operating System Build. The reason, is that they run "patch" updates. So if you've been running a custom ROM, you will need to roll back to a factory 3.x.x and use the matching update file.
Moscow Desire said:
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Click to expand...
Click to collapse
Thank you so much!!!! You save my tablet!!!!:good: :good:
Aelliseu said:
Thank you so much!!!! You save my tablet!!!!:good: :good:
Click to expand...
Click to collapse
I did?
I got no result with those 4 options. Tablet is stil dead. Do you have another option of file?
lahor said:
I got no result with those 4 options. Tablet is stil dead. Do you have another option of file?
Click to expand...
Click to collapse
Not really, you will have to use Timmy Dean's Rollback Tool.
Basically it's an EUUS 3.2.1 ROM that will reset your partitions. The only advantage to running TD's tool, compared to a regular EUUS, is that TD's tool installs it "pre-rooted with a CWM recovery".
Either way, you are going to have to go back to 3.2.1. No way around it.
And... you will need your CPUID number to do it. I hope you had a custom recovery installed, as it should have this number. If not, you will need linux to get it. Neither tool will run without it.
MD
Moscow Desire said:
So for Stock A500 users
MD
Click to expand...
Click to collapse
I used these update.zip's to upgrade my 4.0.2 to 4.0.3. Great, but I can't get adb to recognize the A500. Is there a trick to this?
My A 500 has not been modified, but I too had no result, or at least no positive result. Do I also need to use this Timmy Dean's Rollback Tool? I also don't have my CPUID number. I do have a laptop loaded with Ubuntu 14.04, so can I use that to get it?
rasmith3530 said:
My A 500 has not been modified, but I too had no result, or at least no positive result. Do I also need to use this Timmy Dean's Rollback Tool? I also don't have my CPUID number. I do have a laptop loaded with Ubuntu 14.04, so can I use that to get it?
Click to expand...
Click to collapse
Get your CPUID here, using Ubuntu.
http://forum.xda-developers.com/showthread.php?t=1751978
Download the following Timmy Deans 3.2.1 rollback tool and extract to your PC;
https://mega.co.nz/#!FFoxzRLY!fSmY49VDxCdr-hwv6Tw7GPLIzUQNOzSgDzmzAspwmNc
Run the PBxxx.exe and use administrators rights, Wait till it gives the pop up to put your tab in apx mode and do it and connect. Enter uid number.
Hope it works. Remember that acer no longer has ota servers, for a year now, so you will have to do a manual update.
Thanks for the information MD. I will try this and report back here my results.
Moscow Desire said:
Not really, you will have to use Timmy Dean's Rollback Tool.
Basically it's an EUUS 3.2.1 ROM that will reset your partitions. The only advantage to running TD's tool, compared to a regular EUUS, is that TD's tool installs it "pre-rooted with a CWM recovery".
Either way, you are going to have to go back to 3.2.1. No way around it.
And... you will need your CPUID number to do it. I hope you had a custom recovery installed, as it should have this number. If not, you will need linux to get it. Neither tool will run without it.
MD
Click to expand...
Click to collapse
I am back without results.
1. need linux- i have a linux (Ubuntu ) on my comp
2. I saw the instructions but:
He says: You need to install this: Install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev . where can I find those files and how can I install this?Do you have one package for all files or some links?
I tried to get some file and I begin with gcc apx.c -o apx -lusb-1.0 , then I get on my terminal
[email protected]:/home/deni/Bureaublad# gcc apx.c -o apx -lusb-1.0
apx.c:1:31: fatal error: libusb-1.0/libusb.h: Bestand of map bestaat niet(this is dutch)
#include <libusb-1.0/libusb.h>
What I need to do in this case?
3 Tablet in APX mode? How can I know when my tablet in APX mode is?
4.With all erorrs I tried to type ./apx (rename the apx.c) but I get the message: acces denied??
[email protected]:/home/deni/Bureaublad# ./apx
bash: ./apx: Toegang geweigerd
I need a Help
lahor said:
I am back without results.
1. need linux- i have a linux (Ubuntu ) on my comp
2. I saw the instructions but:
He says: You need to install this: Install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev . where can I find those files and how can I install this?Do you have one package for all files or some links?
I tried to get some file and I begin with gcc apx.c -o apx -lusb-1.0 , then I get on my terminal
[email protected]:/home/deni/Bureaublad# gcc apx.c -o apx -lusb-1.0
apx.c:1:31: fatal error: libusb-1.0/libusb.h: Bestand of map bestaat niet(this is dutch)
#include <libusb-1.0/libusb.h>
What I need to do in this case?
3 Tablet in APX mode? How can I know when my tablet in APX mode is?
4.With all erorrs I tried to type ./apx (rename the apx.c) but I get the message: acces denied??
root[email protected]:/home/deni/Bureaublad# ./apx
bash: ./apx: Toegang geweigerd
I need a Help
Click to expand...
Click to collapse
Moscow Desire Thanks!
I have know Jellytime 4.3 on my tablet.Need a 10 days to make this. In the beginnig everything was difficult but now it seems so simple and easy.
My description for more clarity:
1. UBUNTU last version
2. In this version you have a GCC but not libusb-1.0-dev. The best option is synaptic package manager. Install this from UBUNTU software center.
Open the synaptic and search the all files with libusb -you will get the list with the required files . Just install the all!
3.Make or download apx.c. If you have 32 bit you can use code from this site (something about printif changing). Make the folder APX on Dekstop and put file apx.c there .
4. Open the terminal ( if you can not find the terminal(no experience with UBUNTU , just in search type terminal).
5. In the terminal type dir or ls,. You can see the all folders and then type
cd Desktop/APX. If you get something strange or you get no result try to type sudo su for "refresh"
6. type gcc apx.c -o apx -lusb-1.0
7. If you get message with errors this mean that your libusb 1.0 dev is not installed. If you see a new file apx near your old file apx.c then is OK
8.type ./apx .....(if you get the message acces denied or cannot open device just type sudo su for refresh)and your CPUID is there.
9. then you need SBK
10. Download V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip and unzip this
11.Make APX mode on your tablet ( push reset button(with needle) then power(with finger ) ) everything is black(that's good) and you are ready.
12. open the V8-UNL-ICS-HC-bootloader-MULTI-cwm with V8.bat file, and follow instructions. Use your SBK, choose option 2 and go next(two times). When you get PASS on your tablet your tablet is ready.
13. Download the jellytime 4.3 with GAPPS to your microsd. from
http://forum.xda-developers.com/showthread.php?t=2376662 or HC 3.2 for ( in my case) A501 from this forum
no need to change name to update.zip .
14. The next step: Volume down +power (you are going to the recovery mode) and folow the instructions
Boot in recovery mode to flash theJellytime or HC3.2.
First, don't forget to execute a 'Wipe Data/Factory reset'
Flash the Jellytime
Flash the Gapps
Do a 'wipe cache partition'
Reboot
15. That's it!
16. Enjoy!
Hi Guys,
Some people know me here but for the others, i look for new devices and try to find a way to root. I specified on devices, which are not had many devs, which works to find ways to get root and so i had around 5 Worldfirst roots from Asus to Acer and so on.
So, after 6 days of bricks, flashes, lot of time with the root scripts flooding around, i open the gate now!
The G4s had official 5.1.1 installed and probs to get root, since now.
This root is working on LG devices, which get "fail" on the send_command.exe or doesnt had SU installed after root session finished or doesnt boot after the root was done. So i think a lot of devices out there.
The problem with the new security is, that the diag port is not open. After many testings and time stoping i found the golden 9% after which the gate opens so that we could work with. :good:
on work
Lets try it out. I have also uploadet the kdz Firmware 10D if something goes wrong. Then sinple flash the kdz. No Data lost with the lg flash tool.
Lets start, driver, usb debugging...i think if someone want to root, he must know how to enable.
Deinstall LG Bridge and LG Air if installed!!!
1. Phone plug in with usb on usb port, usb debugging on, MTP
2. Unzip the rootworm.zip and click the rootworm script
3. G3 5.1.1 , LG H631 works without lg flash tool and is rootet now.
Some hard secured phones like the h735 had closed port. So with this devices we must use also LG FLash Tool 2014.
4. Open LG Flash Tool 2014
5. Choose kdz, smartphone (wm) and press normal flash (we dont flash,its only to open the port)
6. Now phone boot will direct try in Download Mode or reboot. On LG Flash tool run the line with the percents %
7. At around 5% the phone reach the Download Mode.
8. Now comes the trick, at 9% the port opens and then in green letters will stand COM X.
9. In this moment with the green COM X letters plug off the usb cable.
10.. Close LG Flash tool with Windows Task Manager. (The Flash progress bar and the flash tool direct).
11. Port is open and can connect again to pc and refresh the driver in device manager (yellow symbol)
12. shift right click in the zip an type SendCommand.exe \\.\COM(yourCOMport)
13. type 1 time ls, this will counter with fail. Then sh /data/local/tmp/rootworm.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /system/xbin/busybox
So, normaly thats it.
If i end my last University thesis, i will look for a twrp.
Have Fun!
Firmware G4s 10C (Phone see the firm as 10F) https://mega.nz/#F!tpMnWQpL!ay-B9yQ9mOi9DreRATpp_g
Why post now, if you have nothing yet?
Wouldn't it more beneficial to post a thread once you have something working?
TonyStark said:
Why post now, if you have nothing yet?
Wouldn't it more beneficial to post a thread once you have something working?
Click to expand...
Click to collapse
I make the script ready. I post that 2 hours before, that people know that and not soft bricking her devices with root methods they not working. Thats the reason.
The more root options the better. Right now, we have to backup system, inject root, and flash a rooted_system.img back to phone. Seems like a lot of work.
However at least the option is there. I am looking forward to your findings.
player911 said:
The more root options the better. Right now, we have to backup system, inject root, and flash a rooted_system.img back to phone. Seems like a lot of work.
However at least the option is there. I am looking forward to your findings.
Click to expand...
Click to collapse
Thank you very much. It was really a lot of work and debugging. Flashed many times to get the exact point were the port goes open without the flash procedure from flash tool.
Hope all goes well, was a lot of write work because lg used a lot of codes in the new phones and different Android versions.
@konsolen, thanks for your efforts.
BTW, which KDZ to choose in step 5? You have not provided link for 10D kdz.
5. Choose kdz, smartphone (wm) and press normal flash (we dont flash,its only to open the port)
Click to expand...
Click to collapse
itskapil said:
@konsolen, thanks for your efforts.
BTW, which KDZ to choose in step 5? You have not provided link for 10D kdz.
Click to expand...
Click to collapse
Thx and sry. Was to late yesterday i forget.
Here it is:
https://mega.nz/#F!dl0E3T6C
it works
thank you.
root lgh735 with flashtool worked great.
LG Spirit H440n 5.0.1 latest version cannot be rooted with kingroot. Do you think I should give your method a try? Which kdz should I use? One of my own?
Edit: I think there has been some mistake and the command is "Send_Command.exe" and not "SendCommand.exe".
Alright. I did the LG FlashTool method with the COM 4 Green letters showing in phone and what I get is:
Code:
C:\Users\myusernamehere\Desktop\root>Send_Command.exe \\.\COM4 < rootworm
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
####
Has anyone tried this with a U.S. G4?
also the mega link requires a decryption key?
I'm also wondering what to do about the .kdz file as I haven't been able to find one online for the g4 beat... Any help is appreciated!!
I ran the script yesterday and it said that Push_File.exe is missing
did you miss to include an file?
my firmware is 10b so i'll assume ill use my own H73510b_00.kdz am i right?
Update: yup im now stuck at %9 with
C:\Users\myusernamehere\Desktop\root>Send_Command.exe \\.\COM4 < rootworm
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
####
aswell... :/
Sry, was the last days at university and could not look.
Here is the link: https://mega.nz/#F!tpMnWQpL!ay-B9yQ9mOi9DreRATpp_g
As i put it only i had a very long tesnight and dont look and the password.
konsolen said:
Sry, was the last days at university and could not look.
Here is the link: https://mega.nz/#F!tpMnWQpL!ay-B9yQ9mOi9DreRATpp_g
As i put it only i had a very long tesnight and dont look and the password.
Click to expand...
Click to collapse
so what do i do after shift right click in the zip an type SendCommand.exe \\.\COM(yourCOMport) < rootworm tho? it just gives me like what i said earlier.. :crying:
dreamnoob said:
so what do i do after shift right click in the zip an type SendCommand.exe \\.\COM(yourCOMport) < rootworm tho? it just gives me like what i said earlier.. :crying:
Click to expand...
Click to collapse
Hi, i put a new script online with small changes. And also few point in the list. I was thinking that everybody do that but i read now that many people dont know the basics. Uninstall LG Air and LG Bridge. These tools take the com port. And for the fail devices i write the last point with the command. Some phones are su withous ls others not. So on the secure side, copy the line.
So, the best is you type now Push_File.exe \\.\COM6 busybox /system/xbin/busybox. Then the last command:
sh /data/local/tmp/rootworm.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /system/xbin/busybox
The other files must in data/local/tmp like always.
konsolen said:
Hi, i put a new script online with small changes. And also few point in the list. I was thinking that everybody do that but i read now that many people dont know the basics. Uninstall LG Air and LG Bridge. These tools take the com port. And for the fail devices i write the last point with the command. Some phones are su withous ls others not. So on the secure side, copy the line.
So, the best is you type now Push_File.exe \\.\COM6 busybox /system/xbin/busybox. Then the last command:
sh /data/local/tmp/rootworm.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /system/xbin/busybox
The other files must in data/local/tmp like always.
Click to expand...
Click to collapse
pretty sure i did it wrongly.. typed 'ls' and came out a long list of stuff.. after that did sh /data/local/tmp/rootworm.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /system/xbin/busybox but nothing happened..
heres a pic http://i.imgur.com/IljBas3.png
i dont have lg air and drive uninstalled it prior to doing this
dreamnoob said:
pretty sure i did it wrongly.. typed 'ls' and came out a long list of stuff.. after that did sh /data/local/tmp/rootworm.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /system/xbin/busybox but nothing happened..
heres a pic http://i.imgur.com/IljBas3.png
Click to expand...
Click to collapse
if you get a long list, that sounds good. Type ls system/Xbin/ and tell me if you see whats in there
konsolen said:
if you get a long list, that sounds good. Type ls system/Xbin/ and tell me if you see whats in there
Click to expand...
Click to collapse
nothing comes up after i entered that :/
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.
JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!
jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...
pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.
How to unbrick by sdcard from 9008 without QFIL
This method works ONLY for qualcomm devices (ANY non-UFS!!) which are already in QDL/EDL/9008 mode!
This method does *not* work for:
Samsung devices in general.
Details:
Samsung is doing things completely different while ofc a qcom based Samsung works with the same principal as "normal" devices. Just the process of building an hnbrick sdcard is different as you can get the pit (partition list) by heimdall but not a flashable gpt. Instead search for "sboot sdcard unbrick" or "sboot sdcard <your model>" . The important part here is "sboot" as that one will be loaded by the iROM when flashed properly (+other stuff).
UFS devices (so not for the G5 or later).
Details:
9008 bricks are not fixable on UFS NAND devices by booting from an SD card. The boot path is stored in QFPROM (on the CPU) and it is something like /dev/block/sdb or /dev/block/sde. On eMMC devices, the boot path is /dev/block/mmcblk0. If you have a 9008 brick, the SD card is seen as /dev/block/mmcblk0 so the phone will boot from it on an eMMC device since that IS the boot path. There is no way to make the SD card appear as /dev/block/sdX. And there is no way to change the boot path once you have a 9008 brick without a firehose. If you have a signed firehose, then you can fix your phone without needing an SD card As for cross flashing. I checked the RSA signature for the H930, H932, H933, and US998 and they are all different. If you flash any of the signed firmware (xbl, abl, hyp, modem, etc) from one of those devices, then you have a 9008 brick and no way to fix it yourself.I didn't bother checking the Verizon or Sprint models since they are even more locked down than the H932 is, but it appears from reading this thread that they have the same key as the US998 (I am not going to waste my time checking).-- Brian
Click to expand...
Click to collapse
If your device is connected and not detected like that the external sdcard method will NOT work for you.
On the LG G4 you can force the sdcard mode by following post #2 . I guess every device has a way to force that mode so google is your friend.
Hint --> If you have no sdcard and own a H815 device (only then) you can make use of these validated QFIL process here
Requirements
1) Ok first of all what you need is Linux. I highly recommend FWUL ( https://bit.do/FWULatXDA ) but any Linux is sufficient if you can handle it.
2) LG models only: you need the latest SALT version ( https://bit.do/SALTatXDA ) which is already included since FWUL v2.5 (one of the reasons why I recommend FWUL).
If you decide to use FWUL and start SALT it should prompt you when an updated SALT version is available. To be sure: just click the Update button in SALT once started.
3) you need an external sdcard which is (to be sure) bigger then your internal storage (the sdcard must have the same size of your internal storage! so in theory a 32GB card should work fine but some cards are sold as 32GB but the real size is less , i.e. 29 GB). Thats the most critical part here as the GPT will be invalid if it does not fit with the sdcard. you can't edit the GPT though as then internal checksum may fail and so it will not work to boot from the sdcard. so ensure you have a bigger sized sdcard to workaround any issues related to this.
4) Another important requirement for that external sdcard is: speed! If you want to ensure that you do not struggle ensure it is at least a class 10 card with UHS. It MIGHT work without UHS and it MIGHT work even on slower cards down to class 4 but when the storage is too slow the device rejects to boot from it as it ran into timeouts and so marking the sdcard as "not good enough" to boot from it.
Of course you can first try a lower speed sdcard but if you encounter issues here then it is likely related to the speed of the sdcard.
5) you need a 100% matching firmware (e.g a KDZ on LG's) for your device model - and very important: with a matching ARB of your current installed firmware!
If your current installed firmware has a higher ARB then the one you flash on the sdcard it will NOT work!
Find out what ARB means here https://bit.do/antirollg4
Steps
1. Boot FWUL (or ur personal Linux)
2. LG models only: Start SALT - ensure that it is v3.5 or higher
3. Extract the firmware file (e.g KDZ) but usually not all partitions are needed - just the bootloader stack
(depends on your device - the following is for any LG G4 model):
Primary GPT
sbl1
aboot
pmic
rpm
tz
laf
sdi
hyp
If you have not all or any of these (first check the note about UFS above) then you must identify your bootloader stack first.
A good start for this is here: https://lineageos.org/engineering/Qualcomm-Firmware but you may have to just try and error here.
For a quick & dirty try: flash every partition which is smaller then 150 MB (i.e. leave out system, cache, userdata and such).
4. Clean dmesg by opening a terminal and type:
Code:
sudo dmesg -c >> /dev/null
5. Connect your external sdcard to FWUL
6. Type this in the terminal:
Code:
dmesg
and find the connect messages there pointing to the device name. usually you see something like "mmcblk0" but sometimes it's different named like sdc or sdd or similar.
We do not need the pXX here. So if you see mmcblk0p1 we need only mmcblk0. If you see a sdc1 or sdd1 we just need sdc or sdd without the number.
7. The device name is needed now! Ensure it has the correct size by typing this in the terminal:
Code:
sudo fdisk -l /dev/mmcblk0
(replace mmcblk0 if you your device is named different in step 6).
This is important because the next step will erase your sdcard completely!
All your data get lost!
So if you choose the wrong one you may overwrite your PC storage in worst case! So double check this before proceeding.
You can do so by disconnecting the sdcard and if the command in this step gives a message about the device cannot be found - connect device again and re-do the above command. if it shows then again your device all is fine
8. Now flash the GPT (partition table) to your device in a terminal:
Change into the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:
Code:
cd /tmp/extracteddz
sudo -s
dd if=PrimaryGPT.gpt of=/dev/mmcblk0 (replace mmcblk0 if you your device is named different in step 6)
sync
hint: do not close the terminal
9. Disconnect the sdcard and connect it again
10. Now flash the rest in a terminal:
First check if the GPT has been flashed fine:
Code:
ls -la /dev/disk/by-partlabel/
if you get nothing as a result or an error message something went wrong. Go back to step 4!
Move to the folder where you extracted the backup. If you leaved the default on SALT it's /tmp/extracteddz:
Code:
cd /tmp/extracteddz
LG G4 - ONLY - Flashing instructions for locked or official unlocked phone (If you UsU'd your device skip this!)
Code:
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=aboot.bin of=/dev/disk/by-partlabel/aboot
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
[B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!
LG G4 - ONLY - Flashing instructions for an UsU'd device
Besides the KDZ extract you also need to grab the UsU unlock zip of your device model first then do this:
Code:
dd if=sbl1.bin of=/dev/disk/by-partlabel/sbl1
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=sdi.bin of=/dev/disk/by-partlabel/sdi
dd if=laf_UsU.img of=/dev/disk/by-partlabel/laf
dd if=aboot_UsU.img of=/dev/disk/by-partlabel/aboot
dd if=rawres_UsU.img of=/dev/disk/by-partlabel/raw_resources
[B][COLOR="Red"][SIZE="4"]sync[/SIZE][/COLOR][/B]
Do [B][U]not forget[/U][/B] that last ("sync") command!! Otherwise it will very likely not work!
11. Now everything is prepared. Take out your sdcard. Take out the battery and disconnect cable. Plugin the external sdcard. Put battery back.
Start the device in fastboot mode and use fastboot flash partition imagename.img
If there is no fastboot possible open the download mode.
For example on the LG G4:
Press volume up (only this) and keep it pressed.
Then connect USB cable while still keep the pressure on volume up for 20 seconds.
The download mode should come up.
Congrats you can now use e.g. LGup (or for Samsung, ODIN etc) for unbricking by flashing a regular firmware on it (beware of the ARB again).
Have fun! :highfive:
Support / TG group
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here.
Note:
be polite, don't ask to ask, be patient(!), respect the timezones, help others.
,-
Force SDCARD boot
How-To force booting from sdcard (LG G4 only) (e.g. when the device is NOT in 9008 / QDL mode)
You may know the 2-pin-bridge method which can enforce the 9008/QDL mode (on the back of the main board which is shown when disassembling the back cover).
Now you may think: you can enforce that mode by bridging these pins and then you could boot from sdcard as this guide here says 9008 mode is a requirement.
The answer is: NO. This will NOT work!
But there seems to be a way (which I personally never have tested!) to force that sdcard boot by doing the following.
Be aware: You do this on your own risk! Do not cry if something is failing/destroyed/whatever. Its totally up to you to proceed or not but its on your own risk like always when following guides.
prepare the sdcard as described in the above guide
insert the sdcard in the device
remove battery of the device
unplug usb cable
disassemble the back cover by loosen all screws
disassembling the mainboard like described here: fixit guide
on the FRONT of the mainboard find 5 (DAT0) and 6 (GND) as shown in the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bridge these both and while bridging plugin the usb cable - WITHOUT TOUCHING anything with your fingers/body/soul on the mainboard!!!!
Keep thumbs pressed.. it may work if you flashed the correct files, with a matching ARB, in a correct way and [fill-on-on-whoever-u-believe-in] is with you
marzsalim said:
5. Connect sdcard with mobile ? Or sdcard just connect to pc? Please reply to me
Click to expand...
Click to collapse
Like I wrote to FWUL so yes to your PC where FWUL is running
Sent from my LG-H815 using XDA Labs
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
commandervadeo said:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
Click to expand...
Click to collapse
This is happening to me too?
commandervadeo said:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
Click to expand...
Click to collapse
Shepxda said:
This is happening to me too?
Click to expand...
Click to collapse
upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
steadfasterX said:
upload the log after extracting a KDZ:
advanced menu -> Logfile -> upload button -> share the link
Click to expand...
Click to collapse
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
Shepxda said:
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
Click to expand...
Click to collapse
Yes. After this do what I said above. Give me the log.
Sent from my LG-H815 using XDA Labs
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.
On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d
I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
birry said:
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.
On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d
I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
Click to expand...
Click to collapse
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).
This was my reference when I destroyed the phone [emoji14]
https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
birry said:
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).
This was my reference when I destroyed the phone [emoji14]
https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
Click to expand...
Click to collapse
well..omg..
ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.
Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H
download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.
if that fails to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N
I would not recommend to go further then that as u otherwise will increase your ARB for sure.
The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.
Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.
.
I hate to say it but Im here....
LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan
never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM
still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)
I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.
I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.
Im at the logo bootloop with pulsing blue LED.
I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.
I was at v20k IIRC and I know for a fact my ARB was 0.
Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.
Any thoughts on what may have happened?
cheers
ac
steadfasterX said:
well..omg..
ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.
Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H
download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.
if that fails to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N
I would not recommend to go further then that as u otherwise will increase your ARB for sure.
The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.
Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.
.
Click to expand...
Click to collapse
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:
Now I can run it into download mode and I could see that info on SALT:
Device model: LG-H811
Firmware (laf): H81120v
Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0
Carrier: TMO
Country: US
UsU: no
GPT compatibility: H811
LAF protocol: 1000001
AntiRollBack: 3
I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)
Thanks for your great work!
Vishnuisgod said:
I hate to say it but Im here....
LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan
never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM
still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)
I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.
I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.
Im at the logo bootloop with pulsing blue LED.
I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.
I was at v20k IIRC and I know for a fact my ARB was 0.
Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.
Any thoughts on what may have happened?
cheers
ac
Click to expand...
Click to collapse
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.
birry said:
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:
Now I can run it into download mode and I could see that info on SALT:
Device model: LG-H811
Firmware (laf): H81120v
Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0
Carrier: TMO
Country: US
UsU: no
GPT compatibility: H811
LAF protocol: 1000001
AntiRollBack: 3
I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)
Thanks for your great work!
Click to expand...
Click to collapse
You're referring to what TOT? The one containing just the aboot?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.
You're referring to what TOT? The one containing just the aboot?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?
I just would like to patch the bootloop (I prefer to have the four tiny cores enabled instead of just one as it normally does and installing stock Rom).
birry said:
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?
I just would like to patch the bootloop (I prefer to have the four tiny cores enable instead of just one as it normally does and installing stock Rom
Click to expand...
Click to collapse
There are 2 patches available. The one with tot and the boot image one.
The TOT one which is something between 4 and 10 MB contains just the aboot one and disables the cores in the aboot itself.
The boot image one is made in the kernel cmdline
Both have the same effect.
The difference : the TOT aboot fixes it permanently (as long as you don't reflash a kdz/tot again). So you can flash custom ROMs without needing to care about it.
The boot image adjustment instead does not touch your aboot but needs to be done on ever new boot image you want to use.
Sent from my LG-H815 using XDA Labs
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)
Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/
The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
birry said:
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)
Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/
The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
Click to expand...
Click to collapse
Afaik there is none for the h811 and I highly recommend to not use any of the others to avoid bricking your phone again. So it seems you're stuck with modifying boot images
Sent from my LG-H815 using XDA Labs
Ok then, I will try this firmwares: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Consider that ARB is 3, which firmware would be the correct one to use?
Edit: now after a pair of boots it started to get download mode in a random way, sometimes it does and sometimes it does not, could it be because I used a ARB 1 extrated kdz?
[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1
[GUIDE/TUTORIAL/HOWTO] HTC One M7 any version (m7, m7ul, m7spr, m7vzw) stock to Android 11 R / LineageOS 18.1
This detailed step-by-step guide helps you transform your HTC One M7 (any version) to a powerful one with Android 11.
Make sure you have the One M7 model, in Android, go to Settings > About phone and check the model.
CHANGELOG
v8. Upgrade to Android 11, improve readability, update pack
v7. Updated pack with MagiskManager 8.0.7 and Magisk 21.4
v6. Infos in case of Simlock
v5. Moved to Android 10 thanks to @tarkzim, updated pack with Magisk 20.4
v4. Moving to Android 9. I was wrong in v3 ;- Thx @tarkzim), good for all M7 versions
v3. Reverted back to Android 7.1. No stable ROM for Android 8 or 9 (and will never be)
v2. Tutorial updated for Android 8.1 Oreo, updated pack with TWRP 3.3.1-0
v1. Initial release
1) DOWNLOAD
- djibe HTC One M7 pack (44.3 Mo) v2 : http://bit.ly/djibe-onem7-v1
(includes HTC drivers, recovery TWRP 3.6.1_9-0 for all m7 by Xeno1, Magisk Root 23 adb & fastboot.exe).
Unzip the djibe folder from the zip on root folder of C: drive.
- ROM Unofficial Lineage OS 18.1 for M7: https://forum.xda-developers.com/t/rom-11-0-unofficial-m7-all-lineageos-18-1-stable.4454219/
Download latest build for M7 here: https://androidfilehost.com/?w=files&flid=334598&sort_by=date&sort_dir=DESC
+ BitGApps ARM 11 v1.4+: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Charge phone to 100 %
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe -> click on Run as administrator and continue the setup.
Then install HTC_BMP_USB_Driver_x64.msi (or *_x86 if you have a 32bits Windows edition).
### Install doesn't work ? Try these drivers for Win10 : https://htcusbdriver.com/download/htc-usb-driver-v4-02-0-001
Now go to my folder flash, and right click the adb 15seconds installer > Run as administrator.
During install, every time the command asks you a confirmation, enter Y and confirm with Enter.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
Collect all personal photos, videos, etc ... and copy these on PC.
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is not accessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock in 1 zipfile flash, follow this tutorial: https://tcg96.github.io/m7gurureset
3) UNLOCK BOOTLOADER
In Android, go to Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to the About menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Toggle on the USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
### Then navigate to my flash folder (if it is on desktop) with this command :
Code:
cd /d C:\djibe\flash
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT35****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Authorize ADB commands on phone.
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type :
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
Type :
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website : https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, chose HTC One (M7), click Begin unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you : Token Submitted Successfully.
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type :
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return :
Code:
unlock token check successfully
Back to phone, press Volume+ to select "Yes, unlock bootloader", then Power button to confirm flash.
Now wait while phone is going to Factory reset.
Don't let Android restart by holding both Power + Volume- to enter bootloader immediately.
FASTBOOT menu is overlined in red.
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter :
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.1_9-0-m7univ.img
Command returns :
Code:
finished. total time: x.xxxxs
##€ If it fails, tries with a Windows Powershell shell.
Now on phone, press Volume- to select Bootloader, confirm with Power button.
You are back to the booloader screen (UNLOCKED is written on top line), press Volume- to navigate to RECOVERY, and confirm with Power button.
Phone reboots in TWRP recovery.
5) WIPE PARTITIONS
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Go to Wipe > Advanced wipe.
Select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
6) FLASH ROM, GAPPS AND ROOT (OPTIONNAL)
We first have to get our zips on the phone.
Still on TWRP Home screen, tap on Mount > deselect all partitions except Data, then connect phone to PC.
In Windows Explorer, you can see MTP Device, copy the zips of ROM, GApps, Magisk + Magisk Manager right in the Internal Storage folder.
Tap on Disable MTP once copy is finished.
Then back to Home screen, tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> Magisk*.zip,
then Add more Zips -> bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
When completed successfully, tap on Reboot.
Tap on Do not install when TWRP asks for the app install.
Wait during long first boot.
Setup Android.
7) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, LineageOS team, tarkzim, zsoerenm, alray, ., Flyhalf205, icxj1, R1ghtC, gimmeitorilltell, All M7/MSM8960 contributors.
Just my 2 cents
Just my 2 cents if it can help
djibe89 said:
- a microSD card (FAT32 format). Copy the zips of ROM, GApps, addonsu and deviceid*.apk (both in my pack) on the root folder of microSD, then insert it in phone.
Click to expand...
Click to collapse
The M7 is not equipped with a mircoSD card slot, only a virtual /sdcard (symlink to /data/media/0) ... So they'll either have to adb sideload or adb push the files to internal memory which is pointless at this stage since it will be wiped during bootloader unlock. Or drag n drop the files using mtp from twrp once it's installed on the phone.
3 ) UNLOCK BOOTLOADER
[...]
Now wait while phone is going to Factory reset.
Setup Android again on next boot.
4 ) FLASH RECOVERY
Now re-enable USB debugging in Android.
Using the same Windows command prompt, type
Code:
adb reboot bootloader
again.
Click to expand...
Click to collapse
You could save a lot of time just force rebooting to bootloader (power + vol down) right after BL unlock/factory reset are completed so you don't have to setup the system you're going to wipe 2 steps later. USB debug anyway isn't required to fastboot flash recovery so it's not like booting back in system is mandatory before flashing recovery.
:good:
@alray : Thank you so much for help.
I'm lazy with baby waking up every night and did some awful copy-paste.
I correct all these right now.
Thanks.
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
Because you are a senior member you know where to download everything.
But everyone is not like you.
So I tried to compile a ready-to-go pack for the newcomers, like I did for many devices by know.
This allows noobs to profit from custom ROMs and don't keep it esoteric.
Like you say, many downloads are just hacks, so I tried to bundle lowest size safe files.
saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
For the official LOS ROM, tell LOS to store official builds. As they don't do it anymore, we must rely on personnal builds.
A lot of guides out there ? Made extensive search for cracking this phone, never found a step by step one.
Five year old device ? Still so good once unleashed. Custom ROMs are for these devices isn't it ?
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
.:B:. said:
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
Click to expand...
Click to collapse
Thanks for your explanations.
Any trouble following this tutorial guys ? How to enhence it ?
802D device supported?
M.Z.F said:
802D device supported?
Click to expand...
Click to collapse
Hi, no idea, does your model has another model name/code ?
djibe89 said:
Hi, no idea, does your model has another model name/code ?
Click to expand...
Click to collapse
Model name & code like?
PRI Version= 4.22_001
PRL Version = 10012
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Rafay106 said:
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Click to expand...
Click to collapse
All the custom roms mentioned above are NOT for your phone variant.There were almost no development for the 802 branch at the peak of it's popularity and I didn't see anything new for this variant in the past 2 years or so. I wouldn't expect a 7.1 roms for this variant...
Maybe you'll have better luck searching on Asian forums
skovatov said:
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
Click to expand...
Click to collapse
Here you have answer:
https://forum.xda-developers.com/showthread.php?t=2522762
---------- Post added at 05:30 PM ---------- Previous post was at 05:20 PM ----------
Hi.
After installing Android 7.1 Google Pay stop working on my phone. I have torn on NFC communication but terminal don't read my card from app. I don't turn on access to root. Any aidia how to solve this issue?
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Bazooka said:
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Click to expand...
Click to collapse
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
alray said:
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
Click to expand...
Click to collapse
Thanks for that. I tried to go through it nice and slow making sure I understood each step. I got to where I needed to open a command window on the "flash" folder to which I must have powershell(?) installed as it gave me that option. After inputting 'adb devices' it listed a device but stated it was offline. This is where I am stuck as the steps after this do not work.
drivers win10
Hi, I have a basic ask. Do you know where to get Win 10 drivers? I can't run the installer HTCDriver_4.2.0.001 on my Windows 10 (version 1803).
It gives me the error: The driver installer is not supported for your operating system. Thanks for your help.