Related
I know some hard work goes into making some of these splash screens, but I'd actually prefer to see kernel messages. Just like what I'd see if I were booting Linux up on a PC. If I delete the splash image files, will this break my phone? Or will it just fall back to giving me the kernel print outs?
If there is a recommended sequence of steps required to do this, it really wouldn't hurt to spell them out for me. Thanks!
I would pm a developer.
Im not sure if it can set up like that.
It would look cool though. Keep us posted.
jokeyrhyme said:
I know some hard work goes into making some of these splash screens, but I'd actually prefer to see kernel messages. Just like what I'd see if I were booting Linux up on a PC. If I delete the splash image files, will this break my phone? Or will it just fall back to giving me the kernel print outs?
If there is a recommended sequence of steps required to do this, it really wouldn't hurt to spell them out for me. Thanks!
Click to expand...
Click to collapse
i have tried by editing the init files, but I didnt make it.
someone?
I posted this over in one of the FAQ threads here. There a few encouraging replies, especially regarding the current line of investigation.
The bad news is that Cyanogen himself has declared this difficult so I don't know how much further we'll get.
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
This is how I un-hard bricked a T-Mobile Note 3 SM-N900T
Part 1: What you need
A SD Card that is the Same Size as your Phone's internal memory. Mine was 32GB and I used it.
The unbrick image which can be found here: mega.co.nz/#!wxZh3CwR!UU1OBBAHACKHEO0eMK4crHBjKXUKJ7y8-vqjkQGzsMY
A program to put the image on a SD Card which is here for windows users: sourceforge.net/projects/win32diskimager
The Stock ROM. I got mine here. samsung-updates.com/device/?id=SM-N900T
ODIN 3.04 (this is what I used): mega.co.nz/#!xw4FHBzD!Zw9EMltI0g5AZYspg8aM6hFSXJFiiwCRORMqxoandW8
Part 2: Prep
Get the battery charged to 100%.
Find a PC and plug the powercord (microUSB Cord) directly into the motherboard. NOT ANY OTHER PORT.
Format the SD Card to ExFAT you need from Part 1.1.
Using the #3 Program from Part 1.3, burn the image to the SD Card. Its simple.
Part 3: Turn it on
Put the battery into the phone.
Plug the charging cord into the phone.
Put the phone into download mode by holding: <Volume Down> + <Home Button> + <Power>
Once you are in download mode press <Volume Up> to enter download mode. Now go to part 4
Part 4: Putting the ROM back on
Don't Deviate from anything here or do extras.
Open Odin from Part 1.5.
Press PDA and Select your STOCK ROM from Part 1.4
Wait a min for Odin to analyze the file.
Hit Start on Odin.
Part 5: How about someone get a MOD to fix the links in Part 1
How about someone get a MOD to fix the links in Part 1 as I was unable to link Properly. I am not going to do it because it pissed me off. :silly:
Notes:
Turn it on was just basic as can be, It just popped right on. Per the USB Ports I did use a USB-3 Ports on the back of my machine. I am not sure if that would make a difference or not.
Credits:
Credits are due, but I need to research who to credit again... It is Christmas Eve, and I am going drinking. I will do this on Monday when I get back to work.
So are these the instructions on the other thread I'd say is the original M
Sent from my SM-N900T using xda app-developers app
Thanks! Whats with the grey letterboxing? Thats probably killing your link. Glad the info on the thread helped you unbrick your device! Because when you pmed me asking me how to do it, I had no idea you already knew Until and if it is fixed, copy/paste works fine.
msmercy42 said:
Thanks! Whats with the grey letterboxing? Thats probably killing your link. Glad the info on the thread helped you unbrick your device! Because when you pmed me asking me how to do it, I had no idea you already knew Until and if it is fixed, copy/paste works fine.
Click to expand...
Click to collapse
system did it automatically. I have no clue why. I do like how it boxed out the parts.
and it is the why you do it from the other thread... I was asked to put links to what I used and how I did it. Nothing pisses me off more than having to dig through a thread looking for the solution. I just put it on top of a new thread. This way people don't have to dig. It does make sense if you think about it.
Imagine how much digging I had to do about two months ago when it seemed like I was the only person in this forum asking about it. Reading the pages in the thread I created answers alot of questions, and has detailed information that could prevent future mistakes that could result in such. Also at the same time actually learning something about the way file system repair and recovery on android can work.
It's all in the way you look at it. I'd open a bag of chips, crack open a beer, and read the whole thing - especially if I could learn new things - no matter how experienced I am.
chuko303 said:
So are these the instructions on the other thread I'd say is the original M
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
These are the steps zinnium took in order to get his to work, but the other thread is the original.
The other thread was pieced together from over a month of research and trial/error. We tried several methods, dug up some secret Samsung documents (credit given to those provided), and then came up with the OP solution by finally piecing some things from the sgs3, sm-n900a, and help from some experienced devs.
The important thing is though, that the method works.
Anyway, @OP, the image I have on media fire seems to download better. Take that link from the other thread and post here. MEGA sucks donkey balls IMO. There servers are slow, and always makes you wait forever.
ive never heard of anyone needing to connect the device before it would sdboot, so the following steps arent needed:
Find a PC and plug the powercord (microUSB Cord) directly into the motherboard. NOT ANY OTHER PORT.
Format the SD Card to ExFAT you need from Part 1.1.
Click to expand...
Click to collapse
HOLY S#!T, That's LEGIT!
A-effin'-MAZING!! I CAN'T THANK YOU ALL ENOUGH!
I CAN'T BELIEVE THAT WORKED!
I couldn't resist recording my first attempt. BOY I WAS SURPRISED!!
*For The Record; Shabby is correct, you don't have to be plugged into any external power source, for this to work...
**ALSO!; The Stock ROM may not always be needed, depending on the individual and their case's circumstances...
I've had ppl tell me that no matter what, they try turning on their phone(SGN2/SGN3/SGS4) and it automatically goes into download mode(without showing the warning screen)... So since it wouldn't boot system OR Recovery, I'd try Button-Combo into ODIN-mode, and press Volume-down at the warning screen, and system would boot!
I Had a hunch that might work in this case, and it DID! lol.
Now I'm just trying to put the unbrick.img onto the sdcard I wrote it to... I can't seem to get MTP up, through USB, though ADB works fine...
**EDIT: I forgot, that before I Bricked it, I had the USB settings to DM+MODEM+ADB, cause I WAS unlocking it...
(until a slip of a click and I wrote a backup of the NVdata to the EFS... =/ )
But, after I put the sdcard into my laptop, realized there's not nearly enough room to copy the .img to it...
***SO.... How am I supposed to be able to "dd if=/sdcard/unbrick.img of=/dev/mmcblk0 bs=1024 count=168960"?
I can't put the .img on the sd? Do I put it on the internal? or do I put it on another sdcard and put it in??
**** ACTUALLY, NVM.... THAT'S what I'm gonna do! XD ha
*****
[email protected]:/ # dd if=/storage/extSdCard/unbrick.img of=/dev/mmcblk0 bs=1024
count=168960
ck.img of=/dev/mmcblk0 bs=1024 count=168960 <
168960+0 records in
168960+0 records out
173015040 bytes transferred in 9.488 secs (18235143 bytes/sec)
[email protected]:/ #
=AWESOME!
M1k3Carson1369 said:
A-effin'-MAZING!! I CAN'T THANK YOU ALL ENOUGH!
I CAN'T BELIEVE THAT WORKED!
I couldn't resist recording my first attempt. BOY I WAS SURPRISED!!
*For The Record; Shabby is correct, you don't have to be plugged into any external power source, for this to work...
**ALSO!; The Stock ROM may not always be needed, depending on the individual and their case's circumstances...
I've had ppl tell me that no matter what, they try turning on their phone(SGN2/SGN3/SGS4) and it automatically goes into download mode(without showing the warning screen)... So since it wouldn't boot system OR Recovery, I'd try Button-Combo into ODIN-mode, and press Volume-down at the warning screen, and system would boot!
I Had a hunch that might work in this case, and it DID! lol.
Now I'm just trying to put the unbrick.img onto the sdcard I wrote it to... I can't seem to get MTP up, through USB, though ADB works fine...
**EDIT: I forgot, that before I Bricked it, I had the USB settings to DM+MODEM+ADB, cause I WAS unlocking it...
(until a slip of a click and I wrote a backup of the NVdata to the EFS... =/ )
But, after I put the sdcard into my laptop, realized there's not nearly enough room to copy the .img to it...
***SO.... How am I supposed to be able to "dd if=/sdcard/unbrick.img of=/dev/mmcblk0 bs=1024 count=168960"?
I can't put the .img on the sd? Do I put it on the internal? or do I put it on another sdcard and put it in??
**** ACTUALLY, NVM.... THAT'S what I'm gonna do! XD ha
*****
[email protected]:/ # dd if=/storage/extSdCard/unbrick.img of=/dev/mmcblk0 bs=1024
count=168960
ck.img of=/dev/mmcblk0 bs=1024 count=168960 <
168960+0 records in
168960+0 records out
173015040 bytes transferred in 9.488 secs (18235143 bytes/sec)
[email protected]:/ #
=AWESOME!
Click to expand...
Click to collapse
Dangit! STILL can't get it to boot back up without the sdcard in it...? =/
Did you flash the stock firmware in odin...?
Also are you SURE that you have a HARD brick? It sounds like you've got a soft brick which has nothing to do with the method we are using here.
Sent from my SPH-L900 using xda app-developers app
M1k3Carson1369 said:
Dangit! STILL can't get it to boot back up without the sdcard in it...? =/
Click to expand...
Click to collapse
you need to have teh sdcard in there, boot to download mode and flash a full odin tar that includes the bootloaders.
once that's all said and done youll be good
shabbypenguin said:
you need to have teh sdcard in there, boot to download mode and flash a full odin tar that includes the bootloaders.
once that's all said and done youll be good
Click to expand...
Click to collapse
Dang! Samsung-Updates is giving me a hard time trying to download from the links (tera-something 7 something-gator)...
Alright, if that's the only choice... =/ ha
ecs87 said:
Did you flash the stock firmware in odin...?
Also are you SURE that you have a HARD brick? It sounds like you've got a soft brick which has nothing to do with the method we are using here.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Yes, I'm quite sure. Read back through the original thread, you'll see my description of it.
**Oh, you know what? While I wait for a successful download of complete stock rom, I'm gonna plug back into the box, and see if maybe rewriting the original backup of the EFS will fix it... (It was originally a mis-click that bricked it to begin with.. Accidentally wrote a backup of the NVdata to the EFS 0_o)
Worst case scenario; I end up still waiting for the download anyway! (if I can ever get it to start dl'ing)
M1k3Carson1369 said:
Worst case scenario; I end up still waiting for the download anyway! (if I can ever get it to start dl'ing)
Click to expand...
Click to collapse
Do you have the SM-N900T? I can pm you my Dropbox link to download the stock firmware.
Sent from my SM-N900T using Tapatalk 2
lm that guy said:
Do you have the SM-N900T? I can pm you my Dropbox link to download the stock firmware.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
That would be AMAZING! I'd really apreciate it. Thanks!
Hahaha! Success!!!! >=p
WOW!!!
I gotta say, when the only Sign of life I got were "QHUSB_BULK" and Google only found FIVE hits relevant, which were all questions about it as well!?! I was pretty distraught. Thought for sure I'd end up having to send for JTAG, or worse, a replacement... 0_o
But Now, Beyond my most wishful thinking, an unbrick method so simply straightforward and effective.... I'm still trying to pull my Jaw back up...
Thank you all; msmercy42, noobtoob, ecs87, aiti1980, shabbypenguin, lm that guy, & especially zinnium (for testing/confirming)!..! And any contributors whom I failed to mention!
Thanks for all your experience and efforts! That right there is why these forums exist...
Hey I appreciate the thanks, you're welcome!! Just glad to help! This is exactly what I started the thread for! Couldn't have done it without the big time developer support, and from Senior members you listed above - we made a great team!! Merry Christmas!
msmercy42 said:
Hey I appreciate the thanks, you're welcome!! Just glad to help! This is exactly what I started the thread for! Couldn't have done it without the big time developer support, and from Senior members you listed above - we made a great team!! Merry Christmas!
Click to expand...
Click to collapse
@msmercy42, i really did think you had completed it back on the original thread. It was so goofy when it kicked on right before I read you email that you never got it to work. I was like, what?????
That download sucks right now from Samsung updates. With Hotfiles gone, we are all going to have to get use to slow ass downloads. Mine took like 10 hours and I even paid for one of the services.... TOTALLY NOT WORTH IT.
I still don't get how you thought that as I never once posted that I managed to unbrick mine. In fact mine technically is still bricked as I do not have the proper size sd card at the moment.
I never even implied it
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
Also a proper dd command in terminal will write the image to the phone, therefore negating the necessity of Odin. However that is entirely by choice. In my opinion, unless you are very comfortable using powerful Linux commands that could damage your phone, thus rendering it unusable - then Odin is a better choice as it is a powerful software flashing tool that can allow you to control multiple functions in a single operation.
I'll throw a N900T Odin tarball I have stashed away onto my mediafire account. It should deliver decent speeds and it won't get shut down for excessive traffic (COUGHDROPBOXCOUGH). Just gotta drag my ass into work today to do it.
Sent from my SPH-L900 using xda app-developers app
ecs87 said:
I'll throw a N900T Odin tarball I have stashed away onto my mediafire account. It should deliver decent speeds and it won't get shut down for excessive traffic (COUGHDROPBOXCOUGH). Just gotta drag my ass into work today to do it.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
HA! I posted the recovery thread via Heimdall here a while back, right before we met through this thread. Within 10 minutes, I hit my "threshold" with drop box. Moved to mediafire and haven't looked back.
Sent from my SM-N900T using Tapatalk
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Oh no...
mingolianbeef said:
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
hallosup said:
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
Click to expand...
Click to collapse
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share ?
Sent from my draconis using Tapatalk
mingolianbeef said:
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Still_living714 said:
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Click to expand...
Click to collapse
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
well I guess it's a lesson learned lol. I get what you're saying but by doing so you still dont know how the phone might react.
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
Well, i am in the same or almost the same pot as you. I flashed Fulmics ROM which was supposed to give me MM. But after downloading the almost 2GB rom, i noticed that my device wasnt part of the supported devices in Aroma Installer. But i went ahead and flashed the D855 version thinking that it might work with my D851 and incase it didnt work, the worst that could happen would be the device getting stuck on the LG Splash Logo. And when that happened, all i would have to do would be to boot into recovery and restore my backup. Little did i know that the ROM dev had added tz.img,rpm.img,boot.img and modem.img to the ROM. And what this means is that, the ROM wasnt just replacing my stock KK with Fulmics, but it was also overwriting and patching my D851 tz.img,rpm.img,boot.img and modem.img with that of the D855. The ROM flashed smoothely without an error and when it finnished, i hit the reboot button. Waiting for the device to bootup up into MM, but sadly, the the device never booted again. All i get now is Battery notifications.
For example, if i connect a USB to the phone without battery inserted, i get an empty battery with a yellow triangle with an exclamation mark in the middle of the yellow triangle. And when i exhaust the battery, and i press the power button, i get presented with an empty battery notification on the screen. Thats all i ever get.
I have tried shorting the pins... which gets me into QDownloader 9008 mode but Board Diag tool doesnt seem to work on the D851. My reasons for saying this is because i helped someone who had a D855 with the Board Diag process and it was able to flash all the files. The only pain was that, after every flash with board diag, we had to disconnect the device and re-short the pins and flash the files till we flashed all the files.
But for some unkown reason, this tool wont work on our device (D851). Apparently, the D851 motherboard is different from the D855. As i compared mine with the D855.
I just hope someone makes a tool to unbrick our D851.
ATTN: I NEED EVERYONE'S HELP!!! PLEASE!!!Here's what I need you to do!Find and Search through your PC's and look for any complete or decently stable ROM's, RECOVERY's, KERNEL's and any possible missing links / files / documents for the LG Optimus V regardless of it's version or kernel and Send me WORKING links, files, of anything you got. All the links for this phone are dead... I've checked all over the web. This is still a great phone, and can still be used either with Boost Mobile or simply with a Credit or Debit card. A friend and I plan on revamping this phone to see if we can't bring it back to it's glory. But in order to do so.... Got to have the Archives! Every link is dead.... PLEASE PLEASE PLEASE search around for anything LG Optimus V, VM670, Thunderc Optimus S is also appreciated.
THANK YOU FOR YOUR TIME AND PATIENCE
Send them to me, in a PM and or share them with me to my Google Drive via email.... PM for email... thanks
You may post links here only as long as the owner hasn't pulled the files for TOS Violations.
To be honest.... if your unsure, just PM the links.
I'm taking any and all files that are DEAD links
anything I can redownload as of today's date, will be unwanted.
But don't let that discourage you from SHARING THEM AWESOME FILES AND RE-UPLOADED LINKS!
THANK YOU THANK YOU THANK YOU!!!
:good::laugh:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Here's some Optimus S stuff I used to use,was able to download from here today, https://archive.midnightchannel.net/zefie/files/cell/LGLS670/
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
timjames474 said:
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
Click to expand...
Click to collapse
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files
Click to expand...
Click to collapse
you have to crack open the boot.img and replace just the kernel with a working one. it's "fun."
and finding a working kernel for the newer screens now as a standalone download is really iffy. (actually, see next post. I found /one./)
if you have another jb rom with working screen you can split that boot.img and yoink its kernel for the one that doesn't have more than a backlight. you can also plop that picasticks kernel from below into any blackscreen recovery images too, they split and recombine just like a boot image.
a lot of people call the boot.img a kernel, but it's actually a combination of kernel and ramdisk.
you can use osm0sis AIK tools to disassemble and reassemble boot.img relatively painlessly.
I'm happy to promote osm0sis's work. he does great things. drop him a donation if you're so inclined, he certainly deserves it.
by the way, don't try to insert the 3.0 kitkat kernel into anything else... it probably won't boot. jb is the best bet to try it on though, thekraven nudged me into porting that kernel from the p500 for his jb roms. I'm glad he did, because the experience has been very useful on other devices.
ok, here's my gift to y'all.
https://www.androidfilehost.com/?w=files&flid=317344
archive of the primary goodies from my old failing NTFS external drive. We'll see how long it takes for androidfilehost to arbitrarily delete them like they did every other file I ever uploaded there for the optimus S/V with no warning or acknowledgment. they never even answered multiple support requests trying to find out why... I'm guessing they decided to clean their servers of things uploaded before a certain date, but no telling since they wouldn't answer.
in the kernels subfolder is a picasticks kernel i built for the old/new screens.
multiple recoveries. some are old and may blackscreen on newer devices, fair warning. some roms will be the same way. the twrp's may or may not have reversed system/userdata like my os2sd twrp, try and see. they should at least be good on any model optimus s/v screen.
several roms, including one harmonia, and PAC-rom from thekraven.
others folder has V drivers... and swype flashable zip, ripped probably from GB stock, maybe from froyo stock.
also multirom recoveries and installer if you like multiboot. thread here
have fun.
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
Click to expand...
Click to collapse
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
timjames474 said:
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
Click to expand...
Click to collapse
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
bigsupersquid said:
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
Click to expand...
Click to collapse
if you manage to find it,do let me know! TIA
timjames474 said:
if you manage to find it,do let me know! TIA
Click to expand...
Click to collapse
I can pull the one from the rom on my V and switch the keys.
no flashable zip, you'll have to use adb to install it, I'll post the commands
it's home and menu that are swapped if I remember right, is that correct?
it's actually a .kcm file, I've messed with so many devices I mix things up sometimes.
Sorry for being gone so long,yes those are the keys,my Optimus S had been dropped one time too many but i finally replaced it and am still interested in getting those files and commands
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
bigsupersquid said:
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
Click to expand...
Click to collapse
Seems that it always goes to /system/usr and the two folders are keylayout and key(something else idr) the one that i cannot remember the name for is where the .kcm files are at
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
bigsupersquid said:
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
Click to expand...
Click to collapse
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
timjames474 said:
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
Click to expand...
Click to collapse
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
bigsupersquid said:
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
Click to expand...
Click to collapse
MicroG has a broken login,the login box is all the way off screen for me,but ive since gotten a modern phone at the gentle prodding at Tello anyway