Related
Hello. As you can see, I'm a new member here and I'm also a new Android user; I bought my Nexus S (GT-i9020A) last week.
After a few days, I started thinking about jailbreaking my phone(rooting in Android's case) but I'm not really sure where to start, what rooting/flashing/ROM/etc means so I am just dumbfounded.
I want to customize my phone, make it look cool, etc.
Help would be greatly appreciated, thanks a lot in advance
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
anremi said:
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
Click to expand...
Click to collapse
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
'one more thing', root =! jailbreak, for god sake! android is 'jailbreaked' by default! =o)
bringonblink said:
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
Click to expand...
Click to collapse
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
3doncrack said:
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
Click to expand...
Click to collapse
The rooting process is the same for 2.3.3 & 2.3.4.
Maximilian Mary said:
The rooting process is the same for 2.3.3 & 2.3.4.
Click to expand...
Click to collapse
okay. Does phone model matter? Like i9020A or i9020T etc.?
3doncrack said:
okay. Does phone model matter? Like i9020A or i9020T etc.?
Click to expand...
Click to collapse
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Maximilian Mary said:
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
zephiK said:
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
Click to expand...
Click to collapse
Pray tell what this difference is.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
Click to expand...
Click to collapse
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
Click to expand...
Click to collapse
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Maximilian Mary said:
Pray tell what this difference is.
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Click to expand...
Click to collapse
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
zephiK said:
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Click to expand...
Click to collapse
I could only find two differences between these guides. One is a patch for the 9023 drivers. I'm assuming Google has fixed this by now. (Can anyone confirm this?)
The other difference is the recoveries they use. Thanks to j_r0dd, you no longer need a separate recovery for the 9023.
Perhaps I should have said "Any up to date GSM Nexus S guide should work."
.
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
Click to expand...
Click to collapse
That is freaking cool. I'm going to unroot and try it. Do you need to do anything special in recovery, or just put the zip in the right place?
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
Click to expand...
Click to collapse
The xda app doesn't show post counts. I figured thumping you in the chest would cover all the bases.
Hello XDA Developers,
Okay so here is my unusual situation...
I have two phones. I have one Verizon (d2vzw) SGS3 that I run CM 11 on with CWM Touch installed on that phone. On my second phone which is also a Verizon (d2vzw) SGS3 i was running stock 4.1.2 ROM which was rooted with CWM recovery manager. The stock SGS3 was the baseband version that supported multi windows.
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3. I knew there had been an update available for some time but I never decided to update my phone because i figured with it being rooted and with CWM recovery manager installed there was no way that the OTA update would work...
So like an idiot i went ahead and tried the update. I figured what is the worst that could happen? I figured that at the worst it was just going to tell me that the update failed and i would just be stuck with Android 4.1.2 which isn't the end of the world. I really like the multi windows setup. Moving on...i downloaded the update and I hit the install update button. My phone booted into recovery manager and it installed the update. When the phone rebooted I saw the message "Android is upgrading" and i thought whoa! no way!. After android finished upgrading which i believe was the dalvik rebuilding I saw a message in notifications saying "upgrade installation failed", however when i went into settings it now told me that i was running Android 4.3. So to me it looked like the upgrade took but I think the problem was that when it asked me to flash the stock recovery there was an option in CWM to say no and i choose that to keep CWM recovery manager instead of the stock recovery manager. Maybe i should have let the update install the stock recovery manager...
Now i knew ahead of time that if this update worked I was going to loose root but again I didn't think it was that big of a deal since I could just re-root my phone and I would be on a newer Android version. I looked around for the best rooting option and I wanted to use Chainfire's CF-AutoRoot exploit but I know that if you do not have the bootloader unlocked that there is a chance of bricking your phone. So after some research (which i should have done before i updated my phone!) i saw that there was an exploit out called "saferoot.zip" and that you could root your phone running a windows.bat file or a shell script if you are in Linux. Even though the program is for SGS4 many users on XDA with SGS3 phones reported success with "saferoot". So i tried saferoot 2 times with no luck. Finally on the third attempt (3rd times a charm!) i was able to root my phone and SuperSU was able to "disable KNOX".
So i now had my Verizon SGS3 updated from Android 4.1.2 to Android 4.3 and I had successfully re-rooted my phone. I was feeling good...
Until I wanted to make sure that CWM Recovery Manager was still on my phone. I opened up the app "quickboot" and choose to boot into Recovery Manager this is where the trouble began...
When my phone booted into recovery mode i saw a big Yellow Triangle. Under this very scary yellow triangle it said that "Verizon has detected unauthorized software on this phone. Please turn off the phone and take it into your nearest verizon store". Other something along those lines...
I thought I was in big trouble...
I could not get the phone out of recovery mode. I tried pulling the battery but every time my phone rebooted it just kept going back into recovery mode. The trick to get out recovery mode was to hold down Volume Down + Home for a few seconds then press the power button. This brought me to a new menu and i was able to hit "cancel" on installing a new OS and it rebooted my phone back to its normal state.
So finally here is my questions...
Question 1: I know i need to unlock my bootloader again. After you apply an OTA update it re-locks your bootloader right? Does anyone know of a method of unlocking the bootloader with the Verizon (d2vzw) SGS3 baseband version I535VRUCML1 running on Android 4.3?
Before when my phone was running 4.1.2 I unlocked the bootloader with Odin and the app EZ-UNLOCK but i don't think EZ-UNLOCK is going to work with Android 4.3
Question 2: Is there a way to get rid of that message about Verizon has detected unauthorized software on this phone? Now I know that ChainFire has a Yellow Triangle Away app on the Google Play store and I will happily buy it but I know that in order for it to work you first must have your bootloader unlocked right? If i try to use that app with my bootloader in a locked state i could brick my phone permanently right?
Is there possibly any file or exploit i can flash with either Odin or the app "Flashify" so that I can unlock my bootloader. Has anyone here tried unlocking their bootloader on their SGS3 running 4.3 with the app "EZ-UNLOCK" ?
I am very concerned about damaging my phone which is a company work phone so if i mess it up i will be in deep trouble...
Oh, one last question...
Question 3: Since i got that yellow triangle message about unauthorized software when i tried to boot into recovery mode could it have possible been because CWM recovery was somehow deleted with the OTA update? After i was able to get out of recovery mode I used the app "ROM Manager" to install CWM Recovery Again hoping that I might have a recovery manager... Now ROM Manager says that CWM Touch was installed successfully but I am not sure since I am kind of scared to boot into recovery mode again until I unlock this bootloader.
If my recovery manager is being blocked until I get my bootloader unlocked could i use the app "flashify" if i need to flash any files?
I know my situation might be a bit unusual but I am really going to need some help on this and someones expertise advice.
I hope to hear from someone soon...
XDA Members, have a great New Years and make 2014 count!
I thank you all for your time and assistance.
-droidshadow
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, debloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
well that stinks...
podspi said:
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, unbloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
Click to expand...
Click to collapse
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
droidshadow said:
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
Click to expand...
Click to collapse
To bad you took the ota. There is a twrp flashable rom for stock 4.3. And no you can not have custom recovery.
droidshadow said:
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3...
Click to expand...
Click to collapse
There's no need to read any further than that.... Sorry to be another bearer of bad news, but if a phone is rooted and you want it to stay that way, "OTA" should be a term that you never, ever, ever even think about !
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
so what entails for the future of samsung phones?
landshark68 said:
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Difference is though, if you were to somehow screw up your car by customizing it you wouldn't try to take it back to the dealership and get a new car under a warranty claim. I would have to think at least part of the reason phone manufacturers and mobile carriers are locking down phones is all the "warranty" claims people are submitting after screwing up while rooting and flashing their phones. Warranty claims are for inherent manufacturer defects, not a hard brick from flashing the wrong software. If more people took responsibility for their mistakes and bought a new phone instead of making the carriers or manufacturers pay for their mistakes, perhaps this wouldn't be happening. I'm not saying absolutely, just perhaps. OK, I'll get off my soapbox now. Happy New Year everyone.
Different animal. You own the hardware, but the providers have the right to control the firmware since it can change how the phone interacts with the network.
Just like the firmware in your cars computer. The manufacturer and the federal government have control over what went in. Modifying it can be done, but it is a violation of EPA emission laws.
Modifying the paint, tires, rims etc is like putting a different case, bling etc on your phone
Your phone needs to have the 4.3 odin tar installed to clean the recovery.
Sent from my SCH-I535 using xda app-developers app
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
These phones are our property...
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using xda app-developers app
DigitalMD said:
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
Click to expand...
Click to collapse
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Insurance companies make big bucks by all the people who never file a claim...but i won't get into that.
Many of you have made excellent points and i respect that. I especially liked the comparison of car rims to phone cases i thought that was great!
Hopefully someone will work it out soon or some how an unlocked bootloader will get leaked.
Come one Verizon developers! Leak it! We wont tell!
I was planning on getting the NOTE 3 but i doubt that phone comes with an unlocked bootloader so this d2vzw (sgs3) will most likely be my last samsung phone that I ever buy. I guess i will have to stick with the Nexus phones... I am going to miss micro sdcards!
-droidshadow
droidshadow said:
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Click to expand...
Click to collapse
Having that debate at this site is kinda silly.... Fact is, "we" will lose the fight against the carriers and/or manufacturers as it stands. The only way to really impact them is to STOP giving them our money, but you know what ? The number of people who "hack" their phones is a tiny percentage in the grand scheme. We'd probably get a "good riddance" response from them anyway.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct and.... read on.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones?
Click to expand...
Click to collapse
That could be the only solution. I believe the success that Samsung/Verizon have had with locking down their phones will soon result in ALL phones on ALL carriers being locked down with little or no possibility of rooting or flashing.
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
It would be a shame....
xs11e said:
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
Click to expand...
Click to collapse
I just rooted and got into CM in the last month. Got rid of all the bloat and installed some neat little apps. And now, just when I get hooked, it's possible that my drug of choice may be going away.
hey there guys, i know this post is a little old, but i just wanted to share my story real quickly with you and to reiterate that messing with the boot loader on an sch-i535 running 4.3 is a HORRIBLE idea.
this is the first phone i have ever tried to root. i successfully rooted the phone, immediately i tried to run cwm recovery. HARDBRICK. i was so proud for all of five minutes that i rooted a phone on my first try. The phone would not power on in ANY mode. i could only get a red light to come on by plugging my phone into my computer with the battery out of the phone. after three days and alot of reading and some help from xda i managed to (amazingly) debrick my phone. I am now very VERY cautious of what i do with my rooted sch-i535 with its HORRIBLE 4.3 crap.
If you are truly hardbricked, im told that jigs (despite what is all over the internet) will not work. (maybe they do but a shop in texas told me a hardbrick will not revive by jig).
JTAG is the most dependable repair.
I revived my phone via debrick image on an sd card.
Bottom line, do everything you can to avoid the situation in the first place.
Never take updates. I unlocked boot loader on 4.3 with ez-unlock app booted into recovery and hard bricked my phone... The fun is over after 4.3...Had to send it to Tampa fl. To get JTAG and it worked.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
xs11e said:
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
Click to expand...
Click to collapse
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
An0nYm0u5.bat said:
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
Click to expand...
Click to collapse
I agree with you if there is a way to lock it there is a way to unlock it.
is just a matter of time some smart brain will figure it out how to and share LOL
Hello,
I am very new to the rooting community, I am above average as a computer user, but mobile programming/rooting is an uncharted territory for me-please forgive the simple nature of this post.
I have a Huawei H892L Raven LTE phone.
I got this phone for cheap, so I didnt mind experimenting with rooting (as a novice) with it because if i bricked it I could just go back to my S4 or note 3.
anyways I have looked all around, looked at other threads, watched videos and most of what I saw was kind of vague. i have grasped the basic concept (i think..) of rooting but some areas are still unclear.
1. I rooted my phone and now I want to make sure I have a backup of it before i proceed with doing much else with it. I have downloaded CWM recovery and some other recovery tools in hope to make a backup of my device. But most of them require premium accounts to make backup from what i can gather.
Using an app called ROM tool box lite > Rom Installer >I see the options to Backup current ROM, Backup Recovery, and Backup Kernel..
Now do I want to make a "backup of my current Rom"? Would this option backup the stock H89RL Raven LTE image that is currently on the phone? or is this feature mean it is used to backup a custom rom that say i downloaded, used on my phone, maybe tweeked a little bit and wanted to back up?"
or when I am backing up my Raven H892L stock image should i use the "Backup recovery" and "backup kernel" options? I used both of these, but I am not sure if those options will suffice as properly and safely giving me reassurance that if i mess up anything i can recover the original format of the phone.
sooo.. what exactly do I need to use and what steps do i need to take to reassure I can play with new root and be able to fix it should i mess up? what file format are proper backups of my phones current settings... .img? and what steps would I take to recovery the old image of the phone?
2. I also need some clarification about SuperUser and SuperSU apps. I used kingoroot and it installed kingo superuser on my phone. Which is the preferred superuser app I should use? if i delete the kingo superuser app will it take away my ability to easily unroot my phone via pc the same way i rooted it? (there is an option on kingoroot when i plug my phone into my computer to unroot) the only reason i kept Kingoroots superuse over superuserSU is because I wanted to make sure I could unroot. what exaclty is the purpose of these apps? to delegate permissions? or is there other uses for them?
3. custom roms- I want to put a custom rom on my phone. i do not see any custom roms for my specific mobile device, (obviously because many people do not have this device, i really didnt expect there to be) Is there, for a lack of better words a "universal," or a custom rom I could use that would be compatible with my device? Are most ROMS used for android not device specific. (Im really sorry if thats a really stupid question.) I dont really understand this. is there a custom rom you would suggest me using?
4. What are some useful tools or cool things that I can do with my newly rooted device? any suggestions? what are your favorite things to do with a rooted device? Am i kind of out of luck because of the specific device I have not being so popular? I'm being a huge newb here but I thought I would give this forum a try.
I really really appreciate you taking the time to read all that if you did!
Hello,
Welcome to XDA.
Ok, first, as far as I know you cannot make a backup without custom recovery. I have searched for a custom recovery for you but I did not find one anywhere in XDA or Google.
You will have to find a custom recovery(CWM or TWRP) for Huawei H892L if it exists anywhere and install it however the guide you find it in says to install it, the method used will depend on what file format your recovery file is, the method also varies from device brand to device brand. Recoveries are very specific things, the recovery for one device brand/model number does not work on another device brand/model number, sometimes recoveries can be shared by devices that are virtually identical in hardware/software but more than most of the time trying a recovery for one device on another results in a bricked device similar to flashing the wrong BIOS on a PC.
As for the superuser, superSU and kinguser, if you have Kinguser I recommend you use the supersume app from the playstore to switch to superSU, it does it for you. If at some point you choose to unroot, there is an option in the superSU app settings that lets you unroot and uninstall superSU and root is completely gone.
Custom ROMs are flashed in custom recovery, for copyright and trademark reasons most custom ROMs have to be flashed along with a compatible Google apps package, referred to as Gapps. They both come in .zip format. The Android version of your ROM and Gapps have to match, 4.4/4.4, 5.0/5.0, 5.1/5.1 etc.. The custom ROMs are also device brand/model specific and also can't be shared. No, there is no "universal" android ROM. You are correct that your device is not popular so you most likely won't find anything as far as custom ROMs and recoveries. You would have been better off rooting and customizing your S4(depending on your model number) or your Note 3, there is plenty available and they are actually much easier devices to work with, I love my Samsung devices, they are easily rooted and usually easy to fix if a modification goes wrong, the device you have will easily get messed up and would likely be almost impossible to fix.
Root gives you control over everything about the device, you can modify any and every part of your systems software to look and function how you choose it to do, you can even modify the apps you install or even add features that it didn't have before as long as your hardware supports it, for example my Straight talk S3 supports Hotspot and tether even though it didn't come with it, and that's just the least of the mods my device has.
For more answers to your questions you can post in the thread linked below, there are many knowledgeable members in that thread, including myself.
http://forum.xda-developers.com/showthread.php?t=2257421
Good luck in your journey, if you choose to customize one of your Samsung devices(which i personally recommend for someone new to this because they are easy to repair), they are virtually impossible to brick beyond repair unless you just completely lose your head and use something meant for another device and 95% of the time even that is fixable.
thank you so
Droidriven said:
Hello,
Welcome to XDA.
Ok, first, as far as I know you cannot make a backup without custom recovery. I have searched for a custom recovery for you but I did not find one anywhere in XDA or Google.
You will have to find a custom recovery(CWM or TWRP) for Huawei H892L if it exists anywhere and install it however the guide you find it in says to install it, the method used will depend on what file format your recovery file is, the method also varies from device brand to device brand. Recoveries are very specific things, the recovery for one device brand/model number does not work on another device brand/model number, sometimes recoveries can be shared by devices that are virtually identical in hardware/software but more than most of the time trying a recovery for one device on another results in a bricked device similar to flashing the wrong BIOS on a PC.
As for the superuser, superSU and kinguser, if you have Kinguser I recommend you use the supersume app from the playstore to switch to superSU, it does it for you. If at some point you choose to unroot, there is an option in the superSU app settings that lets you unroot and uninstall superSU and root is completely gone.
Custom ROMs are flashed in custom recovery, for copyright and trademark reasons most custom ROMs have to be flashed along with a compatible Google apps package, referred to as Gapps. They both come in .zip format. The Android version of your ROM and Gapps have to match, 4.4/4.4, 5.0/5.0, 5.1/5.1 etc.. The custom ROMs are also device brand/model specific and also can't be shared. No, there is no "universal" android ROM. You are correct that your device is not popular so you most likely won't find anything as far as custom ROMs and recoveries. You would have been better off rooting and customizing your S4(depending on your model number) or your Note 3, there is plenty available and they are actually much easier devices to work with, I love my Samsung devices, they are easily rooted and usually easy to fix if a modification goes wrong, the device you have will easily get messed up and would likely be almost impossible to fix.
Root gives you control over everything about the device, you can modify any and every part of your systems software to look and function how you choose it to do, you can even modify the apps you install or even add features that it didn't have before as long as your hardware supports it, for example my Straight talk S3 supports Hotspot and tether even though it didn't come with it, and that's just the least of the mods my device has.
For more answers to your questions you can post in the thread linked below, there are many knowledgeable members in that thread, including myself.
http://forum.xda-developers.com/showthread.php?t=2257421
Good luck in your journey, if you choose to customize one of your Samsung devices(which i personally recommend for someone new to this because they are easy to repair), they are virtually impossible to brick beyond repair unless you just completely lose your head and use something meant for another device and 95% of the time even that is fixable.
Click to expand...
Click to collapse
I really appreciate you taking the time to reply to my questions, and so thoroughly too! And that sounds like a good idea, I am going to just root my S4 and use that for a beginners root device. Nice to know it will be hard to mess that up. so i will download supersume and switch over to superSU automatically.. I also have straight talk, is it really possible to make my s4 a hotspot?? i heard something about that, but also heard something about straight talk being fussy about it? is there a way they would even know, by analyzing data intake maybe? idk where i heard that from. but Anyways. thanks for all the info. I think I will stick around in these forums and gather information and maybe ask for help if I need it.
Have a good night
k
kwotkwot said:
I really appreciate you taking the time to reply to my questions, and so thoroughly too! And that sounds like a good idea, I am going to just root my S4 and use that for a beginners root device. Nice to know it will be hard to mess that up. so i will download supersume and switch over to superSU automatically.. I also have straight talk, is it really possible to make my s4 a hotspot?? i heard something about that, but also heard something about straight talk being fussy about it? is there a way they would even know, by analyzing data intake maybe? idk where i heard that from. but Anyways. thanks for all the info. I think I will stick around in these forums and gather information and maybe ask for help if I need it.
Have a good night
k
Click to expand...
Click to collapse
As long as your S4 doesn't have a locked bootloader you should be fine, if its locked then you'll likely brick it trying anything, post me your model numbers for both the S4 and the Note 3 and I'll see what is out there before you do anything.
Sent from my SCH-I535 using Tapatalk
The note is in my storage two hours away. it also has a crack on the screen so will hold off on that.
But the s4 model number is SCH-I545
Sent from my HUAWEI H892L using XDA Free mobile app
kwotkwot said:
The note is in my storage two hours away. it also has a crack on the screen so will hold off on that.
But the s4 model number is SCH-I545
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, the i545 is one that is a pain, what firmware version does it have? Is it easy to get to? If it's one of the versions with locked bootloader you can root it possibly but custom recovery and custom ROMs is absolutely out of the question. With locked bootloader you'll be stuck with using Safestrap and modified stock ROMs.
Sent from my SCH-I535 using Tapatalk
Android version 5.0.2
Secure boot status says type; samsung
How exactly do you check the firmware, I was under the impression that is was Android version.
Sent from my HUAWEI H892L using XDA Free mobile app
I also have a Motorola droid razr Android version 4.1.2 may be worth considering. I'll do some investigating on whether I can root it. Thanks for conversing with me, I am starting my second degree in the spring. I will be taking computer programming, and i Can't wait to get to the mobile side of the curriculum. Hopefully I will be ahead of the game by then XD
Sent from my HUAWEI H892L using XDA Free mobile app
kwotkwot said:
Android version 5.0.2
Secure boot status says type; samsung
How exactly do you check the firmware, I was under the impression that is was Android version.
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure this isn't 5.0.1? i'm finding i545 root for 5.0.1 but no 5.0.2.
The thread below is root for 5.0.2
http://forum.xda-developers.com/galaxy-s4-verizon/general/rooted-galaxy-s4-t3158098
you"ll have to ask about the bootloader and whether or not you have to use custom recovery(CWM, TWRP) or Safestrap in the i545 forum linked below.
http://forum.xda-developers.com/galaxy-s4-verizon/help
Be careful, I have tried to repair an i545 that had been flashed with TWRP over the locked bootloader, there is no saving it if this is done, be certain of what you have before you do anything, either way isn't too difficult you just have to be sure of which way you have to go.
Exactly which razr model number do you have?
It is 5.0.1 my fault! I was looking right at it too. So the secure boot status=Samsung means the boot loader is definately locked?
On The Razr i have I can't read the model number its scratched on the back..any way to tell via the settings? Maybe xt912? Its not the RAZR max...idk I can't make it out. In the settings it says
Mod number= Droid Razr
Android version = 4.1.2
Baseband version CDMA_N_05.21.00RLTEDC_U_09_.1D.00
Build number 9.8.20-72_VZW-16
Sorry for the questions.
I think this phone is rootable. Def needs a new screen. BTW I'm in NC too. Kitty Hawk NC on the beach
Sent from my HUAWEI H892L using XDA Free mobile app
correction it is 5.0.1
okay MOTXT912W is the model number. i just ordered a replacement screen for it, maybe ill make this badboy my new phone if a root is possible.
Im stressed out thinking about my note 3.. i really hope its in storage, the more i think about it the more I wonder if it got thrown out by my gf bc the screen was trashed.
sure hope not i miss that thing. but im going back to my storage unit maybe this week ill rummage through and see if i can find it.
surely one of my many phones can accept custom roms!
kwotkwot said:
It is 5.0.1 my fault! I was looking right at it too. So the secure boot status=Samsung means the boot loader is definately locked?
On The Razr i have I can't read the model number its scratched on the back..any way to tell via the settings? Maybe xt912? Its not the RAZR max...idk I can't make it out. In the settings it says
Mod number= Droid Razr
Android version = 4.1.2
Baseband version CDMA_N_05.21.00RLTEDC_U_09_.1D.00
Build number 9.8.20-72_VZW-16
Sorry for the questions.
I think this phone is rootable. Def needs a new screen. BTW I'm in NC too. Kitty Hawk NC on the beach
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
OK, I'll check the moto out by the specs you listed.
I've never been to Kitty Hawk. I always wanted to go and see where flight was born.
Sent from my SCH-I535 using Tapatalk
The ordered a new digitizer\glass\blackframe and an eb20 battery too for the xt912 Razr.. But I'm thinking about doing the RAZR maxx conversion and putting an Eb40 battery on it. I know someone named wando Did it on these forums, exciting stuff.
Sent from my HUAWEI H892L using XDA Free mobile app
Yeah I actually went to first flight highschool. You should visit its nice even in the winter!
Sent from my HUAWEI H892L using XDA Free mobile app
kwotkwot said:
The ordered a new digitizer\glass\blackframe and an eb20 battery too for the xt912 Razr.. But I'm thinking about doing the RAZR maxx conversion and putting an Eb40 battery on it. I know someone named wando Did it on these forums, exciting stuff.
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
I've never had a RAZR, never heard of that mod.
Sent from my SCH-I535 using Tapatalk
Basically taking the RAZR Maxx battery (3300 mAh, eb40) and replacing the regular RAZR xt912 battery (1900 mAh eb20) with it. Making it essentially a RAZR max
Sent from my HUAWEI H892L using XDA Free mobile app
Hi everyone,
I am giving this phone to my mom since I don't need it anymore (bought Samsung S6 few months ago)! Phone is currently on Android 4.4.4 kangkat 5.1 and is customised pretty nicely( no Ads, working fast , no FC ,pretty snappy).
Should I update to Marshmallow before I give it to her or should I just leave it the way it is? She is just the regular user and will not use anything more that dialer, sms, browser, weather, calendar, calculator, camera, etc.. So just basic apps and I will strip this phone to bare minimum but was just wondering should I get her Android 6 on this (at least battery live maybe inproved?)
Any thoughts or ideas will be appreciated.
If you have the knowledge to do it, then yes, it's probably worth installing MM as stock and leaving it like that - no custom recovery, no root. That way she can get the regular security updates with the minimum of fuss. The uninterested user doesn't need the hassle of a rooted device. And easier for you in not having to strip the phone - a new installation will do that for you anyway, and will allow her to sign in as herself and properly own the phone.
dahawthorne said:
If you have the knowledge to do it, then yes, it's probably worth installing MM as stock and leaving it like that - no custom recovery, no root. That way she can get the regular security updates with the minimum of fuss. The uninterested user doesn't need the hassle of a rooted device. And easier for you in not having to strip the phone - a new installation will do that for you anyway, and will allow her to sign in as herself and properly own the phone.
Click to expand...
Click to collapse
I do have knowledge (well maybe I might remind myself a little using Google). I am running Xposed on this build and like I've said phone is super stable with this build but also pretty simple to use for basic /regular user. Future updates are just going to confuse her.. The only thing I would like for her is maybe improved battery live and that's why I would go to MM. I was also thinking to maybe get new battery on this one(don't know how hard is to change it?). Anyway thanks for responding ,
Flash latest 6.0.1 MM on it and lock bootloader... give it to her barebones and let her enjoy it...
just did that with my oldest brother who lost his phone to a muggin.... and its the easiest way for them to stay up to date on latest security patches, etc
"maybe get new battery on this one(don't know how hard is to change it?)"
It's actually pretty simple: https://www.youtube.com/watch?v=VSGNUrpwIno
Though there's another thread that I read just today that shows there's a certain risk: http://forum.xda-developers.com/google-nexus-5/help/nexus-doesnt-boot-fastboot-t3282033
chaco81 said:
Flash latest 6.0.1 MM on it and lock bootloader... give it to her barebones and let her enjoy it...
just did that with my oldest brother who lost his phone to a muggin.... and its the easiest way for them to stay up to date on latest security patches, etc
Click to expand...
Click to collapse
I actually never gone back to stock so I don't know how hard is it and how time consuming is it? I am on TW recovery v2.7.0.0. should I just flash nandroid or do I have to flash factory image first and than lock bootloader?
dahawthorne said:
"maybe get new battery on this one(don't know how hard is to change it?)"
It's actually pretty simple: https://www.youtube.com/watch?v=VSGNUrpwIno
Though there's another thread that I read just today that shows there's a certain risk: http://forum.xda-developers.com/google-nexus-5/help/nexus-doesnt-boot-fastboot-t3282033
Click to expand...
Click to collapse
You are right , I am not going to mess with battery replacement. The old one should be OK for some time ...
I would also not bother relocking the bootloader. How many threads in these forums contain wails from people who have cacked their devices and there is no way to recover because the bootloader is locked?
This thread actually refers to the Nexus 6, but since Nexus devices are so similar in many ways it's probably still relevant, and should put you off taking this unnecessary step: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Stock is extremely simple. Download the factory image (Google "factory image"), unzip and run flash-all - obviously after you've got all your drivers set up to communicate with the device. If you haven't yet, I'll bore you again with recommending Wugfresh's Nexus Root Toolkit, which has a really helpful button to walk you through the driver setup. If the flash-all script doesn't work (it doesn't for some people), you can unzip all the components, put them in your ADB/fastboot directory and flash each component separately.
dahawthorne said:
I would also not bother relocking the bootloader. How many threads in these forums contain wails from people who have cacked their devices and there is no way to recover because the bootloader is locked?
This thread actually refers to the Nexus 6, but since Nexus devices are so similar in many ways it's probably still relevant, and should put you off taking this unnecessary step: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Stock is extremely simple. Download the factory image (Google "factory image"), unzip and run flash-all - obviously after you've got all your drivers set up to communicate with the device. If you haven't yet, I'll bore you again with recommending Wugfresh's Nexus Root Toolkit, which has a really helpful button to walk you through the driver setup. If the flash-all script doesn't work (it doesn't for some people), you can unzip all the components, put them in your ADB/fastboot directory and flash each component separately.
Click to expand...
Click to collapse
I just updated Wugfresh Nexus Root Toolkit since I had old version on my laptop. Should I use RESTORE/UPGRADE/DOWNGRADE option and than FLASH STOCK + UNROOT?
P.S. DONE.. Running MM now on it.
Thank you all
roundel.... easy to do
make sure u have latest ADB installed on your PC.... so open SDKManager and run it so it updates...
download the latest Factory Image
extract the image, place it on the platform tools folder of your SDK and double click the flash.all.bat file... let the magic happen
google returning back to stock, there are tons of tutorials out there showing how to do this.
chaco81 said:
roundel.... easy to do
make sure u have latest ADB installed on your PC.... so open SDKManager and run it so it updates...
download the latest Factory Image
extract the image, place it on the platform tools folder of your SDK and double click the flash.all.bat file... let the magic happen
google returning back to stock, there are tons of tutorials out there showing how to do this.
Click to expand...
Click to collapse
I did it and phone is running MM now. I am amazed with battery life now, it is crazy good comparing to KK!
So I am now back to stock unrooted but I left bootloader unlocked. Will she (my mom) get any updates if this Nexus get OTA updates?
A stock unrooted rom with stock recovery is all that is needed for ota updates. The bootloader can remain unlocked for ota updates.
Update it now and give her. I was doing the same stuff with my mom and she denied which then later made me try this phone out. Overall it's good but battery sucks.
I recently updated to marshmallow, and am currently trying everything to root it. I have done everything from trying to unlock bootloader in fastboot, to using apps such as kingroot and framaroot.... to no avail... can anyone help? It would be much appreciated!! Thanks!!!
I know you can't really do anything using MM, but can anyone help me flash stock firmware on my device? (I AM USING LINUX!!) I tried running the windows programs with wine.... Did not work...
Dropped my previous 6045O, Cricket variant on its screen on a bunch of gravel and cracked the screen. Since I am a klutz, I had taken out the insurance/phone replacement with Asurion. Received my replacement, and discovered it was loaded with MM, only, as others have noted, the fastboot commands are not there....
I've tried all the methods folks have offered, and, apparently Cricket is in collusion with Alcatel not to make it merely difficult to root and administer (worked entirely too many tech-support gigs... the uninformed tend to screw things up even with documentation), but to make it, seemingly at present, impossible. I'm stuck, and none of the previous methods have worked. (and, yes, I've read every applicable thread I see... at this point, nothing seems to work to root the beast. Since the ability's there by default to shove the apps that will allow themselves to be shoved to my 32GB SD.... that gets rid of my need for Link2SD, until the gentleman, Bulent Akpinar, gets around to recognizing that Marshmallow's been out a while. (paid for the Plus, and completely unusable, even as a widget, with the new Cricket variant of 6.0.1
I've tried the ROOT .rar, our other gentleman's Suite, and the various methods, and at this point, I'm just kinda lost.
pauljulian said:
Dropped my previous 6045O, Cricket variant on its screen on a bunch of gravel and cracked the screen. Since I am a klutz, I had taken out the insurance/phone replacement with Asurion. Received my replacement, and discovered it was loaded with MM, only, as others have noted, the fastboot commands are not there....
I've tried all the methods folks have offered, and, apparently Cricket is in collusion with Alcatel not to make it merely difficult to root and administer (worked entirely too many tech-support gigs... the uninformed tend to screw things up even with documentation), but to make it, seemingly at present, impossible. I'm stuck, and none of the previous methods have worked. (and, yes, I've read every applicable thread I see... at this point, nothing seems to work to root the beast. Since the ability's there by default to shove the apps that will allow themselves to be shoved to my 32GB SD.... that gets rid of my need for Link2SD, until the gentleman, Bulent Akpinar, gets around to recognizing that Marshmallow's been out a while. (paid for the Plus, and completely unusable, even as a widget, with the new Cricket variant of 6.0.1
I've tried the ROOT .rar, our other gentleman's Suite, and the various methods, and at this point, I'm just kinda lost.
Click to expand...
Click to collapse
Nobody searches the forums anymore ,it has been discussed in depth in many threads, you need to downgrade using eluga switch firmware to get back unlocked bootloader n fastboot, then install TWRP and then you can pick whatever rom you like... If you want stock MM with TWRP use the marionettes v1 MM rom, you loose LTE after using Eluga so you need to fix that also I have posted this link several times read all the threads attached and you will get there
http://forum.xda-developers.com/ido...de-mm-to-install-custom-t3475961/post69028659
kal250 said:
Nobody searches the forums anymore ,it has been discussed in depth in many threads, you need to downgrade using eluga switch firmware to get back unlocked bootloader n fastboot, then install TWRP and then you can pick whatever rom you like... If you want stock MM with TWRP use the marionettes v1 MM rom, you loose LTE after using Eluga so you need to fix that also I have posted this link several times read all the threads attached and you will get there
http://forum.xda-developers.com/ido...de-mm-to-install-custom-t3475961/post69028659
Click to expand...
Click to collapse
Actually I did search before posting my comment, and I have the Eluga executable... after expanding it and trying to do the deed, it doesn't see the phone... I've got the OEM unlocking enabled in the Dev. options on my device...
I admit, though, I may not be doing something correctly, and will try it again.
--- edit ---
Silly me... didn't remember I had to have the phone off... for that matter, since it was a while ago that I rooted the previous one, and that it was running Lollipop 5.0.2, I didn't have to jump through as many hoops as with 6.0.1... Alcatel and Cricket don't make it impossible to do with this phone, as Cricket seems to specify with the ZTE device, and the LG Stylo... Just difficult, but not impossible. Working on it as we speak, and will respond in a bit.
BTW... was a little snarky that no one reads the columns... I obviously missed a few things, but I have read... just sayin'...
pauljulian said:
Actually I did search before posting my comment, and I have the Eluga executable... after expanding it and trying to do the deed, it doesn't see the phone... I've got the OEM unlocking enabled in the Dev. options on my device...
I admit, though, I may not be doing something correctly, and will try it again.
Click to expand...
Click to collapse
Is the phone off? You must have phone off so it can go into download mode.
kal250 said:
Is the phone off? You must have phone off so it can go into download mode.
Click to expand...
Click to collapse
Been referring to Alek Dev's (and others') instructions, have booted into the Panasonic rom, in the process of erasing, and will flash the rest going forward.
Thanks for the links, and I admit a "Doh!" about how to go into download mode... a few devices I'm kinda maintaining around here, and each seems to have a different button process to get there.
Thanks again, and I think I've got it from this point (with multiple tabs up in my browser for reference, of course...)
pauljulian said:
BTW... was a little snarky that no one reads the columns... I obviously missed a few things, but I have read... just sayin'...
Click to expand...
Click to collapse
Sorry, if I seemed rude, been dealing with a few foster children, who want to push every button I have, lol teens.... was just in vent mode I guess....
No need to downgrade to LP, use Alcatel Flasher to flash twrp
Look at this: http://forum.xda-developers.com/idol-3/development/tool-sahara-firehose-test-alcatel-t3454855
install twrp and roo with supersu.zip. That all.
murigny64 said:
No need to downgrade to LP, use Alcatel Flasher to flash twrp
Look at this: http://forum.xda-developers.com/idol-3/development/tool-sahara-firehose-test-alcatel-t3454855
install twrp and roo with supersu.zip. That all.
Click to expand...
Click to collapse
Isn't that still in beta status as test only? The dev has discontinued development?? I have never tried it as I believed it was just still conceptual... I will look into it further..... Was flashing ever implemented??
kal250 said:
Isn't that still in beta status as test only? The dev has discontinued development?? I have never tried it as I believed it was just still conceptual... I will look into it further..... Was flashing ever implemented??
Click to expand...
Click to collapse
No, it's not a test, it work. You can read/write boot and recovery on 6039, 6045 and 6055 for all variants
Look at new howto made by decker.su: http://forum.xda-developers.com/idol-4s/help/howto-idol-4-6055-installing-twrp-t3486077
You Just have to choose "6045" in the app and twrp recovery for 6045
I used the Panasonic eluga software lol.... That program didn't work for me at all...