I've only recently bought an acer a100 but I've also bricked it...
I made a mistake of unlocking the boot loader while I was using a custom rom...
So, I can't get into recovery or something
For now, my question is this..
I used USBDeview or something like that to find out the uid but it seems that it isn't the right one
There's also a500 listed in the list, but it is only 11digits..
I guess this is because I adjusted the build prop.
So, my question is this for now. When you flash another rom or change its device name, does the UID change?
Sorry for my weird english..
Thank you in advance
jasonjjang08 said:
I've only recently bought an acer a100 but I've also bricked it...
I made a mistake of unlocking the boot loader while I was using a custom rom...
So, I can't get into recovery or something
For now, my question is this..
I used USBDeview or something like that to find out the uid but it seems that it isn't the right one
There's also a500 listed in the list, but it is only 11digits..
I guess this is because I adjusted the build prop.
So, my question is this for now. When you flash another rom or change its device name, does the UID change?
Sorry for my weird english..
Thank you in advance
Click to expand...
Click to collapse
Did you mean you locked the boot loader on a custom rom? I suppose this means you also have a custom recovery which means you're locked out, needs to be sent to Acer. We don't have the key to access the firmware to correct this.
Tapatalked from my Galaxy S II.
thx...but
Is there still a way to find out my UID?
Without using the USB thing I mean
Oh god....
jasonjjang08 said:
Is there still a way to find out my UID?
Without using the USB thing I mean
Oh god....
Click to expand...
Click to collapse
Dunno what a uid is but if you mean cpuid its the serial number. Won't matter though, its locked up.
Tapatalked from my Galaxy S II.
Related
Hello everyone,
i've flashed the newest version of the PhilZ Touch custom recovery and now my note 2 can't find my sim-card...
Custom recovery found @ http://forum.xda-developers.com/showthread.php?t=2028103
I flashed it from version 4.35 to 4.63 so the custom recovery was installed and working before.
After reboot i didn't had the possibility to unlock my sim-card (entering PIN-code).
Now i have no network connection at al (obviously)
Everything else is (so far) working...
I'm using the rooted stock rom
greetings,
p.s. i would reply in the specific topic but i can't yet.
Try another recovery or phone.
Sent from my GT-N7100 using xda app-developers app
Stupid question?
UtkarshGupta said:
Try another recovery or phone.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Is it, in any way, possible that a sim-card gets affected when you flash a custom rom?
I'm thinking about this question because my sim-card broke just after flashing without touching it...
(no need to touch your sim-card to flash, but i haven't done anything else where i would have needed to remove/change it)
Its probably just coincidence but it's strange that it just happend after flashing.
(sorry if my english is hard to understand )
greetings from Belgium
ye same problem here, tell me when u found out to get it back so I can use that method =p
I've had no problems after upgrading the recovery.
I would suggest you post in PhilZ's thread. He is very active and will help find out what happened.
Unexist6969 said:
ye same problem here, tell me when u found out to get it back so I can use that method =p
Click to expand...
Click to collapse
Well, i've changed the sim-card (have one for data only...) and that one worked fine...
I tried it in another phone too but i was thinking that it wasn't working because i used an adapter to have a normal sim-card and not the micro-sim format so i did the thing mentioned above...
I decided to sent my parents to a Belgacom support center (one of belgians telecom operators) to ask a new one.
I need to work this weekend and i didn't had the opportunity to go myself, it's stupid to walk with a phone without the ability to call/send messages :silly:...
I just inserted the sim-card my parents got from the center and i've recieved al my missed messages so i know that the new one is working fine.
This is undoubtedly strange that it's possible that a sim-card gets affected/broken when changing/updating custom recovery.
I'm "glad" (if you understand what i mean) that i'm not the only one who is having this problem.
Can someone with experience explain to me and the others what could have been the problem?
Edit: can't post yet in his thread due to too low count of messages
Edit2: i'm sorry that i haven't any easy sollution...
Yours sincerely,
what do you actually get from philz? i can't even feel a butterfly flies in my tummy..
in my opinion, the perseus one is the best choise.
rymote said:
what do you actually get from philz? i can't even feel a butterfly flies in my tummy..
in my opinion, the perseus one is the best choise.
Click to expand...
Click to collapse
Nothing special?
I don't know why you are asuming that i need to get something from it...
I'm just saying in this thread that there has been a problem with the sim-card after flashing this custom recovery .
So i only wanted to say "Hey, after performing this, that went wrong, how to find a solution"
This has nothing to do with liking a custom recovery.
I'm happy for you that you like the perseus one but this one was aproved by someone to solve another problem (and worked)...
I can't understand the point of your reply in this topic, it has nothing to do with not finding/reading the sim-card
p.s.: my wording may seem wrong but well meaning, my english is not perfect since it is not my native language
ahhh .... the device I was rooting was simlocked, he didn't say anything ffs.. that's why
@op try flashing a stock rom(remove sim card), then factory reset in recovery, then flash philz, then flash w/e u want
Unexist6969 said:
ahhh .... the device I was rooting was simlocked, he didn't say anything ffs.. that's why
@op try flashing a stock rom(remove sim card), then factory reset in recovery, then flash philz, then flash w/e u want
Click to expand...
Click to collapse
thanks for your reply, i'll do it when i have some time :good:
Unexist6969 said:
ye same problem here, tell me when u found out to get it back so I can use that method =p
Click to expand...
Click to collapse
same problem just flashed philz and not showing network plz help....
Hi all!
Okay so I'm ready to bash my face off something till I die... lol I've been up all night screwing with my xperia play from rogers. First I did the touchpoint method to unlock the bootloader and s1tool confirms that it's unlocked. However, no fastboot and when I punch in the code provided by SE to see the value of "bootloader unlock allowed"... it's still "no". From what I understand the touchpoint method shouldn't change this value. However because this value is still set, I have a feeling that this is why I can't enable fastboot.
I'm trying to flash a custom jellybean rom using flashtool and because of the aforementioned situation, I can't. I'm wondering if anyone can point me in the right direction to get fastboot working. I hate that I've paid through the nose for all the android devices I own and I yet I still don't technically own them. Anyway I won't rant....
P.S. Just to be verbose, when I do fastboot.exe devices... just hangs saying waiting for device. Device shows up in Device Manager but is code 31 cannot start. Also if I hold search and plug in USB or any of those combos I absolutely cannot get a blue light. I can also assure anyone that I've spent probably 8 hours straight googling the bleep out of this issue and working on it so I'm not being lazy I've just reached the limits of what I can do on my own and am begging for any help that is available!
Thanks in advance!
Also just more info, I've got the devices rooted if that makes anything simpler or opens up options. I'm also wondering if this might be a driver issue because I was doing this on my windows 8 machine and from 7 up you have to do a bunch of stupid temporary system configurations to allow unsigned drivers plus wondering if it's a driver incompatibility issue. If that's the case can I use flashtool on my linux machine? Something I'll look in to... just wanted to post as much info as I can. Thanks again!
So no one in this forum has any idea?
No one here has absolutely any idea about what I can or can't do with this bootloader situation? Wow....
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
psxpetey said:
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Furinax said:
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Click to expand...
Click to collapse
When you do test point unlock you don't get fast boot you have to use flash mode and .ft kernel and whatnot go into flash tool and press boot loader unlock it should fail and say its already unlocked
Sent from my R800i using xda app-developers app
Got it!
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Furinax said:
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Click to expand...
Click to collapse
So uh... what happened to the guide?
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
Honestly this was almost a year ago and I ended up chucking that damn phone out and getting my wife a new one. I barely remember the whole process I just remember it being about 3-4 days of me being intensely angry and frustrated lol. I do recall it involved ripping apart the phone and shorting out certain pins that are covered by the sticker under the battery, but I believe that portion was for unlocking the sim, I really can't remember. I'll see if I can dust off those brain cells and get the whole thing back and post nfo if successful.
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
This I used as for part of the process:
https://www.youtube.com/watch?v=zM8lWE4Layc
However I don't believe this tutorial includes unlocking the bootloader. I believe sony provides a utility or something to unlock the bootloader but you're missing fastboot. I think the process involved flashing a custom kernel, not sure. I'll keep digging into my memory and post more nfo back later. Kernel was Lupus kernel I recall that much.
Edit:
Here is complete guide with bootloader unlock process explained as well.
http://forum.xda-developers.com/showthread.php?t=2187172
More links http://unlockbootloader.sonymobile.com - but as I recall this doesn't work for rogers branded r800a.
Hi guys
i want to root and install custom roms on my note 2 . i just want to know what are the most common problem comes that make your phone completely dead!
is it even possible that one can kill his phone completely that it can never be recovered?
Bumping the thread
why no one answers?
nicholes said:
Hi guys
i want to root and install custom roms on my note 2 . i just want to know what are the most common problem comes that make your phone completely dead!
is it even possible that one can kill his phone completely that it can never be recovered?
Click to expand...
Click to collapse
If you flashed wrong custom ROM via recovery won't be a problem, just reflash any other compatible stock ROM then your problem will be fixed. BUT if you flashed wrong stock ROM via ODIN and you will end up brick. You need a JTAG to revive your phone.
Its pretty hard to destroy your phone completely just by flashing another rom.
Flashing bootloader through recovery is a bad idea.
Repartitioning your device in odin, with files not specific to your device, is a bad idea
Dramatic over-clocking with increased voltages, can be a bad idea
Dropping your device is a bad idea.
Bumping a thread without waiting more than 24 hours, is a bad idea
EmptyArea said:
Flashing bootloader through recovery is a bad idea.
Repartitioning your device in odin, with files not specific to your device, is a bad idea
Dramatic over-clocking with increased voltages, can be a bad idea
Dropping your device is a bad idea.
Bumping a thread without waiting more than 24 hours, is a bad idea
Click to expand...
Click to collapse
i understood sir:good:
soralz said:
If you flashed wrong custom ROM via recovery won't be a problem, just reflash any other compatible stock ROM then your problem will be fixed. BUT if you flashed wrong stock ROM via ODIN and you will end up brick. You need a JTAG to revive your phone.
Click to expand...
Click to collapse
and what is JTAG here?please explain
nicholes said:
i understood sir:good:
and what is JTAG here?please explain
Click to expand...
Click to collapse
JTAG = Joint Test Action Group.
http://en.m.wikipedia.org/wiki/Joint_Test_Action_Group
Sent from my GT-N7100 using XDA Premium 4 mobile app
My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?
Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.
Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...
Good luck. Will Google not rma it?
Hey. I saw that on Nexus 5 someone made bootloader themes, and the new Google Logo on boot. I guess that it isn't so hard to port it. So, can someone make this?
If there are any spelling mistakes, I apologise
razvangabriel82 said:
Hey. I saw that on Nexus 5 someone made bootloader themes, and the new Google Logo on boot. I guess that it isn't so hard to port it. So, can someone make this?
If there are any spelling mistakes, I apologise
Click to expand...
Click to collapse
No, this is not possible, that mod relies on the imgdata partition that the nexus 7 does not have, not a single nexus tablet has that partition.
So editing the bootloader isn't possible?
razvangabriel82 said:
So editing the bootloader isn't possible?
Click to expand...
Click to collapse
Editing the bootloader is definitely possible however, flashing a modified bootloader will not work because fastboot will not allow you to flash a bootloader that's not the same as the original and even if you managed to bypass this, qualcomm secure boot will block it too!
Thanks for info. Right now i am trying to edit the bootloader, and then pack it as a flashable ZIP.
Wish me luck!
There is no unbricking method for this device. A modified bootloader will brick it.
razvangabriel82 said:
Hey. I saw that on Nexus 5 someone made bootloader themes, and the new Google Logo on boot. I guess that it isn't so hard to port it. So, can someone make this?
If there are any spelling mistakes, I apologise
Click to expand...
Click to collapse
It's not worth it to modify the bootloader for something this simple. There is a very high risk of bricking the device.