I just got my ZenFone AR a few days ago and must say I am very impressed. I'm not sure what kind of traction this phone will get because of its high price and the fact that Asus phones are really not too much of popular mainstream products compared to other brands.
But the overall visual hardware specs (native 23MP stills with Sony's new IMX318 sensor and capable of up to 92MP stacked super-resolution still photos), 8GB RAM and AR capabilities of this hardware is absolutely unmatched at this point in time.
This is a very special product, by far the most exciting phone I've seen rolling out this year! I'm working on a full review of the phone and will post it soon along with photo samples at full resolution.
I'd hope to see people joining into getting root and a recovery for this. Ready to contribute to the development and getting things cookin' asap
VeEuzUKY said:
I just got my ZenFone AR a few days ago and must say I am very impressed. I'm not sure what kind of traction this phone will get because of its high price and the fact that Asus phones are really not too much of popular mainstream products compared to other brands.
But the overall visual hardware specs (native 23MP stills with Sony's new IMX318 sensor and capable of up to 92MP stacked super-resolution still photos), 8GB RAM and AR capabilities of this hardware is absolutely unmatched at this point in time.
This is a very special product, by far the most exciting phone I've seen rolling out this year! I'm working on a full review of the phone and will post it soon along with photo samples at full resolution.
I'd hope to see people joining into getting root and a recovery for this. Ready to contribute to the development and getting things cookin' asap
Click to expand...
Click to collapse
You'll never see root if you're on VZW, but I'm shocked no one has unlocked any other variant yet
HipKat said:
You'll never see root if you're on VZW, but I'm shocked no one has unlocked any other variant yet
Click to expand...
Click to collapse
I assume that this means it is not unlockable via fastboot. If so, that is going to be up to Asus. I don't think anyone is likely to work on hacking it unless it becomes much more popular. Asus does have a fairly good record of releasing an unlock tool after the device has been available for some time.
You could ask them if they are going to release an unlock tool.
crpalmer said:
I assume that this means it is not unlockable via fastboot. If so, that is going to be up to Asus. I don't think anyone is likely to work on hacking it unless it becomes much more popular. Asus does have a fairly good record of releasing an unlock tool after the device has been available for some time.
You could ask them if they are going to release an unlock tool.
Click to expand...
Click to collapse
It's not unlockable because of Verizon. Verizon has locked bootloaders on all their newest devices this year. Asus has nothing to do with it if you're on Verizon.
HipKat said:
It's not unlockable because of Verizon. Verizon has locked bootloaders on all their newest devices this year. Asus has nothing to do with it if you're on Verizon.
Click to expand...
Click to collapse
That was in response to the comment: I can't believe no one has unlocked any other variant. Verizon is Verizon.
HipKat said:
It's not unlockable because of Verizon. Verizon has locked bootloaders on all their newest devices this year. Asus has nothing to do with it if you're on Verizon.
Click to expand...
Click to collapse
Verizon has been locking down there phone for years. But if you take a lil time and look through the forms , some of them have root anyway the pixel and pixel xl and Samsung galaxy s8+ have root . It's all up to how much the development community want to mess with said phone. Not saying our ZenFone ar on Verizon will get root but it could.
Sent from my ASUS_A002A using Tapatalk
zman2107 said:
Verizon has been locking down there phone for years. But if you take a lil time and look through the forms , some of them have root anyway the pixel and pixel xl and Samsung galaxy s8+ have root . It's all up to how much the development community want to mess with said phone. Not saying our ZenFone ar on Verizon will get root but it could.
Sent from my ASUS_A002A using Tapatalk
Click to expand...
Click to collapse
I'll keep my fingers crossed but some good phones never got root, either, like the Moto Z Force, for one. I hope so just so I Can edit my mixer_paths and maybe actually hear the person I'm talking to on the phone
HipKat said:
I'll keep my fingers crossed but some good phones never got root, either, like the Moto Z Force, for one. I hope so just so I Can edit my mixer_paths and maybe actually hear the person I'm talking to on the phone
Click to expand...
Click to collapse
Root without breaking Tango or Daydream would be awesome, a phone that might finally slow down my wanderlust in the Android world, LOL....
Sent from my LG G2 using XDA Labs
recovery
VeEuzUKY said:
I just got my ZenFone AR a few days ago and must say I am very impressed. I'm not sure what kind of traction this phone will get because of its high price and the fact that Asus phones are really not too much of popular mainstream products compared to other brands.
But the overall visual hardware specs (native 23MP stills with Sony's new IMX318 sensor and capable of up to 92MP stacked super-resolution still photos), 8GB RAM and AR capabilities of this hardware is absolutely unmatched at this point in time.
This is a very special product, by far the most exciting phone I've seen rolling out this year! I'm working on a full review of the phone and will post it soon along with photo samples at full resolution.
I'd hope to see people joining into getting root and a recovery for this. Ready to contribute to the development and getting things cookin' asap
Click to expand...
Click to collapse
It would be awesome to know how to put the Verizon variant into recovery mode using the button combos as I have tried everything suggested with fail at every turn.
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
HipKat said:
I'll keep my fingers crossed but some good phones never got root, either, like the Moto Z Force, for one. I hope so just so I Can edit my mixer_paths and maybe actually hear the person I'm talking to on the phone
Click to expand...
Click to collapse
any idea on how to get the Verizon variant Asus Zenfone AR into recovery mode using the button combos?
corona63976 said:
It would be awesome to know how to put the Verizon variant into recovery mode using the button combos as I have tried everything suggested with fail at every turn.
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
any idea on how to get the Verizon variant Asus Zenfone AR into recovery mode using the button combos?
Click to expand...
Click to collapse
No, but mine froze up today, completely. For hours it would do nothing except occasionally the captive buttons would like up. I was freaking out, but I found out, hold power and vol down and it did a hard reboot and was fine.
HipKat said:
No, but mine froze up today, completely. For hours it would do nothing except occasionally the captive buttons would like up. I was freaking out, but I found out, hold power and vol down and it did a hard reboot and was fine.
Click to expand...
Click to collapse
You can get to fastboot mode by powering off the device then press volume down and power at the same time. If you need to clear cache you have to have sdk installed on your PC or the quick install ADB. open command prompt on your pc by pressing shift + right click type: fastboot devices when it comes back with your device type: fastboot oem reboot-recovery just like that. it will reboot to recovery then you can clear cache. Thank you.
corona63976 said:
You can get to fastboot mode by powering off the device then press volume down and power at the same time. If you need to clear cache you have to have sdk installed on your PC or the quick install ADB. open command prompt on your pc by pressing shift + right click type: fastboot devices when it comes back with your device type: fastboot oem reboot-recovery just like that. it will reboot to recovery then you can clear cache. Thank you.
Click to expand...
Click to collapse
Oh yeah, duh. Since this is the first Android I've ever had that was not rooted I didn't even consider using ADB. LOL
HipKat said:
Oh yeah, duh. Since this is the first Android I've ever had that was intruded, I didn't even consider using ADB. LOL
Click to expand...
Click to collapse
What I'm saying is on the Verizon Asus AR you can not get to recovery mode with just the phone lol don't know why yet but I'm working on it lol
corona63976 said:
You can get to fastboot mode by powering off the device then press volume down and power at the same time. If you need to clear cache you have to have sdk installed on your PC or the quick install ADB. open command prompt on your pc by pressing shift + right click type: fastboot devices when it comes back with your device type: fastboot oem reboot-recovery just like that. it will reboot to recovery then you can clear cache. Thank you.
Click to expand...
Click to collapse
corona63976, thanks a lot for the info! Right on!!!
Been poking around ASUS website. Found that they've posted kernel source and firmware. Not sure what the differences would be from the WW to Verizon modded one. Also stumbled upon an APK from ASUS for another Zenphone that said it was to unlock phones Android MM and Android N. Tried to install APK. It wouldn't install due to it or another version being installed...? App won't let upload screenshot here's link
goo.gl/photos/GLD3ERKGUdHKN92A6
ExiledBliss said:
Been poking around ASUS website. Found that they've posted kernel source and firmware. Not sure what the differences would be from the WW to Verizon modded one. Also stumbled upon an APK from ASUS for another Zenphone that said it was to unlock phones Android MM and Android N. Tried to install APK. It wouldn't install due to it or another version being installed...? App won't let upload screenshot here's link
goo.gl/photos/GLD3ERKGUdHKN92A6
Click to expand...
Click to collapse
Found same app installed and said not compatible
Sent from my ASUS_A002A using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did some more looking around and it seems the ULT uses a CPU key from device to unlock. I'm wonder if the app could be modified to work... Until or if ASUS releases one for the AR. Running through system process saw that it has root detect service. SafetyNet I think. And wonder if that would cause an issue in the process of getting unlocked boot loader or root. Probably not since Knox is able to be bypassed. Have gotten hotspot and tether going without root. But that's not the reason I want root. Miss having/using Cynogen and Nethunter on phone. Without root it's useless. I have a few more days left to exchange. Still trying to figure if I want keep it and hope for root. Or go back to Notes since the 8 is out... Feel like on the Samsung side they'll make some type of progress. Sooner rather than later...
bricked
Hello everyone.
Today I installed an official OTA update for my brand new ZenFoneAR over the notification bar. Unfortunately the device ended up in a boot loop. I could switch it off and I can access the bootloader with power+volume up. Unfortunately selecting the Recovery mode also leads to a reboot. The three days old, 1000$ phone is essentially bricked.:crying:
I believe I could flash recovery via fastboot if I had a stock recovery image. On the Asus website* I have found some firmware images (zip files) but none of them contains a recovery.img file.
Is there any way to get hold of a stock recovery.img? I don't have a "Verizon" phone (bought it in Switzerland) but it still says "DEVICE STATE - locked" in the bootloader menu...
* THE_WEBSITE/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download (can't paste URLs)
brookman said:
Hello everyone.
Today I installed an official OTA update for my brand new ZenFoneAR over the notification bar. Unfortunately the device ended up in a boot loop. I could switch it off and I can access the bootloader with power+volume up. Unfortunately selecting the Recovery mode also leads to a reboot. The three days old, 1000$ phone is essentially bricked.:crying:
I believe I could flash recovery via fastboot if I had a stock recovery image. On the Asus website* I have found some firmware images (zip files) but none of them contains a recovery.img file.
Is there any way to get hold of a stock recovery.img? I don't have a "Verizon" phone (bought it in Switzerland) but it still says "DEVICE STATE - locked" in the bootloader menu...
* THE_WEBSITE/Phone/ZenFone-AR-ZS571KL/HelpDesk_Download (can't paste URLs)
Click to expand...
Click to collapse
Given that you didn't modify the phone and installed an ota, why not just rma it?
crpalmer said:
Given that you didn't modify the phone and installed an ota, why not just rma it?
Click to expand...
Click to collapse
Yes, I will certainly do that when there is no way to fix it myself. However I can't do a return on the weekend and I'm not keen on waiting for weeks for a replacement either.
Meanwhile I have found out how to create a system.img from the OTA update on the Asus website using sdat2img.py. Unfortunately this can't be flashed via fastboot onto a locked phone. The ZIP also contains images for boot, asusfw, mdtp and splash but sadly no recovery.
Related
Just a background:
This is not my device
This is a stock OS/nonrooted device
I have done some development on Android, so am somewhat experienced
I am helping a friend who just wants it to work again
Kindle Fire HDX 7" model # C9R6QM
What's going on:
Device is stuck on light gray "kindle fire" boot logo.
Device is not showing in device manager on Windows 7 PRO
Device is not showing in adb "adb devices command"
Device seems charged, has been left with cord in for longer than several hours
Tried several different cords to rule out faulty equipment
Tried multiple USB ports including 2.0, 3.0, front and rear ports, even a powered USB hub
Tried hard reset multiple times using power button
Tried power and vol up to go into a recovery, nothing happens.
"fastboot devices" command shows only "waiting for devices"
Help! I just need to get this thing up and running again, no matter the cost to data. Only thing I haven't tried is the bootloop utilities yet, as I am on a work pc and do not have access to download them atm. Will try these later if I need to.
Thanks in advance, and ask any questions if you need more info.
-Tripp
UPDATE 1: Upon further playing with device, I have finally gained access to the "Fire System Recovery" page seen here.
Well I guess since I am a new user still I cannot post the photo, but it is kindlefire recover page with a bunch of E: failed and E:cant mount stuff underneath. If I need to spell it all out I will.
Unfortunatly, neither "reboot your kindle" or "reset to factory defaults" does any good for me. Rebooting just causes it to bootlogo screen again, and Reset to FD fails, getting some weird oldschool tv effect on the screen until it reboots again into recovery and gives me the same two options.
ADB, windows, and fastboot still do not detect the device while in recovery.
Any ideas?
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
EncryptedCurse said:
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
Click to expand...
Click to collapse
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
trippvail said:
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
Click to expand...
Click to collapse
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Davey126 said:
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Click to expand...
Click to collapse
Damn was hoping there was a fix. I am sure that adb was never enabled as they are not tech savvy. Nothing shows in device manager when it is plugged in, ever. No changes.
Update 2:
So I popped in my Ubuntu drive and booted up. After installing adb and fastboot just in case, I tried accessing the kindle in both boot logo and recovery modes. No luck.
Ubuntu doesn't even see it there...
I know I'm not going crazy but it seems like I'm missing something somewhere. I have been through multiple brickings of our developer phones and brought them back to life but they always had adb enabled. Seems like there has to be a work around.
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
trippvail said:
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
Click to expand...
Click to collapse
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Davey126 said:
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Click to expand...
Click to collapse
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
trippvail said:
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
Click to expand...
Click to collapse
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Davey126 said:
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Click to expand...
Click to collapse
Ya I can understand that. I'm actually using an iPhone right now, jailbroken of course lol. But I understand why Amazon did it. Too bad a tablet has to die because of it though. I love the open Android systems but I like apples hardware better. Haven't found an android phone I like better yet. To each his own, right?
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
draxie said:
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
Click to expand...
Click to collapse
I don't and neither does the owner. I would assume the latest if it auto updates, although that may be what bricked it if it didn't have the power to complete the update. Can't confirm any of that though.
I will try both volume buttons in a bit when I get off work. I did the vol up with power to get into recovery, but that did nothing for me as recovery failed every time and rebooting just takes me back to the gray kf logo.
Ok so I tried the vol up and down while powering it on and it just took me to recovery. Same E:failed to mount and E:can't mount/can't open messages below the recovery options in yellow. So I guess I'm screwed then.
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
draxie said:
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
Click to expand...
Click to collapse
I will be trying your methods draxie when I get home and back with the device today if what I am doing now doesn't work. I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
At this point recovering anything from the device is nothing to me, or the owner, as there was nothing important on it. I was hoping to not take the hardware route, but I have the tools, the time, and the hands to do it if necessary. All I need is the knowledge from someone as to what the hell I'm looking for in there.
Just to confirm, after the gray logo of KindleFire comes up, should I be seeing anything else come up while holding buttons for fastboot? <<Just re-read your post and realized it answered this question>>These things are so much easier to use when rooted and TWRP or CWM recoveries are installed. Android makers all over should take note and use the knowledge of the open source community to improve their own devices.
Below is a photo of the recovery screen I see now that I can finally post photos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
trippvail said:
I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
Click to expand...
Click to collapse
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
draxie said:
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
Click to expand...
Click to collapse
Lol thanks. I am sure it will be dead for awhile before I get home, if it's not dead already. But if for some reason it's still alive I will make sure to let it sit for an extra 30 minutes after it goes down.
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
jwcdis said:
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
Click to expand...
Click to collapse
If the bootloader remains locked with no access via tether (or wireless ADB) you are pretty much done. You can attempt the cold start remedy suggested in earlier posts. Long shot at best. Note the device should sit idle for several days after appearing to be depleted as internal circuitry prevents the battery from going completely dead. Even then some charge will remain which is necessary to respond to the power button and protect the battery from permanent damage. Removable primary and backup batteries are the only surefire way to insure a true cold start.
Hello folks, i've been rooted for a while now and i was wondering if there is any custom recovery for the verizon v10 yet? The reason is because i messed up my google apps and i need to flash them to make the market work again. Any input would be appreciated.
As of right now no, we need the bootloader unlocked first and thats gonna be a minute. So just do a flash back to stock. Theres also a option where it won't wipe your data, instead of upgrade in the programs options just select refurbished instead ( I think, you'll have to look it up).
razzrmaxx said:
Hello folks, i've been rooted for a while now and i was wondering if there is any custom recovery for the verizon v10 yet? The reason is because i messed up my google apps and i need to flash them to make the market work again. Any input would be appreciated.
Click to expand...
Click to collapse
No and there's not going to be.
evolver10 said:
No and there's not going to be.
Click to expand...
Click to collapse
Kind of have to agree. There is just is not a following for this phone.
I have really been considering selling this phone and getting a Moto X Pure.
Does anyone have connection with team twrp? Or the developers that usually work an help with rooted phone's recoveries?
I do, and it won't happen without a bootloader unlock.
Haxcid said:
Kind of have to agree. There is just is not a following for this phone.
I have really been considering selling this phone and getting a Moto X Pure.
Click to expand...
Click to collapse
Thats what they said about root for this phone. Give it time dam*it
alvinator94 said:
Thats what they said about root for this phone. Give it time dam*it
Click to expand...
Click to collapse
Good luck with that. I am sure this phone will get root and boot loader but by then I will be long onto another phone. Having used it now for a time, I really wish I went with the smaller moto x pure, I could have gotten it completely customized, and root, and roms... one handed use with this phone sucks even with the tools provided.
for half the price with performance on par...
Haxcid said:
Good luck with that. I am sure this phone will get root and boot loader but by then I will be long onto another phone. Having used it now for a time, I really wish I went with the smaller moto x pure, I could have gotten it completely customized, and root, and roms... one handed use with this phone sucks even with the tools provided.
for half the price with performance on par...
Click to expand...
Click to collapse
Also , I'm starting to see reports of the G4 boot loop of death on the V10. We live and learn I suppose. My v10 is sitting on my desk collecting dust now while I'm rocking my N6P.
evolver10 said:
Also , I'm starting to see reports of the G4 boot loop of death on the V10. We live and learn I suppose. My v10 is sitting on my desk collecting dust now while I'm rocking my N6P.
Click to expand...
Click to collapse
I'm pretty decent at fixing the G4 bootloop. It's caused by the NAND coming away from the board. Have to reflow it and pray it isn't to far gone. Sometimes it works forever sometimes just Kong enough to get data from. Sad to hear that the V10 is displaying the same issue. Haven't seen any at my shop yet but then again have only seen 3 or 4 V10s.
bantzt said:
I'm pretty decent at fixing the G4 bootloop. It's caused by the NAND coming away from the board. Have to reflow it and pray it isn't to far gone. Sometimes it works forever sometimes just Kong enough to get data from. Sad to hear that the V10 is displaying the same issue. Haven't seen any at my shop yet but then again have only seen 3 or 4 V10s.
Click to expand...
Click to collapse
I had to warrenty my v10 due to random issues i.e. icons would be grey blocks, apps would act as if they'd been wiped. Tried doing a recovery restore from my pc and it still did it. Literally the phone was loosing it's memory.
Well I just sold my v10 so be looking for that bootloader to be unlocked soon.
So many know vulnerabilities to try, so little time... HAHA if on 5.1.1 it's possible
I know this might be a long shot since it's an old phone and whatnot, but I've recently breathed new life into my Mega from US Cellular. Had the screen repaired and it's good to go again after previously being destroyed by an estranged ex. I was wondering if there is a way to get the latest marshmallow update to the device? I've seen there are numerous posts for all other Mega models (i.e. - all models except the one I own). I would really like to use my Mega again but with it being on Kitkat, it's kind of useless at the moment.
Any help or advice whatsoever would be greatly appreciated.
And again, I apologize if I'm bringing up an old, dead phone, but I really loved this device years ago and I would like to love it again.
Cheers!
dirty_finnagin said:
I know this might be a long shot since it's an old phone and whatnot, but I've recently breathed new life into my Mega from US Cellular. Had the screen repaired and it's good to go again after previously being destroyed by an estranged ex. I was wondering if there is a way to get the latest marshmallow update to the device? I've seen there are numerous posts for all other Mega models (i.e. - all models except the one I own). I would really like to use my Mega again but with it being on Kitkat, it's kind of useless at the moment.
Any help or advice whatsoever would be greatly appreciated.
And again, I apologize if I'm bringing up an old, dead phone, but I really loved this device years ago and I would like to love it again.
Cheers!
Click to expand...
Click to collapse
Not 100% sure about this, as I am only doing the same as you are with my L600 model (minus the screen repair >.<) lol.
For the Sprint model at least it is pretty much compatible with anything made by Silesh. Hopefully it is the same for you on USC .
Have you gained root or anything yet? that's going to be your first step on anything, old or not hopefully xD.
LilAnt530 said:
Not 100% sure about this, as I am only doing the same as you are with my L600 model (minus the screen repair >.<) lol.
For the Sprint model at least it is pretty much compatible with anything made by Silesh. Hopefully it is the same for you on USC .
Have you gained root or anything yet? that's going to be your first step on anything, old or not hopefully xD.
Click to expand...
Click to collapse
I have rooted my phone, but I have yet to find any roms that are higher than 4.4.2. I'm able to use the phone as it is just by inserting my active sim card, but hardly any of my daily apps will run because of the old OS. I've been too afraid to try any of the other roms for the other megas as I don't want to brick my phone. I just hope there's some way to bring this phone back to life. Hell, even lollipop would be a huge help at this point, lol.
dirty_finnagin said:
I have rooted my phone, but I have yet to find any roms that are higher than 4.4.2. I'm able to use the phone as it is just by inserting my active sim card, but hardly any of my daily apps will run because of the old OS. I've been too afraid to try any of the other roms for the other megas as I don't want to brick my phone. I just hope there's some way to bring this phone back to life. Hell, even lollipop would be a huge help at this point, lol.
Click to expand...
Click to collapse
Haha yea I beyond understand, my daily driver is a Moto E 2014 CDMA only device xD.
If you have acquired root, & custom recovery, try extracting the ROM u wish to install, & ONLY flash the boot.img, I do believe that Lollipop would run on most KK Kernels without much fussing.
LilAnt530 said:
Haha yea I beyond understand, my daily driver is a Moto E 2014 CDMA only device xD.
If you have acquired root, & custom recovery, try extracting the ROM u wish to install, & ONLY flash the boot.img, I do believe that Lollipop would run on most KK Kernels without much fussing.
Click to expand...
Click to collapse
So, I just made a discovery (I think). After taking the back of the phone off to retrieve my IMEI, I noticed that the model number on the phone says L600/R960. Does this, in theory, mean that I can use any roms that would normally be available to the L600 line of megas on my US Cell mega?!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirty_finnagin said:
So, I just made a discovery (I think). After taking the back of the phone off to retrieve my IMEI, I noticed that the model number on the phone says L600/R960. Does this, in theory, mean that I can use any roms that would normally be available to the L600 line of megas on my US Cell mega?!
Click to expand...
Click to collapse
You should be able to not ONLY use any of the great L600 Sprint based custom ROMs, but as I said before anything by Silesh.Nair should actually be compatible . & your radios should stay safe if you don't flash those over, however I am NOT 100% sure of anything I just said, still roughly 80% sure you won't do any real bricking or harm to it xD.
Also, would love to get a PM to discuss how much difficulty you had with your screen replacement, as mine is getting to be totally irresponsive in general haha.
LilAnt530 said:
You should be able to not ONLY use any of the great L600 Sprint based custom ROMs, but as I said before anything by Silesh.Nair should actually be compatible . & your radios should stay safe if you don't flash those over, however I am NOT 100% sure of anything I just said, still roughly 80% sure you won't do any real bricking or harm to it xD.
Also, would love to get a PM to discuss how much difficulty you had with your screen replacement, as mine is getting to be totally irresponsive in general haha.
Click to expand...
Click to collapse
Finally got a day to myself to test out some of these roms and see whether they work or not. As for the screen repair, I had a Verizon store do it for me. I originally was going to attempt it myself, but after reading a very detailed instructable for it.....I changed my mind, lol.
dirty_finnagin said:
Finally got a day to myself to test out some of these roms and see whether they work or not. As for the screen repair, I had a Verizon store do it for me. I originally was going to attempt it myself, but after reading a very detailed instructable for it.....I changed my mind, lol.
Click to expand...
Click to collapse
I do believe you & I have found the same instructions LOL. Verizon store huh?? Wonder if we even have one around these parts hehe, really sucks the newest ROMs seem to require TWRP as I am confined to the volume buttons/home as the only real means of navigation. But thank you for the info, I have friends who work for Verizon so maybe they can help
LilAnt530 said:
I do believe you & I have found the same instructions LOL. Verizon store huh?? Wonder if we even have one around these parts hehe, really sucks the newest ROMs seem to require TWRP as I am confined to the volume buttons/home as the only real means of navigation. But thank you for the info, I have friends who work for Verizon so maybe they can help
Click to expand...
Click to collapse
So I managed to get a custom rom and whatnot onto my Mega. I'm currently running Cm12.1 with Philz Touch Recovery. Been using the phone for almost 24 hours now and all is working well. The only issue I've found this far is that despite being a 4G LTE phone, I can only manage to get 3G. This could just be a carrier problem and not the phone or rom. I'm not at home right now, but when I get home I'll post the instructions I used to get everything working. Cheers!
dirty_finnagin said:
So I managed to get a custom rom and whatnot onto my Mega. I'm currently running Cm12.1 with Philz Touch Recovery. Been using the phone for almost 24 hours now and all is working well. The only issue I've found this far is that despite being a 4G LTE phone, I can only manage to get 3G. This could just be a carrier problem and not the phone or rom. I'm not at home right now, but when I get home I'll post the instructions I used to get everything working. Cheers!
Click to expand...
Click to collapse
try dialing #*#*4636*#*# or *#*#4636#*#* the tapping phone info
LilAnt530 said:
try dialing #*#*4636*#*# or *#*#4636#*#* the tapping phone info
Click to expand...
Click to collapse
So I did that and found that my GSM service is currently active, yet my preferred network type is set to LTE/CDMA. I tried changing it to LTE/GSM to see if that would help anything, but it just sets itself back to CDMA after a few seconds.
dirty_finnagin said:
So I did that and found that my GSM service is currently active, yet my preferred network type is set to LTE/CDMA. I tried changing it to LTE/GSM to see if that would help anything, but it just sets itself back to CDMA after a few seconds.
Click to expand...
Click to collapse
Try switching it to GSM auto (PrL) or CDMA/GSM/LTE, & also keep in mind, some of these old phones simply tell you 3G when in reality you're getting the untapped lol
I dedicated like a week to getting free 4G LTE service, finally have it untapped thru VZW
LilAnt530 said:
Try switching it to GSM auto (PrL) or CDMA/GSM/LTE, & also keep in mind, some of these old phones simply tell you 3G when in reality you're getting the untapped lol
I dedicated like a week to getting free 4G LTE service, finally have it untapped thru VZW
Click to expand...
Click to collapse
I did try your suggestion, but as I said before, none of the changes I make seem to stick. After a few seconds, I can watch the setting change right back to the default setting. I don't know if I'm missing something to make the setting take hold, but for now I'm stuck on LTE/CDMA auto (PRL). I wasn't even aware this was a GSM phone as I thought US Cellular used CDMA. I could be wrong, though.
dirty_finnagin said:
I did try your suggestion, but as I said before, none of the changes I make seem to stick. After a few seconds, I can watch the setting change right back to the default setting. I don't know if I'm missing something to make the setting take hold, but for now I'm stuck on LTE/CDMA auto (PRL). I wasn't even aware this was a GSM phone as I thought US Cellular used CDMA. I could be wrong, though.
Click to expand...
Click to collapse
Try flipping off the radio & swapping it then flipping 'er back on.
I recently bought a ZTE ZFive 2 at Walmart for around $50. Phone was branded as "Total Wireless" aka "TracFone". I'm wondering if this phone has any potential to have a custom recovery & a custom ROM made for it. It's a great device and has a lot of potential "IF" it can be unlocked through customization. Seems the manufacture or more than likely the service provider themselves have locked users out of using "adoptive storage", therefore making the device run out of it's existing "8GB" very fast. (Really only gives you a little over 2GB space to work with after a restore.)
So anyone up for development? I would be very willing to test anything someone could throw together. Just let me know what you need from my phone and how I can get it off of it and to you. Thanks a bunch!
Phones specs can be found at the following link:
ZTE ZFive 2 LTE
InfernoShark said:
I recently bought a ZTE ZFive 2 at Walmart for around $50. Phone was branded as "Total Wireless" aka "TracFone"........
Click to expand...
Click to collapse
Okay according to the CPU-Z app, this device only has 4GB of internal storage. Walmart and even ZTE's own website has this information incorrectly shown as 8GB. What the heck?
Nope it's 8GB but is severely hampered storage wise by what I can only assume is a unseemly bloated version of Marshmallow. It doesn't seem that bloated but it's gotta be. Facebook and Messenger come standard with no way of disabling them. The Google app, Youtube & Gmail which I find completely worthless because I can do them all in a browser also are present with only the exception of the Google app that cannot be disabled. I had a free Alcatel Pixi Unite from Safelink/Tracfone that you could damn near disable everything on. Only bad part was it couldn't be rooted. As unfortunately is the case I believe with the ZTE ZFive 2 LTE. I don't quite know though. I used to dabble more with this kind of thing back in the mid '00's where I practically built my own custom firmware for at the time was a LG Optimus M from Metro PCS.
I'm curious about this also.
Word to the wise...avoid all zte junk like this. They cripple these devices and most...if not all...of their newer devices like these from carriers come without even being able to reboot them to fastboot or anything else. They dummied down the devices ability to use adb to nothing more than adb reboot recovery. Any other adb command simply just reboots the device. They are crippled trash. Stay away from all of these zte devices from strait talk,boost and so on. All are garbage.
Where can I find the factory images for the ZTE Zfive 2
unlock it and enjoy
Curtis1973 said:
Word to the wise...avoid all zte junk like this. They cripple these devices and most...if not all...of their newer devices like these from carriers come without even being able to reboot them to fastboot or anything else. They dummied down the devices ability to use adb to nothing more than adb reboot recovery. Any other adb command simply just reboots the device. They are crippled trash. Stay away from all of these zte devices from strait talk,boost and so on. All are garbage.
Click to expand...
Click to collapse
Just and FYI - I bought a cheapo $29 Walgreen's Simple Mobile Trac Phone ZTE Z557bl ZFive... had no problem getting into dev mode, then setting dev option to allow oem unlock and debugging..
From there it's pretty simple process to install custom roms like every other device out there... works fine.
gozippy said:
Just and FYI - I bought a cheapo $29 Walgreen's Simple Mobile Trac Phone ZTE Z557bl ZFive... had no problem getting into dev mode, then setting dev option to allow oem unlock and debugging..
From there it's pretty simple process to install custom roms like every other device out there... works fine.
Click to expand...
Click to collapse
How did you get into dev mode ? Thanks.
ZTE. It is little bit tough with this name you know.
Development and customization is little pain is ass as per my experience.
I got as far as to set oem unlock and Debugging but like Curtis said, all attempts to enter fastboot just bypass and boot to back to system. It's as if fastboot was stripped...
FRP bypass or Cutom recovery for this ZFive 2 LTE z837vl?
i have been fiddling with with this phone for months, i can get into dev options & fastboot no prob, even though just trying to bypass FRP has got me stuck.
Any info on a custom recovery for the
ZTE ZFive 2 LTE z837vl
Getting this.phone so cheap and being able to root and ROM whould be what it would take to make this phone something a bit more.
I would be truly greatful
Need for ZTE Z557BL custom roms
gozippy said:
Just and FYI - I bought a cheapo $29 Walgreen's Simple Mobile Trac Phone ZTE Z557bl ZFive... had no problem getting into dev mode, then setting dev option to allow oem unlock and debugging..
From there it's pretty simple process to install custom roms like every other device out there... works fine.
Click to expand...
Click to collapse
Please I would like to know where I can download these custom roms. I received a ZTE Z557BL from USA and it is not connecting to my network here in Nigeria. I therefore want to install a custom rom, or if possible unlock the service provider limitation.
Any help please??
Interested
kenside34 said:
Interested
Click to expand...
Click to collapse
Anything we can do with this?
http://download.ztedevices.com/devi...1/Z557BL_Nougat(7.1.1)_kernel(3.10.49).tar.gz
hello to all... is there any chance to put in spanish this cellphone. i tried to root it not posibe, trried to install kingroot (admin blocked) tried to flash not found rom with spanish language.
Just acquired a Z837VL; gotten pretty deep in disabling apps. No root, but there's quite a few followers in the kingroot thread.
If I get anywhere on this I'll be sure and update
Curtis1973 said:
Word to the wise...avoid all zte junk like this. They cripple these devices and most...if not all...of their newer devices like these from carriers come without even being able to reboot them to fastboot or anything else. They dummied down the devices ability to use adb to nothing more than adb reboot recovery. Any other adb command simply just reboots the device. They are crippled trash. Stay away from all of these zte devices from strait talk,boost and so on. All are garbage.
Click to expand...
Click to collapse
I know this is a really late reply, but I just came across this thread because my buddy gave me a ZFive 2 for me to play around with to see if I can make a sweet media player out of it for his son. Your word to the wise is very VERY wise! Haha
It's definitely good to stay away from carrier branded ZTE devices, especially budget ones. It's not really ZTE's fault though, it's the carrier that gets them to cripple and lock down the devices. It's an attempt to make people get annoyed with them really fast so they'll come back and buy a better more expensive device. That's a shame too because ZTE makes some great devices. The new Axon 10 Pro is a beast. They also still work closely with Nubia doing R&D, and the Nubia Red Magic 3 and 3s are absolute animals! Heck... the 3 year old Axon 7 still has a top 5 most powerful Hi-Fi DAC and also still has some of the best sounding dual stereo speakers to this day. Alrighty... sorry for the low key rant. Now back to not being able to do anything with this ZTE Potato. Lol
I have a Z836BL ZFive 2 LTE US purchased at CVS which will not enter fastboot by any method. Fastboot mode will flash for a split second prior to entering recovery mode by pressing the power and volume up buttons until mode is entered.
Well I have a ZTE Avid Plus Z828 with the EXACT SAME SPECS than this device but runs Android Lolipop. I did compile a rom and TWRP image, but it's useless. Even after checking the enable OEM unlock it still won't boot anything except for official signed roms or recoveries. USELESS. The only thing is to modify the bootloader to skip verification checks, (it's already done). I would be very curious to see if the OREO rom from the Zfive2 will work on my device, it has THE SAME HARDWARE. And I bought my device from Canada, normally all the devices from there must be GSM unlocked from the factory, even if you have a contract. And it does not make sense to lock them at least in Canada.
You can probably unlock the bootloader on those by modifying the /devinfo partition. I am not sure if this works on the ZFive 2 but you guys can try it: https://forum.xda-developers.com/an...alcomm-zte-t4100897/post82595723#post82595723
Hey guys, So i got a t-mobile revvl due to an emergency, it has a mtk6738 chip and im trying to root it... can anyone point me to the right place? ive searched and searched but i cant seem to find anything for this chipset on for the MTK65XX.
thanks in advance!
No luck :/
Daisuke1988 said:
Hey guys, So i got a t-mobile revvl due to an emergency, it has a mtk6738 chip and im trying to root it... can anyone point me to the right place? ive searched and searched but i cant seem to find anything for this chipset on for the MTK65XX.
thanks in advance!
Click to expand...
Click to collapse
Phone came out around 2 months ago, same phone and same problem. Sorry to inform Root/TWRP won't be available for a while on the phone since it's so new no developer has gotten their hands on it to start developing for it. I predict it'll be faster than most new phones because it's exclusive to T-Mobile. It would take much longer if the phone had different variants because of the different carriers, but that's not the case with the revvl so what's left to do is to wait and hope ::fingers-crossed:
Anyone has the stock rom for this device?
it is like this phone doesnt exist. cant find anything. Got this phone in america and it seems impossible to unlock in mexico. do you guys think if a root will be available it will be unlocked for use in mexico? thanks!
I may be able to help with root. I don't have the phone, but if someone is willing to potentially risk their device for the sake of science, let me know.
If this goes the way I think/hope it does (since its a MediaTek), we may be able to get root and recovery in a VERY short time for this. If not, then unfortunately you're out of luck for now. But, if one of you is willing to risk it and try, I'll be more than happy to help you out.
For now though, nobody update their firmware AT ALL. They may release a patch in the future that blocks what I want to do.
UPDATE: I got to play with one at a T-Mobile store. CPU Z says this has a 6755 board, which is commonly available through other phones that have been modified. I'm really getting excited about this... If this goes the way I hope it does, you could be having TWRP and root REALLY soon.
i will be back in germany at on dec.21,if german t-mobile can't unlock it for use in germany I am willing to do anything with it for science..since I will throw this useless piece of technology at the wall anyway
luroxx said:
i will be back in germany at on dec.21,if german t-mobile can't unlock it for use in germany I am willing to do anything with it for science..since I will throw this useless piece of technology at the wall anyway
Click to expand...
Click to collapse
Let me know as soon as you have access to a PC with Windows or Linux, which I'm guessing is when you get back to Germany. For now, make sure you DO NOT TAKE ANY SOFTWARE UPDATES AT ALL. You can update apps from the Play Store still, but keep away from all system updates at all costs.
Send me a PM for how I can reach you, when you're ready to work with me. The procedure I'm thinking of will not unlock your phone in terms of network (like using it on other carriers), but if it works you will definitely have TWRP and root access, and MAYBE even a bootloader unlock (for installing custom ROMs).
But in the meantime, I can't stress this enough, AVOID ALL SYSTEM UPDATES. This goes for anyone who may want to root their phone using this method, if this works.
I just bought one to use on a spare phone line - Cyber Monday sale for $48! I'm happy to experiment when it arrives. Maybe the sale price will entice some other developers...
jasonmerc said:
Let me know as soon as you have access to a PC with Windows or Linux, which I'm guessing is when you get back to Germany. For now, make sure you DO NOT TAKE ANY SOFTWARE UPDATES AT ALL. You can update apps from the Play Store still, but keep away from all system updates at all costs.
Send me a PM for how I can reach you, when you're ready to work with me. The procedure I'm thinking of will not unlock your phone in terms of network (like using it on other carriers), but if it works you will definitely have TWRP and root access, and MAYBE even a bootloader unlock (for installing custom ROMs).
But in the meantime, I can't stress this enough, AVOID ALL SYSTEM UPDATES. This goes for anyone who may want to root their phone using this method, if this works.
Click to expand...
Click to collapse
alkoholic said:
I just bought one to use on a spare phone line - Cyber Monday sale for $48! I'm happy to experiment when it arrives. Maybe the sale price will entice some other developers...
Click to expand...
Click to collapse
$48?????? THEY WERE $179 WHERE I WAS!!!!!
For that price I would've bought one myself... But yes, that would be great if you could work with me when it arrives!
I would be willing to help as much as possible with root access as well. If you need any sort of system dump or something let me know I am very much willing to help!
rsuthers08 said:
I would be willing to help as much as possible with root access as well. If you need any sort of system dump or something let me know I am very much willing to help!
Click to expand...
Click to collapse
PM me where I can contact you (hangouts, telegram, etc.)
[REMOVED BY ME]
Overall, it doesn't look like we have any of the obstructions I was afraid we were going to have so far. We need to work on a few things before we can get the whole thing done, but as of now, this hack looks like it will be 100% possible to do
UPDATE: We're running into some trouble again. Stuff I may not be able to bypass. I'm not sure if this will be 100% possible now...
Picked up two of these for $48 each on the T-Mobile Cyber Monday deal and got them to waive the shipping, set one up for my Mom and it's a pretty nice phone. I still have the other one sealed in the box, debating whether to keep it or sell it. Root and TWRP would be awesome, hopefully it comes soon.
Zephead said:
Picked up two of these for $48 each on the T-Mobile Cyber Monday deal and got them to waive the shipping, set one up for my Mom and it's a pretty nice phone. I still have the other one sealed in the box, debating whether to keep it or sell it. Root and TWRP would be awesome, hopefully it comes soon.
Click to expand...
Click to collapse
A device no one has touched could be beneficial, since that means there's no Google Factory Reset Protection on it (no google account associated with it yet). If you want to use your unused device for some of the tests/methods we're working on, let me know.
Another update on our findings: with the help of @lopestom, I've found out that this device looks to be a 1:1 copy of the Alcatel A30 Fierce, and a distant cousin of the A30 Plus that Amazon once sold as a prime subsidized phone. Despite what SPFT and CPU-Z say, this phone should be running an MT6738 chipset, which uses the same partition layout as the MT6735. I have a completed scatter file for the 6735 from my R1HD days, so if this is the case, knowing where the phone's partitions are should be no problem.
[REMOVED BY ME]
jasonmerc said:
Another update on our findings: with the help of @lopestom, I've found out that this device looks to be a 1:1 copy of the Alcatel A30 Fierce, and a distant cousin of the A30 Plus that Amazon once sold as a prime subsidized phone. Despite what SPFT and CPU-Z say, this phone should be running an MT6738 chipset, which uses the same partition layout as the MT6735. I have a completed scatter file for the 6735 from my R1HD days, so if this is the case, knowing where the phone's partitions are should be no problem.
My biggest fear is, again, that SPFT is being blocked in the same way that it now is on the R1HD. Besides that, we found out that Google's FRP may prevent us from accessing the developer menu to enable ADB on the phone. Now, I could've sworn I got into the developer menu in a store demo Revvl by mashing the Build Number entry like I would on any other phone, but for some reason the person I'm working with is unable to get to this menu (mashing Build Number does nothing for him). If another Revvl user is reading this, can you please try to enable the Developer Menu and ADB for me? I want to see if this issue is just for him or if it affects everyone.
EDIT: The error given from SPFT with the Revvl VS with the R1HD are completely different errors, so this gives me hope that we can still use SPFT with the Revvl.
Click to expand...
Click to collapse
Hey my name is Jakob, i also has a T-Mobile revvl (Alcatel 5049w) and yes my developer options have been enabled without any issues and I'm willing to assist in rooting options if I can help
just tried doing a reboot to bootloader with no luck, it reboots, hangs on the power by angroid then fully boots to stock rom.
video attached
https://drive.google.com/open?id=1Pw61qisWQjC9J_Q9jqHNgRG-n7FmIpcq
[removed by me]
Worked on the Revvl Plus with @oasisfleeting tonight. It's a snapdragon 625 based phone, unlike its mediatek based little brother. This phone actually allows us to go into fastboot mode unlike the normal Revvl though. However, with the exception of fastboot devices (just shows what's connected), no commands actually work. They either all return "..." Or show that no device is connected (when it actually is). Even throwing in the device ID: fastboot -i 0x1ebf oem unlock does nothing.
For the mediatek variant, there is still a very small sliver of hope. For the Plus variant, I'm pretty sure you will never get the bootloader unlocked. Root maybe, but that'll be it.
jasonmerc said:
Worked on the Revvl Plus with @oasisfleeting tonight. It's a snapdragon 625 based phone, unlike its mediatek based little brother. This phone actually allows us to go into fastboot mode unlike the normal Revvl though. However, with the exception of fastboot devices (just shows what's connected), no commands actually work. They either all return "..." Or show that no device is connected (when it actually is). Even throwing in the device ID: fastboot -i 0x1ebf oem unlock does nothing.
For the mediatek variant, there is still a very small sliver of hope. For the Plus variant, I'm pretty sure you will never get the bootloader unlocked. Root maybe, but that'll be it.
Click to expand...
Click to collapse
There are other unlocking commands too. Did you try "fastboot flashing unlock" on the plus
I have also seen bootloader mode renamed before. so try "adb reboot fastboot" to get into fastboot.