Off the issue. This thread is to unlock bootloader. Check the threads for that
Sent from my SM-N900V using XDA-Developers mobile app
Sent from my SM-N900V using XDA-Developers mobile app
[WIP] Note Series Developer Edition Conversion
- Thread starter npjohnson
- Start date
Root...
You no longer need to down grade. Root is available through Yemen now for the OF1.
You no longer need to down grade. Root is available through Yemen now for the OF1.
?
i already said i was rooted on of1
guess you missed that part
the only reason to downgrade it to have the kitkat Developer Edition Bootloader
to do that we need root for cid
please rooters root the kitkat
thanks
I don't want to hijack this thread but downgrading and keeping root is easy... Read here... http://forum.xda-developers.com/verizon-galaxy-note-3/help/reboots-lollipop-t3090421
As for Being on 4.4.4, I went back because of battery drain. I tried all the version of Jasmine and the official release. With both, I can never make it longer than 8 hours. On 4.4.4, I can get 4+ hours of screen on time and all day battery.
I'm running a rooted verizon note 3. I'm more than willing to help. I'll run any commands you guys ask.
I'm on 5.0 running JasmineROM_v6.1-LRX21V.N900VVRUEOF1
I have the latest SuperSU installed, BusyBox, Xposed and Flashfire.
I'M READY TO BE FREE
I'm on 5.0 running JasmineROM_v6.1-LRX21V.N900VVRUEOF1
I have the latest SuperSU installed, BusyBox, Xposed and Flashfire.
I'M READY TO BE FREE
ohhh man keeping this bumped. we need this ! I wished I had a dev edition to help out
If you are still looking I might be able to help, PM me.
Note3 pit is different than S5:
CID is in block mmcblk0 CID is something like this (replaced a few numbers with *): 1501004d42473**74300e4f1b***a000
aboot is mmcblk0p6
Read your CID: /sys/block/mmcblk0/device/cid
DevEd note3 dump:
Note3 pit is different than S5:
CID is in block mmcblk0 CID is something like this (replaced a few numbers with *): 1501004d42473**74300e4f1b***a000
aboot is mmcblk0p6
Read your CID: /sys/block/mmcblk0/device/cid
DevEd note3 dump:
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 39533 loop0
7 1 33296 loop1
7 2 6269 loop2
7 3 32256 loop3
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 32 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 10240 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 14336 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 11264 mmcblk0p14
179 15 13312 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 7159 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1 mmcblk0p19
179 20 8 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 9216 mmcblk0p22
179 23 2777088 mmcblk0p23
179 24 1048576 mmcblk0p24
179 25 26521583 mmcblk0p25
179 32 512 mmcblk0rpmb
179 64 62422016 mmcblk1
179 65 62420992 mmcblk1p1
254 0 39532 dm-0
254 1 33295 dm-1
254 2 6268 dm-2
254 3 32256 dm-3
[email protected]:/ #
Code:
/dev/block/platform/msm_sdcc.1/by-name:
lrwxrwxrwx 1 root root 20 Jan 2 18:08 aboot -> /dev/block/mmcblk0p6 <-------aboot
lrwxrwxrwx 1 root root 20 Jan 2 18:08 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 2 18:08 backup -> /dev/block/mmcblk0p17 <-----backup
lrwxrwxrwx 1 root root 21 Jan 2 18:08 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 2 18:08 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 2 18:08 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 2 18:08 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 2 18:08 efs -> /dev/block/mmcblk0p11 <------EFS
lrwxrwxrwx 1 root root 21 Jan 2 18:08 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 2 18:08 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 2 18:08 fsg -> /dev/block/mmcblk0p18 <-----FSG
lrwxrwxrwx 1 root root 20 Jan 2 18:08 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 2 18:08 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 2 18:08 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 2 18:08 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 2 18:08 param -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 2 18:08 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 2 18:08 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 2 18:08 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 Jan 2 18:08 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 2 18:08 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 2 18:08 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 2 18:08 system -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 2 18:08 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 2 18:08 userdata -> /dev/block/mmcblk0p25
#
Last edited:
i read it and it dont mention how to keep root when downgrading from LP 5.0 (OF1) to KK 4.4.4 (NK1 or NJ6)
i might have missed it.
if you could be so kind to provide the exact steps it would be great
thanks
I've got a Note 3 developer device. If this is still a viable option that will work then I'll help out. Just give me directions for how to get what you need. I'm on 4.4 bootloader dev edition. And no I didn't accidently re lock it's still a genuine developer device 4.4 bootloader which means that if this were to work we could boot cm 13 once support is available.
Sent from my SM-N900V using Tapatalk
Last edited:
please keep us updated with any progress if there is any
I'm waiting for someone to tell me what they need and where to send the files to. But no one has responded yet. Try and grab someone's attention so we can get the ball rolling. Anyone that sees this try and help get things moving I can't do anything without further instructions. In other words I'm a noob with a dev edition note 3 so until someone more experienced helps we're still at square one.please keep us updated with any progress if there is any
Try and help if you can get me in touch with the people that need my aboot and I'll email it to them. I'm not sure if it contains sensitive information so I won't post a link to it. However it's on my Google Drive waiting for the right person.
Sent from my SM-N900V using Tapatalk
Last edited:
Npjohnson started this
Sent from my SM-N900V using XDA-Developers mobile app
---------- Post added at 05:43 AM ---------- Previous post was at 05:42 AM ----------
<br />
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.<br />
<br />
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!<br />
<br />
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.<br />
<br />
How does this apply to you?<br />
<br />
The Note 3 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.<br />
<br />
<br />
How can I help this progress?<br />
<br />
I need a few thing to make this work:<br />
<br />
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.<br />
<br />
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command to dump their CID).<br />
<br />
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).<br />
<br />
PLEASE do not post your CID publicly.
Sent from my SM-N900V using XDA-Developers mobile app
---------- Post added at 05:44 AM ---------- Previous post was at 05:43 AM ----------
Thanks alexp. ..
Sent from my SM-N900V using XDA-Developers mobile app
Sent from my SM-N900V using XDA-Developers mobile app
---------- Post added at 05:43 AM ---------- Previous post was at 05:42 AM ----------
All,<br />
<br />
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.<br />
<br />
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!<br />
<br />
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.<br />
<br />
How does this apply to you?<br />
<br />
The Note 3 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.<br />
<br />
<br />
How can I help this progress?<br />
<br />
I need a few thing to make this work:<br />
<br />
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.<br />
<br />
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command to dump their CID).<br />
<br />
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).<br />
<br />
PLEASE do not post your CID publicly.
Sent from my SM-N900V using XDA-Developers mobile app
---------- Post added at 05:44 AM ---------- Previous post was at 05:43 AM ----------
Thanks alexp. ..
Sent from my SM-N900V using XDA-Developers mobile app
I've pm'd him and hangouts messaged him and emailed him but no dice yet. I just don't know what's in these files and if any of it is sensitive so I'm hesitant to post a link directly to it but I'd be more than happy to email it or whatever once he responds to me.
Sent from my SM-N900V using Tapatalk
Last edited:
Hopefully he gets back to you, this would be amazing stuff if a bootloader unlock happened. I'm not holding my breath but crappy noone thought root was going to happen again either.
Sent from my SM-N900V using Tapatalk
All of us thank you for potentially unlocking our Note. We will wait and see ,it is the weekend so lets just hope
Well I gave my aboot and cid to firewaterdevs he said he doesn't have time to work on it today but hopefully in the next couple of days. He checked that my aboot matches my cid which it does.
Now we wait.
Sent from my SM-N900V using Tapatalk
Last edited:
Fantastic. ..your the best my friend. Thanks again
Sent from my SM-N900V using Tapatalk
Sent from my SM-N900V using Tapatalk
I'm glad I found this thread this helps me as well since there's a lack of development due to you guys being locked down. So once we get you guys unlocked it's fun for us all. I really want cm 13 lmfao.
Sent from my SM-N900V using Tapatalk
Yes I would definitely put that on as well. Good I'm glad your in
Sent from my SM-N900V using Tapatalk
Sent from my SM-N900V using Tapatalk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone