Okay here's is my story
I have an O2 UK Dell streak which I had originally rooted using the superboot method (fastboot mode and then run the two commands on the mac terminal window)
I then recently installed the leaked 2.1 update on the handset and everything was fine till tonight. I installed an app which needed root access and having not seen the root access icon in the apps, thought that I need to root the phone again after the 2.1 update.
So I plugged in my phone again in my mac and ran the terminal commands. the first one went ok "chmod +x install-superboot-mac.sh" or I assume its ok as the prompt went down without any errors in terminal window.
The second command "./install-superboot-mac.sh" ran but with errors:
"ERROR: could not get pipe properties
sending 'boot' (2520 KB)... OKAY
writing 'boot'... OKAY
ERROR: could not get pipe properties
rebooting... "
The phone rebooted but is now stuck at DELL logo, I have tried removing and reinserting the battery, also ran the commands again in the fastboot mode but still the same errors and still stuck. when going into fastboot mode, the phone pops some error message but not enough time to note the error, also when trying to normal switch on, the display shows a quarter of white screen for a split second with i suspect the same error as before fastboot mode but is even quicker to even notice
PLEASE PLEASE SOMEONE HELP!
From what is sounds, this should help fix your problem. Sood luck!!
http://forum.xda-developers.com/showthread.php?t=754563
So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?
Why don't you go read the many threads describing your exact same problem you can fix it.
No you can not return it your warranty is now void.
go into irc with vashypool and he might be able to fix it, donate if u can..
mguinta25 said:
So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?
Click to expand...
Click to collapse
It does seem that this is a very popular problem... I am not sure what amazon's requirements are exactly on returns once bricked especially if you rooted, but I will say with how popular this problem seems to be, I am sure many of the experienced devs on this site are working on a fix for this (hopefully)... If not I would suggest donating to one of your choice if possible for the work that they have already put into it, explain your problem to them and I am sure it would motivate them to come up with an easy fix for this. Whatever happens you should definitely post back with your findings so that you can help the comunity further with knowledge...
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
Thank you just had to change the bootmode!
My KF is in a boot loop. Boots to the kindle fire logo, sometime does the animation (highlights letters from right to left), sometimes doesnt.
I've downloaded the KFU and installed the drivers. When I run the bootmode menu, it says ADB Status online, ADB rooted no (even though my kindle IS rooted).
When I try to change bootmode to normal, I get a number of errors:
Error: Could not access the Package Manger. Is the system running?
Error type 2
android.util.AndroidException: Can't connect to the activity manager; is the system running?
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
then it says root activated and that the kindle is running in root mode
<idme> Invalid permission
reboot: Operation not permitted
Then despite all the errors, says kindle has been told to reboot in normal mode.
Kindle still gets stuck in boot loop when I try to power on. I've tried powering off the kindle and then on and retrying, I've tried powering off and disconnecting the kindle and computer, still no luck.
Any advice?
if your kf is constantly rebooting (2-3 sec) read this thread:
http://forum.xda-developers.com/showthread.php?t=1424379
if not and you can connect via kfu set bootmode to normal or do it manually depending on the bootstate your in:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
FWIW, Amazon are really liberal when it comes to returns on the entire Kindle family.
At a X-Mas Eve party, a friend dedcided it would be a good idea to stream some things with AirTwist and left his KF laying on a table, it recieved some pretty serious damage from being dropped, stepped on and having stuff spilled in it, we dont know how, but Amazon replaced it.
So I would say your best bet in case of brick is to at least simulate damage=\
b63 said:
1. run kfu - select change bootmode - select normal -> success ?
Click to expand...
Click to collapse
Thank you.
I just wanted to mention this "as it might help others": I was stuck in Kindle fire screen, can't boot, and can't see the ADB status.
In the device manager I was seeing the yellow mark.
I restarted the device, then the yellow mark went.
Selected change bootmoe -> normal from KFU (even though the status is offline), and worked!
Thank you again.
Having this issue
b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.
I just wanted to add, I just had a similar issue last night. I was loading up the MIUI ICS rom, wiped like normal and rebooted to the firefirefire triangle. ...Did not like... Anyhow, I was following the many unbrick guides and couldn't get anything to work. The KF would reboot, and my system (win 7 x64), would see the KF as an unknown device with, "error 43", device cannot start. Then the unit would disconnect(windows sound) from usb, and reconnect and disconnect and then go no where. Each time I rebooted the KF it would do the same thing, also would not go into recovery if I hit the power button during boot. I made a factory cable from an extra usb micro cable I had, to force it into fastboot, and it would come up in device manager as an android usb device. still could not see it via adb directly or in KFU. I found it was the android sdk drivers messing it up. I uninstalled the Android SDK and reinstalled the KF driver package that came with the KFU and viola! I was able to run the TWRP install, and successfully get into recovery. I tried the MIUI ICS Rom install again with a new download just in case, but with the same results. wash, rinse, repeat. I restored my previous ROM in recovery and it booted up like a champ. I'm assuming that since the SDK drivers were causing the issue, I could have probably got the fastboot in firefirefire(during boot) to work properly, and not needed the factory cable. Just wanted to share my late evening fun.
Cheers!
Rob
alfy984 said:
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.
Click to expand...
Click to collapse
maybe this helps to sort out the driver issue:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
the terminal is showing like this when i try to root my galaxy note 2
--- Samsung Galaxy S4 Android 4.3 Root --
--- Based on the CVE-2013-6282 exploit by cubeundcube --
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
[*] Starting rooting program.
ro.build.product=t03g
ro.build.id=JSS15J
setsockopt() failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.
[*] Checking if rooting succeeded
[*] Unfortunately, rooting failed. Cleaning up.
Press any key to continue . . .
am running on windows 8.1 with samsung kies 3
Hello All,
I'm a fairly new coder and I recently Hard Bricked my Samsung J5 5.1.1
Is this a Bootloader issue or OS problem as to why I have a Galaxy J5 Hard Brick?
Here's how it happened:
* I rooted the phone
* Wanted to enable more storage (4GB to 14GB) via SD Card
* Gained Super User access and had total file control via an app (I can't remember which one). I then found my way to an area where I could transfer the entire phones files (to include the OS files) to the SD Card - so I did
* The dialog box to restart the phone popped up and I pressed restart
From there the phone has not startup (not able to pwr+home or pwr+home+dwn), can't be found in device manager via USB, and can't be found via adb reboot fastboot (gives a *daemon stated successfully* error: device not found)
Why won't it turn on? Is this a boot loader issue or an OS problem?
Hi!
I received a bricked teenager's phone to fix, but I don't know if this is possible at all. Maybe someone can help me or at least tell me if this is a hopeless case or not:
The device is a Xiaomi Redmi Note7 (lavender), model M1901F7G. It is soft bricked - I can't start Android to check the MIUI version (suppose it was 11.0.4.something or 11.0.7.something) nor are usb-debugging and/or oem-unlock enabled. This Note7 is on stock firmware and has always been, has never been rooted and as far as I know nothing has ever been done that is beyond official/public Xiaomi updates.
The error description is the device received an update over the air. After installation was completed the Android start failed with the error message "The system has been destroyed". It was still possible to start Android after the command "fastboot continue". Nevertheless the device was in a buggy state: time/date were completely wrong and what was worse: no network connection anymore, not with LTE and also not with WiFi.
In this buggy state userdata has been cleaned. This was to do a 'soft' attempt to repair and not to reset to factory defaults directly - probably not a smart idea, but anyway. Afterwards the phone came up with an initial installation wizard (language and region selection) and reports the device is locked with a Mi Account and needs to be activated. I have access to this account's credentials, but activation fails as there is still no network access available (same as before: no LTE, no WiFi). So I don't see any possiblility to let me enter Android to enable usb-debugging and oem-unlock.
I can access the Note7 via fastboot, but not with adb everything seems to be locked:
Code:
>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.021s]
finished. total time: 0.023s
So I doubt it is possible to do a complete wipe and flash an (older) firmware.
All in all it appears quite strange to me the phone got these problems after an OTA update. I couldn't find any information about others having the same symptoms with a MIUI 11.0.x update on a Redmi Note7. So, might this be a (hidden) hardware defect?
The phone has been bought in 07/2019, it should still be in warranty. My backup solution is to return it to the shop, but I estimate RMA to be processed in 2-4 weeks only (a nightmare for a teenager without smartphone) and I'm still not sure if this case is covered by warranty. Means I - and especially the owner of that device - would be happy if there would be a way to fix it!
Any hints and solutions are highly appreciated!
Kind regards,
Andy
You can not install older version firmware without rooting. Only new version and maybe same version
Maybe this guide can help if you can get into recovery mode (vol up + power)
Thanks a lot! Your guide helped and it worked!
I didn't know which version was installed and also not from which region. So I ended up with some trial and error. I assumed it would be a European or Global version though and just tried the newest ones I could get. In the end I was successfull with MIUI 11.0.7.0 Europe Stable OTA ROM <can't post links yet: bigota[dot]d[dot]miui[dot]com/V11.0.7.0.PFGEUXM/miui-blockota-lavender_eea_global-V11.0.4.0.PFGEUXM-V11.0.7.0.PFGEUXM-35b08eb301-9.0.zip >.
Code:
* Miui sideload made by Francesco Tescari, updated 02 Feb 2018 *
* Checking device status *
* Getting recovery info *
* Creating file MD5 hash *
* Querying ota update server, attempt #0 *
Data partition format might not be necessary and will NOT be done automatically after installation.
If the device doesn't reboot or some apps crash after reboot, you need to manually format the device using "format-data" command!
* Starting sideload *
Sending file to the device... (~100%)
Checking file checksum...
Installing file on the device... (~42%)
* Sideload output: Installation_complete. *
* Rebooting... *
Installation SUCCEEDED!
Please check your device status after reboot to make sure everything is right!
If everything is right and you want to show your gratitude you can offer me a beer by making a donation to this project, do you want to make a donation? [Y/n]
So thanks again! You safed me a couple of hours trying to find out a solution and made a teenager super having for having her phone back! :good: