Alright, so I know what went wrong. I messed up, I know I did, so please try not to mention it.
I accidentally deleted my lib folder in the /system directory using root explorer. What I was trying to do is replace it with the one found in a different thread (as I was missing some files that I needed to receive the BELL OTA update)
So now the phone will not boot past the above mentioned logo (thread title)
I have tried going into android recovery and wiping and restoring all data but that did not help, my phone is not unlocked and I have never installed a different ROM.
What should I do?
I may be wrong, but if you are not unlocked, you may have to do a full SBF flash to get back up and running. If you were unlocked you could just flash a system.img via fastboot.
Alright, I will look into that, right now I am at school so if you could give me a link to a guide for the Bell Motorola Atrix I would appreciate it, if not I will search through the forums for it later.
Thanks for the help!
what did you make on your case.
I have the same problem.
Please help me
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.
hi still looking for help with my avoca android tablet. it doesnt boot up into android operating system just stuck on boot screen but can go into recovery mode with things like reboot now, update rkimage and so on.
i have tried to root it with an app called kingo root and says its rooted but i have tried to install a custom rom but nothing happens says aborted. is there anything i can do bare in mind i cannot access the tablet to turn usb debugging on and nothing else. if there is a thread here that will help and get things working again then id be really grateful or if someone can tell me what to do any help will be appreciated.
Well first off root will not allow you to flash a custom rom. You need an unlocked bootloader as well as a custom recovery. Your best bet would be find the stock image and flash that to get it running again and then take a week and do some reading and learn what your doing
I no what I'm doing I just can't find the things I need as the company no longer exist and I've searched hi and lo for a copy of their stock rom but nothing if I had that I no il be ok. But not sure how to unlock bootloader as I've used adb and fastboot but it don't work says waiting for device. Any pointers please
spampocket said:
I no what I'm doing I just can't find the things I need as the company no longer exist and I've searched hi and lo for a copy of their stock rom but nothing if I had that I no il be ok. But not sure how to unlock bootloader as I've used adb and fastboot but it don't work says waiting for device. Any pointers please
Click to expand...
Click to collapse
That is one of the biggest issues with cheap devices like this. You will most likely never find drivers or the stock rom for it. The best thing you might be able to pull off is porting a rom from a similar device.
Thanks yeah I think it's my only hope all I got to go by really is that this model of tablet uses jelly bean 4.2 as stock, so may see if can flash a stock rom from googles dev site as they have different model stock rims and just hope that one works. Il try nexus stock one first see if get lucky if not just work done the list. What do you recommend I do first shall I unlock bootloader first even though the command doesn't work in fastboot says device null or waiting when I type fastboot oem unlock. Or am I better starting off with a stock rom using adb? Also what recovery do you recommend I've used twrp and clockwork. Thanks
I'm trying to side load twrp using adb and all I get is opening update package, verifying update package, then installation failed do you no what I'm doing wrong
OK, so here is the situation. My ZTE n9520 is/was rooted, however, it also had an update available for a while. I chose not to update it though due to the fact that it was not worth it at the time. I ended up changing devices and gave the ZTE to my other half to use since it was better than theirs. Without thinking, or asking, they did the OTA update and it seriously screwed up the device since it was rooted and thus the partitions were changed. Now it only boots to the system recovery screen due to the update and root conflicting. I hope everyone's with me so far. If I had a computer, I could connect it and go through the lovely process of fixing it that way. As luck would have it, I do not have a computer and it is no longer under warranty. Does anyone know of any way possible that I can fix this without a computer? I actually dropped the phone I am using and it broke, like into a thousand pieces and I have need of the ZTE. Please help me out, your my only hope my good people.
I see a lot of views, but nothing posted. Please help me out.
Any chance someone has an idea how to fix this?
I actually tried that already. A few times. Since it was rooted when the OTA update was performed, the partitions were changed and that is what caused all of this to happen. I appreciate your advice though.
Would anyone else possibly have an idea on how to fix this?
I take it I am SOL with this since no one else will reply?
Would it be possible to download the stock ROM for this onto an SD card and put it into the ZTE n9520 and go through the recovery that way?
So still no possible answer?
Would anyone have a possible answer to this?
I may get yelled at for this, but would getting a copy of the stock recovery or possible stock ROM for the ZTE possibly work? I am trying anything I can and am coming up short all around. I was hoping I would have gotten more information by this point. I know this thread is oldish, but I really don't have the money for a new one and am still without a computer at the moment.
Would anyone happen to know if there is a way to fix the partitions on the device without a computer?
Small question... Would it be possible to flash the partition without a computer? Or TWRP or CWM? I saw somewhere about an Android 4.1 partition flash and was wondering if there was a way to flash/fix the partition without a PC?
I just recently ran into this problem and was able to fix it.
I know this thread is old but better late than never. Perhaps you still need to fix your ZTE Max after all this time.
Here are two links that will fix your problem.
The first is to "unbrick" it. This is really just to install a custom recovery so that you can flash a working rom. It also allows you to flash some stuff that is supposed to fix the partitioning. (Though i dont think that is actually your problem. I think you are just in a bootloop, but for me flashing a normal stock rom through recovery failed.)
Unbrick:
HTML:
http://androidforums.com/threads/tool-alpha-zte-max-unbrick-tool-need-testers.836089/
Roms/Partition Fixes:
HTML:
http://androidforums.com/threads/zte-max-stock-b06-4-4-2-deodexed-custom-and-unmodified.896210/
The unbrick tool requires you to burn a file to a CD and boot your computer with it. I just tried it on my bricked ZTE Max and it works perfectly.
After that just download the rom/fixes you need, put em on an SD card, and flash em through the newly installed custom recovery.
Double post sorry
I'm totally new to using ADB and am mucking my way through as best I can. To experiment, I'm trying to resurrect an old TMO Alcatel One Touch Pixi 7. I'm reasonably sure that I've found the right boot, recovery and system images and the machine is recognized in ADB but when I try to sideload them, I get a signature verification error. So, I don't know if I need to figure a way to get the signature right (I haven't a clue as to how to do that) or make a .zip that I can load onto the SD card and flash via the stock recovery.
If I'm going to flash via the stock recovery and a .zip, I have no idea how to make a .zip for the SD card. I know that if I use that method, I can turn off signature verification.
Just a note - I am totally new to anything Android development. I have rooted every phone I've ever owned but most are Samsungs and the Pixi died as a result of trying to root it. I managed to resurrect an old Samsung Tab S2 by flashing the firmware via Odin but this is my first foray into ADB or fastboot. This is my long-winded way of saying I don't actually speak the language and have done all my previous work building off the efforts of others. I am, for all intents, talent-less in this regard but trying to learn.
Any ideas/suggestions/indications on a path to follow?
I'm on my back for the next three weeks after surgery, so I might as well do this. No one wants to read my memoirs, that's sure!
Any help is appreciated!