So this is kind of a long story but basically I had a Nexus 7 8GB model. I bricked it by destroying the bootloader and so I sent it back for RMA.
When the thing came back it worked but was laggy as hell. I did all the normal erases and whatnot, even flashed back to stock, still laggy. I figure the EMMC was toast. So I purchased a used Nexus 7 16GB motherboard from ebay.
The new motherboard worked but came encrypted so it booted and asked for the password. Of course, not knowing the password, I had to get into recovery and do a data reset. After all that I was able to root and a Cyanogen mod based ROM.
The problem I currently have is this: I am unable to flash or update the bootloader which is stuck on 4.13. When I try and push the kitkat bootloader via fastboot I get "BAD PARAMETER" and am unable to get passed this.
In case anyone cares I was able to follow the bricksafe flatline procedure and captured the existing bootloader partition blob which is now saved to my computer. I have tried to push that bootloader back to the device and that works but I CANNOT flash the damn 4.23 (kit kat) bootloader.
Basically my Nexus 7 charges at a snails pace now but works. Any help is very much appreciated!
I don’t think the outdated bootloader is the cause of slow charging. I’m using the latest 4.23 and it charges like a snail too.
possibly you are trying to flash (Google-supplied) trash to your bootloader?
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
bftb0 said:
possibly you are trying to flash (Google-supplied) trash to your bootloader?
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Click to expand...
Click to collapse
I've checked the version of the bootloader, should be ok. Also I have tried flashing 4.13, lower versions, higher versions, etc.. all fail with the 'bad parameter'.
Also I get this when I do 'fastboot getvar all'.. note the size of the bootloader, on other devices this is a 0x000.. type number. Not on mine
Code:
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: 015d32205a3cDERP
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000368f00000
(bootloader) partition-type:userdata: ext4
Well, before we get too far off into the weeds (flashing) I will first have to agree with Lim Wee Haut - it is pretty unlikely that the bootloader has any effect on charging whatsoever. Tablets that are pure stock can pull 1.8-2A from the Asus OEM charger, so it's not obvious that software is ever the problem.
For instance, when the tablet is booted into the regular OS, it is impossible for the bootloader to be active. It's not like a PC BIOS (where software interrupt calls from the OS can be vectored through the BIOS). At most, the bootloader could set some hardware registers (e.g. in the SMB USB/charger chip) prior to loading the Linux kernel, but once the kernel is active, it is free to reprogram the hardware through it's device driver(s).
And what about when the tablet is completely off? This situation is less obvious to me - after all, when you plug the N7 onto the charger, a "charging animation" is displayed, and *something* is painting the screen... but I don't really know if that activity is being run by bootloader code or something in the tegra3 "miniloader".(The Tegra3 has a small ROM area in it for storing a tiny executable that can be programmed by the system designer and then protected by use of private keys)
In any event, the problem could be the charger, the battery, the cable, or any number of other things. Note that it is possible to observe the charging current using the "Current Widget" app plus a kernel that has the bq2745 current monitor patch in it, but you need to crank down the max clock and screen brightness - what you observe via that app is literally the current flowing ONLY in to the battery, not the total current provided by the charger. That means - because you can only get the tablet down to about 300 mA of consumption with the screen on - that the most charging current you will observe that way is about 1400-1500 mA on a charger that can put out 1.8A @ 5V.
OK, back to the flashing thing: I skimmed through two of the threads related to the "bricksafe flatline" hack, and I got the impression that once you have used that hack, there is no going back to fastboot for flashing bootloaders any longer - you are stuck using nvflash/wheelie thereafter. Is that incorrect? Or was it just that using fastboot with that patched bootloader (4.13-hacked?) causes flashing problems? It would be consistent with what you are reporting.
Sorry for the apparent randomness of this reply, just throwing out some ideas.
Related
So I heard that the XOOM can be unlocked from fastboot.
I did the same process to my Atrix and it said it completed it with a happy OKAY.
ran the command "fastboot oem unlock" from the Atrix in it's fastloader mode.
It gave a friendly OKAY.
I haven't a clue if it is really unlocked. I just figured this might be helpful info, or maybe not.
While I highly doubt it's that easy on our phones, it's interesting that it returned an OK on the command. Can any proper devs chime in? Does it just give an arbitrary 'OKAY' once the command completes, whether successful or not?
DarkSi08 said:
While I highly doubt it's that easy on our phones, it's interesting that it returned an OK on the command. Can any proper devs chime in? Does it just give an arbitrary 'OKAY' once the command completes, whether successful or not?
Click to expand...
Click to collapse
If you do a "fastboot oem anything" it will return OKAY
I am pretty sure its not doing anything. The phone just return OKAY to whatever oem command you try to execute and doesnt do anything.
uskr said:
If you do a "fastboot oem anything" it will return OKAY
I am pretty sure its not doing anything. The phone just return OKAY to whatever oem command you try to execute and doesnt do anything.
Click to expand...
Click to collapse
I can confirm that the fastboot oem *anything* command gives "... OKAY" no matter what is typed.
A for effort though, OP
What does all this mean?
Code:
C:\Users\Ryan>fastboot getvar all
(bootloader) version-bootloader: 1000
(bootloader) product: olympus
(bootloader) secure: no
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 02884xx
(bootloader) version-baseband: currently un-supported
all: Done
finished. total time: 0.004s
"(bootloader) secure: no"... I'm sure that doesn't mean what I think it does, does it?
I also believe you just gave out your serial number
Sent from my MB860 using XDA App
neer2005 said:
I also believe you just gave out your serial number
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
LOL, nice.
Anyway, I'm sure it was a false alarm... Looked promising, but cant' do anything.
Sorry to make a mess of the forum.
When the Nexus 7 battery dies and shuts off, does it turn itself on when you plug it into the charger?
Thanks
The Nexus 7 won't power on by itself from an off state, regardless of the battery level.
No, it stays off and if you click the power button quickly it will display a charge animation. I personally like this feature as mine normally dies very late at night and I like to be able to plug it in and charge it without it booting up just to sit in sleep all night.
Damn, thank you very much!
Is there any way to MAKE the Nexus 7 start up/power up when you plug in the USB? I actually need this as I am planning on installing one in the car to replace the radio. I would like it to power up when the key is switched to accessory and the USB sees power.
I believe that you need a kernel that's modified to do this.
I don't have any answer, but this might get you thinking in the right direction even though it only has in the info for select Samsung phones.
http://forum.xda-developers.com/showthread.php?t=1815131
Post back if you figure it out. I'm also interested.
Nexus 7 Power on when plugging to charge
dmexs said:
I don't have any answer, but this might get you thinking in the right direction even though it only has in the info for select Samsung phones.
http://forum.xda-developers.com/showthread.php?t=1815131
Post back if you figure it out. I'm also interested.
Click to expand...
Click to collapse
Here is the Score: Before I plugin to charge my nexus 7, I turn it Off, once I pug it in, the pad turns itself ON by itself. If I turn it Off by pressing the side button, I have a hell of a time turning it back on, I mean from 15 minutes to one hour. I wonder if the problem is Software or Hardware. I also wonder why not to many people complain about this. You can see only great reviews but I invite you to find a solution to your problem, when you have one. It is impossible with Google !!
I was suggested to return it or replace it with another one, but I want it fixed.
I also search long time till i found the following
Code:
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
Now the system boots, when USB power is plugged in
gschaden said:
I also search long time till i found the following
Code:
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
Now the system boots, when USB power is plugged in
Click to expand...
Click to collapse
Good find. Do you know if it is available to a locked bootloader?
Hi . Where/how do you enter this code? I've tried on an emulator but says not reconised. My nexus 7 is un locked running tumirs rom.
Thanks
QUOTE=gschaden;39633079]I also search long time till i found the following
Code:
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
Now the system boots, when USB power is plugged in[/QUOTE]
thankkkssssss!!!!!!!!!!!!!1
thanks for posting this, mine has been toggled by something and want it turning off
Hi everyone,
In the past days I tried to unlock and root my Nexus 10, and looks like something went very wrong.
Right now, I'm stuck with the bootloader screen; the tablet boots into bootloader and I can only go to "bootloader" (power + vol up + vol down) or "download" (power and vol up).
The bootloader screen reads:
PRODUCT NAME: mantra
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION : MANTAMD003
CARRIER INFO: NONE
SERVIAL NUMBER: XXXXXXXXX
LOCK STATE: UNLOCKED
REBOOT MODE FLAG: NONE
I've tried using different tools, including "Wugs Nexus Root Toolkit" and command line fastboot.
Some fastboot commands seem to work - e.g.:
fastboot devices (it does recognise my device)
fastboot -w (the messages on the screen seem to suggest it's all ok)
fastboot getvar all:
(bootloader) product: manta
(bootloader) variant: wifi-only
(bootloader) serialno: XXXXXXXXX
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMD03
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000
The problem is with commands like:
fastboot flash bootloader bootloader-manta-mantamd03.img
(or any flashing command for what it matters).
None of them works; after waiting for a long while, the error returned is "Too many links".
I have googled the command, but I haven't found anything meaningful. ADB doesn't work - I must use fastboot to unbrick the device.
Any suggestions?
Andres
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
faiyo said:
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
Click to expand...
Click to collapse
Hi, thanks for the suggestion.
I've tried to flash a recovery image already - that didn't work. That's why I tried flashing anything. I've also tried the "Back to stock" option in the toolkit, and it hangs when trying to flash anything to the tablet...
Andres
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Have you tried using Wugs to Flash the Stock ROM and Unroot? I have been unable to get ADB to find my Nexus 10, even though it's been listed in the Device Manager of Win 8 with each of the 4 suggested drivers suggested. After getting stuck in a Bootloop I was still able to use the 'Back to Stock' option to recover my Nexus 10.
Good luck.
faiyo said:
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Click to expand...
Click to collapse
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
4ndres said:
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
Click to expand...
Click to collapse
Definitely stick to non-counterfeit OEM samsung cables as best as you can. In the past few years, Samsung/Apple have bastardized and corrupted the usb standard. It's usually only noticeable for charging, though in any practical use we find one usb cable is actually better than another It's really disappointing.
Flash the factory image via fastboot. And never use toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app
Hi
my I had my U Ultra working just fine for almost 10 months and suddenly it started to freeze inside OS and reboot constantly then load back in OS and freeze after 10 seconds or so ... Tried a factory reset and also got stuck in Setup screen after factory reset and phone kept crashing , tried TWRP wipe (Full WIPE) and after that phone started to freeze also in TWRP and after a day it didnt load into TWRP neither Download Mode and phone doesnt charge ....
I dont know how it happened or why Im so confused and dont know what to do with it ...
Please share your information , thanks .
also right now in Bootloader mode ADB cant find my device (adb devices command and it cant detect my device but when i want to flash some thing it says cant flash in S-ON State and a day back my phone in download mode was unable to flash becasue battery didnt have enought charge) Im literally stuck , is my phone dead after all ?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdbf000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xdc000000
(bootloader) serialno:xxxxxxxxxxx (censored)
all:
finished. total time: 0.409s
also flashed hosd.img from fastboot but no avail ...
Note : I extracted that hosd.img from my stock Rom , phone rom ver is 1.62.401.10 and rom.zip is 1.62.401.1
desperately looking for help ....
Try charge your phone for a while and then flash RUU
minhnewpro said:
Try charge your phone for a while and then flash RUU
Click to expand...
Click to collapse
THanks for the answer .
How do I charge it ? when i plug into charger phone goes into bootloop , the only place it is stable is the while screen bootloader , does it charge while on bootloader ? if yes I'll give it a try for a while then I'll try , although Im locked out of Download/Recovery/RUU I'll try to flash a stock rom.zip using SD memory card . I'll let you know when I'm done .
Good Guy Greg said:
THanks for the answer .
How do I charge it ? when i plug into charger phone goes into bootloop , the only place it is stable is the while screen bootloader , does it charge while on bootloader ? if yes I'll give it a try for a while then I'll try , although Im locked out of Download/Recovery/RUU I'll try to flash a stock rom.zip using SD memory card . I'll let you know when I'm done .
Click to expand...
Click to collapse
Yes. It can charge in bootloader.
minhnewpro said:
Yes. It can charge in bootloader.
Click to expand...
Click to collapse
formatted a SD card to FAT32 and put the rom.zip inside it (1.64.401.10) the latest RUU I could possibly find and then put the card into phone , shut down phone , turned it on (Download mode / Recovery not accessible due to partition failures or boot failures) only can load bootloader which no reaction to rom.zip happened . Im so confused what to do ....
Can a JTAG service fix this problem ? if yes I know a repair shop who can do this for me .
Good Guy Greg said:
formatted a SD card to FAT32 and put the rom.zip inside it (1.64.401.10) the latest RUU I could possibly find and then put the card into phone , shut down phone , turned it on (Download mode / Recovery not accessible due to partition failures or boot failures) only can load bootloader which no reaction to rom.zip happened . Im so confused what to do ....
Can a JTAG service fix this problem ? if yes I know a repair shop who can do this for me .
Click to expand...
Click to collapse
Maybe you shold go to repair shop. I don't see any bug like this before.
minhnewpro said:
Maybe you shold go to repair shop. I don't see any bug like this before.
Click to expand...
Click to collapse
it was a damn fine phone :crying:
it must be a faulty eMMc or board , thx for helping dude . I'll let you know if it got repaired .
Wow, weird! My wife's phone just started to do the same thing today. She thinks it's about 1.5 years old, yours? No reason, running stock and I'm guessing running whatever is the latest FW. She took it to our carrier's store here in Taiwan, who told her to take it to the HTC service center. The service center couldn't get the bootloop to stop, so they're shipping it to the HTC mothership. They opined it may be a motherboard, and would report back how much it would cost as it's out of warrantee. I'll update here with what happened. Please OP, report back too. Maybe we're (you're...I ain't buyin' no headphone jackless phones no mo' because it's simply user hostile...but who needs/cares about customers anyway??) the first patients of an epidemic?
She got it back today, NT$6660. They replaced both the motherboard, and the screen. The implication is maybe the screen caused the rebooting...
Good Guy Greg said:
THanks for the answer .
How do I charge it ? when i plug into charger phone goes into bootloop , the only place it is stable is the while screen bootloader , does it charge while on bootloader ? if yes I'll give it a try for a while then I'll try , although Im locked out of Download/Recovery/RUU I'll try to flash a stock rom.zip using SD memory card . I'll let you know when I'm done .
Click to expand...
Click to collapse
did u fixed your HTC I am facing same issue with my HTC rebooting I cant enter download mode or even recovery mode
if u fixed then tell me how did...
i neeed usb dubbing mode on how can i do dear ..
plz guide me
zubairikram said:
did u fixed your HTC I am facing same issue with my HTC rebooting I cant enter download mode or even recovery mode
if u fixed then tell me how did...
i neeed usb dubbing mode on how can i do dear ..
plz guide me
Click to expand...
Click to collapse
Same issue on my side, it crashed about two weeks ago while just reading a post on reddit. I still haven't managed to make any progress.
- When plugged in or has some charge, it gets in a boot loop. It tries booting every 15-20 seconds but nothing happens.
- When it is low on battery and you first plug it, it behaves regularly with the low battery logo, the red light showing charging mode.
- Only stable thing is to get into bootloader mode but none of the options work...
Reset with boot loop
I had the same issue after doing the android system update. It would get stuck in a bootloop and try to restart every 10-15 seconds or so. The volume down and power button did nothing. If you hold the volume up+volume down buttons and the power button at the same time it should stop the boot loop. It may take up to two minutes to get it to stop. Once the HTC logo disappears and it looks like its powered off, hold down the volume down+power button to enter download or bootloader mode.
i have the same problem please did you find a fix for it
:crying:
Good Guy Greg said:
desperately looking for help ....
Click to expand...
Click to collapse
today i have the same issue only have access to bootloader mode.phone restart it self.i dont know hwaty juts happen.anyone know please help me
I experience the same issue with my HTC U Ultra last week, still struggling to get a solution. Anyone with a helpful tip?
famousShegz said:
I experience the same issue with my HTC U Ultra last week, still struggling to get a solution. Anyone with a helpful tip?
Click to expand...
Click to collapse
you might need to take it to htc store cause from what i have seen he motherboard is damaged and is what caused the problem i am currently experiencing the same problem for about 5 months but i haven't had the opportunity to take it to a htc store cause there are non in Nigeria
same issue
Good Guy Greg said:
Hi
my I had my U Ultra working just fine for almost 10 months and suddenly it started to freeze inside OS and reboot constantly then load back in OS and freeze after 10 seconds or so ... Tried a factory reset and also got stuck in Setup screen after factory reset and phone kept crashing , tried TWRP wipe (Full WIPE) and after that phone started to freeze also in TWRP and after a day it didnt load into TWRP neither Download Mode and phone doesnt charge ....
I dont know how it happened or why Im so confused and dont know what to do with it ...
Please share your information , thanks .
also right now in Bootloader mode ADB cant find my device (adb devices command and it cant detect my device but when i want to flash some thing it says cant flash in S-ON State and a day back my phone in download mode was unable to flash becasue battery didnt have enought charge) Im literally stuck , is my phone dead after all ?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdbf000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xdc000000
(bootloader) serialno:xxxxxxxxxxx (censored)
all:
finished. total time: 0.409s
also flashed hosd.img from fastboot but no avail ...
Note : I extracted that hosd.img from my stock Rom , phone rom ver is 1.62.401.10 and rom.zip is 1.62.401.1
Click to expand...
Click to collapse
i have the same problem did you fix it?
I also experienced the same problem. Flashing RUU does not fix it. Must be a hardware issue. And must be design fault as well.
Same happened to my phone 2 days ago. Unfortunately there's no way to fix this.. So yeah, time to get a new phone
Hello,
My A1 is bricked since few days.
I've made few trys to get access on the data and i don't find any solution.
I can comunicate with the phone via Fastboot, but did not find a way to do something....
with fastboot oem device-info, i have this result:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.060s]
finished. total time: 0.062s
the oem unlock is not allowed.
With ADB, no success, the USB depuration was not on before the brick so....
Does someone know a way to do something?
is there is a way to load something from a SD card to turn on again the device without erasing everything?
Thank you very much.
Regards
Lebenjb
Nope there is no way. You basically hard brick the device. Did you lock the bootloader after modifying system?
The only way I know of is EDM mode, but it requires opening the phone and short curcuit some contact ponit.
Thanks for your answer.
The A1 get bricked by itself using it with the original rom.
I was so interested to have access to save some files!
I have a new phone, so I'm not in hurry, but if someone knows a way to make a recovery with data or just to have access to the files.
Then I will "wipe and delete" to give it to my son
Regards