Hi there! I need someone help because, i'm really lost. :X
I have one primux bora 7 with ICS 4.0.3 and i want to install the CM9 ROM.
I see in this forum and i download this files that see in this picture:
img231.imageshack.us/img231/1876/pict3012.jpg
After this i install the CM9 nightly and appears in me screen this:
img37.imageshack.us/img37/7249/pict3013.jpg
Until this it's ok.
Then, when i install compatibility mode and/or gapps, appears on my screen this: (and even with only .zip files in the external sd card appears that)
img22.imageshack.us/img22/7228/pict3015i.jpg
Then i reboot the device, and it enter on a boot loop mode, that i can't do anything. Even the tablet it's not recognizes in windows mode (usb drivers didn't work). Touchscreen didn't work to. I'm desperate to fix this. My question is:
Can anyone give me some help, that can permit me to install CM9 in this tablet. I need noob tutorials. I don't understanding nothing of this, and i appreciate some patient from user here. please!
Can anyone help me with this?
Best regards in advance!
Help. I have a Superpad 8 Chinese tablet that will not boot.
At first, it would boot only as far as the "Andrtoid" boot animation and just hang there.
Then I started trying to restore a different ROm to it.
ADB sees it, and I was able to pull the /system directory from the tab.
After trying to flash a ROM to it using this "Livesuite" app I found, , which completed successfully, but since then, when the tab boots, it displays absolutely nothing.
ADB still sees it, but whatever command I send (adb reboot recovery or adb reboot bootloader), it just reboots and does nothing...
Can ANYBODY help, please?
I am still very new to ADB & troubleshooting Android, so I need all the help I can get!
Thanks in advance, and if you manage to get this tab working for me, I'll buy you a beer or 5...
skoop99 said:
Help. I have a Superpad 8 Chinese tablet that will not boot.
At first, it would boot only as far as the "Andrtoid" boot animation and just hang there.
Then I started trying to restore a different ROm to it.
ADB sees it, and I was able to pull the /system directory from the tab.
After trying to flash a ROM to it using this "Livesuite" app I found, , which completed successfully, but since then, when the tab boots, it displays absolutely nothing.
ADB still sees it, but whatever command I send (adb reboot recovery or adb reboot bootloader), it just reboots and does nothing...
Can ANYBODY help, please?
I am still very new to ADB & troubleshooting Android, so I need all the help I can get!
Thanks in advance, and if you manage to get this tab working for me, I'll buy you a beer or 5...
Click to expand...
Click to collapse
Is youre problem solved??
cejean said:
Is youre problem solved??
Click to expand...
Click to collapse
Hi Have the same problem if anyone can help Please. I'm still new to all this
same problem any ideas
any ideas to fit the problem?
Hello, I had a very similar problem which I had which might help with a BC1003 user.
first was the internal LCD cable came loose.. common problem...
Another was it would not boot at all. So I used Livesuit with "sun4i_crane_bc1003.img" dated August 2012... November 2012 did not work!.
It does appear to matter which .img file you use (unfortunately), because the WiFi does not work with the November version.
hi ... same tablet, some problem...
skoop99 said:
Help. I have a Superpad 8 Chinese tablet that will not boot.
hi ... same tablet, some problem...
after 3 days trying every possible firmware, and booting them from external sd card
all i could do was change de logo at boot start from (mapan to kosaco, to oem etc..)
than i had the idea of removing the internal sd card to look at it ...
and guess what it still runs the same with out no sd card in or out
so i thought ... the sd card was never read in the first place cause is damage or corrupted...
so on the 4th day im trying to format and partition the new internal sd card... hoping for the best.
by know u may not even have that tablet anymore but is food for thought for a next android promblems.
:good:
Click to expand...
Click to collapse
Hi everyone,
So I bought my friends HTC ONE X PLUS off him even though he had boot loop following a botched Custom ROM installation.
Stupidly I thought I could fix it.
It is an international device locked to O2. It loops at the HTC logo and allows boot into bootloader and CWM. The problem I have is that the PC doesnt even recognise it as a USB MASS (even after downloading the latest drivers - several times ) CWM wont even mount the storage.
Ive tried sideloading and everything else but no joy. The RUU I need to flash back to stock isnt out yet ? 1.17.206.1 and I cant ( as mentioned ) just dump an img/zip into the root as I cant get access to the storage. Its shows on the PC as removable storage but when I click it it asks me to insert a disk.
When I adb device/fastboot device it gives a number and says fastboot. ADB shows nothing in list of attached devices.
Any suggestions? If anyone in the UK would be happy for me to post it to them so they can have a go Id be happy to fund a beer or 2 in return
Thanks all.
mikejasonsmith said:
Hi everyone,
So I bought my friends HTC ONE X PLUS off him even though he had boot loop following a botched Custom ROM installation.
Stupidly I thought I could fix it.
It is an international device locked to O2. It loops at the HTC logo and allows boot into bootloader and CWM. The problem I have is that the PC doesnt even recognise it as a USB MASS (even after downloading the latest drivers - several times ) CWM wont even mount the storage.
Ive tried sideloading and everything else but no joy. The RUU I need to flash back to stock isnt out yet ? 1.17.206.1 and I cant ( as mentioned ) just dump an img/zip into the root as I cant get access to the storage. Its shows on the PC as removable storage but when I click it it asks me to insert a disk.
When I adb device/fastboot device it gives a number and says fastboot. ADB shows nothing in list of attached devices.
Any suggestions? If anyone in the UK would be happy for me to post it to them so they can have a go Id be happy to fund a beer or 2 in return
Thanks all.
Click to expand...
Click to collapse
The reason why the phone does not boot up anymore is that you friend probably forgot to flash the proper kernel/boot.img for the rom he installed. The kernal can't be flashed in recovery because the phone is still S-ON. In the HTC One X+ General forum you will find two tutorials with everything you need to know about unlocking/rooting/flashing using this phone. If you read both of them carefully, you should be able to solve your problem. Don't forget to press Thanks for the two guys who made these guides!!!
Also here you should be able to find the correct RUU for your CID. But since it needs relocked bootloader, you probably will have to read the to guides anyway and it is probably much easier to stay with unlocked bootloader and do the right flashing procedure.
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
Hello my dear fellow community of XDA
I’m asking you for help, I found myself in a tough situation because I damaged system in tablet Nexus 9. Bootloader was already unlocked in my device when I bought it. I assume that the system was original. I didn’t notice any modifications. I damaged this system by uploading a file in a fastboot mode connected by ADB. This file is for rooting. I used this guide on the YouTube:
After doing everything step by step in this guide and switching my device on there was a sign of launching - vibration. The next thing I saw was white Google logo and after that the animation of loading appeared. It was loading without any success.
Before uploading the root file I also tried to upload TWRP file via ADB but it didn’t make any difference. After uploading TWRP files system launched properly, there is no new app in the app list and no combination of buttons such as power + volume that launches TWRP. Please tell me if I’m doing something wrong…
I tried to fix this bootloop by cleaning files via Hboot - factory reset but it didn’t change anything. I was searching for guides that would help me solve my problem but I couldn’t find anything useful. Each of them was old. They were from 2014 or 2015.
I would like to have a working tablet with TWRP, root and other unofficial system (you can give me some suggestions, I was thinking about Android 9). I don’t know where to start or what should I do first. Fix bootloop or upload TWRP ? What is correct order ? How to upload TWRP eligibly ? I rooted devices only several times so please excuse me, I am not a professional. I know that guide on YouTube mentioned before was for Android „L” not „N”.
Summary:
> Tablet Nexus 9 OP82100 WiFi version 32GB
> I use PC with Windows 10
> After connecting the tablet to the PC via USB cable in fastboot mode the tablet is visible in ADB console on the list of devices.
I hope that each information I gave you is clear enough. This is my first post on this forum. I hope somebody will find some minutes for reading this post. I’m counting on you. Thank you in advance for any help.
Ok, I honestly didn't read everything, but if you have and can access fastboot, flash TWRP, transfer a ROM to the internal memory, wipe data (not storage) and flash your ROM.
Try getting Wug's Nexus Root Toolkit, it's a graphical UI for adb and fastboot, might be a little friendlier for you.