May be a dumb question, but can I flash a flo rom on my Deb N7? I've looked and can't seem to find an answer. Thanks guys
KingVeto said:
May be a dumb question, but can I flash a flo rom on my Deb N7? I've looked and can't seem to find an answer. Thanks guys
Click to expand...
Click to collapse
Short answer: No
Long answer: Most likely the ROM won't boot, and if it flashes a radio it *might* soft-brick
WELL. Haha, I guess that's my answer haha. I got spoiled being able to just edit the Updater script or flash a kernel on other devices. Thanks man.
KingVeto said:
May be a dumb question, but can I flash a flo rom on my Deb N7? I've looked and can't seem to find an answer. Thanks guys
Click to expand...
Click to collapse
Others have reported that you can flash a flo ROM on a deb. You will not have data access though, so it doesn't make much sense to do that.
As always, YMMV.
meekrawb said:
Others have reported that you can flash a flo ROM on a deb. You will not have data access though, so it doesn't make much sense to do that.
As always, YMMV.
Click to expand...
Click to collapse
This seems to be the situation most of the time. The ROM 's will flash but anything extra on Deb that's not on the Flo will not function is data. Which as stated defeats the purpose of having Deb.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
I'm not really concerned with the data being available, but I'm not familiar enough with the device to chance bricking it by flashing an incompatible ROM...so I guess I'll stick to deb-specific builds for now.
KingVeto said:
I'm not really concerned with the data being available, but I'm not familiar enough with the device to chance bricking it by flashing an incompatible ROM...so I guess I'll stick to deb-specific builds for now.
Click to expand...
Click to collapse
It won't boot.
Believe me, I've tried. A lot.
Sent from my Nexus 7 using Tapatalk
Related
hi just wanna ask how do i root my stock 4.0.4 . i want to flash a custom rom. noob here. thanks for the response. coz' when i search in google a lot of different procedure comes up.
please follow this guide: http://forum.xda-developers.com/showthread.php?t=1529058
dont use the toolkit.
just a stupid question. am i gonna follow the first post only?
post 1 is unlocking the bootloader/and getting root
post 2 is flashing a custom rom.
thanks. i'll read it and hopefully i have the courage to apply it. )
just to confirm. this is good for any software version? i have 4.0.4.
I believe so. It's what I did to unlock my 4.0.4 Sprint Galaxy Nexus.
whatthefish said:
just to confirm. this is good for any software version? i have 4.0.4.
Click to expand...
Click to collapse
yes. version doesnt matter.
the only thing that matters is you pick the right recovery.
thank you guys, for helping me. really appreciate it.
Zepius said:
please follow this guide: http://forum.xda-developers.com/showthread.php?t=1529058
dont use the toolkit.
Click to expand...
Click to collapse
Why is it that people recommend against the toolkit? Is there a problem with it or do you just think it's better to do it manually and learn while your are doing it?
Sent from my Galaxy Nexus using XDA
chrikenn said:
Why is it that people recommend against the toolkit? Is there a problem with it or do you just think it's better to do it manually and learn while your are doing it?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
i think they want me to do it manually and learn as a newbie. )
chrikenn said:
Why is it that people recommend against the toolkit? Is there a problem with it or do you just think it's better to do it manually and learn while your are doing it?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Knowledge ftw.
Knowledge.
AND...a big part of it for me...
Is getting ADB/Fastbooot set up...so that we know it's working.
That way...if they come in one day with something wrong:
They:
A) Know what I'm asking them to do.
B) Know that everything is set up correctly...and we don't have to diagnose driver problems and such while the phone is bricked.
If a phone won't boot and all that noise...
ADB/Fastboot might not be working.
But if the user never GOT ADB/Fastboot working to begin with...we'll never know if they did it right or if the phone is simply in that bad of shape.
OP:
What I said sounds scary.
Just do ONE thing...never flash the stock .img's through fastboot that aren't for your device. (Radios/Bootloaders) Flashing the wrong recovery isn't going to brick you...you just won't have a recovery.
That is the big one that seems to get people into hard (or relatively hard) bricked situations.
And you'll be fine.
chrikenn said:
Why is it that people recommend against the toolkit? Is there a problem with it or do you just think it's better to do it manually and learn while your are doing it?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
There is nothing wrong with using a toolkit, IFF you already know what is actually happening when using the toolkit.
I like to think of it this way: in school, they don't let you use a calculator until they teach you how to do arithmatic. Why do you think that is? Because you would never learn to add and subtract.
It's the same issue with a toolkit. It you don't do things manually first, you will never learn...
Sent from my Galaxy Nexus using Tapatalk 2
thanks for the help guys. now im unlocked and rooted. and running AOKP b37 + franco kernel m3.
planning to switch to paranoid android. and comments about the rom? and what is the best partner kernel with the rom when it comes to battery life?
whatthefish said:
thanks for the help guys. now im unlocked and rooted. and running AOKP b37 + franco kernel m3.
planning to switch to paranoid android. and comments about the rom? and what is the best partner kernel with the rom when it comes to battery life?
Click to expand...
Click to collapse
Way to go, one day isn't bad.
My first rooting experience on my Revolution took numerous attempts.
chrikenn said:
Why is it that people recommend against the toolkit? Is there a problem with it or do you just think it's better to do it manually and learn while your are doing it?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
the toolkit works fine, but if he has no idea what he is doing and just blindly goes with what it says and stuff breaks, he has no idea how to fix it.
i would rather him understand what he did so if he has issues, we can help him get everything back in order and he will understand what we are asking him to do.
whatthefish said:
thanks for the help guys. now im unlocked and rooted. and running AOKP b37 + franco kernel m3.
planning to switch to paranoid android. and comments about the rom? and what is the best partner kernel with the rom when it comes to battery life?
Click to expand...
Click to collapse
good job adobostarfish
thephantom said:
good job adobostarfish
Click to expand...
Click to collapse
aw i think i know you.
whatthefish said:
aw i think i know you.
Click to expand...
Click to collapse
Hahaha. Now you know why i'm also a fastboot guy
Sent from my Galaxy Nexus using Tapatalk 2
NOTE: DO NOT FLASH THIS TO YOUR PHONE> IT WILL HARD BRICK!
this is for any dev that wants to try and port android jellybean to the s3 Tmobile version. they already ported it to the internationl version so i think that might make it a little easier. here is the OP in the international section: http://forum.xda-developers.com/showthread.php?t=1737449
fcortes626 said:
NOTE: DO NOT FLASH THIS TO YOUR PHONE> IT WILL HARD BRICK!
this is for any dev that wants to try and port android jellybean to the s3 Tmobile version. they already ported it to the internationl version so i think that might make it a little easier. here is the OP in the international section: http://forum.xda-developers.com/showthread.php?t=1737449
Click to expand...
Click to collapse
Hmmm...
Wonder if we could take that ROM, change the updater-script to match our mounting points....then we just need a kernel....
Which we have one kernel already made. Not sure if it would work though.
If anyone would help set up a build environment that would work for our kernels and roms then I will gladly help and start learning.
Sent from my SGH-T999 using Tapatalk 2
brfield said:
Which we have one kernel already made. Not sure if it would work though.
If anyone would help set up a build environment that would work for our kernels and roms then I will gladly help and start learning.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I think we'd need a stock CM9 based kernel though. If I understand correctly.
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
Well, it shouldn't take too long. It may be possible to build a CM9 Kernel for our phones using parts of the stock kernel that we have access to.
Once the JB source is released, an S3 port might actually be viable. Otherwise it's essentially just flashing a gnex image and praying something/anything works.
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
a CM9 kernel shouldn't be needed, just a modded kernel for our specific phone from what i believe.
We know this, but it's more of an experiment. Also, it helps work out anything we may need to do early on with the modules and drivers
Sent from my SGH-T999 using Tapatalk 2
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
uoY_redruM said:
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
Click to expand...
Click to collapse
It could, in theory. But we would need to work on the modules for anything to work. Could you post our mount points?
why does it have to be a cm9 kernel?
to be completely honest, as soon as we get a cm9 alpha, we will see some worth while stuff! but until then. TouchWiz it iz. We will have team kang's AOKP in no time im sure. i cant wait to see wuts to come. especially since this phone is at all the major carriers and they are all basically exactly the same! should be epic.
Radsolutionz said:
to be completely honest, as soon as we get a cm9 alpha, we will see some worth while stuff! but until then. TouchWiz it iz. We will have team kang's AOKP in no time im sure. i cant wait to see wuts to come. especially since this phone is at all the major carriers and they are all basically exactly the same! should be epic.
Click to expand...
Click to collapse
yea i think once one of the other major carriers (or ares) get cm9 then we will see some awesome stuff for everyones phone!
I think that the only thing that makes them different is the radios in the phone
uoY_redruM said:
Hmmm...
Wonder if we could take that ROM, change the updater-script to match our mounting points....then we just need a kernel....
Click to expand...
Click to collapse
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
uoY_redruM said:
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
Click to expand...
Click to collapse
If aosp was that easy we would all be doing it but no... way more complex than that....
im on my phone. expect terrible typos.
howtomen said:
If aosp was that easy we would all be doing it but no... way more complex than that....
im on my phone. expect terrible typos.
Click to expand...
Click to collapse
Wishful thinking I suppose
in another note i found a mini tutorial on how to port it to other devices if anyone wants to try it here is the guide. it is an SDK port. note: i did not write this guide i am just posting a link to the authors op. you can thank him and/or donate to him. here isorum.xda-developers.com/showpost.php?p=28020178&postcount=36 the link:
fcortes626 said:
in another note i found a mini tutorial on how to port it to other devices if anyone wants to try it here is the guide. it is an SDK port. note: i did not write this guide i am just posting a link to the authors op. you can thank him and/or donate to him. here isorum.xda-developers.com/showpost.php?p=28020178&postcount=36 the link:
Click to expand...
Click to collapse
Link is broken, im not meaning to be a lazy pest.
sswb27 said:
Link is broken, im not meaning to be a lazy pest.
Click to expand...
Click to collapse
sorry about that :silly:
here you go: http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
fcortes626 said:
sorry about that :silly:
here you go: http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
Click to expand...
Click to collapse
i also have a deodexed system dump of jb if you want it let me know.
Source is out
Sent from my Galaxy Nexus using Tapatalk 2
I want to install Fancy Kernal, i am running CM 10.1 right now. Can anyone tell me how to do this, (do i need to format all my data and start fresh or can i just wipe cash or dalvik cash.) If anyone acct. uses it- is it a good idea to switch?
Thanks
Firstly. Wrong section you've posted this. Secondly the instructions are given on the kernels page. Third? It's kernel not kernal, and it's cache, not cash.
Kernels are flash in CWM/TWRP and use, they're straightforward.
Sent from my Nexus 4 using Tapatalk 4 Beta
Misledz said:
Firstly. Wrong section you've posted this. Secondly the instructions are given on the kernels page. Third? It's kernel not kernal, and it's cache, not cash.
Kernels are flash in CWM/TWRP and use, they're straightforward.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
aight relax, its my first post and im tired lol. so i can just flash the zip ontop of CM
aviman123 said:
aight relax, its my first post and im tired lol. so i can just flash the zip ontop of CM
Click to expand...
Click to collapse
I am relaxed if anything. Because the higher ups may either just write this off as 'please use the search function' or answers already given on thread and have this locked.
like I said you need to read the thread, there are alot of things you need to consider. For one you're using Verizon, officially you don't have 4.2.2 or 4. 3 but thanks to cm or muzzy you have 4.3/4.2.2, you can't just flash off without knowing what your firmware is. 4.2.2 or 4.3, it will work for 4.2 just not 4.3
Sent from my Nexus 4 using Tapatalk 4 Beta
Misledz said:
I am relaxed if anything. Because the higher ups may either just write this off as 'please use the search function' or answers already given on thread and have this locked.
like I said you need to read the thread, there are alot of things you need to consider. For one you're using Verizon, officially you don't have 4.2.2 or 4. 3 but thanks to cm or muzzy you have 4.3/4.2.2, you can't just flash off without knowing what your firmware is. 4.2.2 or 4.3, it will work for 4.2 just not 4.3
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for answering, i know what your talking about. And ya i have 4.2.2, so what would you advise me to do.
aviman123 said:
Thank you for answering, i know what your talking about. And ya i have 4.2.2, so what would you advise me to do.
Click to expand...
Click to collapse
Well cm and regular roms usually have different ramdisks. Unless the kernel is universal. If I were you just flash the latest fancy, then boot up. If It loads fine, all and well but if it fails and loops you, just boot into recovery and flash CM again on top. That should save you if you get stuck.
Sent from my Nexus 4 using Tapatalk 4 Beta
Misledz said:
Well cm and regular roms usually have different ramdisks. Unless the kernel is universal. If I were you just flash the latest fancy, then boot up. If It loads fine, all and well but if it fails and loops you, just boot into recovery and flash CM again on top. That should save you if you get stuck.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
kk will do thanks
I really like the ability to use the HTC logo as a button, but the only way i know how to do this is the slim bean rom. So my question is, anyway to get this function on a sense based rom? All info would be greatly appreciated. thanks
delete
Androcles said:
there are many kernels for htc one... check the links below.
http://forum.xda-developers.com/showthread.php?t=2249774
http://forum.xda-developers.com/showthread.php?t=2307371
http://forum.xda-developers.com/showthread.php?t=2255900
Click to expand...
Click to collapse
Woah there!!!!!
OP DO NOT FLASH THOSE KERNELS!
You could brick!
Never flash anything that was not made specifically for your device. If you bother to read the first post in most of those threads they specifically say that Verizon and sprint are not supported.
Please do not post links to potential harmful threads.
We will have custom kernels as soon as HTC releases kernel source for our device. If you can't wait that long then a few of the AOSP ROMs have the HTC logo working as a button.
definitly not flashing any of those haha.
but thank you both for the responses
I'm sorry. didn't notice that. I flashed the aosp one on mine...work pretty well.
Androcles said:
I'm sorry. didn't notice that. I flashed the aosp one on mine...work pretty well.
Click to expand...
Click to collapse
Thanks for editing your post.
None of those kernels were made for our device and could potentially break stuff now that we are s-off.
GrayTheWolf said:
Thanks for editing your post.
None of those kernels were made for our device and could potentially break stuff now that we are s-off.
Click to expand...
Click to collapse
The aosp one works well.
Androcles said:
The aosp one works well.
Click to expand...
Click to collapse
How were you able to run a kernel made for a different variation?
Sent from my HTC6500LVW using Tapatalk
refreblast said:
How were you able to run a kernel made for a different variation?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
flashed it month ago. no any problem. just flash it. i don't know about the google edition and sense, but aosp works
http://forum.xda-developers.com/showthread.php?t=2236121
That is the kernel I using on cm10.2. of course, I'm on verizon.
VanirAOSP uses a custom kernel that allows the HTC Logo to be used as a sleep/wake button.
Hi all,
I'm trying to install Xposed on cataclysm from. I flash the zip file, but after optimization of applications I have a force close of the UI system app. Then I need to uninstall the framework in order to restore the system. Anyone have some suggestions? Any other ROM like cataclysm with Xposed already in?
Thanks all
I know it's not an answer to your question, but I'd advise against using a ROM that's been discontinued half a year ago. Though Cataclysm was a great ROM i moved on to Pure Nexus myself. Works great with Xposed.
peltus said:
I know it's not an answer to your question, but I'd advise against using a ROM that's been discontinued half a year ago. Though Cataclysm was a great ROM i moved on to Pure Nexus myself. Works great with Xposed.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried to install it but has some problem with the root. I flashed the zip of SuperSU but it start to boot loop. For that I turned back to cataclysm. I will wait of someone has some ideas... In case I will install pure and try again!
pacioc193 said:
Thanks for the suggestion. I tried to install it but has some problem with the root. I flashed the zip of SuperSU but it start to boot loop. For that I turned back to cataclysm. I will wait of someone has some ideas... In case I will install pure and try again!
Click to expand...
Click to collapse
You're doing something wrong.
Are you using the correct Xposed? Version 86? X64?
Are you on the latest Pure Nexus and latest Vendor img?
Are you using latest SU? 2.76 ?
If you're saying you are having bootloops with Cataclysm, I and everyone else will not help you. That ROM is dead, it cannot be compatible with anything current.
thenessus said:
You're doing something wrong.
Are you using the correct Xposed? Version 86? X64?
Are you on the latest Pure Nexus and latest Vendor img?
Click to expand...
Click to collapse
My problem is root the system. And yes I'm using the right Xposed in cataclysm.
OK, read my comment again, I edited it a bit.
I advise no one here to assist you as far as Cataclysm goes, sorry.
thenessus said:
OK, read my comment again, I edited it a bit.
I advise no one here to assist you as fast as Cataclysm goes, sorry.
Click to expand...
Click to collapse
The suggestion is use a different ROM right? Have pure Nexus smart radio?
pacioc193 said:
The suggestion is use a different ROM right? Have pure Nexus smart radio?
Click to expand...
Click to collapse
Don't know, haven't used that feature ever on any ROM.
I think Gravitybox has it though? not sure.
Anyway, yeah, just use a different one, that is currently supported. Otherwise it's impossible to pin-point a ROM-SuperSu conflict.
pacioc193 said:
The suggestion is use a different ROM right? Have pure Nexus smart radio?
Click to expand...
Click to collapse
No, but GravityBox has.
I'm using a combination, which you can see in my signature and it works perfectly.
pacioc193 said:
Thanks for the suggestion. I tried to install it but has some problem with the root. I flashed the zip of SuperSU but it start to boot loop. For that I turned back to cataclysm. I will wait of someone has some ideas... In case I will install pure and try again!
Click to expand...
Click to collapse
Some people reported bootloops when flashing in the wrong order. If you clean flash pure Nexus and stick to the flashing instruction there should not be a problem.