Related
This didn't work so plz delete =[
sorry guys
Sexayee.
Will flash now. Also, i think it will be helpful if you link the youtube video to this thread
EDIT: Doesn't work. After flashing, a lot of android processes force close constantly. have to nandroid back. :/ dunno what's the problem
Aoi_sora9x said:
Sexayee.
Will flash now. Also, i think it will be helpful if you link the youtube video to this thread
EDIT: Doesn't work. After flashing, a lot of android processes force close constantly. have to nandroid back. :/ dunno what's the problem
Click to expand...
Click to collapse
What ROM are you using?
bootloops with me. Last CM7
I guess i flopped then =[ it works fine with mine
sorry guys =[ il close the thread
I'm using CM 7.1.1 :/ hmmm any chance that Theme Changer themes screw it up? I'm not using stock theme.
i think i might of uploaded the UNSIGNED version
im uploading the one that is on my phone, i think this is the right one
if not sorry
EDIT: uploaded on first post
Get a developer to help you. It's ****ing amazing, I can't wait to see it stable and implemented into Milestone
might have Another go at it when I get back from college
Sent from my Milestone using XDA App
If that doesn't work...I might make a step by step picture guide to how to get it on any rom
Sent from my Milestone using XDA App
First thing I am sorry if I posted this information the wrong section but this is kinda Q&A
I need help Devs or anyone with a strong knowledge in building roms. Now I'm gonna be very clear I'm more then likely 75% noob when it comes to building roms but I am learning thru trial and error. And every First time dev has a learning curve.
What this thread for I built my first custom ROM and i need some feedback in regards to what the heck im doing wrong.I started using the android kitchen is xda INSTALL Cygwin was fine and all first time preps and tools I believe is all set.
v1
Now so far I have built a rom 3 different versions V1 install was fine all packages came up on got some FCs and freezing and root wouldnt allow access even though SU was present. but the phone was completely functional aside of that.
V2
This time I went in and made mods the android kitchen completely normal su, busy box, all the same however this time I made changes However i did make some BP mods(build prop) and almost every ROM in xda has such as speed tweaks response etc. This time I added a custom boot animation and audio.I also Added a few apks to data/app. This time after flash was done in got the custom boot logo and custom boot audio however I was stuck for 30 min at custom boot. So reset re flash cache fact reset system data cache format with dalvik still nogo.(in other words still a Nogo)
v3
Now this scenario android Kitchen had everything installed except for wipe ROm, Now this time i added the same apks a new custom boot animation/audio But this time i cut down on a few of the build Prop tweaks. and made a few change on the sounds folder and notification/alarms etc. Now i went back into cwm flash as normal- format system,data,cache wipe Fact Reset cache and dalvik again. install was completely fine. went in t reboot device I got the Boot animation/Sound took about 5 minutes then i got the soft keys now me thinking it was gonna go to the main screen it didnt it stayed at the boot animation for another 30min did a Battery reset. soon after comes a flicker onthe screen and then a paper weight phone... it wont boot light up i get nothin. now when i plug it in to get something thru PC I only get "qhsusb_dload" which i know means DEAD/ASTA LA BEASTA/Corpse. i know it requires Jtag to fix im cool with that.
what im trying to accomplish here is some good feedback to anyone who willing to help me learn from my mistakes or can atleast point me in a good directionand places to read etc.
I have channel logs of what mods i made to BP and i have actuall builds of this rom i tried to make. if there is anyone at willing to attempt to atleast have a look at the rom build NOT FLASH cuz i would hate for you to break your phone but atleast Look at what i change and see if there is something i shouldnt of done i would really appreciate it.
If you would like to look at the build and give me some constructive feedback please PM so far i have exhausted all my sources i would really like some feedback.
I WARN YOU DO NOT FLASH THESE ROM FILES DONT BREAK YOUR PHONE I WILL NOT BE HELD RESPONSIBLE IF YOU DO THIS
You guys can flame me all you want i just want to do more then just use your files i want to contribute
Thank you for all those who want to help
First this isn't bad
Second tell us what you did as far as to the Rom use details I don't wanna dig through your zip until I know what you have tried
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Also, I don't think the kitchen is compatible with ICS/JB. Works great with the gingerbread. I'm not sure what you did, usually hard bricks on this device are kernel related. Oh and ditch the kitchen k:thumbup:
Sent from my SGH-I727 using Tapatalk 2
Illnevertell said:
First this isn't bad
Second tell us what you did as far as to the Rom use details I don't wanna dig through your zip until I know what you have tried
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I have chanel logs already generate but im not home to upload them one thing i dont want to do is have a 100% noob flash these files and brick there device. if you want tonight i can sent you the zip and a detailed channel log of what was done
crashpsycho said:
I have chanel logs already generate but im not home to upload them one thing i dont want to do is have a 100% noob flash these files and brick there device. if you want tonight i can sent you the zip and a detailed channel log of what was done
Click to expand...
Click to collapse
Send it to me too plz:beer:
Sent from my SGH-I727 using Tapatalk 2
cdshepherd said:
Send it to me too plz:beer:
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thank you both i will send you the data tonight and just give me feedback when u have chance its not a super priority since Beta galaxy is in Brick City but i have another beta coming soon lol
crashpsycho said:
Thank you both i will send you the data tonight and just give me feedback when u have chance its not a super priority since Beta galaxy is in Brick City but i have another beta coming soon lol
Click to expand...
Click to collapse
As long as your the first to flash it....
Sent from my SGH-I727 using Tapatalk 2
cdshepherd said:
As long as your the first to flash it....
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Illnevertell said:
First this isn't bad
Second tell us what you did as far as to the Rom use details I don't wanna dig through your zip until I know what you have tried
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
shep if we can find wth im doing wrong ill will fix right away and flash again I just got 2 more beta galaxies and you said move away from Android kitchen to you have any good. Reference to help me move away from it. Remember 75% noob such as setting up work station etc
LOL
i just sent the info to both of you when you get a chance hit me back up thread or pM it dont matter to me
I don't have one, but should work out just fine.
Let me know if you have problems.
These ROMs are the T-Mobile Stock ROMs with a few additions:
- Deodexed for custom skins and ease of portability
- Root
- BusyBox Added
4.0.4
http://goo.im/devs/childofthehorn/espresso10tmo/ROMS
Thanks Child, hope your weekend is going well.
Sent from my ADR6400L using xda app-developers app
Getting errors when trying to flash this. Ignore the md5 mismatch, sadly my backup decided to die and now I can get to recovery but stuck there. Hope I can get the rom to flash with help.
Sent from my ADR6400L using xda app-developers app
There is no md5 sum present, so yeah.... Just a signed zip!
The assert is at the top and based off what was in the ATT variant.
If you remove that assert in the updater script, should be fine.
However, those values match what I saw in the build.prop......hmmmmm. I'll have it in the morning for yah!
Sent from my Galaxy Nexus using Tapatalk 2
Childofthehorn said:
There is no md5 sum present, so yeah.... Just a signed zip!
The assert is at the top and based off what was in the ATT variant.
If you remove that assert in the updater script, should be fine.
However, those values match what I saw in the build.prop......hmmmmm. I'll have it in the morning for yah!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I know the md5 is me trying to restore a backup and it failing. I tried to flash the from afterwards to take the picture as once I realized I wanted to show you. No worries or rush at all, I am just thankful for any help
Sent from my ADR6400L using xda app-developers app
Glad to see a start
I just ordered a tab 2 and was kind of sad nobody was working on it at all...and saw this post today and jumped for joy and thought "atleast someone is doing some sort of work on it..and this is a great start....did the t-mo version get 4.1 yet? I hope someone kangs an AOSP rom for some 4.2.1 love...(prob to high of a hope) but I'm glad to see this atleast...so atleast i'll have some wiggle room..but saw a poster was having issues..and don't want to get stuck in his shoes..so i'll wait to flash...and or do anything..seen as there is no odin restore stuff or lots of roms that are known to work and stable and the like.....
Thanks for starting the game tho!!!!
Hellation,
That updater script is 100% correct. Had a user PM me.
Your Backup must have failed and/or you flashed something you shouldn't have.
You need to remove the "assert" line in the top of the updater script (unzip /META-INF/com/google/updater-script. Your issue could be that it cannot read itself right now.
Re-zip the whole thing and try again.
You have no readable props right now, or the readable props are wrong...
Childofthehorn said:
Hellation,
That updater script is 100% correct. Had a user PM me.
Your Backup must have failed and/or you flashed something you shouldn't have.
You need to remove the "assert" line in the top of the updater script (unzip /META-INF/com/google/updater-script. Your issue could be that it cannot read itself right now.
Re-zip the whole thing and try again.
You have no readable props right now, or the readable props are wrong...
Click to expand...
Click to collapse
I ended up reverting back to bare stock through odin, will give this another shot soon as I'm home again and can fully sit down. I'm sure it works and I feel might of been my tablet, all are different. Thank for all our time and I will report back once I manage to get back and tinker with my tablet once more.
Re: No wifi
Hey Bro, sorry 2 bug again but I got the new uploaded zip file you uploaded (thanks for that) and it works but now the wifi doesnt work...ive tried wiping the device then tried flashing the rom again but still no wifi PLEASE HELP
Maybe if u have a nandroid back up u can upload that would be great or maybe a stock zip?
thanks alot
EDIT: IM SORRY I POSTED IN THE WRONG THREAD..i HAVE the AT&T tab 2 10.1...
Hellation said:
I ended up reverting back to bare stock through odin, will give this another shot soon as I'm home again and can fully sit down. I'm sure it works and I feel might of been my tablet, all are different. Thank for all our time and I will report back once I manage to get back and tinker with my tablet once more.
Click to expand...
Click to collapse
did you ever get this to work? I haven't seen any posts from Childofthehorn in a while, but i wanted to try this out.
rmancl said:
did you ever get this to work? I haven't seen any posts from Childofthehorn in a while, but i wanted to try this out.
Click to expand...
Click to collapse
Getting back to you, I sold my T-Mobile model and got a Wi-Fi only one. I was never able to get it to flash. Kept getting Status 7 each time I did.
Sent from my ADR6400L using xda app-developers app
Hellation said:
Getting back to you, I sold my T-Mobile model and got a Wi-Fi only one. I was never able to get it to flash. Kept getting Status 7 each time I did.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thanks for letting me know, i am going to work on my own rom now. I want to port over cm10
It looks like we need to come out with a new OTA base, some of the newer ROM's threads are being closed. Also, there is rumor that some devs are getting banned for posting ROMS's based on original OTA in RootzWiki. Being very new to this whole thing I can help, I attempted to make my my own but ended up rooted and S-ON (fixed now).
In any event I reverted back to stock, no root, did the OTA upgrade (what originally caused be problems since it updated HBOOT to 1.08). I was able to root it and do a backup. Now I am back to S-OFF and rooted, so I want to see what we can do with the backup, as far as I know the boot.img is the missing link. The one that came with OTA ICS installs 1.08 HBOOT (f5e16f3f55ddfb0ec10c8f9a75b35bed boot.img) which is not good.
I think we should create a completely open source version of the OTA and allow anyone and anybody to customize it as they see fit. Let's face it the TBolt lifecycle is at it's end so those of us that are left should work together.
Danm that sucks, I was wondering what was going on.
I love your idea, if I knew anything about this stuff I would help. When I saw the threads were locked for that reason it annoyed the hell out of me. What happened to Android being open source like its supposed to be.
Sent from my ADR6400L using xda premium
Nevermind I see whats going on here. I read Santod040 post in the other thread and he makes some valid points. I wish I could help tho.
I agree with Santod040 as well that is why I am doing this. I will probably not be able to do this all on my own, mostly because I have been basically an ROM end user. By the time I learn all I need to build my own ROM I will hopefully be on another device.
You have to do a system dump using adb. I'm not 100% certain but it may have to be done before it is altered. In other words 100% stock ota.
Sent from my ADR6400L using Tapatalk 2
Good idea!
I also wish I knew more. My simple successes have so far been related to theming of icon color in Browser.apk including some simple string edits, and custom colored or fully transparent LATIN_IME.apks.
I already have Ubuntu on a dual boot PC and Eclipse, and also have an updated SDK, but some 'clif notes' to get me started would be helpful. I've browsed around before and read many threads all over.
I like the idea of us all joining up to see what we can do!
The command for that should be listed with the other adb commands when you type adb in a terminal. You will need tools for splitting the boot.img as well since to make the ota a flashable you will have to package the boot.img in a zip.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The command for that should be listed with the other adb commands when you type adb in a terminal. You will need tools for splitting the boot.img as well since to make the ota a flashable you will have to package the boot.img in a zip.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Isn't HBOOT packaged with the boot.img? For the backup that I did I have all that. What is the difference between doing a backup and doing a system dump with adb?
I finally found OTAUpdate.zip, I am going to dissect that and see what I can come up with. I was just about to downgrade and redownload the otaupdate.zip, saved me some time.
The nand is different because it isn't flashable the same way that a rom is. Theoretically you could upload the nand and people could use that to get the base but it just isn't the typical practice. It is better to have a flashable zip. The otaupdate.zip is not like a normal file especially since the update is a whole lot of patches that have to be applied to the stock gb base. That is why it took santod almost a day to assemble it into a flashable zip.
Sent from my ADR6400L using Tapatalk 2
Yeah it's sad it comes to this though. The community is who loses out in the end. As long as someone isnt profiting off your work I dont see what the problem is with them kanging it. Dev's are all supposed to have the same goal here, enrich the community with roms. They only do it because they are generous and enjoy helping out, especially a dying community such as the Thunderbolt. We need as much dev support as we can get, no matter where it comes from. If your goal is to help the community then you should be happy that they are enjoying your work, it's not like we dont know where the stuff comes from anyway.
Look guys just use the Unlock your bootloader on ICS Method, Get root, Install the recovery, backup the rom. Copy the backup from /clockwork to computer. Zip it and send to me. All we need is the System partition. The rest we will find
disconnecktie said:
The nand is different because it isn't flashable the same way that a rom is. Theoretically you could upload the nand and people could use that to get the base but it just isn't the typical practice. It is better to have a flashable zip. The otaupdate.zip is not like a normal file especially since the update is a whole lot of patches that have to be applied to the stock gb base. That is why it took santod almost a day to assemble it into a flashable zip.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I see FOTA in OTAUpdate, I am assuming that is where HBOOT is being updated. That is what I was planning on doing, getting last GB RUU and manually running the scripts to come up with OTA. But the boot.img is what I don't understand, it seems the various boot.img is various ROM's are different (having different MD5's), are these built?
Guys can we please cut out the name calling and puerile acrimony?
I know that development can be a passion, but we need to work out our differences peacefully and sublimate our passion into development and this verbal venom.
As of right now let's cut out the nonsense, I am going to clean the thread up a bit and attempt to get some specifics, then we can discuss the issues without resorting to flaming.
ViperZ28 said:
I see FOTA in OTAUpdate, I am assuming that is where HBOOT is being updated. That is what I was planning on doing, getting last GB RUU and manually running the scripts to come up with OTA. But the boot.img is what I don't understand, it seems the various boot.img is various ROM's are different (having different MD5's), are these built?
Click to expand...
Click to collapse
Again I'm not 100% certain but i am sure that the new hboot is needed to assemble the ota because the patches in the ota are encrypted and the hboot decrypts those patches and assembles them.
Sent from my ADR6400L using Tapatalk 2
orangekid said:
Guys can we please cut out the name calling and puerile acrimony?
I know that development can be a passion, but we need to work out our differences peacefully and sublimate our passion into development and this verbal venom.
As of right now let's cut out the nonsense, I am going to clean the thread up a bit and attempt to get some specifics, then we can discuss the issues without resorting to flaming.
Click to expand...
Click to collapse
You see who started it. If he wants to troll n call people out he should expect a reply. As long as I've been here and been in this community I've never had to give reports to mods over a user. He should learn to control his mouth and he wouldn't get a Ill mannered response. He thinks he's all perfect then after all the fight gladly advertises and sends you to infected ROM forums and continues to get away with it. He's lost the respect of many over this one.
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
And good job deleting my post but leaving his up. Tbolt community on xda i'm sorry. But you just flat lined. Enjoy
Sent from my DROID BIONIC using Tapatalk 2
[SP]JESTER said:
You see who started it. If he wants to troll n call people out he should expect a reply. As long as I've been here and been in this community I've never had to give reports to mods over a user. He should learn to control his mouth and he wouldn't get a Ill mannered response. He thinks he's all perfect then after all the fight gladly advertises and sends you to infected ROM forums and continues to get away with it. He's lost the respect of many over this one.
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
And good job deleting my post but leaving his up. Tbolt community on xda i'm sorry. But you just flat lined. Enjoy
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
I am going to leave this post here to make a point.
The fact is that you too should learn to control your own "mouth" (or keyboard as it were).
This isn't about who is right or wrong, I honestly don't even know what is going on at this point as I am still trying to figure exactly what the problem is, but this is not the place to go off like an atomic warhead about whatever is going on here. If you allow someone to bait you into these types of remarks, then you are giving that person control over your emotions and your reactions and you then take on the role of villain.
Whatever is going on you can PM a mod or get it sorted out through proper channels, some of our mods and Admin are developers and know the stuff inside out, they can sort out who is actually the instigator here.
End of discussion on this please. PM me if you still have issue. I will figure out what is happening and act on it.
Be civil, I refuse to believe that that is beyond your or anyone else's ability.
RunNgun42 said:
Yeah it's sad it comes to this though. The community is who loses out in the end. As long as someone isnt profiting off your work I dont see what the problem is with them kanging it. Dev's are all supposed to have the same goal here, enrich the community with roms. They only do it because they are generous and enjoy helping out, especially a dying community such as the Thunderbolt. We need as much dev support as we can get, no matter where it comes from. If your goal is to help the community then you should be happy that they are enjoying your work, it's not like we dont know where the stuff comes from anyway.
Click to expand...
Click to collapse
It could be looked at as a dev is getting donations off another devs hard work. So basically he or she is profiting off another's work. It's always best to ask another if they can use their work. I know liquid went through this with cm team. If a dev doesn't ask and just uses another's work. They should expect to get a nastygram from the dev who did the work. Free or paid stealing work is still stealing.
Sent from my ADR6425LVW using Tapatalk 2
Aghhh, can we get back on topic....we need to create a new OTA base.
I just received the OTA notification. Let's install and see how it works.
ctenus said:
I just received the OTA notification. Let's install and see how it works.
Click to expand...
Click to collapse
Could you update the .zip please?
???
share the zip before update....
gerardolan64 said:
share the zip before update....
Click to expand...
Click to collapse
Yes, please pull the OTA zip and upload it somewhere before actually updating. It should be in /cache/
Vultures out here. Is everyone that effing impatient? Lol. Basic rule of xda, no asking of ETA's, we known it's coming. Patience is your friend.
Sent from my SM-P600 using XDA Premium HD app
siralsmooth said:
Vultures out here. Is everyone that effing impatient? Lol. Basic rule of xda, no asking of ETA's, we known it's coming. Patience is your friend.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
When it comes to Devs making ROMs.
And you're probably on a US non Brazil firmware too? And this update is useful to whom? Brazil. And can't be flashed to any other devices other than its intended to. By the time a dev could disect an ota and make it work, we'll probably have the official update. Dev or not, no single person who gets the OTA is obligated to share. People need to be patient. If a dev can work the magic and make something work from a FULL SYSTEM DUMP, awesome. But people harpooning on an update like its a cure for cancer just makes me laugh and shake my head.
Sent from my XT1575 using XDA Premium HD app
Hi, guys, I have a Brazilian XT1572 (dual sim) and I am downloading the OTA file. Now, where I can find it in my phone? I searched in /cache but I didn't find anything, could you help me?
siralsmooth said:
And you're probably on a US non Brazil firmware too? And this update is useful to whom? Brazil. And can't be flashed to any other devices other than its intended to. By the time a dev could disect an ota and make it work, we'll probably have the official update. Dev or not, no single person who gets the OTA is obligated to share. People need to be patient. If a dev can work the magic and make something work from a FULL SYSTEM DUMP, awesome. But people harpooning on an update like its a cure for cancer just makes me laugh and shake my head.
Sent from my XT1575 using XDA Premium HD app
Click to expand...
Click to collapse
Although fairly tricky, there are people with the 1575 who've gotten the Indian 6.0 update working on their phones...just an FYI. I'd assume it's the same here.
Yep.. Don't FTT guys
I´m looking for the OTA too.
I tried to save the .zip from \cache at no avail. It updated itself in a blink.
Looking for it myself.
I liked it very much, but, just for sake of security I wa aiming to save it before upgrade, now I wait for somebody skiller...
I´d love to get it via Mega and/or Google Drive.
The update I did took me a few hours at my office (quite low speed there) and a few dozen miniutes more at home.
By the way, it runs smooth, it worthed my blink distraction, other than the OTA I failed to save.
Never mind. got it myself:
https://drive.google.com/file/d/0Bw5KjSVoc4QNcjhvNVdvbXBPQkU/view
That´s it!
Thank u man, flashed and working!
jglerner said:
I´m looking for the OTA too.
I tried to save the .zip from \cache at no avail. It updated itself in a blink.
Looking for it myself.
I liked it very much, but, just for sake of security I wa aiming to save it before upgrade, now I wait for somebody skiller...
I´d love to get it via Mega and/or Google Drive.
The update I did took me a few hours at my office (quite low speed there) and a few dozen miniutes more at home.
By the way, it runs smooth, it worthed my blink distraction, other than the OTA I failed to save.
Never mind. got it myself:
That´s it!
Click to expand...
Click to collapse
jglerner said:
I´m looking for the OTA too.
I tried to save the .zip from \cache at no avail. It updated itself in a blink.
Looking for it myself.
I liked it very much, but, just for sake of security I wa aiming to save it before upgrade, now I wait for somebody skiller...
I´d love to get it via Mega and/or Google Drive.
The update I did took me a few hours at my office (quite low speed there) and a few dozen miniutes more at home.
By the way, it runs smooth, it worthed my blink distraction, other than the OTA I failed to save.
Never mind. got it myself:
https://drive.google.com/file/d/0Bw5KjSVoc4QNcjhvNVdvbXBPQkU/view
That´s it!
Click to expand...
Click to collapse
Want mega? here you go and also mediafire mirror for those who want you supply I help still waiting for Pure Edition OTA.. can't wait lol.
http://www.mediafire.com/download/6...rsion.24.11.18.clark_retla_ds.retla.en.01.zip
https://mega.nz/#!bYJE2AzB
Unlock Key: !WP-i2aCf7onmUOCq4KCKskjIEAZ7xokzLiIRk-qrN18 [for mega]