Hello,
I hope someone can help in this weird situation that I try to explain in the shortest way possible:
1) I bought a second hand Galaxy S2 GT-I9100 with a broken home button as I was confident to be able to manage everything by Odin and that was the case as I was able to upgrade from ICS to JB
2) once JB was installed I made a backup and decided to install JellyBam which came with Android 2.2 but probably because I forgot to reset to factory testing before installing the rom, I ended up in a non booting up installation where the phone just remains stuck in the loading screen of JellyBam
3) because I can not enter neither in download mode nor in recovery due to the broken home button, I was confident to manage the booting in recovery through ADB, as I did before.
But the problem is that Android 2.2 introduced the whitelist method for connected devices and therefore when I connect the device it is just seen as offline.
Because I never boot up in Jellybam I did not have the chance to accept the certificate that allow the connection with ADB
So, apart changing the piece holding the home button, what I'd like to know is if there is any hack/crack for ADB allowing it to bypass the whitelisting or any other method that allow to connect my device to the adb server
Thanks in advance
Just a suggestion..
Try with a USB Jig to Boot into Download Mode. Then flash ROM with Odin??
Hello!
First of all, sorry for my poor english knowledge. I try to describe my problem clearly.
I recently bought a Pearl Touchlet X10 quad core (PX-8880-675) tablet, but it was full of mods and when i plugged in the charger i received the "plugged in, not charging" message. So i started to clean up the ROM. Finally it showed charging, but now i really messed it up, beacuse now it is not booting. The tablet was not factory software, another tablet software on it that has a volume rocker. To start the flash mode i need the volume up button, but this version of tablet does not have this button. I tried the home button version, but it is not working because of the different firmware.
Here's the thing:
The tablet always starts recovery mode, no screen, but adb working. When i type "ls /dev/block" in ADB shell it shows loop0-loop7 and nandf, so it is not seeing the nand
I have seen other forums that when I type "dd if=/dev/zero of=/dev/block/nanda" it will erase the nand, and the tablet is force booting into fel mode (flash mode), but it not erasing beacuse the recovery is not for this tablet and it not seeing the nand.
My question is: Can I do something or have an expensive paperweight? :crying:
Thanks for the answers, whatever little thing can help me!
Update: nand.ko is from different tab?
Update: I think the nand kernel module is loaded (lsmod shows it), but it is not for this tablet. I pull out the nand.ko from the tablet and the size is different than the original what i extracted from the firmware image. It is possible to replace the nand.ko and then reload it without rebooting? Because if i overwrite it, it overwrites only the ramdisk, and after reboot it disappears.
No one?
BRICKED 7inch Irola Tablet...PLEASE HELP
I am in DIRE need of some help with my tablet. I received this irola dx752 tablet bricked and cannot fix it for the life of me. I am able to hold power and volume up and get into recovery system version 4.2.01. I Have tried a factory reset and a wipe system cache and the tablet just reboots to the green robot with and exclamation mark. If I press volume up, it brings me back to the system recovery. Now i am not very versed in ADB but I tried to sideload just about every firmware I could find for an a13 allwinner a8 cortex 7inch tablet, since the irola website has taken down its firmware. Also, fastboot will not work on this tablet whatsoever (it just says waiting for device) when i enter any command. I have never seen this tablet boot into a rom of any kind and therefore cannot tell if USB Debugging was ever enabled. I also Have tried different drivers but the one that seem to hold is the Android ADB Interface. CAN ANYONE PLEASE GIVE ME SOME SUGGESTIONS OR SOME HELP? It would be greatly appreciated. Thank you.
Unfortunately, I've managed to brick (sort of) my Huawei Mediapad 7 Youth (s7-701u), and I need some help unbricking it.
Complete log of events before and leading up to the brick:
1)Flashed an alpha release of a CWM port than I'm working on, using terminal emulator. It doesn't work, unfortunately. and now I may never get it to work.
2)Had a few xposed modules running:
-Monster UI 4.0
-Permission master
-Guesture Navigation (or something like that)
All xposed modules were working fine together, rebooted quite a few times with them active. So I don't think they're the problem.
3)Removed everything located in the /cust folder. Again, I've rebooted enough times to conclude that this may not be the root of the problem.
4)Changed a few apps into system apps, either to replace those I deleted, or just to ensure they run at boot namely:
-Nova Launcher (to replace Huawei launcher)
-Google Keyboard (to replace Huawei Keyboard)
-Titanium Backup (to replace Backup)
-SD Booster (to change SD card read speeds at boot)
-Monster UI (I figured It may work better as a system app)
-SuperSU (Why not?)
5)I put in a custom boot animation.
I found a lollipop boot animation on OnHax, downloaded the bootanimation.zip, placed it in my /system/media and changed appropriate permissions.
When I rebooted, it worked, but hang halfway. The device booted as normal though. I took apart the bootanimation.zip, messed around with the desc.txt, recompressed it, and once again placed it in /system/media.
Upon rebooting, it didn't work, giving me a blank screen with only the backlight on. However, it vibrated, as it usually does, to indicate that the boot was completing, and it did indeed boot up.
A couple of tweaks to the desc.txt and two bootanimation.zips later, I rebooted, confident I'd at last solved the problem.
Huawei Logo shows up, as usual. Blank screen with only backlight (figured I must still have messed up the desc.txt), the vibration happens, as usual, Then, nothing.
Analysis of current situation
Here's a quick rundown of my tab's current situation:
1) Normal booting
It will show the Huawei logo it shows first, but instead of the boot animation, there's nothing but the backlight. The vibration that happens just before the boot completes still happens, at around the normal time, and after that, the backlight goes on/off if I press the power button.
2) SD Upgrade recovery method
If I copy the update folder (the one named dload) form the official firmware to the SD card, as per the instructions, nothing happens. Probably because I replaced the recovery. It shows the huawei logo, same as when a normal boot happens.
3) Bootloader mode
I can, in fact, boot the tablet into bootloader mode. This is the only reason I haven't given up on this tab. Applications such as RKAndroid and rkflash recognise it, so i think it's just a matter of getting the correct config files and/or proper .img files to use with such apps
4) ADB
Generally, no. ADB will not work. I believe USB Debugging was deactivated. Not too certain though
It did detect the tab once, and only once. Unfortunately, it didn't occur to me then to just delete the offending bootanimation using ADB shell. Never got it to work since. Maybe there is a special order of keys to press to get it to work, I dunno.
Things I have tried
1) Reflashing the stock recovery using RKAndroid
My logic behind this is, if I can get the original recovery back in, I can then get the SD upgrade to work, fixing everything.
2) Getting ADB to recognise it
If I can get ADB to recognise it, I can delete the bootanimation.zip, and maybe reflash the stock recovery using ADB shell
3) Using the SD Upgrade
If this works, then all my problems are solved, right?
Any and all help in this situation will be greatly appreciated. Looking forward to working with you guys to breath life back into this tablet.
Kris the wizz 15 said:
Unfortunately, I've managed to brick (sort of) my Huawei Mediapad 7 Youth (s7-701u), and I need some help unbricking it.
Complete log of events before and leading up to the brick:
1)Flashed an alpha release of a CWM port than I'm working on, using terminal emulator. It doesn't work, unfortunately. and now I may never get it to work.
2)Had a few xposed modules running:
-Monster UI 4.0
-Permission master
-Guesture Navigation (or something like that)
All xposed modules were working fine together, rebooted quite a few times with them active. So I don't think they're the problem.
3)Removed everything located in the /cust folder. Again, I've rebooted enough times to conclude that this may not be the root of the problem.
4)Changed a few apps into system apps, either to replace those I deleted, or just to ensure they run at boot namely:
-Nova Launcher (to replace Huawei launcher)
-Google Keyboard (to replace Huawei Keyboard)
-Titanium Backup (to replace Backup)
-SD Booster (to change SD card read speeds at boot)
-Monster UI (I figured It may work better as a system app)
-SuperSU (Why not?)
5)I put in a custom boot animation.
I found a lollipop boot animation on OnHax, downloaded the bootanimation.zip, placed it in my /system/media and changed appropriate permissions.
When I rebooted, it worked, but hang halfway. The device booted as normal though. I took apart the bootanimation.zip, messed around with the desc.txt, recompressed it, and once again placed it in /system/media.
Upon rebooting, it didn't work, giving me a blank screen with only the backlight on. However, it vibrated, as it usually does, to indicate that the boot was completing, and it did indeed boot up.
A couple of tweaks to the desc.txt and two bootanimation.zips later, I rebooted, confident I'd at last solved the problem.
Huawei Logo shows up, as usual. Blank screen with only backlight (figured I must still have messed up the desc.txt), the vibration happens, as usual, Then, nothing.
Analysis of current situation
Here's a quick rundown of my tab's current situation:
1) Normal booting
It will show the Huawei logo it shows first, but instead of the boot animation, there's nothing but the backlight. The vibration that happens just before the boot completes still happens, at around the normal time, and after that, the backlight goes on/off if I press the power button.
2) SD Upgrade recovery method
If I copy the update folder (the one named dload) form the official firmware to the SD card, as per the instructions, nothing happens. Probably because I replaced the recovery. It shows the huawei logo, same as when a normal boot happens.
3) Bootloader mode
I can, in fact, boot the tablet into bootloader mode. This is the only reason I haven't given up on this tab. Applications such as RKAndroid and rkflash recognise it, so i think it's just a matter of getting the correct config files and/or proper .img files to use with such apps
4) ADB
Generally, no. ADB will not work. I believe USB Debugging was deactivated. Not too certain though
It did detect the tab once, and only once. Unfortunately, it didn't occur to me then to just delete the offending bootanimation using ADB shell. Never got it to work since. Maybe there is a special order of keys to press to get it to work, I dunno.
Things I have tried
1) Reflashing the stock recovery using RKAndroid
My logic behind this is, if I can get the original recovery back in, I can then get the SD upgrade to work, fixing everything.
2) Getting ADB to recognise it
If I can get ADB to recognise it, I can delete the bootanimation.zip, and maybe reflash the stock recovery using ADB shell
3) Using the SD Upgrade
If this works, then all my problems are solved, right?
Any and all help in this situation will be greatly appreciated. Looking forward to working with you guys to breath life back into this tablet.
Click to expand...
Click to collapse
and Now you have another brick in the wall... i'm really sorry for you.
puntoazul said:
and Now you have another brick in the wall... i'm really sorry for you.
Click to expand...
Click to collapse
I haven't given up yet. The way I see it, the only option I have is to figure this out, as it will prove invaluable for others. If I figure this out, then it will be impossible to completely brick this device, a critical factor in this time of development. Inevitably, someone else will brick their device, and if we can find out how to fix it, then it will be of great benefit to all, don't you think?
I also need some help... my huawei mediapad 7 youth (no sim) is on bootloop.... no recovery mode working ... but I can update firmware .. every time I updat3 it ..showing sd fails.. any help..
I was attempting to replace my custom rom, which was Lineage OS, with the kindle fire stock OS. I was using TWRP for this. I flashed the zip file to my kindle. I then wiped everything and rebooted. This is when I was greeted with a black screen.
I think this is where I messed up. I should have flashed two zip files, but I only did one (there's a 4.5.5.5 software update and a 3.2.5 software update. I only did the 3.2.5).
The kindle still connects to my desktop, but it shows up as an unknown device, so Windows won't let me update the driver and use adb or fastboot commands (or at least I haven't figured out a way that I can). Pressing and holding the power button or any combination of buttons doesn't display anything or disconnect the kindle from my desktop, so I dont think I can turn it off or reboot it either.
I'm not sure if I would even be able to fix this, based on what I've just said. Any help would be appreciated.
Failstorm9000 said:
I was attempting to replace my custom rom, which was Lineage OS, with the kindle fire stock OS. I was using TWRP for this. I flashed the zip file to my kindle. I then wiped everything and rebooted. This is when I was greeted with a black screen.
I think this is where I messed up. I should have flashed two zip files, but I only did one (there's a 4.5.5.5 software update and a 3.2.5 software update. I only did the 3.2.5).
The kindle still connects to my desktop, but it shows up as an unknown device, so Windows won't let me update the driver and use adb or fastboot commands (or at least I haven't figured out a way that I can). Pressing and holding the power button or any combination of buttons doesn't display anything or disconnect the kindle from my desktop, so I dont think I can turn it off or reboot it either.
I'm not sure if I would even be able to fix this, based on what I've just said. Any help would be appreciated.
Click to expand...
Click to collapse
You soft bricked your device with an invalid bootloader downgrade. Recovery is possible but quite challenging. Best option is to try the 1-click bootloader unlock tool. Good luck.
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014