yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Azlun:
Do you have plan to support NOTE 4 China N9100 trltechn?

partions are list belows:

adb shell su -c "ls -al /dev/block/platform/msm_sdcc.1/by-name"

lrwxrwxrwx root root 2014-06-22 11:19 aboot -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-06-22 11:19 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-06-22 11:19 boot -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2014-06-22 11:19 cache -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 2014-06-22 11:19 cp2_modem -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2014-06-22 11:19 dbi -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-06-22 11:19 ddr -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2014-06-22 11:19 efs -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-06-22 11:19 fota -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefs1 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefs2 -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefs3 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-06-22 11:19 mdm1m9kefsc -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-06-22 11:19 misc -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2014-06-22 11:19 modem -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-06-22 11:19 pad -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-06-22 11:19 param -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-06-22 11:19 persdata -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 2014-06-22 11:19 persist -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 2014-06-22 11:19 recovery -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2014-06-22 11:19 rpm -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-06-22 11:19 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-06-22 11:19 sbl1bak -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-06-22 11:19 ssd -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2014-06-22 11:19 system -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 2014-06-22 11:19 tz -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-06-22 11:19 userdata -> /dev/block/mmcblk0p27
[Android Q&A, Help & Troubleshooting] mrmark75:
First off I want to say Hsbadr the work you do is pure flipping genius! I want to thank you for all you do for the Android community. This is crazy I can essentially run virtualbox on my phone, how cool is that! So I held out on going to LP from KK until this week. I loaded a clean install of KK then upgraded to Jasmine 5.0 to my stock system and all went well, I even kept root so I did everything right and was happy. I then went and installed busybox , MultiSystem, SU, Terminal, and flashfire. opened up MultiSystem made a copy of my current ROM. After green light went out I chose my created ROM for primary system image. Rebooted phone hit volume up button and after it booted I opened Terminal and issued "MultiSystem status" and it was loop0, I was in the virtual ROM cool. I proceeded to install all my apps and what not. The virtual ROM is running great and battery life is killer almost 2 days on a charge. So after a couple days I decided to boot to the stock ROM so I could load Jasmine 5.1.1 to secondary system image to play with it. When I booted I hit the home key, it appeared to boot to stock ROM but it literally took like 2 hours. First it sat at Samsung splash screen for 45 min then it went to Android is upgrading... optimizing apps X of XXX for another hour. When it finally booted the system was crawling, processes were crashing, and I kept getting out of memory pop up errors. It asks if I want to delete unnecessary files (like 1.6gb of files) and I said OK and it does but keeps coming up saying that it is out of memory, the odd thing is when I look I have 20gb free of 32gb?. The stock ROM is literally unusable and I cant even think of opening MultiSystem app. So I rebooted and hit volume up key to boot to my virtual ROM and I get JasmineROM is upgrading optimizing apps X of XXX, it runs much faster about 10 min. Once I am in virtual ROM everything runs as it should. So the problem I am having is every time I switch form stock to virtual and vice versa it has to optimize the apps and when I am in the stock ROM is unusable because it says its out of memory. Is there a fix for this? is there some commands in Terminal I can run? I hate to Factory reset and start all over again if I don't have to.
[Android Q&A, Help & Troubleshooting] junk007:
I read most of the Q & As... is there potential support for OTG cables/media etc?
[Android Q&A, Help & Troubleshooting] ashmore03:
cloudfone excite 501o

:crying:

please help me with my problems on my cloudfone excite 501o..,

i'd swipe or click the wrong botton and eventually deleted its OS..

i'd try to look for its os here in xda, but couldn't find one.., please, please help me with this..

big thanks and more power..

pardon me,dont know how to post this..
[Android Q&A, Help & Troubleshooting] wanb1i:
Can't load 5.1.1 virtual

I just realized I posted this in the wrong forum, sorry for the double post!:eek:

I have Jasmine 5.0.2 running as Stock on MS. 64gb sdcard setup 40gb fat32/20gb ext4. Copied 5.1.1 to img/system folder, set 5.1.1 as active primary virtual, reboot thru MS to mount 5.1.1, system reboots, but no 5.1.1 love.:(

Any help would be appreciated. :)

Here's Terminal Session :

u0_a251@hltevzw:/ $ su

root@hltevzw:/ # MultiSystem status

/MultiSystem/build.prop: line 22: 5_1_1: command not found

/MultiSystem/build.prop: line 24: 5_1_1: command not found

/MultiSystem/build.prop: line 26: 5_1_1: command not found

--------------------------------------------

MultiSystem for Android

(C) 2014-2015 hsbadr @ xda-developers

Hamada S. Badr <hamada.s.badr@gmail.com>

--------------------------------------------

Current System IMG: Stock

Current System DEV: /dev/block/mmcblk0p23

MultiSystem partition is mounted on /MultiSystem!

Log file: /MultiSystem/log/MultiSystem.log

--------------------------------------------

If you'd like to support my work,

please donate via PayPal or Google to:

Hamada S. Badr <hamada.s.badr@gmail.com>

--------------------------------------------

root@hltevzw:/ #

---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------

I have the same issue, no Red LED during create/copy, so it's difficult to know if it is, in fact, doing anything. It does appear to be copying tho...:confused:
[Android Q&A, Help & Troubleshooting] Sporttster:
All sorts of problems with this thing. I got MultiSystem installed, checked on terminal, showed it there and on stock img. The problem occured when I looked at the stock img area under virtual roms and found about 7 or 8 stock imgs showing. Now, there's only supposed to be one, correct?? Why is there about 7 of em showing??? So I hit the first one under stock after doing the make stock img deal. It showed. I made sure start on reboot was clicked and when it rebooted, it showed the green light so I hit ONLY the up volume, a few times. And the Verizon Note 3 loading screen with that logo wording on it sat there....and sat there....AND sat there, never booting the phone. W T F. So trying to figure out how to fix this and decided to pull the sd card out and reboot. Wala, phone booted up. Put card in, went to Multisystem and turned off start on reboot, turned off virtual image, put the virtual img deal to choose virtual image where it started, and rebooted. Same crap, it will not get past the Verizon Note 3 load screen! So I'm like I'm done with this thing! Took sd card out, again, booted it up and hit 'Uninstall MultiSystem' in the app. Showed a quick SU deal and ....nothing. Sat there and did not uninstall. So I went into applications in settings and hit uninstall and rebooted. The sucker STILL shows a green light and hangs!! WTF is wrong with this?? I can use the phone and the sd card but now the stupid thing hangs when I have to reboot! I even tried reloading MultiSystem from the apk and when I go into Terminal, it says MultiSystem not loaded. So I am going to have to REpartition this sd card again to get this fricking thing off my sd card??? I am DEFINATELY done with this MS crap! One of the worst apps I've seen in quite some time. NO indications of what it's doing. I had the 'no red light' deal too when trying to create a stock img. You just never know what this program is actually doing. And obviously the 'uninstall' button on the app is worthless as it's not doing a darned thing. I'm going to just have to clean my sd card completely, take the multi partition off and forget trying to use a rom and buy a new phone. F this. This locked down BL bs sucks. It's too fricking complicated anymore to get a rom on a phone......
[Android Q&A, Help & Troubleshooting] wanb1i:
OR...

You can just dirty flash 5.1.1 over Jasmine ROM with Flashfire like I did, forget MultiSystem (there's really no other Roms out there anyway), delete the ext4 partition, expand the Fat32 partition & get your entire sdcard back. Be sure to do a battery pull after flashing to prevent a bootloop. ?
[Android Q&A, Help & Troubleshooting] Sporttster:
I'm rooted...will I lose root doing this? Because this might be my only hope of getting a updated ROM on this thing. BTW, how is the radio on 5.11?? Pretty decent? I do not like the one on 4.3 stock. Too darned weak. Another question, is the problem I'm having related to MS still being on the partition I cannot get to? I'm guessing I do have to just clean and expand the sd like you said because I cannot get it off that partition.
[Android Q&A, Help & Troubleshooting] wanb1i:
I didn't lose root, radio is fine no issues. 2 choices, backup fat32 partition & create new fat32 for whole card or delete the ext4 partition & expand the fat32 to the whole card. ?
[Android Q&A, Help & Troubleshooting] Sporttster:
I want to make sure I do this properly. I'm on 4.3 stock.....DL Jasmine 5.11 which IS rooted, flash it using Flashfire WITHOUT having to clean wipe (hence 'dirty flash'), once flashing is done, pull the batt and put back in and reboot and bam....Jas 5.11 rooted. This after having redone the sd card to eliminate the MS partition....correct??
[Android Q&A, Help & Troubleshooting] wanb1i:
So, because you're on 4.3, I'd flash Jasmine ROM 5.0 following the instructions here: http://xdaforums.com/showpost.php?p=60178468&postcount=9684

Then update that to 5.1.1 following instructions from here:http://xdaforums.com/showpost.php?p=61681131&postcount=11196

Lollipop requires a different kernel, so I'm not sure I'd dirty flash it. Sorry, I thought you were already on Jasmine 5.0, my bad. I'd just not worry about MS, too complex right now (IMHO). Don't use xposed without MS tho, could cause bootloop & lose of root.

WAIT!! Hsbadr is releasing Jasmine v6.0 thread says 9/6/15, let me find it & I'll post the link.

Here's V6, which can be CLEAN FLASHED via FlashFire from rooted 4.3!

http://xdaforums.com/showthread.php?t=2760380&page=1178

Post #11774

Check this out then decide which way you want to go.

Let me know the results!
[Android Q&A, Help & Troubleshooting] Sporttster:
Prepping the phone for this today. Wondering if I should DL and use Safestrap to do this? Ideas?
[Android Q&A, Help & Troubleshooting] wanb1i:
Safestrap is not needed, but can be used if you want multiple Roms, but there aren't any that are better than Jasmine. If it were me, I'd follow the version 6 instructions & flash as stock using Flashfire. ?
[Android Q&A, Help & Troubleshooting] wanb1i:
Curious, what was the outcome? ?

If I helped you, please hit the thanks button. ?
[Android Q&A, Help & Troubleshooting] Polarbearking:
Looking for help. I'm on 4.4.2 alliance rom using safestrap. How would I convert to the Jasmin 6.1. And/or convert from safestrap to multi system (if necessary). As you can tell that being I'm on alliance rom, this is my first return, so I'm out of the loop but catch on quick. If someone can point me in the right direction to go from 4.4.2 alliance rom w/safestrap to this sexy Jasmin 6.1, would be more than appreciated. Do I need to convert to multi system and/or what is flashfire and steps to convert to flashfire if necessary? Thanks. I presume I would need to use Odin to update something as well, steps for that please?
[Android Q&A, Help & Troubleshooting] wanb1i:
Here's V6, which can be CLEAN FLASHED via FlashFire from rooted 4.4.x or 4.3!

http://xdaforums.com/show...0380&page=1178

Post #11774

Check this out.

Let me know the results!

I've given up on MultiSystem, too complex... ☺
[Android Q&A, Help & Troubleshooting] Polarbearking:
So it appears as I do have safestrap already, just wipe my current rom, install Jasmin 6.1, then Odin the radio files, wipe again. I don't have to go to Jasmin 2.* to get the 5.0+ I can skip that completely? It doesn't matter that I have alliance rom? Or do I need to go back to Verizon stock firmware?
[Android Q&A, Help & Troubleshooting] wanb1i:
So, follow the directions for the Retail version provided by Hasbdr in the link I gave you. Don't flash anything but V6, the modems etc are for the Developer edition. I'm not sure of 6.1, I have 6.0. I would do 6.0, then add 6.1, unless Hasbdr specifically says you can directly flash 6.1 over 4.4.x like he said for 6.0. Also, I assume you have a Verizon Note 3?
[Android Q&A, Help & Troubleshooting] Polarbearking:
Yes, Verizon note 3. The link you provided does day for retail users to install the partial OF1 radio via odin. I figured I would have to do that since mine are NC4 (kitkat 4.4.2). Would the 6.0/6.1 lollipop work on NC4 radio?
[Android Q&A, Help & Troubleshooting] wanb1i:
Ok, I don't remember flashing the radio, but I do have the OF1 radio installed, so I may have. At any rate, you can't go wrong following Hasbdr's instructions to the letter. ? Be sure to get Flashfire. Google it and you'll find how to get it. ☺
[Android Q&A, Help & Troubleshooting] Polarbearking:
Thumbs up. Thanks. Flashfire. Will look into it. I am due home this weekend. Excited to get updated again. Woohoo.
[Android Q&A, Help & Troubleshooting] wanb1i:
Great, be sure to put in a follow-up post with the results, as it will help others who want to update to this awesome ROM.
[Android Q&A, Help & Troubleshooting] Raj d:
It will work on Micromax Canvas A116?
[Android Q&A, Help & Troubleshooting] wanb1i:
I never heard back from you, how'd it turn out?
[Android Q&A, Help & Troubleshooting] Polarbearking:
Right. Sorry. Lol. I been playing with the new rom and love it. So here is what I recommend and what I did which are two different things lol.

What I did:

I thought (learned later otherwise) I had to upgrade to lollipop before going to Jasmin 6.1. So I followed Jasmin 5.0 instructions to upgrade that first from 4.4.2 alliance rom. So I used safestrap and flashed Jasmin 5.0 after wiping the stock slot in the safestrap ui. But I also flashed Jasmin 5.0.2 the very next step before rebooting into download mode and flashing OBE radio via Odin. (so I downloaded Jasmin 5.0&5.0.2 in one shot and put them on my internal storage and flashed them both then went to download mode.

My next step now that I lost safestrap (again see recommended step) was wanting to get Jasmin 6.1 and OF1 radio. But again I lost safestrap so after some confusion in the lack of info on skipping what I did. I just went ahead and downloaded flashfire I believe 0.24 and downloaded Jasmin 6.1 and placed it in my internal storage. Then I followed this guide (https://youtu.be/UkiKh_M67Bo) in using flashfire to flash Jasmin 6.1 then in flashfire before flashing selected to reboot into download mode so I could then flash the OF1 radio file via Odin that is in the Jasmin 6.1 instructions. That's my steps.

My recommendation:

I realized after those steps above I did a lot of unnecessary stuff. So from alliance rom 4.4.2. All you have to do is go into safestrap, wipe the stock slot (of course back up everything as this is reformatting everything) flash/install Jasmin 6.1 on the stock rom, reboot into download mode, flash the OF1 radio from the 6.1 instructions via Odin, reboot into recovery, use the volume buttons to select wipe/factory default and that's it. It will reboot you will now have Jasmin 6.1 with the new radio.

Note: the first time booting normal after installing Jasmin 6.1 did take like 15 min to finally get to setup wizard (ok, felt like 15 min, probably more realistically 8 min.) the entire time booting the 4 icon animation smoothly continued doing its animation until the setup wizard showed.

Note: The steps of doing Jasmin 5.0/5.0.2 is not necessary (realized after already doing it)

Note: doing this you will lose safestrap, as it's no longer supported beyond 4.4.2 but you have flashfire that has taken over the function of safestrap. And yes Jasmin 6.1 is still rooted.

Note: I did attempt to install multi system and followed the guide to the letter, never could get it functioning on my Verizon note 3.

I love the Jasmin 6.1 undoubtly.
[Android Q&A, Help & Troubleshooting] wanb1i:
Great! Sorry you did so much extra work, but it's a good learning experience, lol.

Yup, I agree, luv the ROM!

Hoping MS V2 makes the loading of different ROMs easier. ?
[Android Q&A, Help & Troubleshooting] hiroller173:
I was running 6.1 successfully since it came out, but I blew up my system when I tried to do a manual re-install of SuperSU.

The only ROM that would boot was 5.0.2 stock. When I tried to boot into 6.1 it locked up on the initial splash screen.

I completely cleaned and reformatted my SD card and reinstalled Multisystem. I got my first 6.1 boot and it was downloading programs. While it was doing that I went into Terminal Emulator to enable toggles. The phone immediately rebooted into stock. Now, no matter how I try - putting 6.1 into the primary or the secondary, doing Multisystem or manual reboots, it only goes to the stock rom. The green light comes on but It appears to be ignoring the volume buttons.

I read where someone mentioned flashing the partial firmware, but I'm not sure where to find it. My baseband version is already N900VVRUEOB6, and the instructions I've seen have this being installed in the initial switchover to JasmineROM.

I've been working on this sucker for two days (at one point I think I was working with a bad SD card) and could really use a suggestion.

TIA.
[Android Q&A, Help & Troubleshooting] Polarbearking:
If your still rooted and assuming you are talking Verizon note 3. A few previous post you will see a link I pasted to YouTube. That link is a walk through on the note 3 using flashfire to upgrade to Jasmin 5.0.2. So I would use flashfire v. 0.24 apk and install the Jasmin rom you want (I did the YouTube just used Jasmin 6.1 instead as that's what I wanted and I flashed the OF1 partial radio via Odin (you can use flashfire to do this but I didnt) of1 is the newest radio. Here is the of1 partial https://www.androidfilehost.com/?fid=24052804347806843

Before doing any of this wipe/factory rest and reformat your SD card via phone menu and do not use multi system until you are up and running again if you really want Multi system.

OB6 radio partial if you really want it. https://www.androidfilehost.com/?fid=95916177934556418

That's my recommendation.
[Android Q&A, Help & Troubleshooting] hiroller173:
Correct about this being a Verizon Note 3 (retail).

I may not have explained myself very well. I have been on MultiSystem from the first open release. 5.0.2 is my base, installed on the phone. I placed 6.1 in the MultiSystem directory (img/system), executed the various commands in terminal emulator and it showed up just fine as an option for installing into the primary or secondary slot. When I first rebooted using MultiSystem's reboot into virtual option, it worked exactly as expected. I did the factory reset, and 6.1 booted up. I initiated the startup and programs began restoring. I reinstalled Multisystem and updated configurations. However, when it rebooted after installing toggles, it rebooted back into the 5.0.2 and will not reboot into any of the Multisystem roms, either by the MS reboot options or using the volume buttons. I used terminal emulator to see that everything was where it belonged, and it all looks good. But no matter what I do, it will only reboot into the 5.0.2 stock rom on the phone.

I just received a new SD card and will try the process again. If that doesn't work, I'll probably go ahead and install 6.1 to stock. I like the MultiSystem philosophy I just wish I could get it to work again.

Thanks.
[Android Q&A, Help & Troubleshooting] hiroller173:
Had similar problems with the new sd card so I opted to go with 6.1 as stock. Worked great - thanks for the help. Only possible issue is that SE for Android status is Enforcing. Haven't run into any problems because of it (yet) but maybe I will (?) Is there some easy way to fix that?

Thanks again.
[Android Q&A, Help & Troubleshooting] Polarbearking:
I don't know what android enforcing is? My previous tip/instructions was given under the impression you did not have a working phone. Was trying to help. I personally don't use multi system as I had problems with it and SD cards. Seems like your up and running at least.
[Android Q&A, Help & Troubleshooting] satyamtg:
Is Multi system stable?????

Does it require any special kernel tweaks
[Android Q&A, Help & Troubleshooting] DhruvalJ:
What is Multi Rom extly to choice and boot rom on bootUp...

I want mod to choice multiple rom in one device as a same time we can use ext sd card nd internal sd card for porting rom...
[Android Q&A, Help & Troubleshooting] Polarbearking:
Xda is not the only ones that do roms. So multi system let's you store multiple roms and you choose which one to boot into. I think it needs to be the same firmware (if your phone is set for lollipop, then you can only use lollipop roms.) As a example. You have Jasmin 6.0 and Jasmin 6.1 (these two are marshmallow not lollipop, but just an example) Multi system let's you swap between those (obviously no reason to swap between those two, but I used them as I do not know any other devs still making roms for note 3 besides hasbdr, but I'm sure other sites do, like cynogen mod is compabitible with most phones. So you boot into cynogen rom if you choose to reboot your phone the next day, you can go to Jasmin, so basically if you find enough roms you can have new software for everyday of the week. But some feel the protection it provides from losing root is worth it. But I never could get it working nor feel the need to use different roms. Let alone each rom is usually minimum 1.5gb. So if you have 7 roms, that's a lot of used space. Pointless I think. But that should answer your question.
[Android Q&A, Help & Troubleshooting] stk23452:
Quickly distinguish between images.

I got my retail Verizon Note 3 flashed to the latest Jasmine 6.1. I then installed MultiSystem and set my primary virtual image to Jasmine 6.1 as well. I am using MultiSystem mostly to protect my root so I'm not worried about trying to test out multiple roms on the same phone. However, it would be nice if there was a better way than terminal commands to distinguish which image I was in at a given time. My biggest fear is that I accidentally boot into the stock image without realizing it, forget to check the status in terminal, and then mess something up that forces me to flash the stock rom and lose root forever. I originally thought simply setting a different wallpaper would be enough for me to instantly know which image I am on however I now realize that the 2 images share everything not system related (including wallpapers and desktop layouts).

Did anyone implement any kind of visual "flag" to distinguish between images that will always remain different between images?
[Android Q&A, Help & Troubleshooting] bnwg:
As far as I understand as long as the device is booted into img (/block/loop) not stock it is safe to flash any flashable zip even a zip ROM.

I would like to confirm this before I would flash another ROM.

Thanks.