Related
I am using a Nexus 5, and I tried to flash the CyanogenMod 11s from OnePlus One to my Nexus following instructions from here:
http://www.ibtimes.co.uk/nexus-5-gets-port-cyanogenmod-11s-featuring-android-4-4-4-1458608
My phone was not rooted, I performed a root and apparently succeeded, because I saw SuperSU installed on my device. I then proceeded to follow the instructions from the site mentioned above, performed a factory reset, and selected the ROM I downloaded to flash. The flashing failed and I am currently stuck in bootloop, afraid to proceed further and brick my phone.
Some of the signs I noted with my phone:
At the ROM installation screen, it says 'checking for MD5 file... Skipping MD5 check: No MD5 file found', 'symlink: some symlinks failed', ' E: Error executing updater binary in zip '/sdcar', and 'Error flashing zip '/sdcard/CyanogenMod_11S_ham'
At Reboot menu, upon tapping on 'Recovery' option it says 'No OS installed! Are you sure you wish to reboot?'
Please help me out, I'm sick at the moment, guess it is not a good idea to flash a ROM when you're sick huh? Been trying to find a solution and can't seem to find it, not sure if because I'm sick and too tired to read through or there really isn't a situation like this...
Thank you!
first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it. second option, flash the factory img via fastboot while youre in the bootloader. it has nothing to do with being sick, it has everything to do about learning all about your device and how to take care of it, before you start modding your device.
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
I build my own ROM even when I'm sick, what do you mean?
Try redownloading as it had flashing issues before
jackhayden said:
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
Click to expand...
Click to collapse
no, you didnt actually. you could have had a bad download, that happens often enough(but i dont think its the case, as it wouldnt remove your rom), you also could have experienced a recovery bug, that also can happen from time to time. btw, did you mention which recovery youre using?
I'm using TWRP.
jackhayden said:
I'm using TWRP.
Click to expand...
Click to collapse
well, try to download it again, and push it to your drvice with adb, then reflash it. or try pushing another rom. or, you always have the failsafe of flashing the factory img. btw, did you happen to make a backup in recovery before you flashed? you should always make a backup in recovery if flashing something new, just in case. in your case, it would make thing extremely easy.
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
jackhayden said:
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
Click to expand...
Click to collapse
you need to bring up the ui for typing.. on my old windows computer at work, i find an empty space on the same page that adb is located on your computer, then i left click and press the shift button on that empty space, then i get a few option that pop up, and i press the option. but im using windows from like 2004-5, lol.
Wow, that's really old.
I saw one of the commands available is 'adb push 'file name', should I try that?
Sorry for the troubles!
yup. first do "adb devices" to make sure adb sees your phone.
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
jackhayden said:
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
Click to expand...
Click to collapse
is the rom zip in the same folder as adb is located? it should be if not. and did adb see your device in with adb devices?
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
jackhayden said:
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
Click to expand...
Click to collapse
hmm.. well, i dont know that error, ive never seen it
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
Flash gapps
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
"first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it."
as @Lethargy said, gapps(google apps), you need to flash them. the google apps are not open source, they are owned by google, and cm isnt allowed to add them to the rom. but you are allowed to flash them separately
Thanks a lot for all the helps given. Really appreciate them! :good:
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
broderp said:
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
Click to expand...
Click to collapse
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
ebonit said:
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
Thanks. As simple as the process was, as a noob (first time attempting this) I was really concerned about screwing this up and bricking my tablet.
The one you linked to was one of the ones I was considering and hence my question regarding what works with what I have already done. The noob mind (mine anyways) finds a dozen questions at every turn. In this case I would ask the following:
Q-Do I have to use Kang TWRP?
Q-How is it different than the TWRP I used on my Tablet?
Q-Will I need to constantly change TWRP versions depending on what ROM I want to use?
Q-Is there a danger to switching TWRPs?
Q-Doesn't flashing SuperSU after I flash Gapps overright and erase SuperSU or is there some unique way to flash (push?) both at the same time?
Q-Many more I'm sure!
To the noob, almost all the instructions I read appear to be written for someone who as done this many times. The level of detail needed for the novice is just not there or lost between the jargon used, with many steps not fleshed out because the author assumes a certain level of expertise.
I will definitely read these threads as best I can, but in the interim, is there any ROM that are known to be able to be flashed via the TWRP I currently have? The author of the version I used certainly made it seem like it was that simple, load the ROM/ zip file onto the MicroSD card and when in Custom recovery simply use the INSTALL feature to navigate to the file and press a button to flash and ..."BAM!!" you are running a new ROM.
ebonit said:
...
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
broderp said:
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
broderp said:
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
ebonit said:
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
Click to expand...
Click to collapse
Sorry, bad choice of words on my part. By dead I meant that the thread was closed and I'm concerned getting answers would be harder as the OP was no longer actively looking there for questions.
ebonit said:
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
Click to expand...
Click to collapse
Ok, so if I read your comment correctly, I can copy the .img file to an SD card, boot into recovery and flash it from there OR I can fire up fastboot and the same steps I originally did to install custom recovery from my PC to accomplish the same thing... either way I should still have custom recovery, but with the KANG version. Right?
THANKS TO BOTH OF YOU FOR RESPONDING TO MY PREVIOUS POST. I appreciate the support.
Oh no....
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
EDIT: After I cleaned my pants, I used abd and fastboot to flash the original Blob file using my PC. This restored the custom recovery. I was freaking out for a few minutes.
I didn't change the file name of the kang .img file. Should I have done something different?
EDIT: Successful recovery to Kang2.8.7.2 !! :good::good: I used adb and my PC to send the .img file (renamed "twrpkang.img" for simplicity) and it worked great. I'm a pro..:silly:
broderp said:
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
Click to expand...
Click to collapse
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
ebonit said:
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
Click to expand...
Click to collapse
Not sure what I did wrong. I tried to do it within the old recovery menu and it hosed it. It found the file and mounted it successfully, but it seemed weird to be within the partition I was overwriting and writing to it. Kind of like you cant install windows while your using Windows...
The new version is much smoother.... Thanks, not to learn about this gapps super SU and how to flash all of these and in what order along with the ROM..as well as this wipe vs format thing...so confusing...
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Joselito.98 said:
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Click to expand...
Click to collapse
You need to downgrade, only with rom if someone have it.
persona78 said:
You need to downgrade, only with rom if someone have it.
Click to expand...
Click to collapse
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Joselito.98 said:
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Click to expand...
Click to collapse
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
persona78 said:
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
Click to expand...
Click to collapse
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Joselito.98 said:
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Click to expand...
Click to collapse
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
magus7091 said:
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
Click to expand...
Click to collapse
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
persona78 said:
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
Click to expand...
Click to collapse
If I have adb and fastboot, with kingroot not working
Now I make a video
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
kt-Froggy said:
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
Click to expand...
Click to collapse
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Joselito.98 said:
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Click to expand...
Click to collapse
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
But does it work with android 6?
And if I get the same error?
Hello ? Can someone help me please
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
Hello, I followed all the steps of this post, but there is a problem, idol 3 6045Y, there is no download mode, as you did
regards
PS: Thank you
Hi, why are not I going? I tried the sahara and firehose
I do everything well does not come out, no error, but at the time of starting the recovery leaves the factory.
I tried that twrp and also several more, but being all ok, I do not know why it's not going
regards
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
And what about the flashtool?
regards
Joselito.98 said:
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
Click to expand...
Click to collapse
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
kt-Froggy said:
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
Click to expand...
Click to collapse
Here you have all the procedure "well done" of how to download twrp with the sahara, and you will see that it does not work ...
https://vimeo.com/210311115
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said