Related
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
MomijiTMO said:
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
Click to expand...
Click to collapse
Simple english please.
I don't think anyone more should flash this fw.
It's buggy and crazy.
Also your nv-data.bin is modified.
I don't want my warranty to be un-voidable(by flashing original firmware).
I flashed through KIES and I believe this doesn't damage your phone. It's only thorugh Odin??
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Zilch25 said:
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Click to expand...
Click to collapse
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
I've restored the stuff in /efs to get my phone back to working order- I still have goofed up build numbers and things like that. It's unfair to imply that this is totally safe for anyone to do, especially those that aren't super comfortable screwing around with protected areas on their phones. It's doubly unfair for people to have the impression that odin is the only unsafe way to install it =P
dutchcow said:
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
Click to expand...
Click to collapse
So essentially I'm f*cked then.
Thread Astaire said:
So essentially I'm f*cked then.
Click to expand...
Click to collapse
Not necessarily, it's too soon to tell if it will effect anything... take comfort in the fact that 85% of the SGS XDA community flashed this. Even if there IS an issue people will find ways around it =P
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
ed10000 said:
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
Click to expand...
Click to collapse
You can, I flashed back JP3 after having a lot of errors with JPC
Zilch25 said:
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
Click to expand...
Click to collapse
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
EDIT:
iuzar said:
You can, I flashed back JP3 after having a lot of errors with JPC
Click to expand...
Click to collapse
After flashing back to JP3, do you still have the new recovery mode or back to the old one? Can you use Clockwork Recovery now?
ed10000 said:
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
Click to expand...
Click to collapse
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Edit: Make sure you flash back to the JPC kernel before you try to actually boot
Zilch25 said:
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Click to expand...
Click to collapse
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
ed10000 said:
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
Click to expand...
Click to collapse
That might be an issue for me because I'm on a captivate No physical home for me haha. I know for I9000 people rooting though they had to flash the original kernel to get it to work (Stole their trick but substituted the I897 kernel to get it to work for me), but I'm not sure why that is
Samsung have disabled the test keys in all firmwares after JP2. We don't have a real key yet, so gotta flash back to JP2 or before in order to apply an update.zip
Hopefully someone will find a new root-workaround soon.
windy31 said:
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Click to expand...
Click to collapse
Perhaps SamFirmware had his SGS brick when he try to flash it with odin3.
Sent from my GT-I9000 using XDA App
Thanks for the clarification Ryan
As for samsung firmwares it seems he's just erring on the side of caution, he's got a post in Dutch up there that seems to roughly translate into him trying to avoid throwing up a suspicious firmware (the EFS changes etc) and potentially screwing tons of people, gotta respect that
Yes, especially since Samsung put this firmware up as a "beta" in kies withouth worrying about screwing people...
My phone has/was working fine for the longest time. Was running cog 3.04. Ever since trying to update to cog4, i get symlink error EVERY time i try to install. I am flashing back to stock, and doing a master clear every time.
Thinking it was the cog4 rom, i have tried serendipity, and paragon. Though the error is on different lines, it gives me a symlink error everytime it is installing. What gives! I will throw this phone in the garbage if i have to be stuck on stock now!
On another note, anytime i try to restore a backup (os backup, not apps), it will successfully restore, but then when it reboots it is back to the stock recovery. UGH. Someone please give me some guidance!
Do you get an error like this:
E: Can't symlink /system/bin/cat
E: Failure a lin 7:
symlink toolbox SYSTEM:bin/cat
installation aborted
I probably get at least one of these errors every time that I flash. I have asked around and some people say that it can be a bad download. I would recommend downloading cog4 again and maybe even 2 to 3 times and putting all of those on your internal memory (name them cog4, cog4a, cog4b.zip or something like that). This is what I do and typically at least one of the three/four that I have on there will work.
Yea I had one of these last night and it was just a bad download. Compared the file size and they were different
Sent from my SAMSUNG-SGH-I897 using XDA App
PLEAE SOMEBODY HELP I AM BEGGING PLEASE.
The ONLY custom rom i can install is cog3.04. Nothing else will work. I have flashed back to stock 2.1 and 2.2 and it does not make a difference. I have master cleared a million times. I have repartitioned my sd card also. From what i am gathering on the internet, is that i need to change the size of the system partition. It is too small. I cannot find ANY WAY AT ALL to do that. I will seriously send someone money over paypal if they just please try to help me. I am dead serious.
xsteven77x said:
PLEAE SOMEBODY HELP I AM BEGGING PLEASE.
The ONLY custom rom i can install is cog3.04. Nothing else will work. I have flashed back to stock 2.1 and 2.2 and it does not make a difference. I have master cleared a million times. I have repartitioned my sd card also. From what i am gathering on the internet, is that i need to change the size of the system partition. It is too small. I cannot find ANY WAY AT ALL to do that. I will seriously send someone money over paypal if they just please try to help me. I am dead serious.
Click to expand...
Click to collapse
The errors are different on every rom, but pretty much the same. It's always symlink error system/xbin/su or system/xbin/cap. ALWAYS. No matter what rom it is. BESIDES COG 3.04. That was the rom i had RIGHT before all this started. I tried to install cog 4 and it ****ed my phone. Not sure what to do....
Dead serious about paying someone to help me.
xsteven77x said:
The errors are different on every rom, but pretty much the same. It's always symlink error system/xbin/su or system/xbin/cap. ALWAYS. No matter what rom it is. BESIDES COG 3.04. That was the rom i had RIGHT before all this started. I tried to install cog 4 and it ****ed my phone. Not sure what to do....
Dead serious about paying someone to help me.
Click to expand...
Click to collapse
You have tried the full ODIN, and using Partition?
When flashing back to stock, use Odin3, and have the Re-Partition box checked
Note: Note I have not ever had to do that before, so not sure if would work
indomikey said:
You have tried the full ODIN, and using Partition?
When flashing back to stock, use Odin3, and have the Re-Partition box checked
Note: Note I have not ever had to do that before, so not sure if would work
Click to expand...
Click to collapse
Yes i have used the one click and the regular full odin. And yes i clicked the re-partition thinking that would help me. Makes no difference
The key to this mystery i think is the fact that cog 3.04 is the ONLY custom rom that will go on here...and was the one i had right before my phone got royally ****ed.
xsteven77x said:
Yes i have used the one click and the regular full odin. And yes i clicked the re-partition thinking that would help me. Makes no difference
The key to this mystery i think is the fact that cog 3.04 is the ONLY custom rom that will go on here...and was the one i had right before my phone got royally ****ed.
Click to expand...
Click to collapse
How about formatting through recovery menu? and then reinstalling with odin
indomikey said:
How about formatting through recovery menu? and then reinstalling with odin
Click to expand...
Click to collapse
Yes i have. Someone with a different phone but the same problem fixed it by doing some type of rm- rf /system through adb? It just totally deletes/wipes system partition? Not sure if that would help but anytime i try it says it cannot access system whether i have it mounted or not.
The problem seems to be (gathered this from reading) that the system partition is full and thats why it can't symlink or something. But if the system partition is getting formatted everytime i dont understand how that makes any sense.
xsteven77x said:
Yes i have. Someone with a different phone but the same problem fixed it by doing some type of rm- rf /system through adb? It just totally deletes/wipes system partition? Not sure if that would help but anytime i try it says it cannot access system whether i have it mounted or not.
The problem seems to be (gathered this from reading) that the system partition is full and thats why it can't symlink or something. But if the system partition is getting formatted everytime i dont understand how that makes any sense.
Click to expand...
Click to collapse
But even then, why would cog 3.04 install? And no other custom rom?
xsteven77x said:
But even then, why would cog 3.04 install? And no other custom rom?
Click to expand...
Click to collapse
Maybe Cog is still "suck" in that partition and can't be deleted, thereby taking up the space..... not sure why though and how to get at it, can you see the files through adb?
indomikey said:
Maybe Cog is still "suck" in that partition and can't be deleted, thereby taking up the space..... not sure why though and how to get at it, can you see the files through adb?
Click to expand...
Click to collapse
Thats an interesting theory, seems to make sense! I know how to do basic adb functions but i never really messed with the files/file system thorugh it. If you wanna give me any type of directions i would love it!
xsteven77x said:
Thats an interesting theory, seems to make sense! I know how to do basic adb functions but i never really messed with the files/file system thorugh it. If you wanna give me any type of directions i would love it!
Click to expand...
Click to collapse
Sorry I'm noobish when it comes to ADB, try this thread.... not sure if it will help: http://forum.xda-developers.com/showthread.php?t=717874 realize, it is not specific for captivate or any of our ROMS, its talking about Cyanogenmod, but hopefully you can use something there
I have to head out, if you are still having problems when I get back, I'll keep searching, good luck
Somebody ANYBODY. I can only install cog 3.04. Anything else and i mean ANYTHING gives me symlink system/xbin/su. That file is not even IN the roms i'm trying to flash in that folder! WTF
xsteven77x said:
Somebody ANYBODY. I can only install cog 3.04. Anything else and i mean ANYTHING gives me symlink system/xbin/su. That file is not even IN the roms i'm trying to flash in that folder! WTF
Click to expand...
Click to collapse
if the file isnt there, THAT is the problem. the update-script is looking for that file. have you tried actually removing that line from the update-script?
Pirateghost said:
if the file isnt there, THAT is the problem. the update-script is looking for that file. have you tried actually removing that line from the update-script?
Click to expand...
Click to collapse
I have tried removing that line, and tried moving that file into the folder. Makes no difference. It's doing this error on EVERY custom rom...i can't believe that every rom maker messed up the su symlink lol.
xsteven77x said:
I have tried removing that line, and tried moving that file into the folder. Makes no difference. It's doing this error on EVERY custom rom...i can't believe that every rom maker messed up the su symlink lol.
Click to expand...
Click to collapse
they didnt. there are literally thousands of people flashing roms every day....
that symlink works properly on all the captivates i have with all the roms that i throw together.....
Pirateghost said:
they didnt. there are literally thousands of people flashing roms every day....
that symlink works properly on all the captivates i have with all the roms that i throw together.....
Click to expand...
Click to collapse
That didnt come out right. It was meant to read "i do not believe that every rom maker messed up the su symlink". Meaning that ya, it is just me, i know it works fine for everyone else.
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
ghane0 said:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
Click to expand...
Click to collapse
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
Click to expand...
Click to collapse
It is a 901s he said non Taiwan
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
seyidaga said:
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Click to expand...
Click to collapse
I have downloaded the Maximus ROM. I am open to doing this, but I cannot figure out how to use the stock recovery (there seem to be no controls).
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Click to expand...
Click to collapse
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
koniiiik said:
If it was a 901S, I'd suggest installing the stock ROM from scratch
Click to expand...
Click to collapse
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
daorderdillon said:
It is a 901s he said non Taiwan
Click to expand...
Click to collapse
Oh, okay, I think I'm getting lost in which area has which version of the phone. Never mind then and thanks for the correction.
ghane0 said:
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
Click to expand...
Click to collapse
Well, to install custom ROMs, you'll have to use either TWRP or CWM, I don't know about a way to do that using stock recovery.
Ok, I did this:
Installed CWM Recovery
Flashed the Stock zip from koniiiik's archive
Rebooted successfully. Lots and lots of force closes, Everything from android.core to ...
Used Rom Manager to restore a backup made a month ago
Rebooted. All OK now
Flashed Stock Recovery (again, thanks koniiiik)
Booted. Checked OTA. Got a small update (1.x)
Applied. Rebooted, Checked OTA again
Got the 4.3 package. Applied.
All is well
Between Step #3 and #4, I got my entire backlog of SMS delivered, which I lost in the next step. But that is a small price to pay.
Thanks to all of you helped,
ghane0 said:
Used Rom Manager to restore a backup made a month ago
Click to expand...
Click to collapse
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Backup of /system, nearly stock
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
koniiiik said:
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Click to expand...
Click to collapse
I have three files in the directory:
system.ext4.tar (0B)
system.ext4.tar.a (954MB)
system.ext4.tar.b (500MB)
Is the split to avoid files greater than 1GB?
Will upload starting a few hours. Dropbox will do?
ghane0 said:
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
Click to expand...
Click to collapse
Don't worry about that, of these three, only root affects /system and it should be not too difficult to revert.
ghane0 said:
Is the split to avoid files greater than 1GB?
Click to expand...
Click to collapse
Most likely – FAT filesystems, depending on inode size and other factors, only support file sizes up to a certain limit. Sometimes it's 2 GB, sometimes 4 GB, sometimes probably as little as 1 GB.
ghane0 said:
Will upload starting a few hours. Dropbox will do?
Click to expand...
Click to collapse
That would be most helpful. Thanks.
Dropbox is back up, I have sent you a link.
Thanks
Hello everybody,
I'm new to the forum and not that of a newbie concerning Android but since I've updated to Marshmallow on my Nexus 6 I cannot edit the build.prop, even if I'm root.
I already tried a lot of things, since now I used ES File Explorer to edit the file, but now when I want to save it it doesn't work that message appears "Error occurred when trying to save the file. It will not be saved.". So I say ok I'll try using a Build Prop Editor App, it requests root access, I allow it, then fails.
So after many tries I try to completely reinstall the system a second time, thinking maybe there was something I did wrong the first time I installed and rooted, I installed a root checker, it said my phone was correctly rooted, so I try again with ES File Explorer (With root explorer enabled) still the same problem.
Then I find a tutorial on how to get the build.prop via adb shell, which I try, and I have a message saying "Read only File system", so I try to remount but it still the same problem.
Just for the info, the first time I installed Marshmallow and rooted was with a guide on "theandroidsoul" (sory I can't post links since I'm new). And the second time was with the one on ibtimes.
It might not be useful but I tried two different kernels so it might give you some extra info.
Could someone please help me ? I hope I gave you enough information and sorry if I made mistakes, English is not my native language.
Thank you very much for your help.
What version SU did you flash and what kernel are you running? Why would you tell us you ran two kernels but not mention what ones... Lol, were they both stock
With Benzo M2 and supersu 2.46 I edited and saved my buildprop this morning with es file explorer. TWRP 2.8.7.1
scryan said:
What version SU did you flash and what kernel are you running? Why would you tell us you ran two kernels but not mention what ones... Lol, were they both stock
Click to expand...
Click to collapse
Sorry, I'm new and I knew I would forget info...
So I used BETA-SuperSU-v2.49 and yes the kernels I used were stock, the first one was kernel-shamu-mra58k-color-root, and the second one was ElementalX-N6-2.03.
Thank you
Francis_37 said:
Sorry, I'm new and I knew I would forget info...
So I used BETA-SuperSU-v2.49 and yes the kernels I used were stock, the first one was kernel-shamu-mra58k-color-root, and the second one was ElementalX-N6-2.03.
Thank you
Click to expand...
Click to collapse
neither of those are stock, stock is stock... Stock based maybe...
I don't know that all kernels have it sorted yet. I haven't really looked over which ones do, but it seems like it ended up taking a few extra tweaks that everyone is sorting.
Benzino was the first I head people having success with, and I want to say I have heard hells core was working too. If you just want to make it work, my best advice would be to reboot to bootloader, reflash boot.img, immediately boot to recovery (either the volume rockers, or just fastboot reboot recovery should work). then flash Benzino. I can at least tell you is should work there. Dirty flashing kernel may have issue with ramdisk modifications clashing (I don't really know much about this, but its usually recommended not to flash one kernel over another). Once things are settled in a little more, go back to your old favorite kernel?
scryan said:
neither of those are stock, stock is stock... Stock based maybe...
I don't know that all kernels have it sorted yet. I haven't really looked over which ones do, but it seems like it ended up taking a few extra tweaks that everyone is sorting.
Benzino was the first I head people having success with, and I want to say I have heard hells core was working too. If you just want to make it work, my best advice would be to reboot to bootloader, reflash boot.img, immediately boot to recovery (either the volume rockers, or just fastboot reboot recovery should work). then flash Benzino. I can at least tell you is should work there. Dirty flashing kernel may have issue with ramdisk modifications clashing (I don't really know much about this, but its usually recommended not to flash one kernel over another). Once things are settled in a little more, go back to your old favorite kernel?
Click to expand...
Click to collapse
Waou, I just tried Benzino and Super SU 2.46, it worked like a charm in no time, I even didn't have to reflash boot.img ! Should I still do it ?
Anyway, thank you very much scryan, it helped me a lot
Francis_37 said:
Waou, I just tried Benzino and Super SU 2.46, it worked like a charm in no time, I even didn't have to reflash boot.img !Should I still do it ?
Anyway, thank you very much scryan, it helped me a lot
Click to expand...
Click to collapse
Meh.
If there are no problems there are no problems
If things start going wrong... maybe look there first. I don't know too much about what can and can't happen dirty flashing kernels, so I wont say too much... I just know its not normally recommended, but I've seen plenty of people do it and not have major issues anyways. I think its the kind of thing where if one dev did things one way, and another the other... you don't clear them out and the clash.... I'd just be happy with what works
scryan said:
Meh.
If there are no problems there are no problems
If things start going wrong... maybe look there first. I don't know too much about what can and can't happen dirty flashing kernels, so I wont say too much... I just know its not normally recommended, but I've seen plenty of people do it and not have major issues anyways. I think its the kind of thing where if one dev did things one way, and another the other... you don't clear them out and the clash.... I'd just be happy with what works
Click to expand...
Click to collapse
Yes you're right And I am happy with what I have now, thanks to you
I'm glad it's been so quick !
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.