Hello All,
Looks like I got myself into a pickle with my DNA......
Right now the only two things I can access on the phone are the bootloader and CWM.
How I got here:
I went into CWM recovery and deleted/formatted everything (absolutely everything that could be deleted and/or formatted), thinking I could flash a radio/firmware upgrade, then the LiquidSmooth rom from adb/fastboot. Been a long time since I've worked with this phone and now all I got is the bootloader and CWM. Thought I could use adb to push the rom zip to the device, then go into recovery and flash it the right way, but when I go to fastboot on the device and use the push command in adb it tells me "error device not found".
Gonna stop right there and seek some advice. What's the best way to correct this mess?
Thanks ahead of time!
PS: Working with a DNA with an unlocked bootloader (S-ON), and it was running the stock rom before the first OTA update. I did make a backup file and save it to my PC before I did anything. But, now adb is suddenly not recognizing that the device is connected so I can't push any files to it.
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
d08speed3 said:
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Not real sure how this will help me.
I cannot boot into Android, and at this point whenever I try to push files to the device via adb it gives me an error and says device not found.
Tried to sideload in recovery?
RLGL said:
Tried to sideload in recovery?
Click to expand...
Click to collapse
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
{
"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"
}
Hackenstein said:
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
Click to expand...
Click to collapse
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
No os installed!!! Need help asap!!!!please
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
CHRIST STARZ said:
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
Click to expand...
Click to collapse
There is a search feature to use for finding out how to recover from your mistakes.
Try searching for error 158.
Hackenstein said:
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
Well Said, and on that note, DEVS - I do appreciate all info that I receive here, whether it's from searching/reading or when a question gets answered. Thanks for all you do!!!
tat
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
I really love the fact that so many came in to actually ANSWER my question(s) and give relevant info on the issues I was experiencing (heavy sarcasm obviously). Ironic that only when I took a jab at someone's work (out of frustration) that the thread became active with people only sounding off on that issue, still ignoring the original problems I brought to the table. Top notch support!!!!!!
With that out of the way, to santod040; please accept my apology. I said that out of complete frustration and it was totally unecessary. Contrary to the negative vibes that comment conveyed, I DO appreciate all the devs hard work and allow me to publicly thank you for that. It was bad night of troubleshooting for me as I've been out of the loop for quite sometime and was rusty in several areas. Adding to that was the complete lack of helpful info I was finding not only on this site but several others. Kept going in circles and getting no where.
It is extremely important I point out that out of five different ROM's I tried to install via sideload, your's is the ONLY one that actually worked and in the end, I went back to it as it allowed me to finally boot into Android and enable USB debugging and help get the S-OFF process started via Firewater. Conclusively, I was finally able to get the baseband upgraded and get the phone fully up to date. So, thank you, wholeheartedly, and I apologize again for letting my stress get the better of me that night. LiquidSmooth saved my ass.
Cheers, my friend, and thanks again.
I can help if your s-off
hackenstein said:
the problem with that turned out to be an outdated version of cwm. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade i also needed a driver upgrade which i took care of (after i had installed twrp to test as well, just stuck with twrp). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When i'm done there, should i run firewater to achieve s-off so i can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
if your s-off i have a method that will help you .....have you switched to s-off?
Related
See my post from below from Original Development section:
Snuzzo said:
Ok from my testing I have found a different way for the s-on flashers to enjoy flashing a new rom without using fastboot. It does involve using an unsecured ram-disk which current JB roms do not offer. Sense roms do however and it works very similar to the DNA/Flashimggui technique of flashing a boot inside the rom. I have a script made for it but need feedback on it:
1) Include the script in ram-disk or system/bin? If ram-disk, a symlink can happen to system/bin if needed. Also might be easier to implement if in ram-disk and won't have to change much to the rom building. This could be easier implemented into ram-disk it's separate in a device tree away from the rom source.
2) Use what boot from what directory? Was contemplating labelling a folder called sonromflash, that would contain a boot.img inside the folder called newboot.img. That is going to have to be a collective census/poll.
3) Implement a menu choice or just a straight confirm flash of boot? Build this up to allow multiple boot.img's on (see point 2). May be named as boot<romname><romversion>.img.
4) An idea or a feasible implementation? This could add yet another factor in an s-on user thinking he/she is soft-bricked, so implement or just keep it as an idea for the future if needed.
5) If it does get implemented, how many users would learn fastboot? We all know some users just dive right in and only read parts of instruction or details (I was one of them when I first got this device, but yet was acclaimated in command prompts/scripts/and some C knowledge). Alot of softbricks can be easily fixed if read instructions properly. This would just add a "link in the chain", refer to 4th point.
This is just part of what I have been working on over the past couple weeks and what I found from that time when working on an update for a kernel on a rom outside of xda of a name I will not mention. It works 110% if utilized properly(read point 5). Tested courtesy of a couple of my faithful users that like the security of s-on & great friends if I might add.
PS:Sorry for the long rambling
Click to expand...
Click to collapse
TL;DR
Found a way to change the current boot flashing for S-On users which could lead into something a little more "user friendly" but could lead to beleiving a softbrick occurred when all that was needed was to factory reset and flash the matching rom upon reboot. I do have another way to utilize which is using another original work by con247 (not modifying his work at all). Feedback is needed in this change.
Snuzzo said:
See my post from below from Original Development section:
TL;DR
Found a way to change the current boot flashing for S-On users which could lead into something a little more "user friendly" but could lead to beleiving a softbrick occurred when all that was needed was to factory reset and flash the matching rom upon reboot. I do have another way to utilize which is using another original work by con247 (not modifying his work at all). Feedback is needed in this change.
Click to expand...
Click to collapse
Seems like a good idea for the people who haven't taken the S-Off plunge. My Rezound is my backup phone which I may give to my sister but I think the rewards outweigh the risks in this case.
Snuzzo said:
See my post from below from Original Development section:
TL;DR
Found a way to change the current boot flashing for S-On users which could lead into something a little more "user friendly" but could lead to beleiving a softbrick occurred when all that was needed was to factory reset and flash the matching rom upon reboot. I do have another way to utilize which is using another original work by con247 (not modifying his work at all). Feedback is needed in this change.
Click to expand...
Click to collapse
Most, if not all of us have s-off'd because of not wanting do deal with flashing via fastboot. I understand that it doesn't take long to flash and the process is pretty painless, but I am rarely sitting in front of a PC when I flash. If we all had the ability to flash the boot.img while being s-on and mobile and still keep the security of being s-on, I think that would be a win/win for everybody involved. Your scripting genius continues to amaze me. As long as those who run this understand the process, I cant see a downside
Hey Snuzzo,
I think this a pretty good idea for those who are not s-off, as long as those few understand and can read instructions. As TheBr0ken stated " Your scripting genius continues to amaze me" says it all about what you have done with your scripting.
Thanks for everything.
1Raiders said:
Hey Snuzzo,
I think this a pretty good idea for those who are not s-off, as long as those few understand and can read instructions. As TheBr0ken stated " Your scripting genius continues to amaze me" says it all about what you have done with your scripting.
Thanks for everything.
Click to expand...
Click to collapse
I agree. The scripts you have are awesome. For those that don't have s off this would cure them of having to do much work. Really its not a lot to do but some are uncomfortable messing with the phone but want the same advantages. I know I was scared at first doing the paperclip thing with the rezound but it turned out a piece of cake. Bricking a phone is natural I think if you really can't follow directions you probably should be extra cautious when messing with these things. But still, it's rare among a well rooted and versed community.
I think it's a great idea. There are plenty of people that are still s-on and this would be a great added bonus to make it easier on them. I also would never have figured out how to do this.
Hats off u da man!!
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
This would definitely help alleviate the questions resulting from standard s-on flashing procedures.
What do you think about point 2? Any input there? External sdcard? Have it search the whole sdcard or only a particular directory?
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
Snuzzo said:
What do you think about point 2? Any input there? External sdcard? Have it search the whole sdcard or only a particular directory?
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Set it to a directory like recoveries do for backups. Would help keep it organized.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
I just went through the learning curve and think this would be great. I think at some point you will still be forced to learn fast boot as I rooted right before the latest update and that upgrade just about convinced me to just go s-off.
But I am staying s-on and would like to fash roms without a pc or a lot of prep work done on a pc.
Sent from my Infected Rezound using xda app-developers app
As the tester who sent his phone into boot loops with it... I'm still a fan of the idea, I just didn't have a good concept of exactly what was going on. I haven't tried to switch off a sense rom yet, but so long as that option would still exist, I'm all for it.
Quick message regarding recovery flashing and s-on from my chatter thread on MikForums
kcirtap420 said:
Had to flash amon ra to get on rezone (ReZone Redux), so I decided to try this and it worked!
{
"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"
}
Sorry about that SU permission in the way.
Click to expand...
Click to collapse
Might be making this live sooner that i thought.
I think it's a great idea. I came from the Incredible which was a tremendous device to flash on because it was so easy and painless, the Rezound...well it sucks being s-on. I hate being tied to a PC to throw on a different ROM and now I have an SDK issue to iron out and it makes me hate flashing rom's because its too many steps/commands. I want Android to be open and easy to flash, not jump through hoop after hoop. If you could make this happen I would come back to the Rezound, I got fed up and went back to my iPhone4. I really miss the Incredible!
So I recently bought this smartphone from walmart under Straight Talk. And from my understanding it must be pretty recently released as I haven't found much in terms of unlocking/rooting/any posting about it on any forums. After numerous failed attempts at rooting it (z4root, poot, bin4ry, etc) I learned that I have to unlock the bootloader first. "Progress! Finally!" I think to myself, go to their website to request an unlock code....and it turns out my phone model isn't listed. At this point I figure if the company website is handing out unlock codes perhaps I can contact support...long story short, no. The support person didnt even believe I was on the right website when I told him you could request unlock codes, and proceeded to ask me the brand of my phone, twice. Go Figure.
Has anyone had any experience unlocking huawei brand smartphones? Is there anything that will help me out with something this new? I google it and get a crap ton of info on modems instead.
whaevr said:
So I recently bought this smartphone from walmart under Straight Talk. And from my understanding it must be pretty recently released as I haven't found much in terms of unlocking/rooting/any posting about it on any forums. After numerous failed attempts at rooting it (z4root, poot, bin4ry, etc) I learned that I have to unlock the bootloader first. "Progress! Finally!" I think to myself, go to their website to request an unlock code....and it turns out my phone model isn't listed. At this point I figure if the company website is handing out unlock codes perhaps I can contact support...long story short, no. The support person didnt even believe I was on the right website when I told him you could request unlock codes, and proceeded to ask me the brand of my phone, twice. Go Figure.
Has anyone had any experience unlocking huawei brand smartphones? Is there anything that will help me out with something this new? I google it and get a crap ton of info on modems instead.
Click to expand...
Click to collapse
Use srsroot. I rooted mine with it. Works like a charm.
amazinglarry311 said:
Use srsroot. I rooted mine with it. Works like a charm.
Click to expand...
Click to collapse
Wow thanks! Took the words right out of my mouth hah, worked like a charm. So you have the same device as me then? Have you tried flashing any custom ROMs to it?? Thats what I ultimately wanted to do but I doubt any would have support for this phone..?
[ QUOTE=whaevr;41912176]Wow thanks! Took the words right out of my mouth hah, worked like a charm. So you have the same device as me then? Have you tried flashing any custom ROMs to it?? Thats what I ultimately wanted to do but I doubt any would have support for this phone..?[/QUOTE]
I wanted to try building clockwork for it, but I can't find the recovery partition. Without a concrete partition table, and not knowing if the recovery binaries are in initramfs of the boot.img, I'm weary of trying it as I don't have a a private PC to install fastboot drivers to test it. Once a custom recovery is built I can start working on a modified ROM and hopefully find some source for the kernel and try overclocking patches etc.
Maybe something like the roms I built for the Samsung optimus q. Or possibly starting an arearom development team over at Androidarea51.com
Out should only be a matter of time before interest picks up, it's one of the best phones straighttalk is offering for the price. If anyone is interested or has information on developing any of the custom recovery programs like twrp 4ext or cwm I'd love to start a team fit development.
I've found firmware files on some Chinese websites, but no straighttalk specific builds.
I apologize for reviving an old thread like this but I've been looking for a custom rom for my ascend plus for about a week now and no luck whatsoever, if you ever find any info, please, let me know!
I'm just waiting on someone to build a recovery
Sent from my HUAWEI H881C using xda app-developers app
I'm about to try to pull the boot.img and take a peek inside. Wish me luck.
Sent from my HUAWEI H881C using xda app-developers app
..and they were never heard from again. Seriously though I'm curious if you made any progress? I'm having fun making this phone better, expanding my storage space with link2sd and anything else I can figure out. The HUAWEI H881C has low internal storage, but for the small price I'm not complaining. I liked it the 5 days I had it before I hacked it and its even better once its rooted and modified.
Besides my Android YINLIPS YDPG18 gaming pad the HUAWEI H881C is my 1st Android phone. Might be fun to try a custom rom on it. Good luck with it.
area51developers said:
we have pulled the boot.img and recovery.img of the H881C and are currently working on a CWM Based recovery for this phone at androidarea51.com.. please hang on while we work this out... thanks...
Click to expand...
Click to collapse
SRSRoot the HUAWEI H881C/Ascend Plus
Its pretty easy rooting the HUAWEI H881C/Ascend Plus with SRS One Click Root in just a few minutes using the [Root Device (SmartRoot)] option.
Before you connect the phone to the PC make sure to go into phone settings and under Settings-->PERSONAL-->Security check/enable the “Unknown sources” option under the DEVICE ADMINISTRATION section. Then back out from there once into the main settings screen again and look toward the bottom under SYSTEM-->{ } Developer options and at the very top of that submenu check/enable the “USB debugging” option.
From a windows PC you will need java, the SRSRoot program available free from their website and the Huawei H881C’s ADB drivers installed. You don't need to find the ADB driver install because its actually in your phone. If you didn't notice before when you plug your phone into a PC it automagically mounts and maps a drive letter to an image/folder on your phone with the install executable for the ADB drivers. On that drive:\drivers\adb_driver you will find the driver installer exe named, "Handset WinDriver.exe".
{
"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"
}
Once all that is installed reboot your PC if necessary. Make sure your phone is plugged in to your PC then run the program link that SRSRoot puts on your desktop by default. If you're on Vista, Windows 7 or 8 you might need to right click the shortcut and run SRSRoot as admin. The rooting process should take less than a minute if all is working correctly.
I would try the [Root Device (SmartRoot)] option 1st. Once its finished rooting your phone SRSRoot will install SuperUser on to your phone and that's it you're rooted.
Good luck!
This will also work in a properly setup virtualbox install of windows. I myself used a virtualbox install of windows xp to root mine since I run arch based Manjaro linux on my PC.
Retro Gamer said:
..and they were never heard from again.
Click to expand...
Click to collapse
Not really :\
From the androidarea51 forums, huawei board
"huawei is the new motorola as the locked bootloader is making it impossible to put cwm on the phone so far. we tried one the other day and bricked the device."
I would link to the post but Im not allowed being a "new" member and all
Ahhh thats too bad, maybe :fingers-crossed: some day someone will find a way. Thanks for the info!
whaevr said:
Not really :\
From the androidarea51 forums, huawei board
"huawei is the new motorola as the locked bootloader is making it impossible to put cwm on the phone so far. we tried one the other day and bricked the device."
I would link to the post but Im not allowed being a "new" member and all
Click to expand...
Click to collapse
Well guys I believe I've pulled the boot.omg anyone know how to build cwm? I can't find my Ubuntu disk to setup the build environment
Sent from my HUAWEI H881C using xda app-developers app
Rooting H881C
found an even easier way using framaroot's Gandalf method one click no adb or anything but make sure its the most up to date version
Help please im a noob...
Okay, so I rooted my H881c with ease, but I've been looking for stuff I can do with it rooted. Ive changed boot animation that was fun, here and there changed some specs. I'm new to the world of modding and android, so i am trying to learn what flashing, kernel, nand are. I'm sorry i am a noob and ill admit it. But since i get have this phone through straight talk, i haven't received and ota updates and i really want to update to 4.1 jelly bean at least. is there anyway of manually putting the update or upgrade on my phone so i can be on OFW jelly bean? I'm sorry if thats a stupid question but no one has been able to answer my question because when i google this phone, no one has it or they have a different Huawei phone. any help guys please, it would be very much appreciated.
Rooting this phone is your only option at this time.
Sent from my Amazon Otter using xda app-developers app
Well I know someone pulled a boot.img so hopefully I won't have to wait to long..
Sent from my HUAWEI H881C
Huawei Pains said:
Well I know someone pulled a boot.img so hopefully I won't have to wait to long..
Sent from my HUAWEI H881C
Click to expand...
Click to collapse
If I root it, can I avoid using whatever UI they've put on it and just customize Android the way I want it?
whaevr said:
Not really :\
From the androidarea51 forums, huawei board
"huawei is the new motorola as the locked bootloader is making it impossible to put cwm on the phone so far. we tried one the other day and bricked the device."
I would link to the post but Im not allowed being a "new" member and all
Click to expand...
Click to collapse
REVIVAL!!!
What has happened to the recovery support for this phone?
I have checked everywhere and seen nothing!!
Is there a unlocker for this thing yet???
I'm so confused as to how I'm going to put a custom recovery on here.
What can I do????
P.S. I've tried to e-mail Huawei and they said they can't provide a code!!! WTF??!!!
And no one responds...
Is there a way I can start the process of unlocking bootloader?
Never tried before. A little help needed.
Sent from my NookColor using XDA Free mobile app
Well...
From what i can tell, the ball is rolling on the Huawei H881C Acsend Ace & have been watching it closely. They have managed to pull the system.img boot.img and recovery.img & successfully UNLOCK the bootloader. BUT the problem is that when they try to make the unlock stick, the "Sig Verify" fails and therefore, nothing more has progressed YET. :cyclops: Still hopeful. :crying:
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.
It's not on the net anywhere either, google is not working for the OT Elevate. There are no custom ROMs for the OT Elevate either.
I know that someone has one of these OT Elevate 5017B phones lying around somewhere. Post a stock ROM for download. People are suffering from bricks and soft-bricks. HELP more, we need to start a project making an attempt to catalog stock ROMs for every android device on earth.
There needs to be a larger archive of these ROMS. iOS developers are killing you. They have a database of all of the iOS firmwares, and there is a database of custom firmwares even for the iPhone 6S.
I know that the iPhone's situation is different, that one company designs the hardware and the software, and that everything is proprietary. I also feel there are too many companies making android phones. competition is one thing, but security of an OS is another. different phones from the same year with older versions of the OS on them, not good.
Marshmellow has been released and there are still 2016 phone releases with 4.5 OS on them. That's not secure. Why can't we make Android more secure by building better custom ROMs for more devices? I know there is a big shortage of developers, but you can recruit. Maybe even get funded by an organization, research grant?
Everyone needs more ROMs. Especially for Alcatel OT Elevate. Let's do something about this.
On 3. 1-2-3, Go Team!!!! :highfive: Let's Get It!
I have one of those Alcatel OneTouch phones right now, and I agree completely upon the notion for a catalog of all android devices that can be flashed.
@mU$!c @tyrex420
These Alcatel devices can only get attention if developers have them in their hands to work with. These devices are running a MediaTek SoC and not many developers like to work with those phones because of a lack of source code to work with or incomplete source in some cases. Yes you are correct in saying that Apple is different as it's one software, one hardware but you have to understand Google only set the stage and the companies do the rest. Not every company is Samsung or Sony. Alcatel has a tool which is really good called Mobile Upgrade Tool which has the factory ROM for their devices (which imho they need work on getting those newer devices supported). It works well if you haven't done much modification to your phone. Now the thing is that when those companies take the phones and modify them in some way like in locking the bootloader or hiding fastboot mode (Tracfone,MetroPCS), there's not much that a developer can do about that. Also those companies do not have that same support tool that Alcatel has which re-downloads the factory ROM because they are modified in some way.
Here's the good part about the phone running a MTK SoC. There are third-party tools such as MTK Droid Tools or SmartPhoneFlashTool (SPFT) which enables the users to make factory backups of their ROMs in the event that their devices suffers from a bootloop. What you can now do is become that developer that you are asking for to work on your phone and make something out of it. Be the first to upload a flashable factory ROM for your phone. Create a thread where users can come and post their issues and assist each other positively. It's nothing hard to do unless as I said before the company locks some part of the phone and makes these tools useless. By the way, MTK Droid Tools developer dropped support at Jelly Bean so KitKat and up won't work with the tool as it should.
Again, yes I agree with you in saying it would be nice for a users to find a compilation of ROMs that they can just follow instructions and flash but the thing is source code and users themselves not knowing how to use the tools mentioned above. If you want you can ask me for help in guiding you on how to use the tools. I've been doing this for 3 years now working with MTK and I'm learning something new everyday.
Sorry for my long reply, I hope to see a reply from you concerning getting a factory ROM for this device maybe a thread similar to mine .
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
bg260 said:
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
Click to expand...
Click to collapse
You're welcome .
kirito9 said:
You're welcome .
Click to expand...
Click to collapse
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
bg260 said:
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
Click to expand...
Click to collapse
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
kirito9 said:
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
Click to expand...
Click to collapse
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
bg260 said:
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
Click to expand...
Click to collapse
Yeah although the information is quite old still useful.
Root with Kingroot and backup with flashify haha. But won't you need the unlocked bootloader to root?
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
bg260 said:
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
Click to expand...
Click to collapse
Ahh cheap phone problems. Let me know if you get through.
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
{
"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"
}
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
bg260 said:
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
View attachment 3906591
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
Click to expand...
Click to collapse
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
kirito9 said:
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
Click to expand...
Click to collapse
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
bg260 said:
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
Click to expand...
Click to collapse
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
kirito9 said:
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
Click to expand...
Click to collapse
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
bg260 said:
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
Click to expand...
Click to collapse
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
kirito9 said:
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
Click to expand...
Click to collapse
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
bg260 said:
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
Click to expand...
Click to collapse
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
kirito9 said:
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
Click to expand...
Click to collapse
See if this is what you need. Created it with DiskInfo Pro. I used a different machine and mounted the system image fine. I thought it was a bad copy because the Build.prop displayed as broken. Then I realized it was just a symlink to the actual build.prop in custpack. At any rate, there's a copy of the build.prop in there as well.
View attachment build.prop-partitions-5017b.zip
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"
}