Im having trouble flashing zips without a custom recovery i have all the kernel apps and the magisks module for flashing in the terminal nothing works. I will just leave screenshots of my attempts any ideas are appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pts any ideas are appreciated thanks
Greeneyes420 said:
Im having trouble flashing zips without a custom recovery i have all the kernel apps and the magisks module for flashing in the terminal nothing works. I will just leave screenshots of my attempts any ideas are appreciated View attachment 5700077View attachment 5700079pts any ideas are appreciated thanks View attachment 5700071View attachment 5700073View attachment 5700075
Click to expand...
Click to collapse
You can't flash custom zips via stock recovery, you can only flash official stock approved zips that have a stock signature, such as a stock update.zip.
If you are rooted, there are apps that can flash .zip files, such as Flashify and Rashr among others.
Droidriven said:
You can't flash custom zips via stock recovery, you can only flash official stock approved zips that have a stock signature, such as a stock update.zip.
If you are rooted, there are apps that can flash .zip files, such as Flashify and Rashr among others.
Click to expand...
Click to collapse
Yes i have these apps and root none work
Im just trying to flash a custom kernel with a kernel manager app i have all of them and the terminal magisk module nothing works
Greeneyes420 said:
Yes i have these apps and root none work
Click to expand...
Click to collapse
Have you set the system partition read/write permissions to r/w? Have you granted root permission to the apps that you are using to flash the zips? There is more to it than just rooting, root does not necessarily "automatically" allow modifying the system partition. If the apps aren't working and if adb isn't allowing you to make changes to the system partition, that may be your issue.
Ya idk maybe i have to change the updater script or something but that would definitely be a first time i could learn but...
Droidriven said:
Have you set the system partition read/write permissions to r/w? Have you granted root permission to the apps that you are using to flash the zips? There is more to it than just rooting, root does not necessarily "automatically" allow modifying the system partition. If the apps aren't working and if adb isn't allowing you to make changes to the system partition, that may be your issue.
Click to expand...
Click to collapse
I set the sytem partition as rw in root explorer and tried but still nothing it says it might have something to do with the /tmp folder in one of the apps that i tried to flash it with
Greeneyes420 said:
I set the sytem partition as rw in root explorer and tried but still nothing it says it might have something to do with the /tmp folder in one of the apps that i tried to flash it withView attachment 5700669
Click to expand...
Click to collapse
What are you trying to flash? There may be another way to do what you want.
Droidriven said:
What are you trying to flash? There may be another way to do what you want.
Click to expand...
Click to collapse
A custom kernel mint kernel even if i can flash it it will probably tag the modifications as dirty anyway thats what it did when i had twrp on an older security patch but i have the latest security patch now and im not even sure if this kernel will work but it would still be nice to be able to flash zips without twrp https://forum.xda-developers.com/t/kernel-r-one-ui-aosp-mint-freshen-up-your-galaxy.4338209/
Greeneyes420 said:
A custom kernel mint kernel even if i can flash it it will probably tag the modifications as dirty anyway thats what it did when i had twrp on an older security patch but i have the latest security patch now and im not even sure if this kernel will work but it would still be nice to be able to flash zips without twrp https://forum.xda-developers.com/t/kernel-r-one-ui-aosp-mint-freshen-up-your-galaxy.4338209/
Click to expand...
Click to collapse
Is your bootloader unlocked? I'm assuming it isn't since you can't flash TWRP. If so, you won't be able to flash the kernel and even if you did find a way to actually flash it, the locked bootloader will not allow it to boot or it will cause the device to be soft-bricked or even hard-bricked. With locked bootloader, you can make modifications but you can't change the stock firmware partitions to to custom software. You can flash a modified stock based kernel or a modified stock based ROM, but, you can't flash a custom kernel or a custom system or a custom recovery,, etc...
Droidriven said:
Is your bootloader unlocked? I'm assuming it isn't since you can't flash TWRP. If so, you won't be able to flash the kernel and even if you did find a way to actually flash it, the locked bootloader will not allow it to boot or it will cause the device to be soft-bricked or even hard-bricked. With locked bootloader, you can make modifications but you can't change the stock firmware partitions to to custom software. You can flash a modified stock based kernel or a modified stock based ROM, but, you can't flash a custom kernel or a custom system or a custom recovery,, etc...
Click to expand...
Click to collapse
Yes my bootloader is unlocked and there is no official custom recovery for my device at all thats the only reason i cant flash twrp i had twrp but it was unofficial and that is not recommended
Droidriven said:
Is your bootloader unlocked? I'm assuming it isn't since you can't flash TWRP. If so, you won't be able to flash the kernel and even if you did find a way to actually flash it, the locked bootloader will not allow it to boot or it will cause the device to be soft-bricked or even hard-bricked. With locked bootloader, you can make modifications but you can't change the stock firmware partitions to to custom software. You can flash a modified stock based kernel or a modified stock based ROM, but, you can't flash a custom kernel or a custom system or a custom recovery,, etc...
Click to expand...
Click to collapse
Ya man my bootloader is unlocked there is no official custom recovery at all of my device
And i also think i already hard bricked it. It was stuck in download mode saying recover with samsung smart switch but i downloaded the most recent firmware and it flashed with odin
Greeneyes420 said:
And i also think i already hard bricked it. It was stuck in download mode saying recover with samsung smart switch but i downloaded the most recent firmware and it flashed with odin
Click to expand...
Click to collapse
What is inside the .zip file? Have you tried extracting the kernel from the zip then converting it to an Odin flashable .tar file then flash it via Odin in the AP slot?
Droidriven said:
What is inside the .zip file? Have you tried extracting the kernel from the zip then converting it to an Odin flashable .tar file then flash it via Odin in the AP slot?
Click to expand...
Click to collapse
Thats how im rooted will i lose root?
Greeneyes420 said:
Thats how im rooted will i lose root?1
Click to expand...
Click to collapse
If flashing that kernel were to cause you to lose root, it would do it regardless of the method that you use to flash it.
Related
S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
beaver2233 said:
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
dotpage said:
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
Click to expand...
Click to collapse
How did you get back to CM10.1?
AlAmeri said:
How did you get back to CM10.1?
Click to expand...
Click to collapse
Flash it using a custom recovery
Me Gusta!
Me Gusta said:
Flash it using a custom recovery
Me Gusta!
Click to expand...
Click to collapse
So flashing ROM without root is possible?
AlAmeri said:
So flashing ROM without root is possible?
Click to expand...
Click to collapse
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
fcknghst said:
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
Click to expand...
Click to collapse
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
AlAmeri said:
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
Click to expand...
Click to collapse
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
fcknghst said:
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
Click to expand...
Click to collapse
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
So you cant restore your backup, from before 4.3?
fcknghst said:
So you cant restore your backup, from before 4.3?
Click to expand...
Click to collapse
Exactly. I tried searching for stock firmware, couldn't find one. So I thought either I find a way to restore. Or flash an already rooted ROM. You see my dilemma.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
dotpage said:
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
Click to expand...
Click to collapse
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
AlAmeri said:
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
Click to expand...
Click to collapse
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
fcknghst said:
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
Click to expand...
Click to collapse
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
If you find 4.2.2 vanilla(T-Mobile) let us know, I am looking for that ROM....
AlAmeri said:
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
Click to expand...
Click to collapse
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
dont know if this will work for you but here goes. i have a T999L (T-Mobile LTE S3) i have twrp installed on it and i have slimbean 4.3 official build installed on it, i had the same issue with getting 4.3 rooted but i got it figured out first make sure in the developer options you have superuser allowed by adb and apps.
( if you don't see developer options in your settings menu
go to :Settings>About Phone> click on your build number several times until you get a toast that says your almost a developer keep clicking until it says it has been enabled)
then you will use motoChopper to push the exploit to get the superuser.apk added to the system/apps folder once you do this it won't work as they have somehow allowed access for the expoit to push the .apk but not push the binary to the system/xbin folder.
now pull the SU binary out of the motoChopper folder on your computer and place in on your sdcard
boot into TWRP, mount the file system and copy it from your sdcard to the system/xbin folder and voila you are done, when you go to reboot your device from TWRP it will ask you if you want to fix the Superuser permissions just skip and reboot
( all rights thanks and so on go to the original developer djrbliss and i do not take any credit for his work, nor did i get permission to modify his work, i tried but got no response so i modded it for myself to use and i am now sharing, all i did was swap the Superuser.apk and SU binaries he used in his exploit.) @djrbliss if you would like this post removed just let me know and i will pull it!
not sure why the list showed up as 1 1 1 2 but i think you get the point
I'm pretty happy with stock 5.0 but I miss OnmiRecents from OmniRom and xposed modules.
On my Note 3 I loved Temasek's CM12 because it included both of these, what ROM would you recommend if I want the bare minimum that supports Onmirecents and Xposed?
I tried useing xposed on stock without any FC's unsuccessfully.
if you are getting crashes with xposed then its likely the module might not be lollipop compatible, im running 5.0.2 with xposed and a few modules I use and its solid
you might be better off looking at some of the aosp/cm based roms in the dev section
I want to give aosp a shot since you recommended it and I think it's exactly what I'm looking for, but I'm having trouble flashing the zip I got from the Free Xperia Project site, I'm trying to flash AOPS_L_MR1_150312_leo.zip and all I'm getting is errors from all 3 custom recoveries, using an unlocked bootloader, the md5 is 2c4006757733d7a57997cfb31ba9efe but I can't find a hash on their site, the only error I have is "E: Installation aborted. press any key to continue". My internet is terribly slow and downloading a 200mb file takes hours, so I'll try re-downloading but I'd prefer not to.
Edit: I've tried 2 ROMs I've verified are downloaded correctly and they won't install, one with an unspecified error (AOSP) and the other will report wrong device saying "This rom is intended for D6603 z3, this device is 'leo'" (pac rom), I have no idea where the problem may be
well I never recommended it, I just said that you might be better off looking at aosp roms as that's clearly what you want rather than stock sony rom, what model is your device and are you flashing the boot.img from the rom and using that recovery?
Ok, I got a bit carried away I ment to say that you where right when saying that AOSP suited my needs.
Richy99 said:
what model is your device and are you flashing the boot.img from the rom and using that recovery?
Click to expand...
Click to collapse
I'm not flashing boot.img from the rom, I'm using CWM TeamWin and Philz recoveries I previously flashed while on stock to flash the zip files. Is this wrong? I've been doing this forever on other devices.
Do people that post ROMs provide boot.img to be flashed using flashtool previous to the flashing of their ROMs zip?
what device do you have? is it the 6603 or 6653? no its not wrong but sometimes the recovery is slightly different from the boot.img and I have seen it resolve the issue in the past, the installation aborted should give an error number after it, normally googling this can lead to why it failed
Richy99 said:
what device do you have? is it the 6603 or 6653?
Click to expand...
Click to collapse
I'm using 6603 and the error I get isn't very descriptive "E:Installation aborted" right after selecting the zip, nothing else.
Only in one isntance did I get something different and the error was something along the lines of "this rom is for 6603 and your device is leo".
which rom did you try? as it sounds like the rom isn't for the 6603
You must edit update.binary and erase z3 and replace it with Leo.
Then re-zip and flash it.
Richy99 said:
which rom did you try? as it sounds like the rom isn't for the 6603
Click to expand...
Click to collapse
This has happened with various ROMs that stated they where for 6603, could it be my recovery isn't playing nice with the zipped ROMs making them think my phone is a diferent model?
Edit:
I flashed bootZ3monxtest01.img with fastboot wich i TWRP and I'm getting nowhere
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
E-Chan42 said:
This has happened with various ROMs that stated they where for 6603, could it be my recovery isn't playing nice with the zipped ROMs making them think my phone is a diferent model?
Click to expand...
Click to collapse
LOL
Read my post.
TheTeslaCoil said:
You must edit update.binary and erase z3 and replace it with Leo.
Then re-zip and flash it.
Click to expand...
Click to collapse
For every .zip I try to flash? I'm not confident I could unzip, modify and re-zip without screwing up somehow, isn't there a specific recovery I can flash that will do this correctly?
UPDATE: using Z3_DooMLoRD_AdvStkKernel_v01_FW-93.img I was able to flash only cm-12.1-20150505-UNOFFICIAL-z3 (1).zip all other files gave me the same error, I'm now running Cyanogen but I still want to find a solution so I can flash other ROMs freely
E-Chan42 said:
For every .zip I try to flash? I'm not confident I could unzip, modify and re-zip without screwing up somehow, isn't there a specific recovery I can flash that will do this correctly?
Click to expand...
Click to collapse
Its not hard, open the zip using 7 zip or any winzip or WinRAR
Drag and drop the updater script out, modify it, drag and drop it back in.
Done
You can also flash CM by: flash boot.img from inside the firmware you want to flash. Unzip the CM ROM and extract boot.img and flash it. [via adb]
Then reboot into recovery.
It will bring you to CM recovery, from there apply update from sdcard1. [assuming that the ROM and gapps are there]
Flash CM
Again apply update and flash gapps.
Done.
After that you can flash another recovery if you want, or kernel, there is also a fota kernel, which updates only the recovery and keeps the kernel the same.
This method is without the need of editing update-binary.
Flash original firmware, [exactly as it is when downloaded] because the CM Recovery will check the signature.
Must have unlocked bootloader.
P.S.
If you edit update-binary do it with Notepad++
I had no idea I could extract boot.img from a ROM and flash it individualy using fastboot, this solved my problem 100%, thanks!
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
already the firmware the have for future if you wish render it to stock and clean
javierduran said:
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image. View attachment 3848895
already the firmware the have for future if you wish render it to stock and clean
Click to expand...
Click to collapse
This is a much better guide for his model
http://forum.xda-developers.com/showthread.php?t=3361990
Sent from my SM-N920T using Tapatalk
You only have to do is flash TWPR in odin (don't forget to uncheck F. Reset time and auto-reboot) before you flash the recovery, download the flashable Super SU and place it on SD , memory, otg or wathever. Just flash recovery, when odin ends, then boot directly into recovery and flash the super su and you are done. if you no want to install custom recovery, you must look for other options
clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Click to expand...
Click to collapse
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
The Apostle said:
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
Click to expand...
Click to collapse
That's correct the new SuperSU modifies the kernel for you
Sent from my SM-N930F using Tapatalk
clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
wrecless said:
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
Click to expand...
Click to collapse
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
The Apostle said:
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
Click to expand...
Click to collapse
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
wrecless said:
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
Click to expand...
Click to collapse
I've did not remove my Google account. I've read that too but believe the circumstances were different.
You said you have OEM unlock ticked off? Should tick it on (so it shows blue)
You may want to dload the official PG1 FW from Sammobile.com and flash from scratch.
I updated to EMUI 5 with nougat, i think i lost my root. Went back to TWRP and about 60% of the way through the install phone reboots by itself with the phone not being rooted. Tried different superSU versions along with an adb sideload, same thing. Anyone have any idea what i'm doing wrong?
richbumx said:
I updated to EMUI 5 with nougat, i think i lost my root. Went back to TWRP and about 60% of the way through the install phone reboots by itself with the phone not being rooted. Tried different superSU versions along with an adb sideload, same thing. Anyone have any idea what i'm doing wrong?
Click to expand...
Click to collapse
twrp is not yet able to flash supersu successfully, if u want to root then flash a patched boot.img from here https://mega.nz/#!69IlASwI!FjF5rhALGGA_tusum7FdXgnO1R45ZIpdrahNa0UXT-8
Root working with B360 (L09 only at the minute)
thanks to @Atarii
Reboot into bootloader mode
Extract files and "fastboot flash boot boot.img"
Reboot into system
Install phh's SuperUser app from Play Store
OR
if u have twrp flash it thru twrp
raza3434 said:
twrp is not yet able to flash supersu successfully, if u want to root then flash a patched boot.img from here https://mega.nz/#!69IlASwI!FjF5rhALGGA_tusum7FdXgnO1R45ZIpdrahNa0UXT-8
Root working with B360 (L09 only at the minute)
thanks to @Atarii
Reboot into bootloader mode
Extract files and "fastboot flash boot boot.img"
Reboot into system
Install phh's SuperUser app from Play Store
OR
if u have twrp flash it thru twrp
Click to expand...
Click to collapse
Hello I have B380 and just tried this, flash the modified boot.img, and install the phh's su but still not rooted, do you have an idea?
remi13014 said:
Hello I have B380 and just tried this, flash the modified boot.img, and install the phh's su but still not rooted, do you have an idea?
Click to expand...
Click to collapse
(for L09)
u didn't mention u are on b380, anyways here is the boot.img for b380,
https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
raza3434 said:
(for L09)
u didn't mention u are on b380, anyways here is the boot.img for b380,
https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
Click to expand...
Click to collapse
i'm on L-04.. would this not work for me then?
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
i dont know its atariis work you can ask there, @Atarii go to his profile search for b378, actually this boot.img is for p9 but due to same kernel it works on h8
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
parleyp said:
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
Click to expand...
Click to collapse
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
parleyp said:
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
Click to expand...
Click to collapse
skrapmetal said:
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
Click to expand...
Click to collapse
So we know it works on the L04 and L14. Does not work on L09.
L09 works
parleyp said:
So we know it works on the L04 and L14. Does not work on L09.
Click to expand...
Click to collapse
Wrong
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the update. I am happy is is working on yours.
skrapmetal said:
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
Click to expand...
Click to collapse
I am also trying to get root on an H8 FRD-L04. So does this boot.img file get flashed in twrp like any other zip file or do I need to choose different options in twrp to write it to the correct place?
Also can you tell me which version of twrp you are using? There seem to be several floating around on xda.
Have you had any other issues with apps that need root since you did this? I'd like to get my favorite xposed mods working on my H8.
vouty said:
I am also trying to get root on an H8 FRD-L04. So does this boot.img file get flashed in twrp like any other zip file or do I need to choose different options in twrp to write it to the correct place?
Also can you tell me which version of twrp you are using? There seem to be several floating around on xda.
Have you had any other issues with apps that need root since you did this? I'd like to get my favorite xposed mods working on my H8.
Click to expand...
Click to collapse
Unzip the file first, that should leave you with bootr.img I think it's called. Make a backup just in case, but yes, flash it just like you would anything else, no need to wipe anything and no I did not change any settings.
I'm using TWRP 3.0.3 found here https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I have tried at least 5 apps that have needed root and have not had any issues. I haven't tried xposed yet though.
skrapmetal said:
Unzip the file first, that should leave you with bootr.img I think it's called. Make a backup just in case, but yes, flash it just like you would anything else, no need to wipe anything and no I did not change any settings.
I'm using TWRP 3.0.3 found here https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I have tried at least 5 apps that have needed root and have not had any issues. I haven't tried xposed yet though.
Click to expand...
Click to collapse
And so the bootr.img is 'pre-rooted" so I don't then need to flash "SuperSU-v2.79-201612051815-EMUI5.0.zip" or any other SU zip file, or format the Data partition as some other threads have mentioned, to get root, is that correct?
vouty said:
And so the bootr.img is 'pre-rooted" so I don't then need to flash "SuperSU-v2.79-201612051815-EMUI5.0.zip" or any other SU zip file, or format the Data partition as some other threads have mentioned, to get root, is that correct?
Click to expand...
Click to collapse
I did not format or wipe anything. I simply backed up my boot.img and flashed bootr.img. I did not flash anything else. After that, I rebooted and installed phh Superuser from the play store. That's it.
skrapmetal said:
I did not format or wipe anything. I simply backed up my boot.img and flashed bootr.img. I did not flash anything else. After that, I rebooted and installed phh Superuser from the play store. That's it.
Click to expand...
Click to collapse
Sounds easy enough. I'll give it a try. Then I'm gonna go for getting xposed and adaway working.
hi, i confirm the modified boot.img (b378) and root works with b380 rom ?
Thanks
Jsbcterpper said:
You are right , i agree with you
Click to expand...
Click to collapse
No.
It does work in the L09, check my post on the previous page.
So I was initially on pixel experience 9.0 plus for my redmi note 7 pro and then decided to flash MIUI V11.0.5.0.PFHINXM via TWRP recovery. After flashing, the phone booted normally. Then I switched the rom to Pixel Experience 10. I didn't like the rom so thought of coming back to 9.0-pixel-experience but when I tried to do so, I got the error Error:7 twrp "this package requires firmware from miui 9.5.14" update your firmware. I tried updating the firmware too by flashing firmware from https://xiaomifirmwareupdater.com/firmware/violet/ but nothing seemed to work. Later I tried flashing pixel experience 10 and got the error. Now I am not able to flash any other rom other than Miui. Can someone help me to fix it, please?
ps: I have already tried flashing factory images of latest miui roms and that has not solved the problems.
which recovery are you using
try changing recovery
check with orangefox
I have tried switching recoveries too. Nothing seem to work.
gursewak.10 said:
which recovery are you using
try changing recovery
check with orangefox
Click to expand...
Click to collapse
I have tried changing the recovery too. Same error.
try flashing stable fastboot rom with option flash all.
then flash orangefox recovery with fastboot and then try.
flashing fastboot rom will undo anything happened to any partition
Seemed like it would have worked
gursewak.10 said:
try flashing stable fastboot rom with option flash all.
then flash orangefox recovery with fastboot and then try.
flashing fastboot rom will undo anything happened to any partition
Click to expand...
Click to collapse
I already tried flashing the latest Fastboot image and then tried flashing again. It still doesn't work.
are you formatting data before flashing??
when you format data there is no residue left of previous roms.
try format data then flash fastboot rom with "flash all" and then install recovery, try orangefox .
Yes
gursewak.10 said:
try flashing stable fastboot rom with option flash all.
then flash orangefox recovery with fastboot and then try.
flashing fastboot rom will undo anything happened to any partition
Click to expand...
Click to collapse
gursewak.10 said:
are you formatting data before flashing??
when you format data there is no residue left of previous roms.
try format data then flash fastboot rom with "flash all" and then install recovery, try orangefox .
Click to expand...
Click to collapse
I first erased everything from wipe and then even removed system,data,cache from advance wipe and then flashed. Whenever I try to flash any rom, it fails at the manifest check and gives the above said error. I even tried flashing the latest firmware. Nothing seem to work for me and now I am stuck at Miui?.
Starksm said:
I first erased everything from wipe and then even removed system,data,cache from advance wipe and then flashed. Whenever I try to flash any rom, it fails at the manifest check and gives the above said error. I even tried flashing the latest firmware. Nothing seem to work for me and now I am stuck at Miui.
Click to expand...
Click to collapse
i guess the rom file you are trying to install is either corrupted or checking for something.
could you upload updater-script file from meta-inf/com/google/Android folder from the rom you are trying to flash which is giving this error.
Please find the screenshot attached.
gursewak.10 said:
i guess the rom file you are trying to install is either corrupted or checking for something.
could you upload updater-script file from meta-inf/com/google/Android folder from the rom you are trying to flash which is giving this error.
Click to expand...
Click to collapse
Btw every rom has that updater line that I have highlighted. If I remove the assert function from the updater, the rom will get flashed but I just want to know why the issue is happening.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/1-7X0FyJH37mjOxVZcpdnb-STaxM2V_BO/view?usp=drivesdk
Please find the screenshot attached.
https://ibb.co/9gCg59f
its for checking, so you cannot flash the rom over a very old version of the stock rom which makes flashed rom not work properly or not booting at all.
they build roms over a specific version on which they test to have it working fine during all phases.
so thats why developers have it to keep a check over version of the rom you are installing upon. so that it has no conflicts between integration in future for running the rom.
moreover i see the version of your rom is old and may have a new version ,so try to have an updated version of the rom which may flash fine.
I tried flashing the lastest today's built of mokee and still the same error
gursewak.10 said:
its for checking, so you cannot flash the rom over a very old version of the stock rom which makes flashed rom not work properly or not booting at all.
they build roms over a specific version on which they test to have it working fine during all phases.
so thats why developers have it to keep a check over version of the rom you are installing upon. so that it has no conflicts between integration in future for running the rom.
moreover i see the version of your rom is old and may have a new version ,so try to have an updated version of the rom which may flash fine.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-EJlMd23ZJXa-Q_G9GCnkAN1oXTPxyGT/view?usp=drivesdk
Starksm said:
https://drive.google.com/file/d/1-EJlMd23ZJXa-Q_G9GCnkAN1oXTPxyGT/view?usp=drivesdk
Click to expand...
Click to collapse
from what i know, mokee rom has a patch for that.
you need to install that patch first.
This ought to be firmware bug. try fw 9.9.3 or the global 11.0.5.0 fw. Might work.....
I thought that too
Roshin1401 said:
This ought to be firmware bug. try fw 9.9.3 or the global 11.0.5.0 fw. Might work.....
Click to expand...
Click to collapse
I tried flashing the latest firmware too but it still doesn't want to work.
there is one simple and easy solution for this "delete that line" and then flash.
Xiaomi firmware update about 65mb
xiaomifirmwareupdater.com
I have tried that already
[email protected] said:
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
It didn't work
Hey! thanks for helping with your solutions. My issue was solved by flashing the latest INDIAN MIUI FIRMWARE. I can now easily flash any rom without any problems. Thanks
Please, can you explain the process, because even I'm getting firmware update error while flashing PE10 even after flashing latest Indian firmware before flashing Custom ROM, Tried Official TWRP, Peter TWRP booth. This started after update of MIUI-11, There was no such issue with MIUI10.