Related
Hi there.
I tried downgrading my 2.3.4 xperia neo to 2.3.2 to root it. It worked, but I have the battery problem and I've heard it's a common issue.
I tried removing the battery for more than 10 min and reinserting it.
I tried upgrading to the latest official ICS with PC companion (strangely enough I could upgrade from 2.3.2 although it showed no new upgrades while in 2.3.4). Didn't solve the problem.
I tried flashing a the stock 2.3.4 rom. Didn't solve the problem.
I found following two threads:
http://forum.xda-developers.com/showthread.php?t=1312398
http://forum.xda-developers.com/showthread.php?t=1510703
Unfortunatly, both of these workarounds require an unlocked bootloader. The problem is, I don't seem to be able to connect my phone to the PC in this unlock bootloader mode, maybe because as soon as I remove the USB cable it thinks it has no battery left and turns all systems off?
I also found this thread for locked bootloaders, but only applicable for the arc: http://forum.xda-developers.com/showthread.php?t=1465702
Is there something like this for the neo? If not is it easy to make?
To summarize, I can flash new roms, but I'm not able to unlock my bootloader. Is there something I could do? Thanks in advance for your help
charge your phone to 100%
take out sim card and memory card .highly recommend to format your card
flash phone using suse or flashtools
and when done replace sim and memory card
then everything is clean
works a treat i have amazing battery life on ics 4.0.4
@OP: Have you try to unlock bootloader wit unofficial way? With s1tool? Check neo v development section for more info.
jasonvoor said:
charge your phone to 100%
take out sim card and memory card .highly recommend to format your card
flash phone using suse or flashtools
and when done replace sim and memory card
Click to expand...
Click to collapse
Have you even read his post?
He already tried flashing.
Which wont help him, because he have 0% problem, because he flashed 2.3.2.
If you don't know about that bug, google a bit.
Madfysh said:
@OP: Have you try to unlock bootloader wit unofficial way? With s1tool? Check neo v development section for more info.
Click to expand...
Click to collapse
Thanks, I'm not sure I like this method, but as it's my only choice at the moment I will try it out, as soon as I can get my hand on the needed materials.
In the meantime, is there any chance somebody could make an locked bootloader workaround like this for the xperia neo? http://forum.xda-developers.com/showthread.php?t=1465702
How much programming skills does it require?
It seems to be the easiest method. I just need my phone to realise it's charged for a few hours, until I can unlock the bootloader and install one of the custom roms workarounds
Thanks again for your quick replies
That kernel module would need to be compiled against whatever kernel you have installed. Chances are it may work 42.
But if you're going to unlock anyway, it's pointless. It's kernels that support the workaround not roms. S1tool works even with the battery out, therefore unlocking is the better option.
There's good tutorials here for unlocking, once done insert battery and leave connected to s1tool, some power will reach the battery, flash your custom kernel of choice.
Sent from my MT11i using XDA
Thanks a lot, I found and followed this guide http://androidflip.com/unlock-xperia-phones-bootloader-without-losing-drm-data-track-id-working/ (bad english, but pretty detailed) and now my bootloader is unlocked.
Unfortunatly, I have a pretty noobish question now: where should the boot.img be stored to upgrade the kernel with s1tool? I tried the s1tool file or the SDcard of the phone, but I just get this message:
Selecct firmware packages
You can select few packages with CTRL button
without any option to actually select anything? Am I doing something wrong? (I decided to take the patched stock kernel v9.6 from this thread http://forum.xda-developers.com/showthread.php?t=1468043)
Until now I've flashed the roms using flashtool and .ftf images. Is it possible to do something similar now? (I'd like to use the patched Cyanogen mod, but in my limited understanding you need to flash the kernel first)
Once your bootloader is unlocked, use flashtool to flash kernel.
Click the lightening symbol, select fastboot mode select kernel to flash.
One more thing, not all kernels match all roms, however most of them have the battery patch, for cm7/9 you need to use the fxp kernel. 9.6 nightelf is for gingerbread.
Sent from my MT11i using XDA
For kernel installation, read this: http://forum.xda-developers.com/showpost.php?p=20649481&postcount=3
EDIT: damn, I really need to start refreshing threads before replying
mpiekp was faster
I think I need a clarification: if you need to flash a new rom you hold the back-button while plugging the USB-cable and see a green LED, if you need to flash a new kernel or unlock the bootloader you hold the menu button and see a blue LED?
Because my problem is that I the green LED part works (for example when I flashed my stock 2.3.4 rom), but I when I hold the menu button and plug the USB cable nothing happens (after a while it shows the red LED for charging I think). ThatI was my problem when I wanted to unlock the bootloader the official way and now I see you have to do the same to flash a new kernel
EDIT: According to the thread you kindly provided
EDIT2: Never mind, I think this time it works. Wish me luck
Thanks a lot, you've both been very helpful
It seems to work just fine right now
Help
I have the same problem, pleas help me, tell me what steps did you followed to get the phone working back.
Thanks.
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
hey guys, im new here.. I have a problem with my sony, I installed a custom ROM and i wanted to return to stock ROM after flashing a stock rom my phone somehow bricked and not even turning on. Im not able to put it on flashmod or fastboot mod it keeps disconnecting when trying to connect it to my PC.. i tried charging my phone a whole day all I see is red LED blinking..
plz help me guys I dont know what to do
You haven't unlocked your bootloader.
The flashing Red LED is the notification that a locked bootloader has encountered a ROM that is not based on Sony's releases. (CM, AOSPA, AOKP and so on.)
You need to unlock your bootloader to flash any ROM found in the Original Android Development section, and in the other Dev section only those marked LB can be installed with a locked bootloader.
http://unlockbootloader.sonymobile.com/instructions
NOTE: Doing so will erase the TA partition (which holds the DRM keys which allow X-Reality, Gracenote and other things to work.) and WILL NOT BE RECOVERABLE unless you back it up.
To back up the TA partition you will need to be rooted on a stock ROM.
Read the following thread, then read it again three more times before proceeding any further.
http://forum.xda-developers.com/showthread.php?t=2569904
And if you bought your Phone from Bell Canada, they won't let you unlock your bootloader.
My phone is rooted and my bootloader is unlocked, I was running AOSP ROM, after returning to stock rom it didn't boot. When I connect my phone to the PC the red led lights up and after 3 seconds it goes off, it keeps connecting and disconnecting
sarkis.tufenkji said:
My phone is rooted and my bootloader is unlocked, I was running AOSP ROM, after returning to stock rom it didn't boot. When I connect my phone to the PC the red led lights up and after 3 seconds it goes off, it keeps connecting and disconnecting
Click to expand...
Click to collapse
How did you return to stock rom?
What rom or FTF did you use?
How did you flash it? Flashtool etc? what version of the program did you use?
How much charge was on the phone when you did this?
I used flash tools to flash stock rom with flashmod and its the latest version of flash tool
I used C6802_14.2.A.0.290_Generic ME.FTF
my phone had almost 70% charge on it
sarkis.tufenkji said:
I used flash tools to flash stock rom with flashmod and its the latest version of flash tool
I used C6802_14.2.A.0.290_Generic ME.FTF
my phone had almost 70% charge on it
Click to expand...
Click to collapse
what version of flashtool did you use?? cause there is a bug with a previous flashtool software version. the bug is that it bricks your phone...
hamdogg said:
what version of flashtool did you use?? cause there is a bug with a previous flashtool software version. the bug is that it bricks your phone...
Click to expand...
Click to collapse
I also think the last brick used that C6802_14.2.A.0.290_Generic ME.FTF firmware but I cant find the thread
Hi all, i have been trying to root and install a custom rom for my Sony Xperia Z2, running stock firmware version 314. Previously i tried using the Dual Recovery that i found on this forum and using that to flash the rom, but it did not boot, so i had to use flashtool to restore my phone to a stock firmware, found on this forum as well. It is also the reason i am running firmware version 314, which i believe is not the latest version available, but i am unable to access OTA sony updates anymore.
I am still able to gain proper root access for my phone (verified using root checker from the play store), but for some reason am unable to flash in a working custom recovery that will help me install CM11 on my phone. I understand now that CM11 requires a custom kernel to operate, but am unable to flash one using Dual Recovery either. I am at a loss as to what to do. Any advice or help is greatly appreciated!
@Taeyeonist9 What did you use to root m8? I think you should read this first m8. You install dual recovery after rooting. If you have any more Q's I'll try and help you. Hope this helps a bit m8:good:
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
Oh, forgot to say that .314 is the latest firmware. May I ask if you have unlocked your bootloader, if you don't have OTA updates You wont get OTA updates if you are on the latest firmware.
Rooting Xperia Z2 Sirius
Hi its the same person here, i've no idea why i have two xda accounts and my desktop's browsers registers taeyeonist9 in chrome, while my laptop's registers taeyeonist, when both chromes are synced to the same google account. Anyhow, thanks for taking the time to look at my issue!
So yea, i realised that 314 is actually the latest version. And ive rooted using the easy root tool in that very link you posted above, i believe. So root access is not the issue. After rooting, I flashed XZ's Dual Recovery ,which includes TWRP, CWM and another third recovery i believe was included in the package. The Dual Recovery as i understand is only meant for devices which run stock kernels, with locked bootloaders. however from my understanding, legal regulations in Singapore, my country of residence, forces telcos to sell their devices without locking their bootloaders. Hence my bootloader is already unlocked and I BELIEVE this is not the issue ( pls correct me if im mistaken).
So the issue comes after i've successfully flashed XZ's Dual Recovery. At first i went on to straightaway flash the corresponding CM11 package for my phone and a copy of Gapps for Kitkat, and my phone soft bricked. Had to use flashtool to restore it with a stock kernel that was obtained from this forum, which resulted in my current condition of the phone - running stock firmware 314, and i was unaware that 314 is actually the latest firmware release, my apologies for that. I've tried flashing a custom kernel package using XZ's Dual Recovery too, DoomKernel v10, DoomLord's Advanced Stock Kernel package that includes CWM in it, neither worked, i ended up in the same softbrick situation. I've tried using fastboot to manually flash the kernels as well, perhaps due to my incompetence, i was unable to get the flash to be successful, it fails no matter what i try. So I'm at a loss now.... my Question is, is there any way i can get CWM onto my Xperia Z2 easily without it softbricking, so that i can then go on to flash CM11 using custom recovery method successfully? It's really frustrating because i know it can be done, i've seen the videos on youtube with ppl using CM11 on their Xperia Z2 devices, and I've tried it out on my spare phone, a SGS3, on which CM11 works wonders, and i really want to experience the magic that is CM11 on my Xperia Z2.
Sorry for my lack of technical knowledge, please go slow on the explanations. And once again, i extend my sincere gratitude to you or any other kind developer here who is willing to shed some light on my problem. i apologise for the wall of text
Thank you!
To clarify, when i say softbrick, i was only able to get the device in fastboot mode, and through flashtool, flash a copy of stock kernel obtained from another xda thread to restore it to factory condition. Other than this restoration method, my phone was essentially a brick. Nevrvewrecking:/ Appreciate the advice!
newbe at XZ2
Hi!
May I include my understanding of the issue.
I will get in the same situation in a view days when my Z2 will arrive.
At first, you have already root rights (rooted device) this doeasnt meen that you can flash what ever you want. It only means that you have more access right to your system than normal.
Bootloaders are locked by default but in some special cases it is not allowed to unlock it. (check service menu to get the info if unlockable or not)
If you want to flash roms with locked bootloader be shore to use roms with are able to be flashed with locked bootloader (LB), because the didn't change your kernel.
If you want to flash roms with a different kernel than stock you have to unlock you bootloader first, than you can flash almost every rom also the one statet (UB).
BTW: I thougt CyanogenMod uses there own kernel so its necessarry to unlock your bootloader if you want to flash CM.
However if you need to unlock the bootloader at first get root rights and backup your DRM keys because if they are lost you are unable to restore them any more, and they are necessarry if you will recover your phone to stock.
So, I cobbled together a (custom-recovery) flashable NC4 stock ROM.
I'm interested to find out whether it is possible to boot it successfully from later bootloader firmware - e.g. NK1, OB6, or OF1
(I'm still on NC4 bl and not planning on upgrading near term. It boots on NC4 bl but that's pretty obvious lol)
[size=+2]Q: Why would this be useful?
A: to provide a means for upgrading bootloader firmware without starting from scratch.[/size]
For instance, there are folks on OB6 firmware that would like to use a custom ROM that will only work on OF1 firmware. They can certainly start from scratch (backup and unload the entire device); an alternative would be to:
- Make a backup of an existing rooted ROM (that more than likely has a custom or modified boot image so is not bootable when the bootloader gets re-locked) using the currently-installed custom recovery (which will also be non-bootable under re-lock).
- Restore a (debloated) pure stock ROM w/ Samsung kernel. Root it with Towelroot (does not touch boot image)
- Flash replacement bootloader only in Odin. Locked bootloader = no custom recovery... but with a rooted stock ROM already in place with an unmodified stock kernel it can be immediately unlocked.
NC4 is easily rooted with Towelroot-v3 "on device". No need for PC drivers, online rooting tools with a separate PC, etc (e.g. as with Yemen rooting methods on OB6, OF1)
This approach in principle saves the need to backup everything up in the /sdcard - but you have to know in advance that the NC4 stock kernel and ROM can successfully be booted with later bootloaders.
So anyway, that's what I'm asking for help testing with - folks that are: (a) unlocked and (b) on NK1, OB6 or OF1 bootloader willing to try flashing a debloated NC4 Stock ROM using their existing custom recovery, and see if it boots, roots, and if root survives a single boot cycle.
Contact me via this thread or PM; I'll provide the flashable NC4 and the Towelroot .apk
.
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
only bug is wifi password resets everytime i reboot
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
hotrod85z said:
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
Click to expand...
Click to collapse
Thank you for posting that, very useful/helpful information to know.
Does Flashfire understand the Samsung "sparse" image format of the system.img.ext4 file inside the Stock (Odin) .md5 tarfile blob? Or maybe somebody else packaged up a "flashable .zip" of NC4?
hotrod85z said:
only bug is wifi password resets everytime i reboot
Click to expand...
Click to collapse
in /system/build.prop, set ro.securestorage.support=false and reboot. You might also want to set ro.config.tima=0 as well.
I suspect that mixing and matching Samsung kernels with bootloader versions breaks something in the TrustZone, and so secure containers and other sort-of-obscure security functions no longer work as the TZ smells something fishy. I am using a rooted PL1 rom on NC4 bl and it would spontaneously reboot (infrequently) until I made the above changes - it's been rock stable for about 4 days now. Why this works I can't really say - it's a "generation skipping" bootloader and stock rom combination - N* bootloader and P* ROM *
hotrod85z said:
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
Click to expand...
Click to collapse
all of the above or none of the above LOL
There are definitely some mysteries here, and I don't claim to fully understand the interdependence of the TZ (== bootloader firmware), the TIMA and RTKP stuff in the kernel, and the cross-communication between kernel and TZ via the qseecom service daemon (which is in the ROM in /system/bin) much less how the APIs of all these interfaces might have changed between major releases.
You could check those two build.prop settings in those ROMs for starters though. I suspect that if the TZ smells something fishy (e.g. a kernel TIMA to TZ info mismatch), a variety of secure credential services in the TZ stop working. It is possible that "ro.securestorage.support" is a toggle that attempts to use TZ services when it is set to "true", and so anything in the ROM which builds on it breaks because the TZ is refusing to play on an otherwise "stock" ROM variant.
FWIW I got the AryaMod (S7Edge MM port) + phantom kernel running on NC4 bl + OF1 modem for a full 24 hours after I disabled the qseecom service daemon. It ran long enough that I had customized the whole thing as a daily driver with all my apps, verified that all sensors & radios worked, made test calls, etc. Rebooted it and the kernel started getting reset by a "Modem Reset". Even weirder was that despite the use of the OF1 "modem" firmware, the kernel was reporting a bunch of RIL "unknown ioctl's". Strikes me as odd that the whole thing could run that long with so many different things happening, and then the "modem" is unhappy - even though other folks are using the ROM with OF1 bl + OF1 radio/modem firmware. (As if the "modem" isn't really the source of the problem, even though that's what initiates the device reset).
.
i initially tried flashing NC4 full tar via ODIN. but even bl unlocked. i got FAIL. flashfire worked!
very curious as to whether a custom n900v kernel would boot my 4.4.2 custom roms..its either that or the BL isnt compatible with non-touchwiz roms....
most of the kernel/modem/firmware links on here are 404 error dead links.. would be nice to see an up to date sticky. ill flash anything as long as i dont end up in JTAG mode with a brick.lol
ive played with verizon s5 atnt s2,galaxy capitivate,atrix 4g and many other phones
the s2 is still by far the fastest Smoothest phone on cm7..the newer the phones..the newer the OS..the bigger the resourse hogs"ram" im a minimalist...
even after flashing NC4 official full tar..im still showing OF1 baseband under settings
@hotrod85z
FWIW I posted a bunch of recovery-flashable stock ROMs here.
There is also a link in that thread to a complete set of (Odin flashable) modems for NC4, NJ6, NK1, OB6, OF1, and PL1 if that is of interest to you.
Maybe I wasn't paying attention, but I could swear that on at least one occasion or two when I performed an Odin modem flash, it didn't "stick", despite no complaints on the handset screen or in Odin - the next boot showed the (prior) baseband version, not what I flashed. Its a bit of a mystery to me; but for now I've resolved to make sure that after the Odin session is complete, I wait 30 seconds or so, then remove the USB cable, and then pull the battery rather than try to restart the device by holding buttons down. It is possible that those events occurred when I soft-restarted the phone, but I'm not sure. For now I'm just trying to always flash and restart with exactly the same method to avoid different behaviors from creeping in.
PS I have no idea if those ROM flashables are compatible with Flashfire. They might be, but I've never tested it, and as they are not pre-rooted I'm not going to suggest it for fear that somebody with a rooted but locked (bootloader) phone will try using flashfire and then end up with a phone that needs a full Odin re-install. Appearances are that each version of the bootloader restricts the Samsung signing verification to only the matching kernel version - you can't even boot a Signed samsung kernel on a locked phone if it is a different version than the bootloader's version.
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Dlind said:
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Click to expand...
Click to collapse
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
Dlind said:
I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode
Click to expand...
Click to collapse
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
bftb0 said:
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
Click to expand...
Click to collapse
Thanks SOOOOOO MUCH for your input I kinda had a feeling that the idea was risky at first and I don't know a whole lot about odin and I wish Samsung could have created something much easier to use, but thanks for answering the wayyyyy off topic question, I'm gonna smash that thanks button, I'm also going to take the advise on not cross flashing different modems, its just to risky. You answered all my questions so thanks, Also I want to say thank you for your continued work on this phone is by normal terms "old" now but in reality its still an amazing phone with the right custom software, and happy flashing!