Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
mrz80 said:
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
Click to expand...
Click to collapse
Is kingroot the only way still? I have OF1 but I cant get kingroot to uninstall properly.
bobturismo said:
Is kingroot the only way still?
Click to expand...
Click to collapse
I *think* it is. After desiccating my eyeballs reading a bazillion posts about rooting late-code S4 phones, this is the most promising thing I came up with:
https://forum.xda-developers.com/ga...-to-root-verizon-galaxy-s4-android-5-t3655127
bobturismo said:
I have OF1 but I cant get kingroot to uninstall properly.
Click to expand...
Click to collapse
I took a flyer and tried Kingroot on my GPL1 phone, with (pretty much as expected) nil results. I finally got Kingroot uninstalled by long-press selecting it & dragging it to the trash, clicking "uninstall", then clicking thru the "can't uninstall 'cause it's an administrative app" screen. That landed me on a screen where I could deactivate it. Once it was deactivated, it (at least theoretically... let's see what happens after a reboot... yep, all gone) could be deinstalled.
mrz80 said:
I.
Click to expand...
Click to collapse
When I would try supersu me, it would delete kingroot, then restart like halfway (like crash or error) then I would restart and not have root anymore.
I ended up doing this and it was super simple
https://forum.xda-developers.com/android/general/guide-to-replace-kinguser-supersu-t3185998
BUT this was using an older kingroot 4.1.something and then after supersu me froze, then I did this and during the process while trying to delete kingroot files, it kept saying "File not found". So there is a possibility I didn't need to run the MRW script....
mrz80 said:
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
Click to expand...
Click to collapse
I just swapped out main boards from my old GS4 to my semi newer one. So now I'm back on MK2 with Safestrap installed and thank God I had Safestrap because it allowed me to bypass my lockscreen since it wouldn't accept my old pattern or pin number.
mrz80 said:
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
Click to expand...
Click to collapse
Sorry to tell you, OF1 is still locked. Lineage OS can't be run on your device. MDK was the build that was unlockable.
bobturismo said:
Is kingroot the only way still? I have OF1 but I cant get kingroot to uninstall properly.
Click to expand...
Click to collapse
This is much easier - https://forum.xda-developers.com/showthread.php?t=3254434
{
"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 used kingroot to root GPL1. Getting rid of kingroot for superSU to take over was a slight pain. I had to download ES file explorer, terminal emulator, and some kingroot_to_superSU.zip file that had 4 files inside. After it was all said and done, I finally got superSU to work and got rid of kingroot (I think).
npjohnson said:
Sorry to tell you, OF1 is still locked. Lineage OS can't be run on your device. MDK was the build that was unlockable.
Click to expand...
Click to collapse
Yeah, I realized I got my research crossed up. Oh, well... at least I've got an extra phone with no broken glass. Wonder if anyone's got an S4 in a box in a closet somewhere that never got past kitkat.
Hi!
Just picked up one of these in great condition not crackedd or anything its verizon of course not on OF1 its oni545vrufnk1
anyway, was wondering if you could share some info with me on this device. I have tmobile and im wanting to go with the tmobile version of this phone.. (i dont know if there a unlocked firmware version)
is this the way to go should i just flash it with tmobile or unlocked firmware?
thanks
xsnrgx said:
Hi!
Just picked up one of these in great condition not crackedd or anything its verizon of course not on OF1 its oni545vrufnk1
anyway, was wondering if you could share some info with me on this device. I have tmobile and im wanting to go with the tmobile version of this phone.. (i dont know if there a unlocked firmware version)
is this the way to go should i just flash it with tmobile or unlocked firmware?
thanks
Click to expand...
Click to collapse
Nope, you're out of luck.
No ROM's either.
Best bet is to update to PL1 (the newest build) via OTA, and just pop the TMO SIM in, and set the APN by hand.
Related
Anyway to fix that or am I boned?
What did you do before this? Is this after the official AT&T OTA?
Edit: What he said^^^^^
Sent from my MB860 using XDA Premium App
infinite01 said:
Anyway to fix that or am I boned?
Click to expand...
Click to collapse
{
"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"
}
ya I read some articles that flashing it after the gingerbread update does that... after I did it. But ya I got it after trying to flash back to the 1.2.6 update, just got unlucky I guess. I plan on going to AT&T store today and telling them it was the gingerbread update.
infinite01 said:
Anyway to fix that or am I boned?
Click to expand...
Click to collapse
What did you do?
Which version were you on, and which version were you flashing to?
What mods had you done to your phone?
0x1000 is what people get with hard brick:
http://forum.xda-developers.com/showthread.php?t=1165154
Like I said above, basically I had just got the Gingerbread update, but my fingerprint scanner hadn't been working, figured a flash might fix that but I knew the new update was coming out so I thought, if i'm lucky that will fix it, it didn't so I flashed it to 1.2.6, (and it was the same SBF I've used a few times before so i don't think it was that) and it said the flash failed and i got that wonderful hard brick screen.
infinite01 said:
Like I said above, basically I had just got the Gingerbread update, but my fingerprint scanner hadn't been working, figured a flash might fix that but I knew the new update was coming out so I thought, if i'm lucky that will fix it, it didn't so I flashed it to 1.2.6, (and it was the same SBF I've used a few times before so i don't think it was that) and it said the flash failed and i got that wonderful hard brick screen.
Click to expand...
Click to collapse
Yup, that sounds like what bricks everyone else. Never flash backwards after the OTA.
Well I've done it before a few times and there was never a problem, I've looked online and it appears this is specifically a bug with there Gingerbread update. I'm wondering what there policy on this is, I mean if i don't tell them about the flashing, just there update bricked it. I've had a phone go bad before and they sent me a replacement.
infinite01 said:
Like I said above, basically I had just got the Gingerbread update, but my fingerprint scanner hadn't been working, figured a flash might fix that but I knew the new update was coming out so I thought, if i'm lucky that will fix it, it didn't so I flashed it to 1.2.6, (and it was the same SBF I've used a few times before so i don't think it was that) and it said the flash failed and i got that wonderful hard brick screen.
Click to expand...
Click to collapse
Hard brick. You cannot flash back after doing the OTA 4.5.91 upgrade.
You could while on Froyo (2.2.*), but those were updates (4.1.26, 4.1.57, 4.1.83) and not upgrades, which the flash to GB is. AT&T made it so you cannot flash back to an earlier Android version with this upgrade.
See my link in post #6.
infinite01 said:
Well I've done it before a few times and there was never a problem, I've looked online and it appears this is specifically a bug with there Gingerbread update. I'm wondering what there policy on this is, I mean if i don't tell them about the flashing, just there update bricked it. I've had a phone go bad before and they sent me a replacement.
Click to expand...
Click to collapse
You had done it before while on Froyo. That's why you had no problems. I have not flashed the OTA, but I imagine/assume (I know, never assume) that there was probably a warning before installation telling you you could not flash back. If there was not, you could argue they never told you that you could not flash back after upgrading.
Well thanks for the knowledge i'm going to go to the store now I'll keep ya'll up to date for future reference
Also see here ----> http://forum.xda-developers.com/showthread.php?t=1160408
CaelanT said:
Also see here ----> http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
Wow.......I almost feel bad for Motorola that many of these bricks aren't their fault and is a prime example of why they didn't want to unlock the bootloader for us and for why RSD was never meant for us. Would be nice if people would do a little more research before just jumping in with both feet. They were nice and gave us the means to unlock, the least we could do is to take responsibility for if we screw up our phones.
I spend hours on this tread to avoid bricks at all costs.
Honestly i could careless for the unlocked bootloader, didn't even want root except for 3rd party app support, and either way I would have went to get a new phone bricked or not, the fingerprint scanner was defective, but as of now the phone was under warranty so either of the issues would have warranted me a new or refurbished phone, which I now have after about an hour of waiting. I've never flashed my phone unless the problem that i was trying to fix would otherwise have me seek a phone replacement anyways, so i wouldn't feel bad for Motorola when I'm getting a replacement for faulty software/hardware.
infinite01 said:
Honestly i could careless for the unlocked bootloader, didn't even want root except for 3rd party app support, and either way I would have went to get a new phone bricked or not, the fingerprint scanner was defective, but as of now the phone was under warranty so either of the issues would have warranted me a new or refurbished phone, which I now have after about an hour of waiting. I've never flashed my phone unless the problem that i was trying to fix would otherwise have me seek a phone replacement anyways, so i wouldn't feel bad for Motorola when I'm getting a replacement for faulty software/hardware.
Click to expand...
Click to collapse
In your case, that is probably true. Reading through the treads lately, my comment was more towards all of the people that didn't take the time to read before they start flashing. Many of the bricks aren't necessarily due to Motorola update, but that people are trying to flash back after.
Gr8Danes said:
In your case, that is probably true. Reading through the treads lately, my comment was more towards all of the people that didn't take the time to read before they start flashing. Many of the bricks aren't necessarily due to Motorola update, but that people are trying to flash back after.
Click to expand...
Click to collapse
i also dont understand why people keep flashing back to froyo after flashing GB. the build is very stable and doesnt have any serious issues.
neotekz said:
i also dont understand why people keep flashing back to froyo after flashing GB. the build is very stable and doesnt have any serious issues.
Click to expand...
Click to collapse
I 2nd that thought.
Like I said I did it to see if I can't get the scanner to work again, but after using it a little I'm finding it a lot slower than froyo
{
"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"
}
Oops, rooted I-545 running 4.3 was accidently updated to KitKat 4.4.2 and I lost root HELP!
I am starting a new thread because I think my message got lost in a 45-page thread and this is urgent.
My original S4 had the updating software renamed so that I wouldn't even be notified about updates, but I had to get a warranty replacement. I rooted it, but forgot to turn of the ability to update. Last week, while I was undergoing surgery for a kidney stone, my wife was using the phone in the waiting room. She saw a message that an update was ready and, since her S3 is totally stock and she always updates, she hit the ok button. That night, I discovered I was no longer rooted and that KitKat 4.4.2 was the new O/S.
I am very dependent on functionality that will only run rooted, so I really need to clear this up. For example, I use RCB as my phone and text blocker and it requires root to run. It's big advantage is that it does this all silently before the call bubbles up to where non-rooted call-blockers do a pickup and hangup (with an annoying fragment of a ring each time). Since I'm unable to run RCB or a root-level file browser to recover the logs of blocked numbers to use (temporarily, I hope) in something like Mr. Number.
Is there anything I can do to either root under KitKat, or back down my version of Android to 4.3 and then re-root the standard way?
Blue Sun
"Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity."
-- Charles Mingus
Here you go.
http://forum.xda-developers.com/showthread.php?t=2726868
Dooley69 said:
Here you go.
http://forum.xda-developers.com/showthread.php?t=2726868
Click to expand...
Click to collapse
This does not help him because he lost root & wants to get it back. This instructional thread assumes root has been maintained. Currently, there is no root solution for the 4.4.2 version. Apparently, patience is the only solution.
OffcerClancy said:
This does not help him because he lost root & wants to get it back. This instructional thread assumes root has been maintained. Currently, there is no root solution for the 4.4.2 version. Apparently, patience is the only solution.
Click to expand...
Click to collapse
Actually it should because you can downgrade partially back to MK2 and then root using saferoot and then follow the top instructions to go back to fnc5 and it works because I have done it. If you havent done it you shouldnt comment.
That's what I learned TechGuy. Just trying to help out!
Techguy2002 said:
Actually it should because you can downgrade partially back to MK2 and then root using saferoot and then follow the top instructions to go back to fnc5 and it works because I have done it. If you havent done it you shouldnt comment.
Click to expand...
Click to collapse
Yeah, whatever you say Supreme Leader. In any case, if you have actually done this, you should share your gift w/this thread: http://forum.xda-developers.com/showthread.php?t=2734309
Reply
Blue Sun said:
Oops, rooted I-545 running 4.3 was accidently updated to KitKat 4.4.2 and I lost root HELP!
I am starting a new thread because I think my message got lost in a 45-page thread and this is urgent.
My original S4 had the updating software renamed so that I wouldn't even be notified about updates, but I had to get a warranty replacement. I rooted it, but forgot to turn of the ability to update. Last week, while I was undergoing surgery for a kidney stone, my wife was using the phone in the waiting room. She saw a message that an update was ready and, since her S3 is totally stock and she always updates, she hit the ok button. That night, I discovered I was no longer rooted and that KitKat 4.4.2 was the new O/S.
I am very dependent on functionality that will only run rooted, so I really need to clear this up. For example, I use RCB as my phone and text blocker and it requires root to run. It's big advantage is that it does this all silently before the call bubbles up to where non-rooted call-blockers do a pickup and hangup (with an annoying fragment of a ring each time). Since I'm unable to run RCB or a root-level file browser to recover the logs of blocked numbers to use (temporarily, I hope) in something like Mr. Number.
Is there anything I can do to either root under KitKat, or back down my version of Android to 4.3 and then re-root the standard way?
Blue Sun
"Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity."
-- Charles Mingus
Click to expand...
Click to collapse
Okay so the way to do this is simple: You will need to factory reset to stock. This will wipe all of your data, but if you do this correctly with Odin, then you will be surprised with how it works.
Use this thread to do a full or no wipe: http://forum.xda-developers.com/showthread.php?t=2578209"]http://forum.xda-developers.com/showthread.php?t=2578209
Once you do that, you have to go through the processes and go to settings>phone info>software update and update your system software.
After that, you can re-root your device through this thread: http://www.ibtimes.co.uk/root-galaxy-s4-snapdragon-600-exynos-5-android-4-3-without-warranty-void-1431730
Your welcome.
Do I neet root to use Surges downgrade??
I upgraded to leaked kitkat nc2 and lost root of course..I want to downgrade with Surges method back to mk2..does his downgrade process require root to downgrade?? First post.... Thanx..
OffcerClancy said:
Yeah, whatever you say Supreme Leader. In any case, if you have actually done this, you should share your gift w/this thread: http://forum.xda-developers.com/showthread.php?t=2734309
Click to expand...
Click to collapse
Somebody already told that guy to do that. It is a known method.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I just received the prompt to do a System Update, see the image below:
{
"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"
}
Does anyone have any idea what it is? Lollipop??
If anyone has installed it, does it break root?
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Interested in knowing if this breaks root as well. Til then, no install for me.
No idea. Got the update notification just now but since I'm rooted and on a custom ROM, I don't think I should flash it.
If you're rooted, and unlocked, I would avoid this update like the plague. Give the devs time to look at it.
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
ryman222 said:
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I suggest never taking an OTA update if you aren't 100% stock.. and def never do one if on TWRP.
Fix being stuck in twrp - http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
General info on taking OTA - http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'd assume this new OTA update today will block ioroot and stump from working. Whether a previously rooted phone will retain root through the OTA is a gamble.. may or may not work. Some have reported already that root has stuck thru the OTA. So might luck out with this one. For those who are not rooted and take the OTA update.. gaining root again may not be so easy (without downgrading).
Without seeing the bootloader.. can't say if Bump is blocked. Most likely not yet though.
Dobrah said:
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
Click to expand...
Click to collapse
Yeahh if we could get that, that'd be great. I don't wanna have to deal with breaking root/unlocked bootloader.
What I did when it asked for a time to update was just press the home button. Then it went into a notification saying an update is available. I think that'll keep it at bay.
Dobrah said:
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
Click to expand...
Click to collapse
If you just press the back button itll stay in your notifications, but it wont force you to do anything. Notice the blue checkmark.
Guys come on updates should never be taken period rooted. Sooo wait few days until there is time to examen and provide the community with info
dabug123 said:
Guys come on updates should never be taken period rooted. Sooo wait few days until there is time to examen and provide the community with info
Click to expand...
Click to collapse
+1 lol...
Guys just freeze system update with titanium backup...
Lollipop? On Verizon? Hilarious.
I took the update. I'm not an expert but it looks like it's just an update from software version B to C. It puts a camera shortcut on the lock screen, which isn't really necessary given the back button shortcut. Still missing the rom I had on my Galaxy Nexus, which was more current than this. Love my phone, hate having outdated Android.
Root does not appear to be affected. I am not a dev, just a rooted phone owner so take that for what it's worth.
To Block OTA's visit this thread:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-disable-ota-downloads-verizon-t2914735
I caught wind of this on reddit before the update showed up and had a feeling my IORoot/Bump unlock setup wouldn't agree with this OTA. I used TiBu to freeze "System updates 1_13_10_0" and made a nandroid backup just in case. All good so far. Several redditors with custom recovery softbricked when they tried to install it, so this seems like the way to go for now.
ryman222 said:
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I just accidentally installed it and the same thing happened to me. This got me out of it:
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
I noticed this sitting there today and was wondering about it before i proceeded. I never use WiFi so it won't download so for now I am safe.
I just don't get it..Blow away!
Anyone know where the update is stored once downloaded? I'm assuming it's somewhere in the system folder, but not sure where to look.
My wife had apparantly rooted the device without me knowing, went to update it for my daughter for christmas, and now all I can get is a booting icon, and into the recovery menu. I'm sorry if someone has already received help for this, but i need to know how to get it back to stock. it has stock recovery menu, and i can't seem to find which recovery menu is compatible with this device, as well as an OTA file for it, or even a stock file
any help is very much appreciated.
k35513r said:
My wife had apparantly rooted the device without me knowing, went to update it for my daughter for christmas, and now all I can get is a booting icon, and into the recovery menu. I'm sorry if someone has already received help for this, but i need to know how to get it back to stock. it has stock recovery menu, and i can't seem to find which recovery menu is compatible with this device, as well as an OTA file for it, or even a stock file
any help is very much appreciated.
Click to expand...
Click to collapse
. Oh no.
I'm afraid we don't have a recovery or stock image for the new Nabi JR. If you can't get back in to Android there isnt much we can do. Even if we could there is no custom recovery yet. We could make one if we could boot in to Android possibly. You could try booting stock recovery and pressing vol + and vol - at the same time. That will bring up a menu where you could try a factory reset. I don't think that will help but it's worth a shot.
aicjofs said:
. Oh no.
I'm afraid we don't have a recovery or stock image for the new Nabi JR. If you can't get back in to Android there isnt much we can do. Even if we could there is no custom recovery yet. We could make one if we could boot in to Android possibly. You could try booting stock recovery and pressing vol + and vol - at the same time. That will bring up a menu where you could try a factory reset. I don't think that will help but it's worth a shot.
Click to expand...
Click to collapse
unfortunately a factory reset didn't do the trick. would it be worth contacting customer support? purchase date was 11/30, receiving date was the 22nd
k35513r said:
unfortunately a factory reset didn't do the trick. would it be worth contacting customer support? purchase date was 11/30, receiving date was the 22nd
Click to expand...
Click to collapse
Its always worth a shot to see what they say. For someone to help you here there will need to be someone with a Nabi JR S model that is willing to root it, and grab the boot.img, then we need to build recovery and get a good image from a working device. It could take hours or it could take a month, or maybe never(although I know at least 2 people are interested in a recovery).
It's also possible someone could build the kernel from source if the Fuhu source is good and make a recovery(but you still need a 2nd tablet from someone to get a working system image). Either way it can't hurt to see what Nabi support will do.
I'll be calling them next week, if they don't fix it, I'll just buy another, and then I can assist you with getting a recovery image and whatnot. If they do fix it, then I can still assist, lol. Either way Id be happy to help when possible.
No response from customer support after a total hold time of 5 hours on 3 attempts. Corporate offers no response either. Probably short staffed after the bankruptcy filing
Sent from my SM-N910T using Tapatalk
k35513r said:
No response from customer support after a total hold time of 5 hours on 3 attempts. Corporate offers no response either. Probably short staffed after the bankruptcy filing
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I read the public record bankruptcy filing. They owe a lot of back pay to workers. I am sure the customer service could use a morale boost.
aicjofs said:
I read the public record bankruptcy filing. They owe a lot of back pay to workers. I am sure the customer service could use a morale boost.
Click to expand...
Click to collapse
i'll be watching if we get a system dump.
if it ends up being a total loss (as in fuhu doesn't come through), could always pull/tap the nand chip and dump it old school.
jr S seems to be out of stock everywhere now :-\
edit: also watching for any jr S ota url
PS what method did your wife use to Root it?
saw my first jr S in the wild today.
store only had a display model, or i might've picked one up to get at the special bits.
by chance anyone know the nabi default temp parent passwd (to get back to full android)?
default pass is usually zxcv6789
I have the SNBJR-MT5C, and I have been able to get root using the Kingo method through sideloading. It's a persistent even through factory reset with busybox installed. If someone could help I'd be happy to provide whatever is needed to get TWRP and Gapps on it.
Backups
I have a backup of everything off of this device. It is a mediatek 8127, and it is a PAIN. I have twrp installed on one, but the other one I have, installing the SAME ONE, bootloops. Is there somewhere I could upload that stuff to, so you guys can help?
peppy6582 said:
I have a backup of everything off of this device. It is a mediatek 8127, and it is a PAIN. I have twrp installed on one, but the other one I have, installing the SAME ONE, bootloops. Is there somewhere I could upload that stuff to, so you guys can help?
Click to expand...
Click to collapse
So you made TWRP for the new JR? Just zip it up and use google drive or something?
aicjofs said:
So you made TWRP for the new JR? Just zip it up and use google drive or something?
Click to expand...
Click to collapse
Not really a twrp backup. I got the files backed up with MTK Droid Tools. https://drive.google.com/file/d/0B9xUxjr7RhzYb19iekMydVZUS00/view?usp=sharing
Corbow6 said:
default pass is usually zxcv6789
I have the SNBJR-MT5C, and I have been able to get root using the Kingo method through sideloading. It's a persistent even through factory reset with busybox installed. If someone could help I'd be happy to provide whatever is needed to get TWRP and Gapps on it.
Click to expand...
Click to collapse
awesome, i'm not in here all the time and somehow missed the notification. if someone doesn't beat me to it, i'll try to write something up. in the meantime, don't brick it!
Install Google Play Store
Corbow6 said:
default pass is usually zxcv6789
I have the SNBJR-MT5C, and I have been able to get root using the Kingo method through sideloading. It's a persistent even through factory reset with busybox installed. If someone could help I'd be happy to provide whatever is needed to get TWRP and Gapps on it.
Click to expand...
Click to collapse
I just figure it out an way to install GAPPS on this model of Nabi Jr.
See my guide at : http://forum.xda-developers.com/android/development/guide-manually-install-play-store-fuhu-t3435200
peppy6582 said:
I have a backup of everything off of this device. It is a mediatek 8127, and it is a PAIN. I have twrp installed on one, but the other one I have, installing the SAME ONE, bootloops. Is there somewhere I could upload that stuff to, so you guys can help?
Click to expand...
Click to collapse
How are you able to get the firmware dump off the Junior? My friend and I are struggling to get SP Flash Tool to work properly on a Nabi SE unit we're attempting to dump the ROM from. With the driver Windows 10 automatically downloads upon detecting an MTK device, I get a COM port error, but when I used the one downloaded off Miracle Box's support page, all I get is this:
{
"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"
}
We tried practically everything to no avail (and nearly soft-bricked one of the SEs my friend has, only for it to somehow pull off a Lazarus lol), and I am at a loss at this. Care to help? More so if you by any chance have an SE at hand.
I have just purchased the Alcatel Raven A574BL with a Qualcomm 210 chipset . It's a great value running Android N and 2gb RAM, so being able to run a custom recovery will also make it a great value as a developer's tool. At $30 it's basically expendable, so I don't mind risking to brick it. So far I have not been able to find any root support for this device on Google. If anyone can help me get started with this, or point me in the right direction, it will be much appreciated.
mscott9437 said:
I have just purchased the Alcatel Raven A574BL with a Qualcomm 210 chipset . It's a great value running Android N and 2gb RAM, so being able to run a custom recovery will also make it a great value as a developer's tool. At $30 it's basically expendable, so I don't mind risking to brick it. So far I have not been able to find any root support for this device on Google. If anyone can help me get started with this, or point me in the right idirection, it will be much appreciated.
Click to expand...
Click to collapse
My understanding is the system is locked down and cannot be done. I've been wanting to do the same on same phone in your post.
thanks for the reply. i am disappointed to learn that it's impossible to root this phone... what i really need is a phone which is under $50 and can be easily rooted. also otg support will be a great bonus. it's totally ridiculous to pay up to $500 for a pixel... just so i can have root functionality. even if i could find a good deal on a recertified, most likely it won't support the latest android OS. if anybody out there can help me with this issue... which really shouldn't be an issue at all, it will be much appreciated. i'm trying to run android N at a minimum.
mscott9437 said:
thanks for the reply. i am disappointed to learn that it's impossible to root this phone... what i really need is a phone which is under $50 and can be easily rooted. also otg support will be a great bonus. it's totally ridiculous to pay up to $500 for a pixel... just so i can have root functionality. even if i could find a good deal on a recertified, most likely it won't support the latest android OS. if anybody out there can help me with this issue... which really shouldn't be an issue at all, it will be much appreciated. i'm trying to run android N at a minimum.
Click to expand...
Click to collapse
Search on the TWRP website, if a phone has TWRP available for it, it will also have a rooting solution.
The rest like searching one with Android N or above, I leave it to you.
HIT THANKS IF FOUND USEFUL
How do I root my Alcatel Raven
https://clickitornot.com/unlock-bootloader-on-alcatel-device/
Alcatel raven
Has anyone found a way to unlock bootloader and root this phone yet?
crazypwn said:
Has anyone found a way to unlock bootloader and root this phone yet?
Click to expand...
Click to collapse
I would like to bump this thread. I am in the same boat. Googling has gotten me now where.
Possibly
Although KingRoot seems to have found an exploit, it is iffy. The problem seems to be lack of supported fastboot. Not sure about Oem unlocking, though the option still is under settings>dev options>allow oem unlock(need dev access settings>about phone>build number tap 7x) Without full fastboot support, I can't see if it does anything. There is a possible solution, but since I'm new I can't share the link
Without a potential hard brick and basically cracking the OS, root is improbable. I nay have a solution. Still working on it.
Possible solution
King root seems to have taken down the exploit, since it rarely worked. There is a post on stupdroid that may have a solution. From what I can tell(I own the A574BL), although the OEM unlock function works, fastboot either does not work, or is locked down
To root your phone there are many way.
I can help you rooted your phone by getting boot.img
If you give boot.img there might be a hope
and to get TWRP
I'll need to port it by using your stock recovery.img as base.
or or or or....
You can make it by scracth
Reeak
I don't know of a way to get boot img. How do I make it myself?
or just give me your firmware files
Re
Peak.Krittin said:
or just give me your firmware files
Click to expand...
Click to collapse
How do I get those? Once again, these things are not publicly available for my device
clcombs262 said:
How do I get those? Once again, these things are not publicly available for my device
Click to expand...
Click to collapse
Well You got no hope right now.
If you came back with boot.img I will make the magic happen
Peak.Krittin said:
To root your phone there are many way.
I can help you rooted your phone by getting boot.img
If you give boot.img there might be a hope
and to get TWRP
I'll need to port it by using your stock recovery.img as base.
or or or or....
You can make it by scracth
Click to expand...
Click to collapse
you seem very helpful..
I just got this phone at BB for $15, on sale for 20 then another 5 email credit. Still using my Alcatel Ideal for phone use with Red Pocket AT&T sim for now, just using the Raven as kind of small wifi tablet. But I really like it after having gotten set up just right I'm pretty satisfied even with it not rooted. I'm watching this thread though, I'd probably be all over it if someone comes up with something. Good luck!
Maxxvds said:
https://clickitornot.com/unlock-bootloader-on-alcatel-device/
Click to expand...
Click to collapse
I have an Alcatel ZIP (A576BL), and I find it odd that you can root Alcatel's other devices and ported re-badged phones (ex ZTE Blade) but not THIER phones...
You can port TWRP recovery from alike devices with same chipset , android and kernel version etc. Also you can try 'systemless root' , for example Magisk.
Working with ADB Shell
So having just finished successfully rooting the Alcatel 5059r last night I was hoping I'd have some luck with the Raven. However I have not! At the moment I've hit a wall working with ADB Shell commands, hoping to push, move, mount/remount, and get a root out of it. As i've exhuasted the extent of my tools so down to the nitty gritty. So the problem I'm having with the ADB Shell end of things is that although I've got the proper commands nailed, I can't seem to mount/remount my system folder into read/write. Thats not a huge surprise considering I have no access beyond user. I have however found several folders and files of interest. I can manipulate the oem folder, but honestly at this point the easiest thing would justbe for me to move SuperSu Binary or MagiskSU.zip from storage or SD to the proper folders. As this is really the first time I've had to resort to such methods, and the literature on the subject is at first glance somewhat lacking; as it always is when things get this specialized.
If anyone has any ideas of how to go about using ADB Shell commands or any other method I haven't tried (all in one tool, platform tools, alcatel flasher, sp flasher, odin, frp hijacker tools ect) Keep in mind this phone at this moment in time doesn't support SD updating thru recovery, fastboot/bootloader/download is locked away somewhere, and yes ADB Sideloading methods as well. I'm willing to try anything and I'll put the time in and exhaust any ideas you guys may have for me!
{
"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"
}