Related
for the purpose of dualbooting ParanoidAndroid & Ubuntu using MultiRom.
I read that it is recomended to update your bootloader to at least version 4.13 to avoid potential problems.
I need some basic information about the bootloader that I could not find by "google-ing".
I am currently running:
ParanoidAndroid 4.1.1 & would like to keep it as it is.
bootloader version 3.34
TWRP version 2.4.1.0
My Question is:
If I extract bootloader-grouper-4.18.img from the 4.2.2 Factory Image & flash it to my Nexus 7, will that work?
Will it leave my current installation of ParanoidAndroid as is & be able to boot it? Or will it cause some sort of problem?
thanks in advance
You can update your bootloader with the image that you have extracted without problems. Flash it with fastboot.
Definition of a bootloader
http://m.androidcentral.com/what-is-android-bootloader
http://forum.xda-developers.com/showthread.php?t=2150251
Hey guys,
Its been a very long time since I flashed a rom on my N7. I was busy with the damn uni but now that summer is here I can play with my N7
Let me make this quick, I have unlocked the N7 using the tool kit long time ago and Im not sure if it still exists on my PC
Im currently running - CM10 4.1.2
Modle - GT-I9000
-Bootloader-
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
UNLOCKED
Recovery - i think CMW
Now I want to update to 4.2.2
Can I just flash a ROM with 4.2.2 or I have to do something with bootloader?
And btw just after going to the bootloader today which I didn't see long time ago the N7 didn't boot when I choose start then I held the power button till it rest and it worked but now a random reboot occurred :|
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Westervoort said:
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Click to expand...
Click to collapse
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
mr.dj26 said:
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
Click to expand...
Click to collapse
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Westervoort said:
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Click to expand...
Click to collapse
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
mr.dj26 said:
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
Click to expand...
Click to collapse
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
eddiehk6 said:
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
Click to expand...
Click to collapse
okay m8
thank you all for being very helpful ^^
Great im on 4.18
now ill get in to recovery and erase every thing then ill flash a new recovery and a new rom
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.
i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.
forgot to attach the screenshots
GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Hey,
Download the stock nexus 4 factory image and flash only the system image through fastboot. This will revert your system partition to stock and it will allow the installation of the ota to continue without any loss of user data. You can wait for the next update prompt or you can just download the ota from the ota thread and flash it yourself through TWRP.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
ninjames said:
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Click to expand...
Click to collapse
The update process usually goes through even if you have TWRP.
You can try flashing the stock recovery through fastboot.
Which is the stock Nexus 4 factory image? You mean what it launched with, or do you mean the factor 4.4.2 image since that's what I'm on? Also I'm not sure how to flash through fastboot at this point. Will that remove my custom loader or just remove my root?
You can get the latest factory image from here https://developers.google.com/android/nexus/images
Flashing only the recovery will not remove root. It'll only replace the custom recovery (loader).
Sent from my Nexus 4
---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------
You can follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Flash only the recovery (refer section D, sl no.12 in the above guide)
Sent from my Nexus 4
I don't believe the reason for your OTA failure is a custom recovery, it is most likely a modification to the system partition. You should extract the system partition image from the factory image and flash that through fastboot, which will remove your root but you can get that back by flashing the SuperSU zip. Then after restoring back to a stock /system partition, take your OTA like normal.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
ninjames said:
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
Click to expand...
Click to collapse
So, have you got your adb and fastbooot drivers set up?
Sent from my Nexus 4
I think so, yeah. Sorry for the delay in my posting but I'd really like to get this figured out in advance of 5.0 so I can, you know, use it.
So I mean, I'm willing to wipe everything, go back to stock, whatever I need to do to set myself up for getting all the OTAs all the way to 5.0. I just need a little bit of help with that ... I backed up all my stuff, so.
Why don't you just go ahead and flash android lollipop? Since you've already backed up all your data, you can start afresh.
1. Download the factory image from Google's developer site.
2. Extract the contents to the folder android/SDK/platform tools.
3. Connect your phone via USB, boot into bootloader and check if it is recognized by using a command prompt and using command fastboot devices, it should return a value.
4. Run the file flash-all.bat which you can find from the extract.
5. It'll take care of the rest and you'll be good to go.
But it'll wipe all data and bring it to an out of the box state.
Sent from my Nexus 4
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
ninjames said:
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZK6hYVuKNlw - This one works perfect just replace the file he tells you with
https://dl.google.com/dl/android/aosp/occam-lrx21t-factory-51cee750.tgz < Factory 5.0
Hope this helps
Hit The Thanks if it did
I couldn't really figure out that video .. he was talking about installing APKs and stuff and I didn't know which file from the factory image I was supposed to use? So I extracted it into a directory with the fastboot stuff as per another guide, hit flash all and it said it all worked ... and it did! So ya'll got me started and I stumbled my way to the finish. THANKS SO MUCH!
from this thread/post by Hashcode, to install KK "4.4.2 Stock Root Odex/DeOdex [04/23/14]" by BeansTown106 on dev edition note 3:
I have a dev edition VZW Note 3 still with the 4.3 (JellyBean) bootloader / aboot. Obviously I can't just flash the 4.4 aboot without locking it and turning it into a retail version.
I'm aware of the bootloader unlock using the CID exploit to convert any VZ Note 3 into a dev edition version, however, I'd like to avoid modifying my CID and want to keep it as is.
Apparently, there is this kernel that will let the "older" dev edition to run a 4.4-based rom. The links in the post seem to have expired, or are no longer working now;
"(Goo.im)"
"(Crackflashers)"
I also did a search for that file on google, and nothing useful came up.
With a regular 4.4.2 kernel, my phone just gets stuck at the "Note 3" screen after running the kernel, it won't get to /system, if I use the de-odex rom's kernel from Hashcode, the 4.3 bootloader won't even run the kernel and just freezes. I'd really appreciate it if someone could re-post it with a link here, if they still happen to have that modified 4.4.2 kernel for the dev edition, it is called
flash-vzw-de-4.4-kernel-v1.0.zip
supposedly it also needs this file, but I'm sure it'll still work without it:
flash-tw44-sys-files-fixes-v1.0.zip
If anyone still happens to have these files, I would really appreciate it they could post a link for download.
There is a link for the kernel source in that post, but I'm not really good at compiling my own kernels.
Thanks for any assistance
newuser134 said:
from this thread/post by Hashcode, to install KK "4.4.2 Stock Root Odex/DeOdex [04/23/14]" by BeansTown106 on dev edition note 3:
I have a dev edition VZW Note 3 still with the 4.3 (JellyBean) bootloader / aboot. Obviously I can't just flash the 4.4 aboot without locking it and turning it into a retail version.
I'm aware of the bootloader unlock using the CID exploit to convert any VZ Note 3 into a dev edition version, however, I'd like to avoid modifying my CID and want to keep it as is.
Apparently, there is this kernel that will let the "older" dev edition to run a 4.4-based rom. The links in the post seem to have expired, or are no longer working now;
"(Goo.im)"
"(Crackflashers)"
I also did a search for that file on google, and nothing useful came up.
With a regular 4.4.2 kernel, my phone just gets stuck at the "Note 3" screen after running the kernel, it won't get to /system, if I use the de-odex rom's kernel from Hashcode, the 4.3 bootloader won't even run the kernel and just freezes. I'd really appreciate it if someone could re-post it with a link here, if they still happen to have that modified 4.4.2 kernel for the dev edition, it is called
flash-vzw-de-4.4-kernel-v1.0.zip
supposedly it also needs this file, but I'm sure it'll still work without it:
flash-tw44-sys-files-fixes-v1.0.zip
If anyone still happens to have these files, I would really appreciate it they could post a link for download.
There is a link for the kernel source in that post, but I'm not really good at compiling my own kernels.
Thanks for any assistance
Click to expand...
Click to collapse
Suggest you try to PM hashcode if you haven't already.
For what it's worth... I am running Jasmine 6.1 (based on lollipop OF1) witb the lean kernal and NC4 bootloader. I am not seeing any issues with that combination.
I do have a TWRP backup of the bootloader if that would do you any good.
Sent from my SM-N900V using Tapatalk
donc113 said:
Suggest you try to PM hashcode if you haven't already.
For what it's worth... I am running Jasmine 6.1 (based on lollipop OF1) witb the lean kernal and NC4 bootloader. I am not seeing any issues with that combination.
I do have a TWRP backup of the bootloader if that would do you any good.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your offer to help. I wish that would work. I'm assuming you have a retail version Note 3 that was bootloader unlocked with the CID conversion method, right?
I can always do it that way, but then I will have to change my phone's CID, which is a unique number to the device. That's what converts any retail Note 3 into a dev edition Note 3.
The phone I have came as a dev edition (unlocked bootloader) from the manufacturer. That means it has a bootloader from factory with a signature in it matching my original CID. Obviously that makes it impossible for me to use anybody else's bootloader other than my own, unless I also change my CID to theirs (which defeats the purpose because my phone already has an unlocked bootloader).
My problem is that my bootloader is Android 4.3-based (JellyBean), not 4.4 (KitKat). Any Android version above 4.3 WILL run on the 4.4 bootloader. That's why your Lollipop-based (Android 5.x-based) rom will run on a 4.4 (KitKat)-based bootloader. The bootloader I have is older than KitKat, it's from Android JellyBean (4.3). The version of the bootloader that you have is exactly what I need, but not just from any phone, it would have to be "signed" with the CID from my phone.
You CANNOT backup the bootloader (aboot) with twrp, what you have backed up, is the BOOT partition, boot.img, which is the kernel image or backup. Bootlader is even at a lower level on your phone than kernel, it's the very first thing that runs when you power up your phone, which shows the "Note 3 - Custom" screen while it's booting up. It's what you overwrote when you unlocked your bootloader, if that's what you did. Be very careful that you NEVER overwrite it from what you have now, otherwise you will either lock your phone back, or you will hard brick it.
You can backup your bootloader (or aboot) using either ADB from a pc, or from Terminal Emulator app (if your phone is rooted) with this set of commands:
su <enter>
dd if=dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/aboot.mbn <enter>
Don't type <enter>, that just means you hit enter after typing the command(s).
That set of commands will produce a backup file called "aboot.mbn", which is exactly 2.0 Mb, on the main directory of you external sd card if you need to keep it for later. DO NOT ever try to write to the aboot partition unless you know what you're doing, and DO NOT enter the commands above incorrectly, it could easily hard-brick your phone, it cannot be recovered from that if it gets hard-bricked.
Anyway, what you have backed up with twrp, is boot.img, a backup of the lean kernel you use. It should be stored in your TWRP "BACKUP" folder, along with an MD5 file, they are called boot.emmc.win and boot.emmc.win.md5 depending on your version of twrp, the first file should be between 10 to 12 Mb, the md5 file is under 1Kb, like maybe 48 bytes. Could you get those two files and share them with me, I might be able to use the lean kernel to fix my issue. If you are unable to post a link to share those with me, or link them on this thread to share, could you point me to where you downloaded the lean kernel you use from? You should be able to share those files with dropbox or google drive or something similar.
Thank you again
newuser134 said:
Hi,
Thanks for your offer to help. I wish that would work. I'm assuming you have a retail version Note 3 that was bootloader unlocked with the CID conversion method, right?
I can always do it that way, but then I will have to change my phone's CID, which is a unique number to the device. That's what converts any retail Note 3 into a dev edition Note 3.
The phone I have came as a dev edition (unlocked bootloader) from the manufacturer. That means it has a bootloader from factory with a signature in it matching my original CID. Obviously that makes it impossible for me to use anybody else's bootloader other than my own, unless I also change my CID to theirs (which defeats the purpose because my phone already has an unlocked bootloader).
My problem is that my bootloader is Android 4.3-based (JellyBean), not 4.4 (KitKat). Any Android version above 4.3 WILL run on the 4.4 bootloader. That's why your Lollipop-based (Android 5.x-based) rom will run on a 4.4 (KitKat)-based bootloader. The bootloader I have is older than KitKat, it's from Android JellyBean (4.3). The version of the bootloader that you have is exactly what I need, but not just from any phone, it would have to be "signed" with the CID from my phone.
You CANNOT backup the bootloader (aboot) with twrp, what you have backed up, is the BOOT partition, boot.img, which is the kernel image or backup. Bootlader is even at a lower level on your phone than kernel, it's the very first thing that runs when you power up your phone, which shows the "Note 3 - Custom" screen while it's booting up. It's what you overwrote when you unlocked your bootloader, if that's what you did. Be very careful that you NEVER overwrite it from what you have now, otherwise you will either lock your phone back, or you will hard brick it.
You can backup your bootloader (or aboot) using either ADB from a pc, or from Terminal Emulator app (if your phone is rooted) with this set of commands:
su
dd if=dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/aboot.mbn
Don't type , that just means you hit enter after typing the command(s).
That set of commands will produce a backup file called "aboot.mbn", which is exactly 2.0 Mb, on the main directory of you external sd card if you need to keep it for later. DO NOT ever try to write to the aboot partition unless you know what you're doing, and DO NOT enter the commands above incorrectly, it could easily hard-brick your phone, it cannot be recovered from that if it gets hard-bricked.
Anyway, what you have backed up with twrp, is boot.img, a backup of the lean kernel you use. It should be stored in your TWRP "BACKUP" folder, along with an MD5 file, they are called boot.emmc.win and boot.emmc.win.md5 depending on your version of twrp, the first file should be between 10 to 12 Mb, the md5 file is under 1Kb, like maybe 48 bytes. Could you get those two files and share them with me, I might be able to use the lean kernel to fix my issue. If you are unable to post a link to share those with me, or link them on this thread to share, could you point me to where you downloaded the lean kernel you use from? You should be able to share those files with dropbox or google drive or something similar.
Thank you again
Click to expand...
Click to collapse
Towards the bottom of this post is a link to the lean kernel under dev edition options (part of the Jasmine 6.1 announcement.
http://forum.xda-developers.com/showthread.php?p=62769340
Yes.. On aboot... The code for the exploit is on github under beaups and if you read YOUR cid and then use that and YOUR aboot signature you can redo YOUR cid and signature to re unlock your dev edition.
Read these 2 threads
http://forum.xda-developers.com/showthread.php?t=3359370
http://forum.xda-developers.com/showthread.php?p=66068899
Sent from my SM-N900V using Tapatalk
donc113 said:
Towards the bottom of this post is a link to the lean kernel under dev edition options (part of the Jasmine 6.1 announcement.
http://forum.xda-developers.com/showthread.php?p=62769340
Yes.. On aboot... The code for the exploit is on github under beaups and if you read YOUR cid and then use that and YOUR aboot signature you can redo YOUR cid and signature to re unlock your dev edition.
Read these 2 threads
http://forum.xda-developers.com/showthread.php?t=3359370
http://forum.xda-developers.com/showthread.php?p=66068899
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I'm very grateful that you let me know about the exploit code on how to use your own original CID and maybe sign the new 4.4 bootloader with my own CID. That was very nice to point me in that direction. Looks like I need to do a little research and figure out how to do that.
Now I wonder though that if I upgrade my bootloader to the next version, even if I am able to unlock my dev edition again, if I'll be able to use use JellyBean android with the newer aboot if KitKat or Lollipop don't work out for me?! I am under the impression that once you upgrade your bootloader, you CANNOT roll it back, it blacklists all the older aboot versions. Looks like I also need to figure out if older kernels will run on the newer bootloader, the reverse of what I am having trouble with now, with a newer kernel and older bootloader problem.
newuser134 said:
I'm very grateful that you let me know about the exploit code on how to use your own original CID and maybe sign the new 4.4 bootloader with my own CID. That was very nice to point me in that direction. Looks like I need to do a little research and figure out how to do that.
Now I wonder though that if I upgrade my bootloader to the next version, even if I am able to unlock my dev edition again, if I'll be able to use use JellyBean android with the newer aboot if KitKat or Lollipop don't work out for me?! I am under the impression that once you upgrade your bootloader, you CANNOT roll it back, it blacklists all the older aboot versions. Looks like I also need to figure out if older kernels will run on the newer bootloader, the reverse of what I am having trouble with now, with a newer kernel and older bootloader problem.
Click to expand...
Click to collapse
The original code for an S5 us here:
https://github.com/beaups/SamsungCID?files=1
There's also a Sam_Dunk pdf that explains the exploit.
My SLIGHTLY modified version of beaups code is in the zip located here
http://forum.xda-developers.com/showthread.php?p=66529761
Hopefully you can read and modify C code, I compiled it right on my Note 3 using C4DROID app and its GCC module.
@beaups can probably tell you if the exploit can be used to go backwards on ABOOT
Sent from my SM-N900V using Tapatalk
donc113 said:
The original code for an S5 us here:
https://github.com/beaups/SamsungCID?files=1
There's also a Sam_Dunk pdf that explains the exploit.
My SLIGHTLY modified version of beaups code is in the zip located here
http://forum.xda-developers.com/showthread.php?p=66529761
Hopefully you can read and modify C code, I compiled it right on my Note 3 using C4DROID app and its GCC module.
@beaups can probably tell you if the exploit can be used to go backwards on ABOOT
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thank you
I know enough C to probably figure it out. I'm glad to hear that it is possible to compile code on the phone with an app, I haven't used a PC for years to compile any kind of computer code, it's a lot easier to setup an android phone for that. I will give it a try.
I wasn't able to get stock (or de-odexed) KitKat 4.4.2 to work on the older aboot even with Lean Kernel. I was, however, able to get get the latest version of Jasmine Rom (to which you provided the link to get Lean Kernel from its post ), even though it's even newer than KitKat 4.4.2! As you said, Jasmine Rom 6.1 is Lollipop-based, KitKat 4.4.2 is a lot closer to my own JellyBean aboot (4.3), so if Android 5.0 or 5.1 is working on the old aboot, I don't see why Android 4.4.2 should be able to work?! I know for sure it has something to do with the kernel, I know if I flash the right kernel, it will work. Stupid somewhat-locked bootloader! On older phones with truly unlocked, unsigned bootloaders, once the bootloader handed the chain to the kernel, it would care less if they were "compatible", the kernel would then run and boot into /system. These signed/encrypted bootloaders, along with secure boot being on on the phone, aren't really unlocked even when unlocked, they just enforce slightly less when checking for boot.img or recovery.img signature, they still check for version and compatibility. I've never had an issue with a bootloader version not being compatible with kernel version, the bootloader's purpose is just to load the operating system or kernel. Ever heard of a PC's bios not being compatible with a version of Windows or Linux?!
I confirmed with someone else's dev edition phone that the new aboot (version 4.4) will NOT boot into old Android 4.3 JellyBean, so since downgrading aboot may not be possible, I will hold on upgrading my aboot for now till I figure out more. If Lollipop will work with the older aboot, then KitKat must be able to as well, it's just a question of figuring it out eventually, and getting the right kernel. Maybe I'll have to start learning on how to modify kernels and turn on/off kernel modules.
Thank you for all your help again. I'll get your code and look at it a little later once I figure it out a little more.